Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Wed Dec 1 12:37:57 2021 
    icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Wed Dec 1 13:05:14 2021 
       icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 7 08:28:19 2021 
          icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Tue Dec 7 11:56:37 2021 
             icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 7 14:25:37 2021 
                icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Tue Dec 7 14:46:16 2021 
                   icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 7 15:09:36 2021 
                      icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Tue Dec 7 17:50:37 2021 
                         icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Wed Dec 8 10:49:20 2021 
                      icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Tue Dec 7 18:24:42 2021 
                         icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Wed Dec 8 10:59:58 2021 
                            icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Wed Dec 8 11:23:48 2021 
                               icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Wed Dec 8 12:05:43 2021 
                                  icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Wed Dec 8 13:19:55 2021 
                               icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Thu Dec 9 10:33:09 2021 
                                  icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Thu Dec 9 21:58:08 2021 
                                     icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Fri Dec 10 21:41:05 2021 
                                        icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 14 21:42:45 2021 
                                           icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Thu Dec 16 18:24:41 2021 
                                              icon2.gif   Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Thu Dec 16 21:34:05 2021 
Message ID: 69436     Entry time: Wed Dec 8 10:49:20 2021     In reply to: 69434
Icon: Reply  Author: Jose Caballero  Author Email: jcaballero.hep@gmail.com 
Category: Question  OS: Linux  ELOG Version: 3.1.4 
Subject: Re: Unclear how to use the command line tool /usr/bin/elog 

I don't see anything in httpd logs.

I am just reusing an entry I created via web, so the attributes are correct. Nothing is missing, correct spelling, etc.  I keep trying. 

BTW, I have just realized that the output of "elog -h" does not "man log", which is the one I have been using so far. Which one is correct? 

 

Stefan Ritt wrote:

The reply from the server

Response received:
HTTP/1.1 404 Not Found
Date: Tue, 07 Dec 2021 07:26:07 GMT
Server: Apache/2.4.6 (Scientific Linux) OpenSSL/1.0.2k-fips PHP/5.4.16
Content-Length: 204
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /LogBook/ was not found on this server.</p>
</body></html>

comes definitively from the Apache browser (See the "Server" line). So apparently it does not succeed in forwarding your request to the elogd server. Look into the Apache log and see what's wrong there.

Jose Caballero wrote:

Not really. The full URL in the browser is https://elog-1.matrix.com/LogBook. That's why I am trying with "-h elog-1.matrix.com -l LogBook"

I have just tried with -p, here is the full output:

[root@elog-1 ~]# /usr/bin/elog -h elog-1.matrix.com -p 443 -v -x -l LogBook -u jcaballero xxxx -a Team='Team Name' -a Category='Category Name' -a 'Affected service'='Affected Service' -a Criticality=Normal -a 'Oncall Documentation'='No modifications required' -a Subject='This is a test, ignore me' 'This is a test, ignore me'
Successfully connected to host elog-1.matrix.com, port 443
Request sent to host:
POST /Tier1/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------462A01443E24BC6541C5BB72
Host: elog1.matrix.com:443
User-Agent: ELOG
Content-Length: 1610


Content sent to host:
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="cmd"

Submit
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="unm"

jcaballero
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="upwd"

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="exp"

LogBook
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="suppress"

1
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="encoding"

ELCode
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="Team"

Team Name
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="Category"

Category Name
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="Affected_service"

Affected Service
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="Criticality"

Normal
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="Oncall_Documentation"

No modifications required
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="Subject"

This is a test, ignore me
---------------------------462A01443E24BC6541C5BB72
Content-Disposition: form-data; name="Text"

This is a test, ignore me
---------------------------462A01443E24BC6541C5BB72

Response received:

Error transmitting message

 

 

Stefan Ritt wrote:

If you use HTTPS, you have to connect to port 443 of your server, using the "-p" option.

Furthermore, you run under an Apache server, right? How do you do the redirecting to elogd? I guess you specified a subdir in the URL named /LogBook to redirect to elogd. The you use another part of the URL to select the logbook, which again might be "LogBook". Is that correct? So your full URL in the browser would be https://elog-1.matrix.com/LogBook/LogBook. If that's the case, you have to tell the elog tool that you use a subdir in the URL using the "-d" option.

Stefan

Jose Caballero wrote:

This is what I get with -s:

---------------------------------

Successfully connected to host elog-1.matrix.com, port 80
elogd server does not run SSL protocol

---------------------------------

And the entry has not been created. 

 

Andreas Luedeke wrote:

If you need HTTPS then you must specify the "-s" option.

You could have looked into the help of the elog command:

> elog -h
elogd 3.1.4 built Jun 14 2021, 18:01:54 revision 611489b
usage: elog
elog -h <hostname> [-p port] [-d subdir]
                              Location where elogd is running
     -l logbook/experiment    Name of logbook or experiment
     -s                       Use SSL for communication
     [-v]                     For verbose output
     [-u username password]   User name and password
     [-f <attachment>]        (up to 50 attachments)
     -a <attribute>=<value>   (up to 50 attributes)
     [-r <id>]                Reply to existing message
     [-q]                     Quote original text on reply
     [-e <id>]                Edit existing message
     [-w <id>|last]           Download existing message (last message)
     [-x]                     Suppress email notification
     [-n 0|1|2]               Encoding: 0:ELcode,1:plain,2:HTML
     -m <textfile>] | <text>
Arguments with blanks must be enclosed in quotes
The elog message can either be submitted on the command line, piped in like
"cat text | elog -h ... -l ... -a ..." or in a file with the -m flag.
Multiple attributes and attachments can be supplied

 
Jose Caballero wrote:

Hi Stefan,

Here is the, I believe, relevant part of the output:

-------------------------------------------------

Response received:
HTTP/1.1 404 Not Found
Date: Tue, 07 Dec 2021 07:26:07 GMT
Server: Apache/2.4.6 (Scientific Linux) OpenSSL/1.0.2k-fips PHP/5.4.16
Content-Length: 204
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /LogBook/ was not found on this server.</p>
</body></html>

-------------------------------------------------

Note that the URL https://elog-1.matrix.com/LogBook/ exists and works. That's how we create all our log entries via web browser. 

 

Thanks,

Jose

 

Stefan Ritt wrote:

Please issue the elog command with an added "-v" flag and post the output here.

Stefan

Jose Caballero wrote:

Hello,

 

I am trying first time to use the tool /usr/bin/elog. From the documentation is not clear to if everything must be in quotes or not, if every attribute requires -a.

Here is how my attempt looks like (changing actual data by fake one):

      /usr/bin/elog -h elog-1.matrix.com -l LogBook -u jcaballero mypassword -a Team='Team Name Here' Category='Category Here' -a 'Affected service'='Name of affected service here' -a Criticality=Normal -a 'Oncall Documentation'='No modifications required' -a Subject='here is the subject line' 'here is the text'

I just get "Error transmitting message". 

Attributes Team and Category are of checkbox type. Attributes Criticality and Oncall Documentation are of radio type.

What is wrong with my command attempt?

 

Thanks a lot in advance.

Cheers,

Jose

 

 

 

 

 

 

 

 

 

 

 

ELOG V3.1.4-bcd7b50