Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 86 of 807  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  69772   Mon Apr 8 10:49:10 2024 Entry Stefano Lacaprarastefano.lacaprara@pd.infn.itQuestionLinuxELOG V3.1.4-395today date in template
Hello,
  I am using template for some elogbook entries.

Is is possible to automatically change the template using the actual date in some filed. 

Something like: the template has a place-holder <start date> and this is replaced with today's date when a new entry is created.

I already have a "date" filed which is automatically filled, but I've been asked to have the date also in the template.

Thanks in advance
Stefano
  Draft   Wed Sep 23 23:57:43 2015 Warning Stefanostefano.colafranceschi@gmail.comQuestionLinux3.1.0elog from php

Hi,

I need to run elog command in an online php script. The problem I see is that the script works from the command line but not from the browser. In the script I just use:

system(elog -h mypc -p 8080 -l bla -a Author=\'io\' -a Type=\' ..etc.etc

any suggestions?

  68128   Sat Sep 26 03:34:44 2015 Reply Stefanostefano.colafranceschi@gmail.comQuestionLinux3.1.0Re: 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(&quot;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
  68501   Thu Dec 15 01:38:20 2016 Reply stefano bonaldostefano.bonaldo.13@gmail.comQuestionMac OSX3.1.2Re: MacOS install failure - cannot find ssl.h

On Sierra Macports install openssl in /opt/local/include/ , but copy it into /usr/local/include. You should able to fix it.

sudo cp -r /opt/local/include/openssl /usr/local/include/

Stefan Ritt wrote:

My macports puts it under

/opt/local/include/openssl/ssl.h

Christina Swinson wrote:

I responded too quickly.

I already have openssl installed via macports (this is the "Mac version" of libssl-dev).

Does anyone know where exactly elog is looking for openssl/ssl.h? I have just updated Macports and upgraded to Sierra, so maybe it's been dumped it in a different location.

Christina

Christina Swinson wrote:

Oops!

I think that I must have skipped straight to the MacOS notes instead of reading the linux section properly.

Thanks for the help,

Christina

Stefan Ritt wrote:

If you look into the documentationa at:

http://midas.psi.ch/elog/adminguide.html#unix

you will see that for Linux (as well asl MacOS) you need the libssl-dev packaged to be installed. There are many ways to install this on MacOS, I personally use the MacPorts distribution:

https://www.macports.org/ports.php?by=library&substr=openssl

Best regards,
Stefan

 

Christina Swinson wrote:

Hi,

I am trying to install on MacOS Sierra. I believe that I have followed all the steps correctly, but the install is failing with the following error: 

cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -DHAVE_SSL -o elog src/elog.c crypt.o  -lssl
src/elog.c:57:10: fatal error: 'openssl/ssl.h' file not found
#include <openssl/ssl.h>
         ^
1 error generated.
make: *** [elog] Error 1

Help appreciated!

Thanks,
Christina

 

 

 

 

 

  68505   Thu Dec 15 14:44:32 2016 Reply Stefano Bonaldostefano.bonaldo.13@gmail.comBug reportMac OSX3.1.2Re: elogd crash on sorting the entries by an datetime attribute

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

 

 

  68506   Thu Dec 15 15:04:53 2016 Reply Stefano Bonaldostefano.bonaldo.13@gmail.comQuestionMac OSX3.1.2Re: 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)
  68509   Fri Dec 16 02:44:53 2016 Reply Stefano Bonaldostefano.bonaldo.13@gmail.comBug reportMac OSX3.1.2Re: 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

 

 

  68512   Fri Dec 16 14:44:19 2016 Agree Stefano Bonaldostefano.bonaldo.13@gmail.comBug fixMac OSX3.1.2Re: 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

 

ELOG V3.1.5-3fb85fa6