ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67818
|
Sat Feb 28 14:08:43 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | 2.9.2 | Re: Elog stability with multiple users |
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. |
67817
|
Fri Feb 27 23:06:53 2015 |
| Alan Grant | agrant@winnipeg.ca | Question | Windows | 2.9.2 | Re: Elog stability with multiple users |
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. |
67816
|
Thu Feb 26 10:39:58 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.9.2 | Re: Elog stability with multiple users |
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.
Alan Grant wrote: |
Are there any known or reported daemon stability issues with an increase of concurrent users logged in to view and search entries, while the elog client is also adding 5 to 10 new entries every minute during a peak 2-hour period each day?
|
|
67815
|
Wed Feb 25 08:41:59 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | All | 3.0.0 | Re: Enter past date for logbook |
As an administrator of the logbook you could add an additional attribute, e.g. "when" of type datetime.
Each entry would then have the unchangeable entry time and an addtional time, e.g. of the event you are describing in the entry.
For more details look here: elog:67712
Banata Wachid Ridwan wrote: |
Is it possible to enter past date in logbook
I forgot to enter log yesterday, is it possible to add up now?
|
|
67814
|
Wed Feb 25 07:52:21 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.0.0 | Re: Enter past date for logbook |
No. The date/time tag is there to actually document the time when the log was made. If you are late, you are late.
Banata Wachid Ridwan wrote: |
Is it possible to enter past date in logbook
I forgot to enter log yesterday, is it possible to add up now?
|
|
67813
|
Wed Feb 25 03:28:24 2015 |
| Banata Wachid Ridwan | jogjacard@yahoo.com | Question | Windows | 3.0.0 | Enter past date for logbook |
Is it possible to enter past date in logbook
I forgot to enter log yesterday, is it possible to add up now? |
67812
|
Fri Feb 20 16:18:36 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.7.1 | Re: maximum attributes for drop down menu. |
Hi Rob,
I don't think the default number of 100 has ever changed. However, you can change the number in the source
code and recompile. This was discussed in elog:67674
I increased my maximum from 100 to 120 and recompiled. At some point, though, you'll overflow some stack or other, and maybe that's why you've got the limit of 250. You might also want to consider Andreas's alternative (which I am also thinking about).
rob wrote: | We use a servername field to be able to select a server.
When i entered my entire serverlist (574 entries), only 250 of them show up.
Looking at the online documentation about attributes, it is stated that there is a maximum of 100 entries.
With the version we are using (2.7.1) it seems the limit is 250
Can someone tell me if version 3 has the same limitation, or that the max has been increased?
Rob. |
|
67811
|
Fri Feb 20 11:04:03 2015 |
| rob | rob@5db.nl | Question | Linux | 2.7.1 | maximum attributes for drop down menu. |
We use a servername field to be able to select a server.
When i entered my entire serverlist (574 entries), only 250 of them show up.
Looking at the online documentation about attributes, it is stated that there is a maximum of 100 entries.
With the version we are using (2.7.1) it seems the limit is 250
Can someone tell me if version 3 has the same limitation, or that the max has been increased?
Rob. |