| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68608
|
Fri Apr 21 02:21:59 2017 |
 | Xuan Wu | wux@ihep.ac.cn | Bug report | Windows | 3.1.2 | Re: Elog crashes with null Username |
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)
|
|
|
|
68610
|
Fri Apr 21 05:27:35 2017 |
| Alan Grant | agrant@winnipeg.ca | Bug report | Windows | 3.1.2 | Re: Elog crashes with null Username |
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)
|
|
|
|
|
68611
|
Fri Apr 21 08:19:05 2017 |
| Xuan Wu | wux@ihep.ac.cn | Bug report | Windows | 3.1.2 | Re: Elog crashes with null Username |
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)
|
|
|
|
|
|
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 |