Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 676 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  446   Sun Oct 26 18:32:17 2003 Reply Dave Truesdelldavet@ttfn.comCommentOtherelog2.3.9Re: FreeBSD Install
> 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.
> It's been running under heavy use for at least a month now.

FYI- the default "make" on FreeBSD is BSD, not GNU.

The easiest way to build elog on FreeBSD is to install "gmake" (via the port or
package) and type "gmake".  That's all it took for me to build a freshly
downloaded copy on 5.1 not 5 minutes ago.
  674   Thu Aug 19 06:21:38 2004 Question Dave Beckerdbecker@lanl.govQuestionLinux2.5.4write access for elogd
Newly installed elog gives this response when I try to submit a new record:

New entry cannot be written to directory "./logbooks/Linux/" 
Please check that it exists and elogd has write access

I started the daemon.  I've not yet assigned passwords -- just checking
things out.  How can I create this access to my own directory?
  Draft   Thu Mar 10 00:16:33 2016  Davedavid.levine@lmco.comQuestionWindows2.71elogd -m

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.

Can anyone tell me why I get this error?

==============================

Here is the command & output:

c:\Program Files (x86)\ELOG>elogd -m

Retrieving entries from "http://166.22.64.201/Equipment Log"...
All entries identical

Retrieving entries from "http://166.22.64.201/System Log"...

Error sending local entry: Error transmitting message

  68279   Thu Mar 10 00:26:03 2016 Question Davedavid.levine@lmco.comQuestionWindows2.71elogd -m Error sending local entry: Error transmitting message

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.

Can anyone tell me why I get this error?

==============================

Here is the command & output:

c:\Program Files (x86)\ELOG>elogd -m

Retrieving entries from "http://166.22.64.201/Equipment Log"...
All entries identical

Retrieving entries from "http://166.22.64.201/System Log"...

Error sending local entry: Error transmitting message

  67820   Mon Mar 9 17:03:38 2015 Entry Darren Hollinrakehollinrakedp@gmail.comQuestionWindows2.9.2Is it possible to only send an email based on the value of multiple attributes?
My current setup notifies users if downtime = yes.
Email Downtime Yes = user1@xyz.com, user2@xyz.com

Is it possible to only send an email based on the value of multiple attributes?
For my use:
user1 only needs notifications if Platform = Workstation and Downtime = Yes
user2 only needs notifications if Platform = Network and Downtime = Yes
  68289   Sat Mar 19 15:24:29 2016 Reply Darren Hollinrakehollinrakedp@gmail.comQuestionLinux3.1.1Re: Installation: Failed Dependencies

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

yum install -y elog-latest.i386.rpm

This should install all the required dependencies.

Phil Rubin wrote:

Is there anything I can do about this?


kernel:  2.6.32-279.14.1.el6.x86_64

ldd (GNU libc) 2.12

/lib64/libc.so.6

/usr/lib64/libssl.so.10


rpm -i elog-latest.i386.rpm

error: Failed dependencies:

libc.so.6 is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.0) is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.1) is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.1.3) is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.3) is needed by elog-3.1.1-1.i386

libssl.so.6 is needed by elog-3.1.1-1.i386

 

  68385   Fri Aug 19 19:39:50 2016 Question Darren Hollinrakehollinrakedp@gmail.comQuestionWindowsV3.1.1-3f311c5elog client cmd line submission of attributes with spaces.
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 the elog client in Windows?

Command being entered:

Quote:
C:\Program Files (x86)\ELOG>elog -h 127.0.0.1 -p 443 -s -l "Oceana Logbook" -u j
ohn.smith john.smith -v -n 0 -a Platform=LSOT -a "Start Time"="Fri, 19 Aug 2016
12:58:01 -0500" -a "Author=John Smith" -a "Device=2H111-1" -a "Action Type"=Mai
ntenance -a "Maint Type"=Unscheduled -a "System=Device" -a "Downtime=No" -a "Man
Hours"=1.0 -a MAF="" -a "Lost Time"="" -m "testing"

You can see where I have multiple attributes with spaces. Below you see where the name shows an underscore instead of a space.


Quote:
Successfully connected to host 127.0.0.1, port 443
Request sent to host:
POST /Oceana+Logbook/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------22C602B76
C41
Host: 127.0.0.1:443
User-Agent: ELOG
Content-Length: 1790


Content sent to host:
---------------------------22C602B76C41
Content-Disposition: form-data; name="cmd"

Submit
---------------------------22C602B76C41
Content-Disposition: form-data; name="unm"

john.smith
---------------------------22C602B76C41
Content-Disposition: form-data; name="upwd"

JUl77l/.kXYBzfoOZpsy.URRZEZpg2SHZNZIum6Rh/5
---------------------------22C602B76C41
Content-Disposition: form-data; name="exp"

Oceana Logbook
---------------------------22C602B76C41
Content-Disposition: form-data; name="encoding"

ELCode
---------------------------22C602B76C41
Content-Disposition: form-data; name="Platform"

LSOT
---------------------------22C602B76C41
Content-Disposition: form-data; name="Start_Time"

Fri, 19 Aug 2016 12:58:01 -0500
---------------------------22C602B76C41
Content-Disposition: form-data; name="Author"

Bruce Slack
---------------------------22C602B76C41
Content-Disposition: form-data; name="Device"

2H111-1
---------------------------22C602B76C41
Content-Disposition: form-data; name="Action_Type"

Maintenance
---------------------------22C602B76C41
Content-Disposition: form-data; name="Maint_Type"

Unscheduled
---------------------------22C602B76C41
Content-Disposition: form-data; name="System"

Device
---------------------------22C602B76C41
Content-Disposition: form-data; name="Downtime"

No
---------------------------22C602B76C41
Content-Disposition: form-data; name="Man_Hours"

1.0
---------------------------22C602B76C41
Content-Disposition: form-data; name="MAF"


---------------------------22C602B76C41
Content-Disposition: form-data; name="Lost_Time"


---------------------------22C602B76C41
Content-Disposition: form-data; name="Text"

testing 123
---------------------------22C602B76C41

Response received:
HTTP/1.1 404 Not Found
Server: ELOG HTTP 3.1.1-3f311c5
Content-Type: text/html;charset=ISO-8859-1
Connection: Close

<!DOCTYPE html>
<html><head>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<title>ELOG error</title>
<link rel="stylesheet" type="text/css" href="elog.css">
</head>
<body><center>
<table class="dlgframe" width="50%" cellpadding="1" cellspacing="0"<tr><td class
="errormsg"><i>Error: Attribute <b>Start Time</b> not supplied.</i><p>
Please go back and enter the <b>Start Time</b> field.
</td></tr>
<tr><td class="errormsg"><script language="javascript" type="text/javascript">
document.write("<button type=button onClick=history.back()>Back</button>");
</script>
<noscript>
Please use your browser's back button to go back
</noscript>
</td></tr>
</table>
</center></body></html>

Error: Missing required attribute "Start Time"

  68404   Thu Aug 25 18:18:57 2016 Reply Darren Hollinrakehollinrakedp@gmail.comQuestionWindowsV3.1.1-3f311c5Re: elog client cmd line submission of attributes with spaces.
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 just a dash "-". It was a dash with both the "0" set and my previous format as well.

I did a bit more troubleshooting and if I removed the "Start Time" attribute from the list of required attributes, then my command would also be accepted. It was only choking on the datetime field as it appears I'm supplying it an invalid value. I just gave it a current epoch time and it functioned normally when a datetime attribute is not required. If I require my "Start Time" attribute and give it a valid epoch time (1472144295), it again throws the error that I'm missing a required attribute.


Andreas Luedeke wrote:
If the "Start Time" attribute is of the type "datetime", then you cannot assign a date string to it.
Instead you'll have to assign the seconds of the epoch.
Try assigning a "0", that should be the 1st of January 1970.

I hope that helps,
Andreas

Darren Hollinrake wrote:
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 the elog client in Windows?

Command being entered:

Quote:
C:\Program Files (x86)\ELOG>elog -h 127.0.0.1 -p 443 -s -l "Oceana Logbook" -u j
ohn.smith john.smith -v -n 0 -a Platform=LSOT -a "Start Time"="Fri, 19 Aug 2016
12:58:01 -0500" -a "Author=John Smith" -a "Device=2H111-1" -a "Action Type"=Mai
ntenance -a "Maint Type"=Unscheduled -a "System=Device" -a "Downtime=No" -a "Man
Hours"=1.0 -a MAF="" -a "Lost Time"="" -m "testing"

You can see where I have multiple attributes with spaces. Below you see where the name shows an underscore instead of a space.


Quote:
Successfully connected to host 127.0.0.1, port 443
Request sent to host:
POST /Oceana+Logbook/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------22C602B76
C41
Host: 127.0.0.1:443
User-Agent: ELOG
Content-Length: 1790


Content sent to host:
---------------------------22C602B76C41
Content-Disposition: form-data; name="cmd"

Submit
---------------------------22C602B76C41
Content-Disposition: form-data; name="unm"

john.smith
---------------------------22C602B76C41
Content-Disposition: form-data; name="upwd"

JUl77l/.kXYBzfoOZpsy.URRZEZpg2SHZNZIum6Rh/5
---------------------------22C602B76C41
Content-Disposition: form-data; name="exp"

Oceana Logbook
---------------------------22C602B76C41
Content-Disposition: form-data; name="encoding"

ELCode
---------------------------22C602B76C41
Content-Disposition: form-data; name="Platform"

LSOT
---------------------------22C602B76C41
Content-Disposition: form-data; name="Start_Time"

Fri, 19 Aug 2016 12:58:01 -0500
---------------------------22C602B76C41
Content-Disposition: form-data; name="Author"

Bruce Slack
---------------------------22C602B76C41
Content-Disposition: form-data; name="Device"

2H111-1
---------------------------22C602B76C41
Content-Disposition: form-data; name="Action_Type"

Maintenance
---------------------------22C602B76C41
Content-Disposition: form-data; name="Maint_Type"

Unscheduled
---------------------------22C602B76C41
Content-Disposition: form-data; name="System"

Device
---------------------------22C602B76C41
Content-Disposition: form-data; name="Downtime"

No
---------------------------22C602B76C41
Content-Disposition: form-data; name="Man_Hours"

1.0
---------------------------22C602B76C41
Content-Disposition: form-data; name="MAF"


---------------------------22C602B76C41
Content-Disposition: form-data; name="Lost_Time"


---------------------------22C602B76C41
Content-Disposition: form-data; name="Text"

testing 123
---------------------------22C602B76C41

Response received:
HTTP/1.1 404 Not Found
Server: ELOG HTTP 3.1.1-3f311c5
Content-Type: text/html;charset=ISO-8859-1
Connection: Close

<!DOCTYPE html>
<html><head>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<title>ELOG error</title>
<link rel="stylesheet" type="text/css" href="elog.css">
</head>
<body><center>
<table class="dlgframe" width="50%" cellpadding="1" cellspacing="0"<tr><td class
="errormsg"><i>Error: Attribute <b>Start Time</b> not supplied.</i><p>
Please go back and enter the <b>Start Time</b> field.
</td></tr>
<tr><td class="errormsg"><script language="javascript" type="text/javascript">
document.write("<button type=button onClick=history.back()>Back</button>");
</script>
<noscript>
Please use your browser's back button to go back
</noscript>
</td></tr>
</table>
</center></body></html>

Error: Missing required attribute "Start Time"

ELOG V3.1.5-3fb85fa6