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 |
|
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 |
|
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. |
|
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? |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Fri Dec 10 21:41:05 2021
|
It is the default. If you install ELOG on your PC and run it, then every access will be directly to the ELOG web service. If you want to have Apache
inbetween, it is some extra effort.
Jose |
Log4j exploit, posted by Alan Grant on Tue Dec 14 19:16:57 2021
|
Is there any potential impact/concern with the Log4j exploit in Elog applications?
|