| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
65754
|
Thu Feb 21 15:09:25 2008 |
 | stephane | stephane.brisson@synchrotron-soleil.fr | Question | Linux | 2.7.2.2041 | Re: elog hand once mirror started |
| Stefan Ritt wrote: |
|
| 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.
|
Hello,
The server hang at this point :
ID362 : 45F505AF26644D7F71A2AF6E9822554D
Cache : 45F505AF26644D7F71A2AF6E9822554D
Remote : 45F505AF26644D7F71A2AF6E9822554D
I can't stop the process with ctrl+c
Kind regards
Stéphane |
|
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. |
|
65756
|
Fri Feb 22 06:32:48 2008 |
| stephane | stephane.brisson@synchrotron-soleil.fr | Question | Linux | 2.7.2.2041 | Re: elog hand once mirror started |
| Stefan Ritt wrote: |
|
| 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.
|
How can I put the output in a file to send it to you ?
|
|
65757
|
Fri Feb 22 08:38:38 2008 |
| stephane | stephane.brisson@synchrotron-soleil.fr | Question | Linux | 2.7.2.2041 | Re: elog hand once mirror started |
| stephane wrote: |
|
| Stefan Ritt wrote: |
|
| 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.
|
How can I put the output in a file to send it to you ?
|
I solve my mirror problem. It came from old logbooks made with old elog version. I replicate these manually and exclude them from mirror.
Kind regards
Stéphane |
|
1428
|
Wed Oct 5 13:24:52 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | | Linux | 2.6.0 | Re: elog fails to connect with "cannot get host name: Success" message |
| ScottK wrote: | I can't seem to connect using elog:
elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt
|
Maybe a
elog -h <myhost> -p 8080 -v -l .... ??? |
|
1448
|
Tue Oct 11 15:09:42 2005 |
 | ScottK | snkgak@yahoo.com | Question | Linux | 2.6.0 | Re: elog fails to connect with "cannot get host name: Success" message |
| Stefan Ritt wrote: |
| ScottK wrote: | I can't seem to connect using elog:
elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt
|
Maybe a
elog -h <myhost> -p 8080 -v -l .... ??? |
Oops - amazing when I read the syntax correctly -- it works! Thanks for taking the time to reply to a "dumb, RTFD" question, Stefan. Thank you for making a great program!
ScottK |
|
66877
|
Fri Aug 6 13:01:24 2010 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | unknown | Re: elog editor loses all text |
| Kontantin Olchanski wrote: |
|
I just typed a long text into this elog, clicked "submit" and it bombed with "you must select an Icon", returned me to the editor with all my text gone gone gone. I do not want to select icons, I just want to report a problem with elog. Well, 2 problems, now.
K.O.
|
Well, first RTFM: "Fields marked with a * are required" on top of the elog entry page. Then, use a reasonable browser on a reasonable OS 
On Google Chrome the text is still there (actually I just tried it with this entry). No idea what Safari under OSX does. Under Windows, Safari keeps the text. Actually this is controlled by the FCKEditor inside elog which is written by someone else. So complain there! Funny: We have about 1000+ entries in this forum, and you are the first one complaining about this. |
|
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 |