ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
65746
|
Mon Feb 18 08:00:44 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.2 2041 | Re: elog crashing on startup |
Jeff Stoner wrote: |
I create 14 of them, one for every 2 letters of the English alphabet and 0-9. The logbook name and Subdir change appropriately. When I start elog, it stays up for about 30 seconds, then crashes. No messages are recorded in syslog nor in the logfile. The only thing that looks suspicious are a couple lines in syslog:
Feb 15 17:11:05 iadopsutil04p elogd[23761]: elogd 2.7.2 built Feb 14 2008, 20:55:38
Feb 15 17:11:05 iadopsutil04p elogd[23761]: revision 2041
Feb 15 17:11:05 iadopsutil04p elogd[23761]: FCKedit detected
Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot restore original GID/UID. Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Feb 15 17:11:05 iadopsutil04p elogd[23761]: Server listening on port 80 ...
This is obviously the child process responsible for the highlighted lines and it's coming from the cleanup function. Why it's getting called is beyond me.
Ideas?
|
The error message above come from the PID file /var/run/elogd.pid which cannot be removed. This file is only for information purpose, to tell any script which PID the elogd daemon has. If one elogd crashed in the past, the file might still be there although the program is not running, causing some error to show up, but which can normally be ignored.
The fact that elogd stays for about 30 seconds can only be contributed to the fact that you have very large logbooks, which are scanned during startup. You can check this by starting elogd interactively with the "-v" option. Then you will see the scanning process. The next thing is if you really get a crash, you can produce a core dump, so it can be analyzed to figure out where elogd has crashed. To my knowledge the only way you can do that is by having some logbooks with invalid data. Can you try your set-up with empty logbooks?
- Stefan |
65748
|
Mon Feb 18 17:51:49 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | | Re: error "Cannot retrieve host name: No error" using command line in Windows |
Dan Gawarecki wrote: |
QUESTION: does command line ELOG connect differently than ELOG through the browser?
I ask this question for perhaps the A-V SW *is* blocking some port or whatever, and I will need to ask our IT department how to remove such a restriction.
|
ELOG connects in the same way as the browser, but it is a different program. I have seen some firewalls which explicitly exclude browsers in firewall rules. So it might well be that yours blocks ELOG but not your browser. So give it a try and disable it. |
65750
|
Thu Feb 21 08:04:50 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | ELOG V2.7. | Re: Message ID and trouble ticketing system |
Richard Ecclestone wrote: |
I tried the 'Preset ticket = TCK-#####' method to create unique numbers for our application. This worked very nicely until we replied to a earlier message, if we then create a new message the system creates a sequential number after the last message number we replied to. For example if we have 10 messages. If someone replies to message number #2 then when a new record is created it is then assigned number #3 not #11, thus making a duplicate entry for #3.
Any ideas?
|
Yes. If you want this feature to work also for replies, you have to put following into your config file:
Preset ticket = TCK-#####
Preset on reply ticket = TCK-#####
|
65753
|
Thu Feb 21 14:36:32 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.2.2041 | Re: elog hand once mirror started |
stephane wrote: |
Hello,
When I started elogd on the mirror server, I can access to the website on it until cron job started. Once cron job started, the elog mirror server hang and I can't obtain any response on it.
How can I solve this problem ?
|
With this information I cannot diagnose the problem. I would recommend you to run the elogd on the mirror server in interactive mode with the "-v" flag, so you see all net traffic. Maybe this sheds some light on the problem. |
65755
|
Thu Feb 21 17:18:55 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.2.2041 | Re: elog hand once mirror started |
stephane wrote: |
Hello,
The server hang at this point :
ID362 : 45F505AF26644D7F71A2AF6E9822554D
Cache : 45F505AF26644D7F71A2AF6E9822554D
Remote : 45F505AF26644D7F71A2AF6E9822554D
I can't stop the process with ctrl+c
|
No, that does not help me to come to a conclusion. So I have no idea what's going on. When you do mirroring, you can start the synchronization from both server sides. Can you maybe try to do that from the "other" server? Maybe you have some firewall problem. |
65759
|
Wed Feb 27 03:46:28 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.3 | Re: Problem updating from 2.7.2 to 2.7.3 |
Uwe wrote: |
Hello,
I am trying to update from version V2.7.2-2041 to V2.7.3 but getting the attached error message. OS is Windows 2003. I installed the update on Windows XP without a problem. Does anybody know ho to solve that problem? Thanks!
|
The shared library msvcr71.dll should be part of the operating system and placed under c:\windows\system32\msvc71.dll. If not it can be downloaded from
http://www.dlldump.com/download-dll-files.php/dllfiles/M/MSVCR71.dll/download.html |
65764
|
Sat Mar 1 14:53:16 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.3 | Re: German language |
Salvatore wrote: |
In der Config-Datei habe ich den Eintrag "language = german" vorgenommen. Was unter Windows funktioniert, verweigert mir Linux: Die Umstellung des Logs auf Deutsch. Wer kann helfen?
Salvatore
|
Das kann drei Ursachen haben:
1) Die Installation under Linux ist nicht vollstaendig. Die Datei resources/eloglang.german muss vorhanden und von elogd lesbar sein
2) Der linux-daemon braucht ein Neustart nach jeder Aenderung der Sprache
3) Nochmal ueberpruefen, ob der Eintrag "language = german" auch wirklich vorhanden im richtigen config file ist. |
65765
|
Sat Mar 1 15:08:07 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.3-2058 | Re: Problem with Email Notification |
mike cianci wrote: |
Sorry to bother you with this, but I am not a programmer and this is probably a simple question but I need some help if someone has the time.
Under Global I have the command - SMTP host = smtp.comcast.net
ELOG responds with - Error sending Email via "smtp.comcast.net": 5.1.0 sender rejected : invalid sender domain
|
Your SMTP server does not accept the email send request from ELOG. That can have many reasons. Most systems are set up so that they do not accept SPAM. To do that, they do various checking of the sender address etc. Maybe you need an "Email from = mike2.cianci@comcast.net" in your config file to have a "real" sender address. Some more information you can get if you start elogd interactively in a DOS box with the "-v" flag, because then you will see all the debugging output of the communication between elogd and your SMTP server. |