Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 771 of 796  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6361 Entries 
Goto page Previous  1, 2, 3 ... 770, 771, 772 ... 794, 795, 796   Next  
ID Date Icon Author Author Emailup Category OS ELOG Version Subject
  69075   Fri Dec 6 15:40:19 2019 Reply David Walliswallis@aps.anl.govQuestionLinuxV3.1.3Re: Change column width in list mode?

Awesome, thank you!

Stefan Ritt wrote:

You need

.listframe td:nth-child(3) {
   min-width: 250px;
}

/Stefan

David Wallis wrote:

In some of our logbooks, some columns are very narrow, which makes their content difficult to read. I have tried adding a custom css file like this:

listframe td:nth-child(3) {
   width: 250px;
}

But I find that the column width does not change. I have verified via element inspection that the width attribute is active on the correct column (td).

Am I doing someting wrong, or is this not possible?

 

 

  69237   Tue Oct 20 15:08:17 2020 Question David Walliswallis@aps.anl.govQuestionLinuxELOG V3.1.4-ba8From command line: "command Submit not allowed"

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"

  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"

 

  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"

 

 

 

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

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"

 

 

 

 

  69247   Wed Oct 21 15:14:13 2020 Reply David Walliswallis@aps.anl.govQuestionLinuxELOG V3.1.4-ba8Re: From command line: "command Submit not allowed"

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 file-based days, with passwords, that match the AD usernames. I'm wondering if elogd is trying to use the password in the password file, rather than via PAM. I don't remember the old passwords, so I can't check, and I've run into problems trying to change the passwords. I'm wondering if there's a way to generate a new password from the command line, that would allow me to test the theory.

David Dunne wrote:

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"

 

 

 

 

 

 

  69251   Tue Oct 27 16:00:03 2020 Question David Walliswallis@aps.anl.govQuestionLinuxV3.1.4-ba84827Create entry from command line - override Date?

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?

  69253   Tue Oct 27 16:37:07 2020 Reply David Walliswallis@aps.anl.govQuestionLinuxV3.1.4-ba84827Re: Create entry from command line - override Date?

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
 

 

Goto page Previous  1, 2, 3 ... 770, 771, 772 ... 794, 795, 796   Next  
ELOG V3.1.5-fe60aaf