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: 65817     Entry time: Wed Apr 9 14:41:12 2008     Reply to this: 65819
Icon: Warning  Author: Yoshio Imai  Author Email:  
Category: Bug report  OS: Linux  ELOG Version: 2.7.3-2072 
Subject: Problems with elog client 

Hi!

 

Since our upgrade to elog 2.7.3, it is not possible any more to edit an existing elog entry using the elog client with -e <id> option. The only console output is "Error transmitting message". Submitting an entry via the client is not problem.

Running the server with -v option does not yield any output at the time of the edit attempt. Running the client with -v option also doesn't help, because whatever the other options, only the help page is printed out and nothing else done. Btw, there is now a conflict between -s for "use SSL" and -s for the "subdir" option.

 

Any ideas?

 

Yoshio

ELOG V3.1.5-2eba886