Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 493 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  65786   Thu Mar 20 23:46:42 2008 Reply svrmartysvrmarty@gmx.netQuestionLinux2.7.3Re: German language

Stefan Ritt wrote:

Salvatore wrote:

Wen es interessiert:

der Eintrag "eloglang = german" gehoert in das Verzeichnis "usr/lib/elog/resources". Dort wird er von elogd ausgelesen.

 

Wie bitte ist der dorhin gekommen? Normalerweise wird elogd.cfg unter /usr/local/elog gespeichert. Wenn man natuerlich diese Datei von Hand irgendwo andershin kopiert, muss man sie auch dort veraendern, sonst schiesst man sich selbst in's Bein.

 

Wie und wo funktioniert das mit dem debian package ?

hier gibt es nur /etc/elog.conf, egal in welchem teil ich es reinschreibe, groß, klein,

ich habe leider noch immer alles in englisch

 

  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

 

  68605   Thu Apr 20 13:35:53 2017 Reply Kp1454477@mvrht.comQuestionLinux2.9.2Re: Full anonymous access

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

 

 

  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

 

 

 

  68607   Thu Apr 20 13:48:43 2017 Reply Kp1454477@mvrht.comQuestionLinux2.9.2Re: Full anonymous access

OK, i will try that. Thanks.

Stefan Ritt wrote:

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

 

 

 

 

  69239   Tue Oct 20 17:50:50 2020 Reply David Walliswallis@aps.anl.govQuestionLinuxELOG V3.1.4-ba8Re: From command line: "command Submit not allowed"

Update: I tried switching the logbook to no authentication reqiured, and still get the "command Submit not allowed" response.

David Wallis wrote:

I'm running  Elog version V3.1.4-ba84827 on Red Hat Linux 7.9. As part of migrating from an older in-house logbook to Elog, I need to upload all the old logbook entries. However, when I attempt to do that with the "elog" command line tool, I'm getting the error "command Submit not  allowed.

I read through a similar report from 2015 (entry #68149), but none of the potential causes seem to be at play here. The logbook is using PAM authentication, and I can log in to the web interface using the same credentials I'm using from the command line. The other case mentioned a dis-allowed encoding format, but my logbook is configured to allow all formats.

 

This is the command line I'm using:

/usr/local/elog/bin/elog -v -h logbook.aps.anl.gov -p 8081 -l On_Call -x -n 2 -a Date='10/19/2020 01:02' Author="David Wallis" Title='Test Upload' Status='Open' System='On-Call' -u 'wallis' '*****'  "This is a test message"

 

  69240   Tue Oct 20 18:02:42 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxELOG V3.1.4-ba8Re: From command line: "command Submit not allowed"

"submit not allowed" you typically get if there is a "guest menu" for read-only access and you are not logged in. I never tried the elog program with PAM authentication, but you said that your turned authentication off. What I would do is to strip down your elogd.cfg to a very simple form until the elog utility works, then figure out which configuration makes the trouble.

Stefan

David Wallis wrote:

Update: I tried switching the logbook to no authentication reqiured, and still get the "command Submit not allowed" response.

David Wallis wrote:

I'm running  Elog version V3.1.4-ba84827 on Red Hat Linux 7.9. As part of migrating from an older in-house logbook to Elog, I need to upload all the old logbook entries. However, when I attempt to do that with the "elog" command line tool, I'm getting the error "command Submit not  allowed.

I read through a similar report from 2015 (entry #68149), but none of the potential causes seem to be at play here. The logbook is using PAM authentication, and I can log in to the web interface using the same credentials I'm using from the command line. The other case mentioned a dis-allowed encoding format, but my logbook is configured to allow all formats.

 

This is the command line I'm using:

/usr/local/elog/bin/elog -v -h logbook.aps.anl.gov -p 8081 -l On_Call -x -n 2 -a Date='10/19/2020 01:02' Author="David Wallis" Title='Test Upload' Status='Open' System='On-Call' -u 'wallis' '*****'  "This is a test message"

 

 

  69241   Tue Oct 20 18:26:26 2020 Reply David Walliswallis@aps.anl.govQuestionLinuxELOG V3.1.4-ba8Re: From command line: "command Submit not allowed"

Hmmm... I added "New" to the Guest menu list, and the button showed up for a guest user. But when I submitted the new ticket, I got the message Error: Command "Submit" is not allowed for user ""

Stefan Ritt wrote:

"submit not allowed" you typically get if there is a "guest menu" for read-only access and you are not logged in. I never tried the elog program with PAM authentication, but you said that your turned authentication off. What I would do is to strip down your elogd.cfg to a very simple form until the elog utility works, then figure out which configuration makes the trouble.

Stefan

David Wallis wrote:

Update: I tried switching the logbook to no authentication reqiured, and still get the "command Submit not allowed" response.

David Wallis wrote:

I'm running  Elog version V3.1.4-ba84827 on Red Hat Linux 7.9. As part of migrating from an older in-house logbook to Elog, I need to upload all the old logbook entries. However, when I attempt to do that with the "elog" command line tool, I'm getting the error "command Submit not  allowed.

I read through a similar report from 2015 (entry #68149), but none of the potential causes seem to be at play here. The logbook is using PAM authentication, and I can log in to the web interface using the same credentials I'm using from the command line. The other case mentioned a dis-allowed encoding format, but my logbook is configured to allow all formats.

 

This is the command line I'm using:

/usr/local/elog/bin/elog -v -h logbook.aps.anl.gov -p 8081 -l On_Call -x -n 2 -a Date='10/19/2020 01:02' Author="David Wallis" Title='Test Upload' Status='Open' System='On-Call' -u 'wallis' '*****'  "This is a test message"

 

 

 

ELOG V3.1.5-3fb85fa6