Re: FreeBSD Install, posted by Dave Truesdell on Sun Oct 26 18:32:17 2003
|
> I got elog 2.3.9 running on FreeBSD 5.1 successfully,
> I compiled elog on a redhat box and then just copied over all the files to
> the FreeBSD box and ELOG just ran with no issues.
|
write access for elogd, posted by Dave Becker on Thu Aug 19 06:21:38 2004
|
Newly installed elog gives this response when I try to submit a new record:
New entry cannot be written to directory "./logbooks/Linux/"
|
elogd -m , posted by Dave on Thu Mar 10 00:16:33 2016
|
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG. |
|
elogd -m Error sending local entry: Error transmitting message, posted by Dave on Thu Mar 10 00:26:03 2016
|
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG. |
Is it possible to only send an email based on the value of multiple attributes?, posted by Darren Hollinrake on Mon Mar 9 17:03:38 2015
|
My current setup notifies users if downtime = yes.
[CODE]Email Downtime Yes = user1@xyz.com, user2@xyz.com[/CODE]
|
|
Re: Installation: Failed Dependencies, posted by Darren Hollinrake on Sat Mar 19 15:24:29 2016
|
I did the following on CentOS 6.7 (Should work for Fedora and RHEL as well):
yum install -y wget
wget http://midas.psi.ch/elog/download/RPMS/elog-latest.i386.rpm |
|
elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Fri Aug 19 19:39:50 2016
|
I was setting of a local test copy of my logbooks on my Windows 7 PC to begin testing automation of submissions without spamming the live logbooks. While
trying to make entries from the command line I get an error that I am missing a required attribute. I have multiple attributes that have spaces in them
an the verbose output indicates that the space in the name is being changed to an underscore. Is this the expected behavior or a bug when submitting to |
|
Re: elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Thu Aug 25 18:18:57 2016
|
Thanks for the reply. You're correct that the "Start Time" attribute is a datetime field. I tried your suggestion and placed "0" for that field but it still
returns the same error: Error: Missing required attribute "Start Time"
I tested after commenting out the required attribute line and the command was accepted. However, the datetime field does not display a valid date/time |