Crashes when editing entries, posted by T. Ribbrock on Wed Jul 22 12:12:37 2009
|
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 |
Re: Crashes when editing entries, posted by T. Ribbrock on Wed Jul 22 12:15:56 2009
|
T. Ribbrock wrote:
For some odd reasons, we are experiencing frequent crashes of elogd over the past few days. It has been |
|
Re: Crashes when editing entries, posted by Stefan Ritt on Wed Jul 22 12:46:36 2009
|
T. Ribbrock wrote:
For some odd reasons, we are experiencing frequent crashes of elogd over the past few days. It has been |
|
Re: Crashes when editing entries, posted by T. Ribbrock on Wed Jul 22 15:35:57 2009
|
Stefan Ritt wrote:
well, I need to reproduce your problem in order to fix it. The failed assertation you get is due to some internal |
|
Re: Crashes when editing entries, posted by Stefan Ritt on Wed Jul 22 16:30:48 2009
|
T. Ribbrock wrote:
Nonetheless, given that this set-up has been a great help for us - if you ever get the chance to make |
|
Re: Crashes when editing entries, posted by T. Ribbrock on Wed Jul 22 16:52:13 2009
|
Stefan Ritt wrote:
|
Wrong error message if invalid attribute is used, posted by T. Ribbrock on Mon Jul 27 10:20:14 2009
|
I just ran into this little bug: I had defined a new logbook in my config file and suddenly got the message Attribute "Date" not allowed.
While I did have several attributes starting with the word "Date" (e.g. "Date In Service", "Date Retired") I had no attribute
"Date" in there. After some pondering and wildly commenting out lines, it finally dawned on me: I had used an attribute "ID" - which |
|
Re: Wrong error message if invalid attribute is used, posted by Stefan Ritt on Mon Jul 27 10:49:19 2009
|
T. Ribbrock wrote:
I just ran into this little bug: I had defined a new logbook in my config file and suddenly got the |