Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Tue Dec 7 14:46:16 2021
|
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 |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 7 15:09:36 2021
|
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 |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Tue Dec 7 17:50:37 2021
|
The reply from the server
Response received:
HTTP/1.1 404 Not Found |
|
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. |
|
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. |
|
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. |
|
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 |
|
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 |