Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   Elog crashing at random intervals, posted by Lee Burnside on Sat Jan 28 22:23:46 2017 
    icon2.gif   Re: Elog crashing at random intervals, posted by Lee Burnside on Mon Jan 30 12:03:36 2017 
Message ID: 68554     Entry time: Mon Jan 30 12:03:36 2017     In reply to: 68553
Icon: Reply  Author: Lee Burnside  Author Email: lee.burnside@ttu.edu 
Category: Bug report  OS: Linux  ELOG Version: 3.1.2 
Subject: Re: Elog crashing at random intervals 

Never mind, version from github solved issue.

 

Lee

Lee Burnside wrote:

We're running Elog 3.1.2 om SL 7.2 and keep getting random crashes, sometimes when no one is accessing a logbook. The following is from /var/log/messages with debugging turned on after the latest crash.

Jan 28 12:43:56 archer elogd[9629]: POST /PHYS3305Spring2017/ HTTP/1.1
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "ajs_anonymous_id"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "ajs_user_id"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "ajs_group_id"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "__utma"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "__utmz"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "elc"
Jan 28 12:43:56 archer elogd[9629]: Received unknown cookie "_ga"
Jan 28 12:43:56 archer kernel: elogd[9629]: segfault at 0 ip 000000000042237e sp 00007ffe50fcfdc0 error 4 in elogd[400000+8b000]
Jan 28 12:43:56 archer systemd: elogd.service: main process exited, code=killed, status=11/SEGV
Jan 28 12:43:56 archer systemd: Unit elogd.service entered failed state.
Jan 28 12:43:56 archer systemd: elogd.service failed.

Nothing odd in the logbooks, no real activity happening at the time of any crash. Crashes after any amount of time from 1 hour to 24 hours, with littleAny clues? 
 

 

ELOG V3.1.5-fe60aaf