Hi Stefan,

This has happened twice on this forum now, starting from Mon 23rd November.

Someone submits an entry (Me, 66625, Bertram Metz 66628)
I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
yourself.  My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.

Is this a bug, or some wierd affect of us forgetting to log out?

Regards,

David.

> Hi Stefan,
> 
> This has happened twice on this forum now, starting from Mon 23rd November.
> 
> Someone submits an entry (Me, 66625, Bertram Metz 66628)
> I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
> yourself.  My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.
> 
> Is this a bug, or some wierd affect of us forgetting to log out?
> 
> Regards,
> 
> David.

Thanks for pointing out this issue. This bug was introduced recently, when I tried to avoid the

Re: Re: Re: ...

in the subject line. I changed this now completely so that we can have

Preset on reply Author = $full_name
Preset on first reply Subject = Re: $Subject

which fixes both things. The modification is in revision 2271.

> > Hi Stefan,
> > 
> > This has happened twice on this forum now, starting from Mon 23rd November.
> > 
> > Someone submits an entry (Me, 66625, Bertram Metz 66628)
> > I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
> > yourself.  My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.
> > 
> > Is this a bug, or some wierd affect of us forgetting to log out?
> > 
> > Regards,
> > 
> > David.
> 
> Thanks for pointing out this issue. This bug was introduced recently, when I tried to avoid the
> 
> Re: Re: Re: ...
> 
> in the subject line. I changed this now completely so that we can have
> 
> Preset on reply Author = $full_name
> Preset on first reply Subject = Re: $Subject
> 
> which fixes both things. The modification is in revision 2271.

Thanks Stefan!

We are trying to track down an issue where elogd just stops, and I cannot seem to find a cause.

In the logs, I see:
Dec  3 14:01:23 nissrv18a kernel: [419738.139675] elogd[32003]: segfault at 4 ip 00007f183b19b560 sp 00007fff79f5e278 error 4
in libc-2.10.1.so[7f183b119000+166000]
 

Any thoughts?

 I need more information about that. Please have a look at Faq #19.

Grrr.  Forgetting to pick an icon means my message was blasted.

I have installed elog 2.7.8 and it is running.  When I connect to it and get a login window, I am always denied.  If I remove the passwords, then I can login with no password information.  I have tried both command line for setting passwords and directly in the elogd.cfg file.

Suggestions on what I might be doing wrong would be appreciated.

Regards,

Ian

PS - are there RESTful interfaces to automate the generation of log entries via an HTTP POST or HTTP GET?

Which password scheme are you using? Is it Read passoword = ... or Password file = ...? If you use a password file (that's what most people do) you have to create yourself an account just as you did for this forum here. There is no other way to enter the encrypted password into the password file. Just follow "To start a new password file..." in the documentation.

I am in the process of setting up a new ELOG logbook.  I checked out rev2280 from svn.savannah.psi.ch.  I knew I wanted to encrypt passwords, so when I compiled, I used flags

USE_SSL=1

and

USE_CRYPT=1

I am running Red Hat enterprise linux 3, glibc-devel-2.3.2-95.50, openssl-devel-0.9.7a-33.25

Everything seemed to be working fine--I was able to set up logbooks using both a password file as well as write passwords and make entries to the logs.  Then I tried to use the command line 'elog' to make an entry which failed to both logbooks.

/opt/elog/pro/elogd -c /opt/elog/pro/dansce_fancy.cfg -l Demo1 -w <mypassword>

Would change the password in dansce_fancy.cfg and I could make entries through the web interface, but

elog -h acouture -s -p 8081 -w <mypassword> -l Demo1 -a Author="Aaron Couture" -a Type=Routine  -m Sampleinfo.txt -x -n 1

failed with

Error: Invalid user name or password

I got the same behaviour when I used a logbook with a user/password pair defined in a password file.

When I looked at the output from running elogd with the -v flag, I could see that everything was being received on the server side, but that the password did not agree with the write password in dansce_fancy.cfg

I then recompiled elog with

USE_SSL=1

USE_CRYPT=

And then the elog command line entries worked, both with write passwords and a password file (after recreating the password file and the write password).  Looking at the elog.c source code, it appears that it does not know to use crypt rather then base64_encode when USE_CRYPT is true.  elogd.c defined different behaviour if USE_CRYPT is defined.

Thanks,

Aaron Couture