Re: elog client cmd line submission of attributes with spaces., posted by Andreas Luedeke on Sat Aug 20 12:17:10 2016
|
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"
|
|
|
|
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 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"
|
|
|
|
Re: elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Thu Aug 25 18:32:13 2016
|
Thanks for the response. You are indeed correct that the issue disappears when I comment out my required attributes line. If I just remove my "Start Time" attribute, all the other attributes work as well.
| Rudy Taraschi wrote: | | Try commenting out the Required Attributes line in your elogd.cfg file before submitting. I think it's a bug but this work-around gets around it. |
|
|
Re: elog client cmd line submission of attributes with spaces., posted by Rudy Taraschi on Thu Aug 25 18:45:48 2016
|
| Darren Hollinrake wrote: | | Thanks for the response. You are indeed correct that the issue disappears when I comment out my required attributes line. If I just remove my "Start Time" attribute, all the other attributes work as well. |
I used to just comment out that one field in Required Attributes as well, but it was a pain to edit the CFG file, so I took the lazy approach and just commented out the whole line - less typing  |
|
Re: elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Thu Aug 25 19:04:11 2016
|
Agreed, I just wanted to clarify for anyone else though that the issue seems to be centered on my "Start Time" attribute which is a datetime field. All the other attributes (with spaces) allowed submission of the entry so long as the "Start Time" attribute wasn't set to required. That appears to be the one with the actual issue. Giving a valid epoch time when that field isn't required allows the field to be populated correctly. However, if the "Start Time" attribute is required (same epoch time used when it wasn't a required field), I again receive the error that the "Start Time" attribute is missing.
| Rudy Taraschi wrote: |
| Darren Hollinrake wrote: | | Thanks for the response. You are indeed correct that the issue disappears when I comment out my required attributes line. If I just remove my "Start Time" attribute, all the other attributes work as well. |
I used to just comment out that one field in Required Attributes as well, but it was a pain to edit the CFG file, so I took the lazy approach and just commented out the whole line - less typing |
|
Gmail email smtp settings, posted by Devrim Esenturk on Mon Jan 2 16:32:18 2017
|
Hi all
I am trying to send email via Gmail smtp with no success. Elog uses port 25 which is not allowed. I need to use 587 or 465 ports to send mail. How can I change the port?
Have a good year all!
Devrim |
|
Re: subject line bug on resumit elog entries as new?, posted by David Pilgram on Tue Jun 9 16:17:06 2015
|
Hi Stefan,
I see that you've updated the elog running this forum today, 5 versions after you reported fixing the "A new elog entry has been entered" and "An old elog entry has been updated" issue. But the emails coming out are still all of the "An old elog entry...", rather than "A new..."
David.
| Stefan Ritt wrote: |
|
I fixed both issues, now resubmitting an entry or submitting a new entry both yields "New LEOG entry".
| Jacky Li wrote: |
|
Hi,
I updated an old elog entry and resubmit it as new by checking the box resubmit as new. Does the subject line should said it is a "New ELOG entry" instead of "Updated ELOG entry"? Thank you.
Also when some people submit a new elog, the subject line is "Updated ELOG entry". This is a bit odd. I can't reproduce that bug when I did my test.
Jacky
|
|
|
|
Re: subject line bug on resumit elog entries as new?, posted by Stefan Ritt on Tue Jun 9 16:46:48 2015
|
Any better now?
| David Pilgram wrote: |
|
Hi Stefan,
I see that you've updated the elog running this forum today, 5 versions after you reported fixing the "A new elog entry has been entered" and "An old elog entry has been updated" issue. But the emails coming out are still all of the "An old elog entry...", rather than "A new..."
|
|