Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 676 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6451 Entries 
Goto page Previous  1, 2, 3 ... 675, 676, 677 ... 805, 806, 807   Next  
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  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"

  68405   Thu Aug 25 18:32:13 2016 Agree Darren Hollinrakehollinrakedp@gmail.comQuestionWindowsV3.1.1-3f311c5Re: elog client cmd line submission of attributes with spaces.
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.
  68407   Thu Aug 25 19:04:11 2016 Reply Darren Hollinrakehollinrakedp@gmail.comQuestionWindowsV3.1.1-3f311c5Re: elog client cmd line submission of attributes with spaces.
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 Wink
  68426   Sun Sep 18 03:31:42 2016 Idea Darren Hollinrakehollinrakedp@gmail.comBug fixLinux3.0.0Re: notification error services in CentOS 6.5

The quick fix I found was to uncomment line 10 in the init.d file. (This was tested on a CentOS 6.8 AWS instance.)

. /etc/rc.d/init.d/functions

This will allow the status command to function properly.

Clean install:

[centos@ip-172-31-51-59 ~]$ service elogd status
status: invalid option: -p
 

After uncommenting line 10:

[centos@ip-172-31-51-59 ~]$ service elogd status
elogd (pid  11438) is running...

When you start elog it still won't show that the service started successfully (No 'OK'). If you go to stop the service, it will give you the proper 'OK' indicating it stopped successfully.

So to fix the missing 'OK' (or 'FAILED') we need to update the start section around line 51 as follows:

          touch /var/lock/subsys/elogd
        echo_success
        else
        echo_failure
        fi
        echo
        ;;
 

I've attached my modified init file which I believe corrects the above issues. I will say though that I'm not a programmer so I won't guarantee it's perfect. I haven't checked to see if CentOS 7 works with this modified version. Just checked it on a CentOS 7.2 AWS instance and it also appears to function correctly.

[root@oceana ~]# systemctl status elogd
● elogd.service - SYSV: ELOG is a weblog with integrated database
   Loaded: loaded (/etc/rc.d/init.d/elogd)
   Active: active (running) since Sun 2016-09-18 22:35:44 UTC; 7s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 2263 ExecStop=/etc/rc.d/init.d/elogd stop (code=exited, status=0/SUCCESS)
  Process: 2275 ExecStart=/etc/rc.d/init.d/elogd start (code=exited, status=0/SUCCESS)
 Main PID: 2277 (elogd)
   CGroup: /system.slice/elogd.service
           └─2277 /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg

Sep 18 22:35:44 oceana elogd[2277]: elogd 3.1.1 built Aug  4 20...0
Sep 18 22:35:44 oceana elogd[2277]: revision
Sep 18 22:35:44 oceana elogd[2277]: Falling back to default gro..."
Sep 18 22:35:44 oceana elogd[2277]: Falling back to default use..."
Sep 18 22:35:44 oceana elogd[2277]: CKeditor detected
Sep 18 22:35:44 oceana systemd[1]: Started SYSV: ELOG is a webl....
Sep 18 22:35:44 oceana elogd[2279]: Falling back to default gro..."
Sep 18 22:35:44 oceana elogd[2279]: Falling back to default use..."
Sep 18 22:35:44 oceana elogd[2277]: ImageMagick detected
Sep 18 22:35:44 oceana elogd[2277]: SSLServer listening on port....
Hint: Some lines were ellipsized, use -l to show in full.

The old SysV style commands ('service elogd start|stop|status') also function correctly.

[root@oceana ~]# service elogd stop
Stopping elogd (via systemctl):                            [  OK  ]
[root@oceana ~]# service elogd start
Starting elogd (via systemctl):                            [  OK  ]

 

Stefan Ritt wrote:

The init script supplied with elog was originally written for Redhat. It seems like CentOS has slightly changed the init daemon management, but I'm not an expert on that, nor do I have CentOS installed. If somebody comes with a fixed elogd.init for CentOS, I'm happy to include that in the distribution.

/Stefan

Banata wrote:

hello, I just upgrade from 2.9 into 3.0.0 in CentOS 6.5

but after upgrade, I can't check elogd services via command line

service elogd status,

always result in missing argument, while it works with httpd or mysqld services and old elogd version.

I try to uninstall and install rom scratch and same result,

Okay I give you screenshoot of that,

you may notice, on check service status and stopping services, error resulted

 

 

Attachment 1: elogd_modified 
#!/bin/sh

# chkconfig: 3 90 10
# description: ELOG is a weblog with integrated database
# processname: elogd
# config: /usr/local/elog/elogd.cfg
# pidfile: /var/run/elogd.pid

# Source function library.
. /etc/rc.d/init.d/functions

# Check for the config file
if [ ! -f /usr/local/elog/elogd.cfg ]; then
    exit 0
fi


# See how we were called.
case "$1" in
  start)
        if [ -f /var/run/elogd.pid ] ; then
	   pid=`cat /var/run/elogd.pid`
	   if [ -d /proc/$pid ] ; then
	     echo "elogd already running"
	     # echo_failure
	     exit 1
	   fi
	fi
        if [ -f /var/run/elogd.pid ] ; then
           rm -f /var/lock/subsys/elogd
	   rm -f /var/run/elogd.pid
        fi
	echo -n "Starting elogd: "
	/usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg  > /dev/null 2>&1 
	RETVAL=$?
        if [ $RETVAL -eq 0  ] ; then 
          touch /var/lock/subsys/elogd
        echo_success
	else
	echo_failure
        fi
	echo
	;;
  stop)
     echo ""
      if [ -f /var/run/elogd.pid ] ; then
        echo -n "Stoping elogd: "
        /bin/kill `cat /var/run/elogd.pid`
        rm -f /var/lock/subsys/elogd
	rm -f /var/run/elogd.pid
        echo_success
        echo
     else
        echo -n "No elogd running?"
	echo
     fi
     
	;;
  status)
     status -p /var/run/elogd.pid /usr/local/sbin/elogd
     RETVAL=$?
        ;;
  restart|reload)
	$0 stop
	sleep 1
	$0 start
	;;
  *)
	echo "Usage: $0 {start|stop|status|restart}"
	exit 1
esac

exit 0
  67266   Wed May 9 00:55:08 2012 Question Danielle Gillandersdanielle.gillanders@fortisbc.comQuestionWindowsLatestAdding an image to the top text

Hi there,

I am new to ELOG, trying to add an image (logo) in my top text.

Theme = default
Comment = TRIPLE POINT Log
Top text = Logo.png

results in ‰PNG  .

When I just enter a string of text it seems to work fine... I would really appreciate any help!

 

thanks!

  68018   Sun Jun 14 21:30:14 2015 Question Daniel Sajdykdaniel.sajdyk@gmail.comQuestionWindowsELOG V3.1.0-3c6"Preset on reply" not work?

Hi all :)

I try to setup my first lobgook, and have some problem. 

I want that Author was preset by $long_name, and it can't change its name. That works correct. I also want, when other user click Reply, that he will be author of reply, but Author windows goes emtpy... No Author, or Reply User in that field. Is it correct?

Do you have any suggestions? 

Here is part of config I use:

; preset author and email
Preset Author = $long_name
Preset Author Email = $user_email

; these attributes cannot be changed
Locked Attributes = Author

; options for reply
Subst on reply subject = Re: $Configuration Name
Remove on reply = Author, Author Email
Preset on reply Author = $long_name

 

Regards

Daniel.

  68022   Mon Jun 15 09:16:00 2015 Reply Daniel Sajdykdaniel.sajdyk@gmail.comQuestionWindowsELOG V3.1.0-3c6Re: "Preset on reply" not work?

Ok. Now it works :) Thank you :) I'm translating Elog into Polish. When I finish, can I send it to you?

Regards Daniel. 

Stefan Ritt wrote:

You have "Remove on reply" together with "Preset on reply Author". Since the first is executed later, you first preset the author name, then remove it again. Just discard the "Remove on reply" and you are fine.

Daniel Sajdyk wrote:

Hi all :)

I try to setup my first lobgook, and have some problem. 

I want that Author was preset by $long_name, and it can't change its name. That works correct. I also want, when other user click Reply, that he will be author of reply, but Author windows goes emtpy... No Author, or Reply User in that field. Is it correct?

Do you have any suggestions? 

Here is part of config I use:

; preset author and email
Preset Author = $long_name
Preset Author Email = $user_email

; these attributes cannot be changed
Locked Attributes = Author

; options for reply
Subst on reply subject = Re: $Configuration Name
Remove on reply = Author, Author Email
Preset on reply Author = $long_name

 

Regards

Daniel.

 

 

Goto page Previous  1, 2, 3 ... 675, 676, 677 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6