Re: Undesirable TAG { }, posted by Alex H on Tue Nov 22 11:35:56 2005
|
[quote="Stefan Ritt"]That problem was fixed on June 24th, 2005. So please upgrade to the current 2.6.0-beta5 version.[/quote]
Updated ! Thanks |
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Wed Dec 1 13:05:14 2021
|
Please issue the elog command with an added "-v" flag and post the output here.
Stefan
Jose |
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 7 08:28:19 2021
|
Hi Stefan,
Here is the, I believe, relevant part of the output:
------------------------------------------------- |
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Tue Dec 7 11:56:37 2021
|
If you need HTTPS then you must specify the "-s" option.
You could have looked into the help of the elog command:
> elog -h |
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 7 14:25:37 2021
|
This is what I get with -s:
---------------------------------
Successfully connected to host elog-1.matrix.com, port 80 |
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 |