ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69246
|
Wed Oct 21 03:08:21 2020 |
| David Dunne | ddunne@seven.com.au | Question | Linux | ELOG V3.1.4-ba8 | Re: From command line: "command Submit not allowed" | 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.
On the server end the logbook uploading to is set for Plaintext
# Set entries to TEXT Only format
Default encoding = 1
Allowed encoding = 1
Elog server authenication is standard built in to elogd, no PAM, no LDAP, no Kerberos
Below is what works for me, I’ve replaced my Elog Server Hostname, Elog Username & Password used to connect to the server with generic.
Elog Server version = elog-3.1.4-2
# Log details in Elog Server
/usr/local/bin/elog -h HOSTNAME -p 80 -l Backups -u USERNAME PASSWORD -a Backup=NightlyBackupScript -a Hostname=$HOST -n 1 -x -m /tmp/elog.nightly.script.$TIMESTAMP
I've been caught out in the past having a very old version of the elog command line talking to a recent Elog Server build or Encoding not matching
David Wallis wrote: |
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".
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"
|
|
|
|
|
|
69259
|
Tue Nov 17 12:10:07 2020 |
| David Dunne | ddunne@seven.com.au | Question | Linux | 3.1.4 | Style <attribute> and Cell Style <attribute> on the same row | Query
(FYI, OS = FreeBSD, Elog Version as showing on logon box = V3.1.4-)
Is it possible to use both Style <attribute> and Cell Style <attribute> on the same row?
For example, have a Logbook containing several Attributes and display a subset of those attributes in Summary Mode. Two attributes are of interest for this query which are part of the attributes displayed in Summary Mode, attributes ‘Assign Line’ and ‘Service’
If the ‘Attribute Assign Line = Assign 1’ then shade all cells in that row #808080
but if the ‘Attribute Service = 1600’ always shade that cell #7A5776
Config file includes
Style Assign Line Assign 1 = background-color:#808080
Cell Style Service 1600 = background-color:#7A5776
The result is the row gets shaded #808080 if ‘Assign Line = Assign Line 1’ but fails to shade the Service cell colour #7A5776 if it equals 1600
Extract from HTML source for the ‘1600’ cell when both conditions are correct shows both background-color values are present and the cell is styled the first value listed (which is Style Assign Line Assign 1 = background-color:#808080 but I always want #7A5776 for cell Service when it is of value 1600)
.
<td class="list2" style="background-color:#808080" style="background-color:#7A5776"><a href="../Daily/1">1600</a></td>
Thank you,
David |
67349
|
Tue Oct 2 21:58:20 2012 |
| David Chastain | David_Chastain@sra.com | Question | Linux | 2.9.1 | Importing XML | I was wondering if anyone out there has had any success with importing XML data into ELOG. Using the XML schema which I derive from the EXPORT data from ELOG into XML format or creating the file from scratch, I either blowup the system and have to restart elogd or it doesn't work and says, XML file doesn't contain ELOG_LIST element (which I create and it still doesn't work).
Basically, I am trying to take spreadsheet data, convert it into XML and upload it as a logbook so I don't have to perform lots of data entry. I also tried .CSV but have had no luck.
Any thoughts or ideas? |
1057
|
Wed Apr 6 01:51:42 2005 |
| David Brody | dbrody@echo-inc.com | Question | Windows | 2.5.8.2 | Conditional Attributes/Preset Text | I upgraded from ver 2.5.5-2 to 2.5.8-2 and found that none of my preset text
worked any longer. I struggled with it for several hours and then reverted
back to 2.5.5-2 and the preset text worked again. I have attached my
elgd.cfg file for review. Thanks in advance for your help... |
1063
|
Thu Apr 7 00:51:05 2005 |
| David Brody | dbrody@echo-inc.com | Question | Windows | 2.5.8.2 | Re: Conditional Attributes/Preset Text | > > I upgraded from ver 2.5.5-2 to 2.5.8-2 and found that none of my preset text
> > worked any longer. I struggled with it for several hours and then reverted
> > back to 2.5.5-2 and the preset text worked again. I have attached my
> > elgd.cfg file for review. Thanks in advance for your help...
>
> Your config file really helped. You found a bug which happens only if one uses
> conditions with lowercase letters, so that's why nobody else saw it before. I
> fixed it and released V2.5.8-3
Thanks for the information.
ELOG is terrific! |
1579
|
Tue Jan 10 00:32:19 2006 |
| David Brody | dbrody@echo-inc.com | Question | | 2.5.8-2 | Date imports from CSV incorrectly | When I import from a CSV file, dates formatted as mm/dd/yy always get imported as 12/31/1969
Here are the parameters I am using for dates:
Attributes = Ticket #, Status, Assigned To, Status Date, Install Date, Category, Activity, Environment, Component, TstTrk
Type Status Date = date
Type Install Date = date
Date format = %A, %d %B, %Y
Preset Status Date = $date
Thanks!
DB |
1581
|
Tue Jan 10 19:30:09 2006 |
| David Brody | dbrody@echo-inc.com | Question | | 2.5.8-2 | Re: Date imports from CSV incorrectly |
David Brody wrote: | When I import from a CSV file, dates formatted as mm/dd/yy always get imported as 12/31/1969
Here are the parameters I am using for dates:
Attributes = Ticket #, Status, Assigned To, Status Date, Install Date, Category, Activity, Environment, Component, TstTrk
Type Status Date = date
Type Install Date = date
Date format = %A, %d %B, %Y
Preset Status Date = $date
Thanks!
DB |
Never mind. I figured it out! |
423
|
Thu Aug 7 15:21:40 2003 |
| David | benutzersupport@bkitech.de | Question | Windows | 2.38 (?) | email Notification | Good day! I´m a german guy so my english is not the best sorry for this...
I have my Elog completely configured now have I still another problem I
would like with a new entry a E-Mail address to select to be able itself
where the again provided entry am then hang-sent can me there someone
help? already the whole has after forum answers scanned. Thanks David |
|