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
But if I put:
http://local.host.com:8080/65+nm/?sort=Record+date&mode=summary
This last URL is working. This means that the issue come out, when I change the dispay mode by the buttons "Full, Summary, Threaded" and then I click on the Coloumn "Record date" for sorting it. Hope you understand and you can reproduce it. Many thanks
EDIT: I'm facing the same problem on another MAC with a fresh installation of elogd.
| Stefan Ritt wrote: |
|
I tried your config file on my Mac and it just worked fine without any crash:
Could it be that on entry has corrupt data and is killing your server? Have you tried on a pristine new logbook?
Stefan
| stefano bonaldo wrote: |
|
Hello,
I'm facing with a crash, which happen when I sort the entries by a datetime attribute (sort or rsort) and then i change the display mode from Full, Summary and Threaded.
For example, the elogd crashes when I try to connect from the Full display to Summary in sort mode. The issue presents for example by entering with the following URL:
http://host.name.com:8080/65+nm/?mode=summary&sort=Record+date
Can you please help me?
Here I reduced my elogd.cfg at minimum and I still get this issue:
[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
|
|
|
|
Re: MacOS install failure - cannot find ssl.h, posted by Stefano Bonaldo on Thu Dec 15 15:04:53 2016
|
Currently, in my MacBook Pro with Sierre, the search path /opt/local/include of the prprocessor is not included.
cpp -v
Apple LLVM version 8.0.0 (clang-800.0.38)
Target: x86_64-apple-darwin16.1.0
....
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/8.0.0/include
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include
/usr/include
/System/Library/Frameworks (framework directory)
/Library/Frameworks (framework directory) |
|
Re: MacOS install failure - cannot find ssl.h, posted by Stefan Ritt on Thu Dec 15 15:41:59 2016
|
export C_INCLUDE_PATH=/opt/local/include
should do the trick. Put this into your .profile
| Stefano Bonaldo wrote: | Currently, in my MacBook Pro with Sierre, the search path /opt/local/include of the prprocessor is not included.
cpp -v
Apple LLVM version 8.0.0 (clang-800.0.38)
Target: x86_64-apple-darwin16.1.0
....
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/8.0.0/include
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include
/usr/include
/System/Library/Frameworks (framework directory)
/Library/Frameworks (framework directory) |
|
|
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 even using "date" as an isolated word within an attribute name (eg: Record date vs Record_date) can cause some issues. In my case, it caused a problem with the elog client when trying to update records which was only resolved when I changed the name of the attribute to Date/Time Received from Date and Time Received. Long story short, I avoid using any reserved words as part of attribute names.
Alan.
| stefano bonaldo wrote: |
|
Hello,
I'm facing with a crash, which happen when I sort the entries by a datetime attribute (sort or rsort) and then i change the display mode from Full, Summary and Threaded.
For example, the elogd crashes when I try to connect from the Full display to Summary in sort mode. The issue presents for example by entering with the following URL:
http://host.name.com:8080/65+nm/?mode=summary&sort=Record+date
Can you please help me?
Here I reduced my elogd.cfg at minimum and I still get this issue:
[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
|
|
|
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
| Alan Grant wrote: |
|
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 even using "date" as an isolated word within an attribute name (eg: Record date vs Record_date) can cause some issues. In my case, it caused a problem with the elog client when trying to update records which was only resolved when I changed the name of the attribute to Date/Time Received from Date and Time Received. Long story short, I avoid using any reserved words as part of attribute names.
Alan.
| stefano bonaldo wrote: |
|
Hello,
I'm facing with a crash, which happen when I sort the entries by a datetime attribute (sort or rsort) and then i change the display mode from Full, Summary and Threaded.
For example, the elogd crashes when I try to connect from the Full display to Summary in sort mode. The issue presents for example by entering with the following URL:
http://host.name.com:8080/65+nm/?mode=summary&sort=Record+date
Can you please help me?
Here I reduced my elogd.cfg at minimum and I still get this issue:
[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
|
|
|
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:
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?
|
|
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 "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 |
Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefano Bonaldo on Fri Dec 16 14:44:19 2016
|
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
|
|