After patching a windows 7 computer with MS12-006, can no longer connect to elog, get page cannot be displayed

See

http://support.microsoft.com/kb/2643584

Hi there, I just compiled and installed elog on a machine running the newest Ubuntu server. Everything went fine - no problems. Running elog on it's own (no apache).  I moved over a bunch of logbooks from an older elog, which seemed to work. Now, elog seems to crash when people are uploading files. Here is a snip from my syslog, and you can see each time it crashes with "error 4."

Jul 16 14:02:45 GrattaLab3old elogd[4526]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 14:02:45 GrattaLab3old elogd[4526]: revision 2111
Jul 16 14:02:45 GrattaLab3old elogd[4526]: FCKedit detected
Jul 16 14:02:45 GrattaLab3old elogd[4526]: ImageMagick detected
Jul 16 14:02:45 GrattaLab3old elogd[4526]: Server listening on port 8080 ...
Jul 16 16:02:42 GrattaLab3old kernel: [10631.276626] elogd[4526]: segfault at b4466000 eip 080adf19 esp bfa281d0 error 4
Jul 16 16:05:24 GrattaLab3old elogd[5509]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 16:05:24 GrattaLab3old elogd[5509]: revision 2111
Jul 16 16:05:24 GrattaLab3old elogd[5509]: FCKedit detected
Jul 16 16:05:24 GrattaLab3old elogd[5509]: ImageMagick detected
Jul 16 16:05:35 GrattaLab3old elogd[5509]: Server listening on port 8080 ...
Jul 16 16:06:06 GrattaLab3old kernel: [10834.637427] elogd[5509]: segfault at 091d7000 eip 080adf19 esp bfc313f0 error 4
Jul 16 16:07:10 GrattaLab3old elogd[5517]: elogd 2.7.4 built Jul 15 2008, 18:44:44
Jul 16 16:07:10 GrattaLab3old elogd[5517]: revision 2111
Jul 16 16:07:10 GrattaLab3old elogd[5517]: FCKedit detected
Jul 16 16:07:10 GrattaLab3old elogd[5517]: ImageMagick detected
Jul 16 16:07:10 GrattaLab3old elogd[5517]: Server listening on port 8080 ...
Jul 16 16:07:49 GrattaLab3old kernel: [10937.923301] elogd[5517]: segfault at b7c0d000 eip 080adf19 esp bffc1780 error 4

I run elog as:

Usr = elog

Grp = elog

/usr/local/sbin/elog -p 8080 -c /usr/local/elog/elogd_exo.cfg -D

where elogd_exo is my config file. Nothing special in my config file.

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? 
 

I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:

16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)

Some user wanted to modify the URL by hand and succeeded to crash the elogd process with npp=now
It appears that npp=0 crashes elogd with the following error message:

Program received signal SIGFPE, Arithmetic exception.
0x0808eba2 in show_elog_list (lbs=0xab3c770, past_n=0, last_n=0, page_n=1,
    default_page=1, info=0x0) at src/elogd.c:20214
20214            sprintf(str + strlen(str), loc("Page %d of %d"), page_n, (n_msg - 1) / n_page + 1);

I guess this bug is not OS dependent: you can crash every logbook that you can search ;-)

I'm trying to use the command line to post automatically entries from a web based calendar. I run elogd behind SSL with user/pass configuration. I created an account for the calendar and used the following command line.

[gornea@lheppc63 ~]
$ elog -v -s -a Subject=Test -a Type=Notice -a Category=Planning -h svn.lhep.unibe.ch -p 443 -l "LHEP EXO General" -u calendar ******** "SORRY for SPAMMING! Testing automated posts from command line"

It seems like all parameters are OK but for some reason the connection gets closed. Anybody has an idea why? The SSL certificate is not valid and on the web page users have first to accept it. Can this explain the problem? Is there a flag for elog command line to instruct it to ignore SSL warnings? Thanks a lot!

Command line output:

Successfully connected to host svn.lhep.unibe.ch, port 443
Request sent to host:
POST /LHEP+EXO+General/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------16B1637A4CDBB4E6448003F4
Host: lheppc63.lhep.unibe.ch
User-Agent: ELOG
Content-Length: 1105


Content sent to host:
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="cmd"

Submit
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="unm"

calendar
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="upwd"

Z28yQjUyIQ==
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="exp"

LHEP EXO General
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="encoding"

ELCode
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Subject"

Test
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Type"

Notice
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Category"

Planning
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Text"

SORRY for SPAMMING! Testing automated posts from command line
---------------------------16B1637A4CDBB4E6448003F4

Response received:
HTTP/1.1 302 Found
Server: ELOG HTTP 2.9.2-2455
Location: https://svn.lhep.unibe.ch/LHEP+EXO+General/
Connection: Close

<html>redir</html>

Message successfully transmitted, ID=
[gornea@lheppc63 ~]
$
 

<p>Hi,</p>

<p>I have a problem running elog command from php script. Basically in the php I call system(&quot;elog -h etc etc.. And from the php command line works but not in the browser apparently without errors (php apache logfile no problem), any suggestions?</p>