I grant that this may be a complete red herring, but your description below  - not available and having to reboot - 
might have another explanation.  At least in Linux.

I have found that if you have a broken thread, and you try to access that thread, the daemon goes into an endless
loop and
I could not kill off the daemon by normal means, but had to reboot the computer.  The daemon cannot cope with not
finding 
an entry where one is referenced by a subsequent (or previous, I assume) entry.

A broken thread can occur if you move a thread with a large number of subsequent entries - more than say 50 (I
don't know 
the precise number) from one log book to another.  The copy part of the move works, but the deleting of the entries
in the 
original log book is incomplete, leaving an orphan set of (later) entires.  Access those, and it's time for a
reboot.  Which makes 
finding them a potentially tedius and multiple rebooting exercise.  I know, because I've had to track a number in
my time.

Just a thought.

David.


> We have reduced entries for Search reasons by removing older text files and that seems to speed up things. 
> However, a recurring problem persists during peak period where the service connection is lost (site says "Not 
> found" on both client and directly on server), and it cannot be restarted or killed. Only a reboot of the 2010 
> x64 virtual server will make it available again. 
> 
> Any further info or details I can provide please advise. Thank you Stefan.

Being not able to kill a server running in an endless loop seems strange to me. If you put any program artificially into an endless loop, you can kill it via "kill -9 <pid>". Have you tried that? The only exception I 
can imagine is if there is a problem in the file system, like your elog logbooks are mounted via NFS or some other remote filesystem, and you have a problem there. Since the process might be stuck in kernel 
mode, you cannot kill it. That's why I have all my servers running on local file systems. Just another thought.

/Stefan

You need the netdb.h header file to compile elog. I see that you compile under Windows. You have to make sure that your compiler installation comes with all header files. The netdb.h file is usually in /usr/include under Unix.

Welp, nevermind, I dug a little more and managed to compile it on 14.1 using cmake.

The detection in elogd works by executing the command "convert" and check if the program executes. If you start elogd as a service, the program might see another path variable. Maybe reboot Windows or start the service in the environment of a real user instead of system, where it might miss your modified "path".

Stefan

Ok. It take me a while, but I reinstalled ImageMagick with marked option "convert". Now, when I start elog, it can see ImageMagick, but screenshots attached to elog entries are still in original sizes. And, I don't see buttons for rotating, resizing images. 

I look into elog cfg options, but only what I found is Thumbnail size which, it looks, don't work.

Don't know what more I should check. 

Daniel.

Hi,

Maybe the post is outdated already, but I want to share my experience anyway. I faced the same problem as Daniel: The most recent ImageMagick package was not detected by elogd even though it was installed. I could trace back the problem to the following issue:

Stefan mentioned that the ImageMagick software is detected via the 'convert' command. Since ImageMagick V7, however, the 'convert' command is no longer supported. So, when installing ImageMagick V6 the detection works.

@Stefan: Maybe you could adapt the software detection at some point? Thanks.

Christian

Update:

While the image scaling via ImageMagick works when running elog manually it doesn't when running elog as a service. The service is hosted in the same user environment that allows image scaling with elog started manually. What else could go wrong?

Christian