Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   Problems with elog client, posted by Yoshio Imai on Wed Apr 9 14:41:12 2008 
    icon2.gif   Re: Problems with elog client, posted by Stefan Ritt on Wed Apr 9 23:03:53 2008 
       icon2.gif   Re: Problems with elog client, posted by Yoshio Imai on Thu Apr 10 14:21:13 2008 
          icon2.gif   Re: Problems with elog client, posted by Stefan Ritt on Thu Apr 10 15:39:26 2008 
             icon14.gif   Re: Problems with elog client, posted by Yoshio Imai on Thu Apr 10 15:56:12 2008 
          icon2.gif   Re: Problems with elog client, posted by Stefan Ritt on Tue Apr 15 20:34:49 2008 
             icon2.gif   Re: Problems with elog client, posted by Yoshio Imai on Thu Apr 17 19:11:36 2008 
                icon2.gif   Re: Problems with elog client, posted by Stefan Ritt on Thu Apr 17 21:23:06 2008 
                   icon14.gif   Re: Problems with elog client, posted by Yoshio Imai on Fri Apr 18 14:17:52 2008 
Message ID: 65822     Entry time: Thu Apr 10 14:21:13 2008     In reply to: 65819     Reply to this: 65823   65831
Icon: Reply  Author: Yoshio Imai  Author Email:  
Category: Bug report  OS: Linux  ELOG Version: 2.7.3-2099 
Subject: Re: Problems with elog client 
I have tried the new revision, recompiling both client and server.
Unfortunately, the overall situation has not changed. We can still create new entries using the elog client, but editing an existing entry still does not work. However, thanks to your patch, the -v option now works again for the client side:
> elog -s -h <elog server> -p 443 -l current -u <user> <password> -a <Attributes> "TEST ENTRY"
Message successfully transmitted, ID=1

> elog -s -h <elog server> -p 443 -l current -u <user> <password> -e 1 "EDIT THIS ENTRY" -v
Successfully connected to host <elog server>, port 443
Request sent to host:
GET /current/1?cmd=download HTTP/1.0
User-Agent: ELOG
Cookie: unm=<user>;upwd=<password>;


Response received:
ET
Error transmitting message
Again, there is no output on the server side even when running with -v in console mode. There is the expected output when an entry is successfully created using the elog client. One aspect about this output is strange, though: the "Return" statement
==== Return ================================
HTTP/1.1 302 Found
contains the wrong "Location" header. It is not
Location: https://elog-server.domainname/logbook/ID
but rather
Location: https://client-host.domainname/logbook/ID
where "client-host" is the hostname of the computer where the elog client was called. But, since the logbook entry is correctly created, this is perhaps not a problem at all.



Another thing: I have noticed that when using conditional preset texts, the "Preset Text =" statements have to be declared for each logbook of a logbook group; it is not sufficient to only declare it in the "[global]" section of the logbook group. This means that we only need to declare the conditions once, e.g.
Options Category = .... , Shift {1} , ....
{1} Options Subject = Shift start {a}, Shift end {b}, ....

but the preset text declarations
{1&a} Preset text = shift_checklist.txt
{1&b} Preset text = shift_summary.txt
have to be declared in every individual logbook section for the logbooks of this group. Is this expected behaviour, or a bug?

Cheers

Yoshio
ELOG V3.1.5-3fb85fa6