ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68518
|
Thu Dec 22 09:41:35 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | 3.1.2 | Re: Elog source code giving errors when compiling about missing header files |
You need the netdb.h header file to compile elog. I see that you compile under Windows. You have to make sure that your compiler installation comes with all header files. The netdb.h file is usually in /usr/include under Unix.
rahul bhandari wrote: |
I downloaded the source code from the git repository which contained the new fix that was made for the missing username-crash error. I tried compiling the elogd.c file using a GCC compiler and it gave an error about missing header files. It first gave an error about netdb.h file and when I commented that header file call, it gave further errors for other header files. I do not really understand why it gives an error about that.
|
|
68517
|
Wed Dec 21 20:15:19 2016 |
| rahul bhandari | rbhandari@winnipeg.ca | Info | Windows | 3.1.2 | Elog source code giving errors when compiling about missing header files |
I downloaded the source code from the git repository which contained the new fix that was made for the missing username-crash error. I tried compiling the elogd.c file using a GCC compiler and it gave an error about missing header files. It first gave an error about netdb.h file and when I commented that header file call, it gave further errors for other header files. I do not really understand why it gives an error about that. |
68515
|
Mon Dec 19 19:42:05 2016 |
| Alan Grant | agrant@winnipeg.ca | Bug report | Windows | 3.1.2 | Re: Elog crashes with null Username |
Thanks for the speedy fix.
FYI, our other Elog instances which are running ealrier versions do not exhibit this problem, as I confirmed that entering null ID/password returns "Invalid Username or password" as expected. This may be why it wasn't mentioned by anyone else before. Maybe something got inadvertently dropped in the newer version.
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)
|
|
|
68514
|
Mon Dec 19 12:28:47 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 3.1.2 | Re: Elog crashes with null Username |
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)
|
|
68513
|
Sun Dec 18 08:51:47 2016 |
| Alan Grant | agrant@winnipeg.ca | Bug report | Windows | 3.1.2 | Elog crashes with null Username |
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) |
68512
|
Fri Dec 16 14:44:19 2016 |
| Stefano Bonaldo | stefano.bonaldo.13@gmail.com | Bug fix | Mac OSX | 3.1.2 | Re: elogd crash on sorting the entries by an datetime attribute |
Bug FIXED! Many thanks Stefan and my warmest congratulations for the elog project.
Stefano
Stefan Ritt wrote: |
Ok I found it!
Was tricky. In my development environment (XCode) it worked fine. Only when I compiled elogd under Sierra on the command line, the probelm occured. That's why I did not see it earlier. It has to do with some functions Apple apparently changed ("strlcpy"). These function now have a new "functionality": When two parameters overlap, the function just aborts the process. This is specific to Sierre, so on any other Linux this does not happen. I changed now the soruce code to take care of the modified functions, and now it works fine. Please update to the newest GIT revision of elogd and recompile.
Stefan
|
|
68511
|
Fri Dec 16 09:55:20 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 3.1.2 | Re: elogd crash on sorting the entries by an datetime attribute |
Ok I found it!
Was tricky. In my development environment (XCode) it worked fine. Only when I compiled elogd under Sierra on the command line, the probelm occured. That's why I did not see it earlier. It has to do with some functions Apple apparently changed ("strlcpy"). These function now have a new "functionality": When two parameters overlap, the function just aborts the process. This is specific to Sierre, so on any other Linux this does not happen. I changed now the soruce code to take care of the modified functions, and now it works fine. Please update to the newest GIT revision of elogd and recompile.
Stefan |
68510
|
Fri Dec 16 09:27:26 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Mac OSX | 3.1.2 | Re: elogd crash on sorting the entries by an datetime attribute |
Still no luck. Tried your URL and still works fine for me:

Here is my full elogd.cfg:
[global]
port = 8080
[65 nm]
Attributes = Record date
Type Record date = datetime
Preset Record date = $date
List Display = Record date
Start page = ?sort=Record date
Anything else I coudl try to reproduce your error?
|