| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1012
|
Thu Mar 24 11:01:06 2005 |
 | Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | Linux | | Re: Crash with Protect Selection page = 1 | > > Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> > as soon as it is accessed.
>
> Thanks for reporting this bug. I fixed it and committed the change to CVS.
>
> - Stefan
wow, who's Speedy Gonzales ?!? :-P |
|
1013
|
Thu Mar 24 11:28:13 2005 |
| Stephen A. Wood | saw@jlab.org | Bug report | Linux | | Re: Crash with Protect Selection page = 1 | > > Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> > as soon as it is accessed.
>
> Thanks for reporting this bug. I fixed it and committed the change to CVS.
>
> - Stefan
That was fast! I put the elogd.c from the cvs on top of 2.5.8 and now I can run
the server with Protect Selection page=1 again.
Logins work OK if the username/password is valid. However, if I try to login
with invalid authentication, the server crashes. If I turn off the protect
selection page, then invalid authentication does not crash elogd.
Thanks, Steve |
|
1014
|
Thu Mar 24 11:47:58 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | | Re: Crash with Protect Selection page = 1 | > Logins work OK if the username/password is valid. However, if I try to login
> with invalid authentication, the server crashes. If I turn off the protect
> selection page, then invalid authentication does not crash elogd.
Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
I fixed that as well and committed the changes.
Greetings to JLab (I once worked at UVa in Charlottesville...). Is David Abbott
still there?
- Stefan |
|
1015
|
Thu Mar 24 12:09:55 2005 |
| Stephen A. Wood | saw@jlab.org | Bug report | Linux | | Re: Crash with Protect Selection page = 1 | > > Logins work OK if the username/password is valid. However, if I try to login
> > with invalid authentication, the server crashes. If I turn off the protect
> > selection page, then invalid authentication does not crash elogd.
>
> Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
>
> I fixed that as well and committed the changes.
That seems to do the trick! Thanks, Steve |
|
1025
|
Fri Mar 25 12:44:49 2005 |
 | Alex H | alex@synergie-inf.com | Bug report | Linux | | Re: Crash with Protect Selection page = 1 | > > > Logins work OK if the username/password is valid. However, if I try to login
> > > with invalid authentication, the server crashes. If I turn off the protect
> > > selection page, then invalid authentication does not crash elogd.
> >
> > Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
> >
> > I fixed that as well and committed the changes.
>
> That seems to do the trick! Thanks, Steve
Hi,
where can I find this correction for ELOG?
thanks a lot :o) |
|
1028
|
Fri Mar 25 18:25:59 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | | Re: Crash with Protect Selection page = 1 | > > > > Logins work OK if the username/password is valid. However, if I try to login
> > > > with invalid authentication, the server crashes. If I turn off the protect
> > > > selection page, then invalid authentication does not crash elogd.
> > >
> > > Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
> > >
> > > I fixed that as well and committed the changes.
> >
> > That seems to do the trick! Thanks, Steve
>
> Hi,
> where can I find this correction for ELOG?
> thanks a lot :o)
It's under CVS. You have to recompile the executable yourself, or you wait for the next
release (;-) |
|
66456
|
Wed Jul 22 12:15:56 2009 |
| T. Ribbrock | emgaron+elog@ribbrock.org | Bug report | Linux | 2.7.6r2233 | Re: Crashes when editing entries |
| T. Ribbrock wrote: |
|
For some odd reasons, we are experiencing frequent crashes of elogd over the past few days. It has been working fine so far, but more or less out of the blue it became rather unreliable. The current configuration is installed on two servers, one running 2.7.5.-r2174 on ClarkConnect 4 and one running 2.7.6-r2233 on Debian 4.0 - both show the same problem. Each of them has an "active" group with four logbooks and an "archive" group with three logbooks. In the "active" group, there are two logbooks that share the same index (using Subdir=...) and it looks like the crashes occur most of the time in these, though that's just a hunch so far. Also, most of the crashes seem to happen when submitting an entry that has been edited. Actually, submitting a modified entry has always been strange in our logbooks: When we hit submit, we get a pop-up window asking "Submit modified entry?". When choosing "OK", the entry that has been edited is duplicated. When choosing "Cancel", it is submitted correctly.
I've been running elogd like this (to get more info)
elogd -v > elog-2233-2.log 2>&1
The last entry I get in the log when elogd crashes is:
Same index as logbook Machine Log
elogd: src/elogd.c:727: xfree: Assertion `*((unsigned int *) (temp - 4)) == 0xdeadc0de' failed.
Received unknown cookie "wikidb_mw__session"
Received unknown cookie "wikidb_mw__session"
I did actually make a few changes to the configuration before we noticed the crashes: I added one extra attribute and a few more conditionals.
Any additional information you need: Just let me know.
Regards,
Thomas
|
Forgot to mention: I've also seen error messages like this upon a crash:
*** glibc detected *** corrupted double-linked list: 0x0911bbc0 ***
Regards,
Thomas |
|
66457
|
Wed Jul 22 12:46:36 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.6r2233 | Re: Crashes when editing entries |
| T. Ribbrock wrote: |
|
For some odd reasons, we are experiencing frequent crashes of elogd over the past few days. It has been working fine so far, but more or less out of the blue it became rather unreliable. The current configuration is installed on two servers, one running 2.7.5.-r2174 on ClarkConnect 4 and one running 2.7.6-r2233 on Debian 4.0 - both show the same problem. Each of them has an "active" group with four logbooks and an "archive" group with three logbooks. In the "active" group, there are two logbooks that share the same index (using Subdir=...) and it looks like the crashes occur most of the time in these, though that's just a hunch so far. Also, most of the crashes seem to happen when submitting an entry that has been edited. Actually, submitting a modified entry has always been strange in our logbooks: When we hit submit, we get a pop-up window asking "Submit modified entry?". When choosing "OK", the entry that has been edited is duplicated. When choosing "Cancel", it is submitted correctly.
I've been running elogd like this (to get more info)
elogd -v > elog-2233-2.log 2>&1
The last entry I get in the log when elogd crashes is:
Same index as logbook Machine Log
elogd: src/elogd.c:727: xfree: Assertion `*((unsigned int *) (temp - 4)) == 0xdeadc0de' failed.
Received unknown cookie "wikidb_mw__session"
Received unknown cookie "wikidb_mw__session"
I did actually make a few changes to the configuration before we noticed the crashes: I added one extra attribute and a few more conditionals.
Any additional information you need: Just let me know.
|
well, I need to reproduce your problem in order to fix it. The failed assertation you get is due to some internal writing beyond array boundaries, but I have no clue which part of the code makes this. It might be related to the fact that you use the same index (via Subdir=...) for two logbooks. In this scenario, you are only allowed to modify/add entries to one logbook, not the other. The other one may only be used for reading. And even then it's not guaranteed that new entries show up in the second logbook immediately, you might have to restart the server in order to re-index the logbooks. Internally, the daemon does not know that two logbooks are "the same" and one instance will not realize if the other instance modifies the data "below its feet". Can you try to give up the double logbooks and see if the problem goes away? |
|