Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 194 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown Text Attachments
  68510   Fri Dec 16 09:27:26 2016 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.2Re: elogd crash on sorting the entries by an datetime attributeStill no luck. Tried your URL and still
works fine for me:

 Screen_Shot_2016-12-16_at_9.26.51_.png 
  68511   Fri Dec 16 09:55:20 2016 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.2Re: elogd crash on sorting the entries by an datetime attributeOk I found it!

Was tricky. In my development environment
(XCode) it worked fine. Only when I compiled
  
  68512   Fri Dec 16 14:44:19 2016 Agree Stefano Bonaldostefano.bonaldo.13@gmail.comBug fixMac OSX3.1.2Re: elogd crash on sorting the entries by an datetime attributeBug FIXED! Many thanks Stefan and my warmest
congratulations for the elog project.

Stefano
  
  67931   Fri May 22 13:59:41 2015 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.0Re: elogd complains about unknown cookies> elogd is spewing these messages about unknown
cookies:
  
  67932   Sat May 23 02:49:22 2015 Reply Konstantin Olchanskiolchansk@triumf.caBug reportLinux3.1.0Re: elogd complains about unknown cookies> > elogd is spewing these messages about
unknown cookies:
> > 
  
  68933   Tue Apr 23 14:26:51 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1This kind of behavior we typically see
if some elog entry is corrupt. After a few
hours you might access this corrupt entry
  
  68942   Thu Apr 25 11:16:06 2019 Reply Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1Thanks for the prompt feedback.

a) I confirm that the problems
shows up also when running interactively
  
  68943   Thu Apr 25 11:27:21 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1What you recommend is enough. Just make
sure to compile elogd with the flags mentioned
before, and when you get the segment violation,
  
ELOG V3.1.5-3fb85fa6