Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefan Ritt on Thu Dec 15 13:59:14 2016 
|
I tried your config file on my Mac and it just worked fine without any crash:
|
|
Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefano Bonaldo on Thu Dec 15 14:44:32 2016
|
Hello Stefan, thanks for your answer. So I made a new logbook, without entries. I generated, as you, two new entries and I discover that this problem
come out when in the URL the command for the sorting follow the command of the display mode. So for example the following URL give me the issue:
http://local.host.com:8080/65+nm/?mode=summary&sort=Record+date |
|
Re: elogd crash on sorting the entries by an datetime attribute, posted by Alan Grant on Thu Dec 15 15:42:06 2016
|
Hi Stefano.
This may or may not have anything to do with your specific problem but I notice you have the single word "date" as part of your
attribute name and Date is actually a reserved word in Elog. Although your attribute is not exclusively called "date" I have found that |
|
Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefano Bonaldo on Fri Dec 16 02:44:53 2016
|
Hello Alan,
I tried with a new logbook with an attribute without "date" name, but unfortunately I got the same error. Any other suggestions?
Thanks |
|
Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefan Ritt on Fri Dec 16 09:27:26 2016
|
Still no luck. Tried your URL and still works fine for me:
|
|
Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefan Ritt on Fri Dec 16 09:55:20 2016
|
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 |
Elog crashes with null Username, posted by Alan Grant on Sun Dec 18 08:51:47 2016
|
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: |
|
Re: Elog crashes with null Username, posted by Stefan Ritt on Mon Dec 19 12:28:47 2016
|
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 |