| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68506
|
Thu Dec 15 15:04:53 2016 |
 | Stefano Bonaldo | stefano.bonaldo.13@gmail.com | Question | Mac OSX | 3.1.2 | Re: MacOS install failure - cannot find ssl.h |
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) |
|
68507
|
Thu Dec 15 15:41:59 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Mac OSX | 3.1.2 | Re: MacOS install failure - cannot find ssl.h |
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) |
|
|
68508
|
Thu Dec 15 15:42:06 2016 |
| Alan Grant | agrant@winnipeg.ca | Bug report | Mac OSX | 3.1.2 | Re: elogd crash on sorting the entries by an datetime attribute |
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
|
|
|
68509
|
Fri Dec 16 02:44:53 2016 |
| Stefano Bonaldo | stefano.bonaldo.13@gmail.com | Bug report | Mac OSX | 3.1.2 | Re: elogd crash on sorting the entries by an datetime attribute |
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
|
|
|
|
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?
|
|
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 |
|
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
|
|
|
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) |