ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68612
|
Fri Apr 21 10:57:07 2017 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 3.1.2 | Re: Elog crashes with null Username |
I made a new release for you 3.1.3
Xuan Wu wrote: |
No, We are using the released version 3.1.2
How to use the current git revision or is it a long time to wait for the next release?
Alan Grant wrote: |
Are you using the current git revision Xuan?
Xuan Wu wrote: |
We also meet this issue occasionally, so how can we get rid of this?
Stefan Ritt wrote: |
Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.
Alan Grant wrote: |
I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:
16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)
|
|
|
|
|
|
68613
|
Fri Apr 21 12:18:57 2017 |
| Xuan Wu | wux@ihep.ac.cn | Bug report | Windows | 3.1.2 | Re: Elog crashes with null Username |
Awesome!It's appreciated. Many Thanks!
Stefan Ritt wrote: |
I made a new release for you 3.1.3
Xuan Wu wrote: |
No, We are using the released version 3.1.2
How to use the current git revision or is it a long time to wait for the next release?
Alan Grant wrote: |
Are you using the current git revision Xuan?
Xuan Wu wrote: |
We also meet this issue occasionally, so how can we get rid of this?
Stefan Ritt wrote: |
Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.
Alan Grant wrote: |
I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:
16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)
|
|
|
|
|
|
|
67123
|
Tue Sep 13 13:38:19 2011 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug fix | Linux | 2.9.0-2414 | Re: Elog crashes with URL find npp=0 |
> [...] It appears that npp=0 crashes elogd [...]
Here's a patch: search for "npp" in src/elogd.c and add the following line:
if (n_page<=0) n_page = 20;
Here's the diff output for version 2.9.0-2414
*** 20092,20096 ****
if (isparam("npp"))
n_page = atoi(getparam("npp"));
+ if (n_page<=0) n_page = 20;
if (page_mid) { |
68127
|
Fri Sep 25 22:37:08 2015 |
| Edmund Hertle | edmund.hertle@kit.edu | Question | Linux | 3.1.0 | Re: Elog command not working properly |
> <p>Hi,</p>
>
> <p>I have a problem running elog command from php script. Basically in the php I call system("elog -h etc etc.. And from the php command line works but not in the browser apparently without errors (php apache
logfile no problem), any suggestions?</p>
Hey,
this sounds more like a PHP issue.
Which PHP version are you using?
Which webserver?
Which php function are you using: shell_exec() or exec()? Try looking at the return of exec()
Is the elog file set to the correct file permissions to be executed by the webserver?
Is the elog file in the PHP path or do you take care of defining the correct path?
eddy |
68128
|
Sat Sep 26 03:34:44 2015 |
| Stefano | stefano.colafranceschi@gmail.com | Question | Linux | 3.1.0 | Re: Elog command not working properly |
Yes it was a path issue PHP was not loading correctly environmental path
> > <p>Hi,</p>
> >
> > <p>I have a problem running elog command from php script. Basically in the php I call system("elog -h etc etc.. And from the php command line works but not in the browser apparently without errors (php apache
> logfile no problem), any suggestions?</p>
>
> Hey,
> this sounds more like a PHP issue.
> Which PHP version are you using?
> Which webserver?
> Which php function are you using: shell_exec() or exec()? Try looking at the return of exec()
> Is the elog file set to the correct file permissions to be executed by the webserver?
> Is the elog file in the PHP path or do you take care of defining the correct path?
>
>
> eddy |
67095
|
Fri Jul 22 10:31:27 2011 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | All | 2.9.0 | Re: Elog client usage |
Alan Grant wrote: |
I have searched the Elog forum and docs at length for actual examples of how to use the Elog client and I apologize if I missed it somehwere but could someone please provide some actual examples of how the parmeters are used? I haven't had much success setting it up just going by the Elog command syntax quide.
What I intend to do is load a raw text file into an active logbook directly, either one line at at time or batched from a text file ("m" option).
Also, I saw a Perl script contribution somewhere on the site which appears to offer the same functionality as the above util. Just wondering why there would be two methods, and which might be the best for me to use? Thank you.
|
I suppose you have your demon "elogd" running and you can connect to your logbook via the web interface?
Then you can use the "elog" command to upload a text file as one entry.
If you want to split the text file to one-entry-per-line, you need to write a batch script to do that.
The usage of the "elog" command is descibed in the ELOG User's Guide: https://midas.psi.ch/elog/userguide.html#misc
The command line for "elog" has to define all "Required attributes" with "-a ..."
elog -h <host> -p <port> -l <logbook> -u <user> <password> -a <attribute>=<value> -n 1 -m <text-file>
<port> can be omitted if port 80 is used, "-u <user> <password>" can be omitted if anonymous entry creation is allowed.
Here's an example to write to the demo logbook at midas (local text file /tmp/hello.txt contains "hello world")
elog -h midas.psi.ch -l Linux+Demo -d elogs -a Author=nobody -a Type=Other -a Category=test -a "Subject=hello" -m /tmp/hello.txt
I hope this helps.
PS: please never refer to a location as "somewhere on the site". |
67096
|
Tue Jul 26 21:50:05 2011 |
| Alan Grant | netman311@mts.net | Info | All | 2.9.0 | Re: Elog client usage |
Andreas Luedeke wrote: |
Alan Grant wrote: |
I have searched the Elog forum and docs at length for actual examples of how to use the Elog client and I apologize if I missed it somehwere but could someone please provide some actual examples of how the parmeters are used? I haven't had much success setting it up just going by the Elog command syntax quide.
What I intend to do is load a raw text file into an active logbook directly, either one line at at time or batched from a text file ("m" option).
Also, I saw a Perl script contribution somewhere on the site which appears to offer the same functionality as the above util. Just wondering why there would be two methods, and which might be the best for me to use? Thank you.
|
I suppose you have your demon "elogd" running and you can connect to your logbook via the web interface?
Then you can use the "elog" command to upload a text file as one entry.
If you want to split the text file to one-entry-per-line, you need to write a batch script to do that.
The usage of the "elog" command is descibed in the ELOG User's Guide: https://midas.psi.ch/elog/userguide.html#misc
The command line for "elog" has to define all "Required attributes" with "-a ..."
elog -h <host> -p <port> -l <logbook> -u <user> <password> -a <attribute>=<value> -n 1 -m <text-file>
<port> can be omitted if port 80 is used, "-u <user> <password>" can be omitted if anonymous entry creation is allowed.
Here's an example to write to the demo logbook at midas (local text file /tmp/hello.txt contains "hello world")
elog -h midas.psi.ch -l Linux+Demo -d elogs -a Author=nobody -a Type=Other -a Category=test -a "Subject=hello" -m /tmp/hello.txt
I hope this helps.
PS: please never refer to a location as "somewhere on the site".
|
It seems straight forward enough but I must be missing something in my elog command string. I run the client utiltiy but it always hangs after pressing Enter from the cmd window. It could be the way I specifying the host or subdir but I'm not sure. I tried multiple variations.
Some more info: For the prototype I'm just running Elog locally. I installed it to my XP in "c:\program files\elog". I verified tht elogd process is running. With the Elog page already open (ref my attached cfg file) I typed the following, observing case sensitivity, then press enter and at this point it just hangs:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11"
Note since all attributes are optional I only included "Ticket Date" for now until I can get this cmd working.
Please bear with me as I don't have an extensive technical background but I would be very grateful for any help as it's for a project at work. Soonest response would be greatly appreciated.
Thanks.
Alan
|
67097
|
Wed Jul 27 04:36:40 2011 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | All | 2.9.0 | Re: Elog client usage |
Alan Grant wrote: |
Andreas Luedeke wrote: |
Alan Grant wrote: |
What I intend to do is load a raw text file into an active logbook directly, either one line at at time or batched from a text file ("m" option). [...]
|
[...] The usage of the "elog" command is descibed in the ELOG User's Guide: https://midas.psi.ch/elog/userguide.html#misc |
[...] I typed the following, observing case sensitivity, then press enter and at this point it just hangs:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11"
|
You wrote you want to upload a text file, then you need to add at the end "-m <file>". E.g. if the text-file is named "C:text.txt", then write:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11" -n 1 -m C:text.txt
The "-n 1" is just to tell elog to upload plain text. If you do not specify "-m <file>" then it expects input from a pipe and therefore hangs. If you don't know what "input from a pipe" means then ALWAYS use the "-m <file>" option.
PS: if "Ticket date" is of the format "date" then it is sensitive to the formatting of the date string. "Jul26/11" is likely not a legal date format. Better do not specify it for the first test. Write instead:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -n 1 -m C:text.txt
PPS: do you really use a sub-directory "elog" instead of the default location "logbooks" for your ELOG logbook files? If not, then leave out this option, too.
elog -h localhost -p 8080 -l Tartan+Tow+Log -n 1 -m C:text.txt
|