Any known issues running in Win Server 2008 R2, 64 bit environment? We sometimes lose connection with the Elog app (ssl) and wonder if due to 64bit or other factor in this set up. A forum search does not explicitly reveal any clues however I did find an entry from someone posting a similar question without a response yet (#67061).

Anyone using elog on FreeBSD nowadays?  I know it used to be in the ports tree about 10 years ago but seems to be abandoned.  Tried to compile from source on 14.1, but no luck there.

Hello.

I finally try add ImageMagick to ELOG.

I downloaded latest version (ImageMagick-7.0.3-Q16) and installed it. Everything looks ok, but when I start Elog service it says that "ImageMagick not detected". 

When I look at the "path" variable i have "C:\Program Files\ImageMagick-7.0.3-Q16;C:\ProgramData\Oracle\Java\javapath;[...]".

What else can I check?

Regards

Daniel.

Ps. My system is Windows 7 Pro. 

Hi,

is it possible to change the name ELOG from all HTML titles.

E.g. find/search. If you click on find/search the browser/html tag/title is 'ELOG search'. Is it possible to change this to 'xxx search' and how.

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)