Re: From command line: "command Submit not allowed", posted by David Wallis on Tue Oct 20 17:50:50 2020
|
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 |
|
Re: From command line: "command Submit not allowed", posted by Stefan Ritt on Tue Oct 20 18:02:42 2020
|
"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. |
|
Re: From command line: "command Submit not allowed", posted by David Wallis on Tue Oct 20 18:26:26 2020
|
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 |
|
Re: From command line: "command Submit not allowed", posted by Stefan Ritt on Tue Oct 20 18:40:05 2020
|
Giving up. Send me your config file and I will debug it.
Stefan
David |
|
Re: From command line: "command Submit not allowed", posted by David Wallis on Tue Oct 20 20:44:03 2020
|
I've been able to work around this by completely turning off authentication, and adding New to the Guest menu list.
One additional question: since I'm uploading historical logbook entries, is it possible to set the entry creation date via the command line?
It seems that elogd is overriding the attribute "Date". |
|
Re: From command line: "command Submit not allowed", posted by David Dunne on Wed Oct 21 03:08:21 2020
|
FYI, I had problems a few weeks ago trying to get the command line elog working, blamed everybody and everything but myself.
In my case it was command line syntax errors and eventually got it going as part of a nightly script
While testing I ran the Elog Server from the command line in verbose mode to see if that helped determine the problem. |
|
Re: From command line: "command Submit not allowed", posted by David Wallis on Wed Oct 21 15:14:13 2020
|
Hi David, thanks for your input!
This logbook has been around for almost 10 years, and has evolved from file-based authentication, to LDAP, and finally to PAM (that can use any
of local password files, LDAP, and Active Directory), and I'm thinking that might be the root of this problem. There are old account entries from the |
Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 16:00:03 2020
|
I'm converting our on-call logbook, with 25 years of history, to elog. Is there a way to override the current date/time for the Date field with the
creation date/time of the original logbook entry? |