I just had a look in the password file and found ...

 <full_name>Mark Campbell</full_name>

    <last_logout>Tue Oct 22 10:56:27 2013</last_logout>

    <last_activity>Wed Nov  6 01:17:08 2013</last_activity>

    <inactive>0</inactive>

 Yah! It's working again ...

I found out I was still logged on to one workstation, I logged off from there, waited a few hours and tried again. All good.

Regards Mark

We recently installed ELOG and it works pretty well, but the load times are rather inconsistent. Most of the time 
it is very fast, but it also often hangs for around 5-10 seconds while loading. It seems to affect all parts of 
the page that are returned at random, so sometimes the main html file will hang, sometimes the css file and 
sometimes the images.

The hardware it is running on is nothing special, an older 3 GHz Celeron, but it should be fast enough. It is 
running on Debian 7. 

Any ideas what the problem could be, or how I could investigate it further to find the bottleneck?

> We recently installed ELOG and it works pretty well, but the load times are rather inconsistent. Most of the time 
> it is very fast, but it also often hangs for around 5-10 seconds while loading. It seems to affect all parts of 
> the page that are returned at random, so sometimes the main html file will hang, sometimes the css file and 
> sometimes the images.
> 
> The hardware it is running on is nothing special, an older 3 GHz Celeron, but it should be fast enough. It is 
> running on Debian 7. 
> 
> Any ideas what the problem could be, or how I could investigate it further to find the bottleneck?

I'm not an expert in debugging web applications. Here are my two cent:
We once had a problem when we hosted very large logbooks (several 10 thousands of entries) that the server would run
out of real memory and was slowed down by swapping. Therefore my first idea would be to monitor the server: Is
the CPU load peaking? What happens with the memory consumption? Any other suspicious process running on the server?
But it could be as well a network or browser problem. Did you try different browsers?
Did you check the elogd log file?

> I'm not an expert in debugging web applications. Here are my two cent:
> We once had a problem when we hosted very large logbooks (several 10 thousands of entries) that the server would run
> out of real memory and was slowed down by swapping. Therefore my first idea would be to monitor the server: Is
> the CPU load peaking? What happens with the memory consumption? Any other suspicious process running on the server?
> But it could be as well a network or browser problem. Did you try different browsers?
> Did you check the elogd log file?

The logbook only has a few hundred entries, elogd is using only around 20-30 MB and there is enough free RAM. The load 
average for the server is around 0.2, elogd only uses 5% CPU at most when it is accessed and the CPU is idle most of the 
time. 

Strangely it happens mostly when using Chrome, and almost never with Firefox. I captured the network traffic, but I can't 
see anything unusual. It just takes very long until the answer is returned by the elogd server.

> > I'm not an expert in debugging web applications. Here are my two cent:
> > We once had a problem when we hosted very large logbooks (several 10 thousands of entries) that the server would run
> > out of real memory and was slowed down by swapping. Therefore my first idea would be to monitor the server: Is
> > the CPU load peaking? What happens with the memory consumption? Any other suspicious process running on the server?
> > But it could be as well a network or browser problem. Did you try different browsers?
> > Did you check the elogd log file?
> 
> The logbook only has a few hundred entries, elogd is using only around 20-30 MB and there is enough free RAM. The load 
> average for the server is around 0.2, elogd only uses 5% CPU at most when it is accessed and the CPU is idle most of the 
> time. 
> 
> Strangely it happens mostly when using Chrome, and almost never with Firefox. I captured the network traffic, but I can't 
> see anything unusual. It just takes very long until the answer is returned by the elogd server.

My tuppance worth.  I have noticed (firefox) that some attachments take rather longer than might be expected to upload.  I
originally thought this was the ghostview program processing say a pdf to make pngs etc, but have more recently started to
question that assumption.  No solution or much clue, just another observation.

Hi noob question I was looking for a config but i cant make it, how to i make multitab logbook like this page?

Like in Discussion there are forum,config examples,contribution and vulnerabilities under it

Thanks

 NVM found it Thanks