Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 274 of 808  Not logged in ELOG logo
    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 
But this is real progress! Now elog successfully connected, and all your data was transmitted, but elogd refused your content.

A possible explanation is that one required attribute of this logbook was not provided in your elog command, or that one value of an
attribute does not match any allowed value for that attribute.
    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 
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.
    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 
Ok, you Apache listes on two ports. On port 80 with HTTP and on port 443 with HTTPS. If you connect to port 80, there is no fowarding to elogd, that's
why Apach complains 

The requested URL /LogBook/ was not found on this server.
    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 
Thanks for the comments. I will pass them to the admins. 

 




Stefan
    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 
With curl, I get this as part of the output:

<table class="dlgframe" width="50%" cellpadding="1"
cellspacing="0"<tr><td class="errormsg">Error: Command "<b>Submit</b>" not allowed</td></tr>

Hopefully
    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 
That reply indicates that the login was not successful. So something went wrong with the authentication. You can try to switch off passwords to see if
that makes a difference.




Jose
    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 
Have you tried to connect directly to elogd and not going through Apache? 




Jose
Caballero wrote:



Thanks for the comments. I will pass them to the admins. 
    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 
Nope. How? Is it documented? 




Stefan
Ritt wrote:



Have you tried to connect directly to elogd and not going through Apache? 
ELOG V3.1.5-3fb85fa6