Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 310 of 807  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  68579   Wed Mar 15 16:42:35 2017 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.1Re: Possible misuse of email headers Message-Id and In-Reply-To

Pull-request merged.

fbretel wrote:

Pull-request posted. Cheers.

 

  68590   Wed Apr 5 13:16:34 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowsV3.1.0-3c6435eRe: Elog not see image magick

Must be your PATH environment variable. You have usually different paths when running interactively or as a service. Try to change the path seen by services, or put the ImageMagick executable in the same directory as elogd.

Stefan

christian wrote:

Update:

While the image scaling via ImageMagick works when running elog manually it doesn't when running elog as a service. The service is hosted in the same user environment that allows image scaling with elog started manually. What else could go wrong?

Christian

  68594   Fri Apr 7 10:22:03 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowsV3.1.0-3c6435eRe: Elog not see image magick

I don't undersand myself fully how services see the environment. Like if they see the PATH at all. In some occations it helped to run the service not under the SYSTEM account, but under the (admin) account of a real user.

Stefan

christian wrote:

This I do not fully understand: To my understanding the PATH environment variable (includes the ImageMagick path) is a system variable and should be accessable from any account and should be valid under any conditions. Am I wrong? Additionally, I tried adding the system Path variable to the user specific variables for that user that runs the service (Path = %Path%) in the system settings. Finally, I tried copying the imdisplay.exe (ImageMagick executable) and convert.exe (used for the software detection) from the ImageMagick installation directory to the same directory as elogd. Neither of these approaches was successfull.

Christian

Stefan Ritt wrote:

Must be your PATH environment variable. You have usually different paths when running interactively or as a service. Try to change the path seen by services, or put the ImageMagick executable in the same directory as elogd.

Stefan

christian wrote:

Update:

While the image scaling via ImageMagick works when running elog manually it doesn't when running elog as a service. The service is hosted in the same user environment that allows image scaling with elog started manually. What else could go wrong?

Christian

 

 

  68595   Fri Apr 7 10:24:31 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowsV3.1.0-3c6435eRe: Elog not see image magick

Ah sorry. I recall now: Under Windows, calling subprocesses from a service does not work at all. After a couple of days of work I was not able to get this running. If somebody has some idea, I'm happy to try it. So most people use the elogd daemon in the background only under Linux.

Stefan

Stefan Ritt wrote:

I don't undersand myself fully how services see the environment. Like if they see the PATH at all. In some occations it helped to run the service not under the SYSTEM account, but under the (admin) account of a real user.

Stefan

christian wrote:

This I do not fully understand: To my understanding the PATH environment variable (includes the ImageMagick path) is a system variable and should be accessable from any account and should be valid under any conditions. Am I wrong? Additionally, I tried adding the system Path variable to the user specific variables for that user that runs the service (Path = %Path%) in the system settings. Finally, I tried copying the imdisplay.exe (ImageMagick executable) and convert.exe (used for the software detection) from the ImageMagick installation directory to the same directory as elogd. Neither of these approaches was successfull.

Christian

Stefan Ritt wrote:

Must be your PATH environment variable. You have usually different paths when running interactively or as a service. Try to change the path seen by services, or put the ImageMagick executable in the same directory as elogd.

Stefan

christian wrote:

Update:

While the image scaling via ImageMagick works when running elog manually it doesn't when running elog as a service. The service is hosted in the same user environment that allows image scaling with elog started manually. What else could go wrong?

Christian

 

 

 

  68597   Fri Apr 7 12:16:24 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.1Re: command line and apache+ldap authentication

Hi, the elog command line client does not know anything about Apache authentication, therefore the authentication with the elog username/password fails. As an alternative to the command line client you can use the "curl" utility (available under Linux). This tools has the "-u" flag, which works with Apache. The tricky thing is now to "emulate" your browser submitting an entry. You can do

$ curl -u <username>:<password> -F cmd=Submit -F Author=CURL -F Text="This is the CURL text" http://<your host>:8080/<logbook>

(of course your attributes might be different than "Author"). If you have a multiline text body, you can read that from a file (in this case "file.txt"):

$ curl -u <username>:<password> -F cmd=Submit -F Author=CURL -F Text="@file.txt" http://<your host>:8080/<logbook>

When I wrote "elog" orginiallly (199x?), "curl" was not available or at least I didn't know of. Right now it almoste completely can replace the elog tool.

Stefan

  68604   Thu Apr 20 12:59:24 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2Re: Full anonymous access

Sure. Just remove "Password file = ..." and any guest menu.

Stefan

K wrote:

How can i configure eLog to be used completely anonymous without the need to log in?

I tried menu and guest menu settings without luck. I do not use password files. With earlier versions this was easy to set up...

 

Thanks in advance

 

  68606   Thu Apr 20 13:45:42 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2Re: Full anonymous access

Version 2.9.2 is hopelessly outdated. Please upgrade to the current version on bitbucket. You also might have to delete any cookie in the browser sent to the elog server.

K wrote:

Does not work.

Clean install (debian 8 x64, with aptitude), only thing i've changed in the config is "URL"-parameter (global section) and redirection with Apache. No luck. Edit or delete gives an error "Error: Command "Delete" not allowed", "New" opens login-windows.

Now i removed all (guest) menu and URL settings a use it directly (port 8080), still no luck. "Error: Command "Delete" not allowed". When i click on "New" a login-windows opens.

Tested with the demo-logbook.

Stefan Ritt wrote:

Sure. Just remove "Password file = ..." and any guest menu.

Stefan

K wrote:

How can i configure eLog to be used completely anonymous without the need to log in?

I tried menu and guest menu settings without luck. I do not use password files. With earlier versions this was easy to set up...

 

Thanks in advance

 

 

 

  68612   Fri Apr 21 10:57:07 2017 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows3.1.2Re: Elog crashes with null Username

I made a new release for you 3.1.3

Xuan Wu wrote:

No, We are using the released version 3.1.2

How to use the current git revision or is it a long time to wait for the next release?

Alan Grant wrote:

Are you using the current git revision Xuan?

Xuan Wu wrote:

We also meet this issue occasionally, so how can we get rid of this?

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)

 

 

 

 

 

ELOG V3.1.5-3fb85fa6