Hi Stefan,

There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time".  I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results.  And it gets annoying that the default default is "Day", the number of times I've forgotten...

I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick. 

Email Downtime Yes = user1@xyz.com, user2@xyz.com

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

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.

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.

By desing, there is no collision between different users, since all requests are executed in sequence (single thread). The only problem is that the server becomes unavailable for others if it executes a long search. This is why most users of large lobooks restrict their search to let's say the last month or so by default. This speeds up the search and limits the dead time for others. This can be done via the show last default = <days> directive.