Dear Soren,

sorry for the trouble, but it's very hard to diagnose this remotely. This forum here runs fine for many months, so in principle Elog should be stable (at least the current version 2.7.5). If you have an older version, please upgrade. If you have a way to reproduce the problem reliably, you can send me your config file and explain step-by-step how you make Elog crash. Then I can try to reproduce it here. Otherwise the only chance I see is to run elog from inside the debugger, and once it crashes record the stack trace and send it to me. If you don't know how to use the gnu debugger, I'm sure you find someone at CERN who knows. 

Best regards,

   Stefan

Dear Stefan,

Thanks for your reply.

I started running elog in February and it never failed. Then it started failing regularly towards the end of September. There were no system changes until then, except the daily automatic Yum updates (SLC4). Then I upgraded to the latest version (tar ball of 2.7.5). Then yesterday it crashed again. I saw that it crashed around the time when a user was doing something - inputting new data. I can monitor when it crashes and correlate it with user activity. But it is not easy to reproduce since I don't know exactly what the user is typing.

It would be necessary to record the user input forms and then replay them against a known server state. But that is not so easy.

I will think about doing something else - maybe running inside a debugger as you suggest.

i have been using elogbook V2.7.6 on my XP machine for a number of years. I ahve recently upgraded to windows 8 and the reply function on my entries has changed. I can now see the previous entrys in HTML format rather than the reply box which used to appear and also my ability to upload attachments and paste working linls is removed. Do i need to upgrade to the latest version and do i ned to back up my previous entries and how do i do this?

Thank you

I was wondering if anyone would be able to assist me in getting the ImageMagick/figure scaling working on an elog running under windows 11 (Microsoft Windows Version 22H2 (OS Build 22621.3880)).   I've followed the installation instructions and checked that $PATH contains the directory for both ImageMagick and GSS.  In a 'command prompt' window, when I execute "identify -version" from any directory I get the response:

Version: ImageMagick 7.1.1-35 Q16-HDRI x64 d775d2a:20240714 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Channel-masks(64-bit) Cipher DPC HDRI Modules OpenCL OpenMP(2.0)
Delegates (built-in): bzlib cairo flif freetype gslib heic jng jp2 jpeg jxl lcms lqr lzma openexr pangocairo png ps raqm raw rsvg tiff webp xml zip zlib
Compiler: Visual Studio 2022 (194033811)

which I believe is correct.  I've looked through the source-code for the elog and I believe that upon initialisation elogd is looking for a response containing "ImageMagick" somewhere in the response [image_magick_exist = (strstr(str, "ImageMagick") != NULL);] so I'm not sure I understand why this isn't being satisfied.  When I run elogd I get the statement "ImageMagick NOT detected. Image scaling will not work.".

I have the feeling that this is some security restriction in windows 11, so was wondering if anyone had seen this problem before and knew of a solution.

Many Thanks

We are currently having problems with Elog, I never had a problem installing it before but with my last 3 install I can't get it to work. We are running under Windows XP, the installation works perfectly but when I try to use the shortcut pointing to the localhost 8080, I get an error page from Internet Explorer telling me that the server cannot be found. I've rebootied the computer to make sure the server was running but still the same problem. Is there a basic requirement I should look at (Dotnet versionX or specific DLL required)?

No, there is no Dotnet or DLL required. Just start the ELOG server manually by clickin on Start/Programs/ELOG Server/Start ELOG server manually and watch if you can spot any error. One person reported that downloading again the package solved a similar problem.

 Since we updated to 2.7.8 we've found a problem.

Previously, when we used 

Subst on reply subject = Re: $subject