Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 330 of 807  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  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"

 

 

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

Giving up. Send me your config file and I will debug it.

Stefan

David Wallis wrote:

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"

 

 

 

 

  69250   Mon Oct 26 11:42:53 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows | Mac OSX | All | Other3.1.4Re: MEG style elog configuration

It was done using the "groups" feature:

https://elog.psi.ch/elog/config.html#groups

Stefan

Daniel Kohl wrote:

Hello,

 

I'm new to elog software and I could not find a solution to my configuration issue. I would like to setup a configuration file similar to MEG experiment's elog.

https://elog.psi.ch/elogs/meg/

I'm interested in creating similar to the structure: "General", "Collaboratoin", "Sub-groups (with sub-sub groups "Software", "Hardware" etc). I cannot tell if this was created by using Top Group feature.

Can someone explain how this design structure can be achieved?

 

Thanks,

Daniel

 

  69252   Tue Oct 27 16:15:26 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV3.1.4-ba84827Re: Create entry from command line - override Date?

You have to manually manipulate the logbook files YYMMDDa.log where you find the date at the top like:

MID@$: 1
Date: Wed, 02 Sep 2020 15:38:09 +0300 <==== change here !!!!
Author: Stefan
Type: General
Category: 
Subject: CURL test
Attachment: 
Encoding: plain
========================================
Text body
 

  69254   Tue Oct 27 16:49:53 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV3.1.4-ba84827Re: Create entry from command line - override Date?

"Date" must be on the first line on each entry and it must be named "Date".

Stefan

David Wallis wrote:

Hi Stefan, thanks! Does the Date field need to be the first field in each entry? I can see adding a "termpory" field called "Orig Date", upload the old entries, then edit the file(s), delete the Date field, and rename Orig Date to Date. Will that work?

Stefan Ritt wrote:

You have to manually manipulate the logbook files YYMMDDa.log where you find the date at the top like:

MID@$: 1
Date: Wed, 02 Sep 2020 15:38:09 +0300 <==== change here !!!!
Author: Stefan
Type: General
Category: 
Subject: CURL test
Attachment: 
Encoding: plain
========================================
Text body
 

 

 

  69267   Wed Dec 2 11:51:24 2020 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.7.7-2246Re: Change / List Change doen't work anymore?
Yepp, the documentation was wrong. I fixed it.

Stefan
  69275   Thu Dec 3 09:57:20 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows | Mac OSX | All | Other3.1.3Re: length of condition names

You can easily use multi-character conditionals, up to 256 chars.

Harry Martin wrote:

The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions.  I don't see any update/change to that rule anywhere in the docs.

I have been using multi-character condition names successfully.   I find these are easier to use since they can be more descriptive of each condition.   It works, but I am concerned I may be doing something that might not be supported going forward.   (It is simple enough to change these, but I'd prefer to know if this practice is acceptable.)

Thank you, again, for this fine (and, may I add, fun?) tool.  I'm having a good time with it!

 

  69276   Thu Dec 3 09:58:44 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows3.1.3Re: Options <...> vs ROptions <...>

For conditional attributes, you have to use Options, not ROptions. Maybe I will implement that one day, but only if I will have plenty of time...

Harry Martin wrote:

Same problem here, in version 3.1.3.   It would be very nice if this worked.

Wolfgang Bayer wrote:

According to section "Syntax of elogd.cfg" of the "Administrator's Guide" Options <attribute> = <list> and  ROptions <attribute> = <list> should be the same. But there is a litle difference, because choosing an entry of the Options-pull-down menu causes a reload of the entry mask while choosing a ROption-radio-button the entry mask is not reloaded. This causes a problem using conditional attributes. The condition is only paid attention to in case of Options but not in case of ROptions. In my case I would like to use ROption, as it is faster to set a radio button than to choose an item in a pull-down menu, but I can't as I have also to use conditional attributes. Is there any solution?

 

 

ELOG V3.1.5-3fb85fa6