Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 466 of 808  Not logged in ELOG logo
    icon2.gif   Re: synchronization, posted by lance on Fri Jun 19 09:44:02 2009 

lance wrote:

We are running elog across two sites and synchronizing every four hours on change only. There are about 100 entries per day of which most are just one line entries. However this is taking up to 9 mins and during the replication process the server gives us an "unavailable" error. We are using a T1 across the sites so bandwidth should not be an issue, I am confused as to why this takes so long.

The issue for us is not how long the sync takes, providing this was happening in the background, and doesnt lock out the server while the replication was taking place. We are operating under a 24 hour call center type environment so the server being available all the time is of paramount importance.

We use version 2.7.2 and I know there have been several changes made since this version. Would changing to the latest version have any impact on this?

 

Cheers,

 

Lance

 

Stefan,

I have been running logging and I think I have found the problem however I do not know how to resolve it.

Here is where it is going wrong:

19-May-2009 04:02:48 [] {NSS} MIRROR: ID21268: Local entry submitted

19-May-2009 04:07:34 [] {AMC} MIRROR: send entry #31056

It seems that when it has finished replication on one logbook there is a significant time before the next logbook replication starts. During this time the server is not avalable. I have noticed that the time between ending one logbook and starting the next differs betwee 2 and 5 minutes. Again the server is not available when this happens.

Do you have any idea?

Cheers,

 

Lance

    icon2.gif   Re: synchronization, posted by lance on Fri Jun 26 14:27:27 2009 log_for_stefan.pdfPMCLogfile

Stefan Ritt wrote:

lance wrote:

lance wrote:

We are running elog across two sites and synchronizing every four hours on change only. There are about 100 entries per day of which most are just one line entries. However this is taking up to 9 mins and during the replication process the server gives us an "unavailable" error. We are using a T1 across the sites so bandwidth should not be an issue, I am confused as to why this takes so long.

The issue for us is not how long the sync takes, providing this was happening in the background, and doesnt lock out the server while the replication was taking place. We are operating under a 24 hour call center type environment so the server being available all the time is of paramount importance.

We use version 2.7.2 and I know there have been several changes made since this version. Would changing to the latest version have any impact on this?

 

Cheers,

 

Lance

 

Stefan,

I have been running logging and I think I have found the problem however I do not know how to resolve it.

Here is where it is going wrong:

19-May-2009 04:02:48 [] {NSS} MIRROR: ID21268: Local entry submitted

19-May-2009 04:07:34 [] {AMC} MIRROR: send entry #31056

It seems that when it has finished replication on one logbook there is a significant time before the next logbook replication starts. During this time the server is not avalable. I have noticed that the time between ending one logbook and starting the next differs betwee 2 and 5 minutes. Again the server is not available when this happens.

Do you have any idea?

Cheers,

 

Lance

Hi,

I need more information to narrow down the problem:

- does this only happen on automatic mirroring or also when you do a manual synchronize?

- does this happen on both sides, like when you make the "other" elog server the master?

- if the server is inresponsive, does the CPU on that machine go to 100% or to 0%?

- do you have very long attachments in your logbooks?

- do you have the same problem on a "tiny" logbook like it comes with the distribution?

- are you using any Apache proxy in between?

I'm afraid that in the end you have to debug this yourself, since it will be very hard for me to reproduce exactly your problem (unless you send me all your files). 

Cheers,

  Stefan

Stefan,

Thanks for the reply.

This happens on automatic mirroring and by manual sync. However only the site initializing the mirror is locked out the remote seems to still be able to function.

The CPU jumps from very little usage to 50%+ being used by elogd.exe as soon as you start the mirroring/sync process

I have attached a file that that is in three parts and its pretty big. When I start up the elogd -v it takes over two minutes to scroll through hundreds of  files. I have attached the last of those entries in the first part of the attached PDF, the second part of the PDF shows a manual sync and the third part shows the same sync on the same logbook a few mins later. It seems to take about 3 minutes even when there has been no new log entries. In addition if you are mirroring more that one log book through the automated cron job it can take about 3-5 mins before the second logbook starts its replication. I have also added a screenshot of the completed replications on both runs.

If there is a way to redirect the output of the cmd window when running elogd -v I would capture all the data for you but the standard redirect ">> elog.txt" only creates a blank file.

We are running several logbooks and it does look like the smaller logbooks still take several minutes to start up. I have attached the PMCLogfile and if you look between the NSS and the AMC replications on any day there seems to be a 3 min gap between one book finishing and another starting.

We are not using Apache prox in between.

I am not a programmer but I can follow instruction, if you need anything else let me know.

Stefan this has been driving me nuts for a while now so any help you can give would be more than appreciated.

Cheers,

 

Lance

 

icon5.gif   Elog Crashes, posted by lance on Mon Jul 20 09:26:41 2009 Elog_crash_events.doc
Stefan,
 
Our log is crashing on a regular basis and I have been unable to identify the reason. Now the if the log crashes that is not a major problem however when you try to stop the daemon from the services it fails to stop. This means that the daemon cannot be restarted. The only way then is to start killing processes. This is not something I want none experienced guys to do.
 
Looking at the processes is look like the elogd.exe is still running and doesn’t die when you try to stop the daemon service.
 
I checked the times it was crashing with events in the elog logfiles but there was nothing actually happening at these times. It seems something is causing it to just hang.
 
I have attached the eventlog files for you if you have any ideas I would appreciate them.
 
I have not run the log in verbose mode as I have thus far been unable to redirect the output of the screen in order to see what is happening. If you have any tips on how to redirect the output I would save the file for off line analysis. Our log is used 24/7 therefore it is critical that it be kept running so if I was to run it with the –v option the guys would have to restart it and I would lose the data.
 
Any help is much appreciated
 
 
Regards,
 
Lance
icon5.gif   SQL Database, posted by lance on Thu Sep 2 10:30:14 2010 

We have been running elog for a few years now and its solid. The only thing is we are getting to 140k entries over a few books and its starting to slow down whist searching. My questions is can we go to an SQL type database rather than a flat file? Is it worth it? Is anyone running this type of configuration?

icon1.gif   Does there is a way to no the $message_id when creating a new submission, posted by Lagarde on Thu May 9 13:34:55 2019 

Hello,

I would like to know if it's possible to know the message_id of when creating a new entry in elog ?

I would like to do something like this Preset text = $message_id

Thx;

icon7.gif   Reply not working correct, posted by kyle carpenter on Tue Jul 21 22:29:17 2009 

Hi,

I love this software. I am not a programmer but have learned alot about the program.

I have 2 questions.

1. when i do a reply it will bring the original qutes with it but i have the option to change what had been entered. once i do the reply and reply to the reply i can not change the first reply but can change the second reply. This just started last week and i am not sure what has changed. i even uninstalled and reinstalled. If I try to just the HTML i tcomes up with code? If I do elcode seems to do ok just not able to stop the editing of the the last reply. Plain seems to do the same as ELcode.

2. I have also had trouble with E-Log not starting on my XP machines. Any ideas?

 

Thanks for sharing such a powerful program it is sweet.

Kyle

icon5.gif   Unable to send mails through elog, posted by Kumar on Wed Jun 8 10:45:18 2005 
Hi All

I need to send mail through Elog. With Version 2.5.7 it seems to work only when less content is in the elog entry. But when I fill in a lot of content into one entry, it confirms the mail is sent but I dont receive the mail.

I thought it was a bug in 2.5.7, so I installed the new version 2.6-beta. With this version I am not even able to send any mail eventhough elog confirms it has been sent. Same is it case for 2.5.9.

Please let me know if there is a fix..

Thanks
Raj
icon5.gif   Cloning, posted by Gerfried Kumbartzki on Fri Jun 17 20:30:53 2005 
Elog is installed on a laptop (Redhat Linux 2.4.20-8) for quite a while. I like to have a "base" of that logbook on a server and keep it
in sync. Mirroring seem to be the perfect solution. For that I updated to elog v2.6.0 yesterday.

The server is an Alpha running Linux Redhat 7.1. I compiled from elog-latest.tar and installed elog in the 'same' locations as on the laptop.
Created a user elog and a group elog, put elogd.cfg, themes, logbooks ... in /usr/local/elog, owned by elog. Started the elogd, tested,
all seems to work. The elogd.cfg has a read and write passwd set. Any user can access the logbook, read and write after providing the proper user id and password.
Next I wanted to clone the logbooks from the laptop to the server. As superuser I can start elogd -v -C http://latop:8080, but get stuck right away with "Cannot contact elogd at http://laptop:8080/"
As user it works as follows:

Remote configuration successfully received.

Option "Mirror server = http://wotan.rutgers.edu:8080" added to config file.
Logbook directory "logbooks" successfully created.
Created directory "demo"
Indexing logbook "demo" ... Found empty logbook "demo"
Created directory "tfexp"
Indexing logbook "tfexp" ... Found empty logbook "tfexp"

Retrieve remote logbook entries? [y]/n:

Retrieving entries from "http://wotan.rutgers.edu:8080/demo"...
ID1: Remote entry received

Retrieving entries from "http://wotan.rutgers.edu:8080/tfexp"...
Error accessing remote logbook

Cloning finished. Check elogd.cfg and start the server normally.

Allthough, tfexp contains a number of entries all owned by elog like the entry in demo.
Beside missing the real stuff everything ends up in the users home directory. I would like it in the general area (/usr/local/elog for instance).

The other option is to use synchronize after changing [global] from with in the browser. Start elogd, open the logbook and click on config,
enter a Mirror server = http://laptop:8080/
Clicking synchronize give "Error accessing remote logbook"

Again, the logbooks are on both machines in /usr/local/elog/logbooks (owner:group elog:elog). The tfexp in this case is passwd protected.
Any user can access the elogs in both machines, locally or remote. But, I'm unable to synchronize the two.
Maybe somebody can point me in the right direction.

Thank's Gerfried
ELOG V3.1.5-3fb85fa6