Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 292 of 807  Not logged in ELOG logo
    icon14.gif   Re: "Slow script" problem posting/editing from Safari -- browser hangs, times out, posted by Michael Kelsey on Sun Apr 15 08:03:21 2018 
Thank you for your suggestion, Stefan!  The sysadmin who handles our e-Log server implemented your suggestion earlier today (Saturday).  I
have been able to successfully create and modify e-Log entries with Safari since then.  Since the "slow script" issue has been intermittent
in the past, I plan to continue testing and monitoring for the next day or so.  Nevertheless, it appears that removing the waiting loop has alleviated
    icon2.gif   Re: "Slow script" problem posting/editing from Safari -- browser hangs, times out, posted by Stefan Ritt on Mon Apr 16 08:19:16 2018 
Ok, I removed the code from the official code now. 

A bit background: The "autosave" mechanism in elog saves regularly the current content in a "draft" message, so that the
data does not get lost if the browser for example crashes. The saving is done asynchronously via some AJAX call. This call takes some time, since it's
icon4.gif   elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Tue Apr 23 14:06:36 2019 
Dear all.

I am running elog 

elogd 3.1.4 , revision ead6bbc6
    icon2.gif   Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Tue Apr 23 14:26:51 2019 
This kind of behavior we typically see if some elog entry is corrupt. After a few hours you might access this corrupt entry by accident, and then the
server stops. If you see however this behavior on a fresh logbook with no corrupt entries, then the problem must lie somewhere else.

Do you see the same problem running under linux?
    icon2.gif   Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Thu Apr 25 11:16:06 2019 
Thanks for the prompt feedback.

a) I confirm that the problems shows up also when running interactively the elog through  elogd -p 8080

b) I am trying to catch the exit using lldb on the mac machine. I will be able to give you some feedback on that I hope in the next week (not
    icon2.gif   Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Thu Apr 25 11:27:21 2019 
What you recommend is enough. Just make sure to compile elogd with the flags mentioned before, and when you get the segment violation, do a stack trace
inside the debugger to learn where the fault happend. Maybe also print the contents of some variables at the current location.

Stefan
    icon2.gif   Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Tue Apr 30 12:47:46 2019 
I was finally able to catch the crash.

I paste below the info provided by lldb..

It seems that it has something to do with the 'first' logbook that contains 115 entries and is displayed in 6 pages.
    icon2.gif   Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Tue Apr 30 14:07:52 2019 
Actually it is a little bit more difficult than that.

I have restarted elogd and got a crash but this time it seems related to a different logbook...

Below the stack trace..
ELOG V3.1.5-3fb85fa6