| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
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 |
|
1174
|
Sat Jun 4 12:25:57 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.5.9 | Re: elog crashes when admin tries to register new users |
| Heiko Scheit wrote: | When pasting the URL for the registration of new users (with 'Self register = 3') elog
crashes with segmentation fault. I don't have the time currently to give you more
debuging information but maybe you can have a look the same. It crashes after
the user is registered. The Email is sent, too. |
I cannot reproduce this problem either. The only difference I see is that I use thunderbird as my email client, where I don't have to copy/paste the activation URL into my browser, but just click on it. If maybe the copy/paste operation adds an additional CR/LF or so, that could be a problem. Can you check again? A stack trace of the crashed elogd would help as well. |
|
1189
|
Thu Jun 9 15:20:04 2005 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | Linux | 2.5.9 | Re: elog crashes when admin tries to register new users |
| Stefan Ritt wrote: |
| Heiko Scheit wrote: | When pasting the URL for the registration of new users (with 'Self register = 3') elog
crashes with segmentation fault. I don't have the time currently to give you more
debuging information but maybe you can have a look the same. It crashes after
the user is registered. The Email is sent, too. |
I cannot reproduce this problem either. The only difference I see is that I use thunderbird as my email client, where I don't have to copy/paste the activation URL into my browser, but just click on it. If maybe the copy/paste operation adds an additional CR/LF or so, that could be a problem. Can you check again? A stack trace of the crashed elogd would help as well. |
The following appended after the base (!) URL results in a segmentation fault
?cmd=Activate&new_user_name=test1&new_full_name=Test1
It works fine, if a specific logbook is given. So
http://my.ho.st/?cmd=Activate&new_user_name=test1&new_full_name=Test1
is not OK, while
http://my.ho.st/myLogBook/?cmd=Activate&new_user_name=test1&new_full_name=Test1
is OK. |
|
1198
|
Fri Jun 17 22:33:29 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.5.9 | Re: elog crashes when admin tries to register new users |
Thanks for that info. It helped me debugging things. The problem is that the "activation" URL does not contain a logbook if there is a global password file. I have never tried that so of course it crashes 
I tried to fix this and committed the changes to CVS. Can you try with that version? |
|
1206
|
Tue Jun 21 19:24:58 2005 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | Linux | 2.5.9 | Re: elog crashes when admin tries to register new users |
| Quote: |
Thanks for that info. It helped me debugging things. The problem is that the "activation" URL does not contain a logbook if there is a global password file. I have never tried that so of course it crashes
I tried to fix this and committed the changes to CVS. Can you try with that version? |
Not really, unless you have a fixed 2.5.9 version. Version 2.6 has
way too many new features, which I don't want at the moment. Or is
there a config option to get the old behavior?
I also saw that the format of the email notification has changed. As
I have scripts (bash, akw, procmail) that depend on this format I
would need much more time than I currently have to actually test
everything.
Maybe you should consider supporting two branches, say 'stable' (2.5.9
currently) and 'experimental' (2.6 currently)? For 'stable' only
severe bugs and security issues are fixed and in 'experimental' new
features are introduced. What do you say?
For me the risk of upgrading to 2.6 now seems to high, as many people
depend on the logbook. |