Elogd crashes with: *** stack smashing detected ***, posted by Niklas on Fri Nov 21 10:53:09 2008
|
Hi,
elogd sometimes crashes when there are large cookies. Or I'd guess it has something to do with the cookies, elogd crashed over and over again until |
|
Attribute value lost when adding to another extendable attribute, posted by Dennis Seitz on Thu Dec 11 03:13:31 2008
|
Here is an excerpt from my config file:
Type Last Edit = datetime
Preset Last Edit =$entry time |
|
Odd behaviour with gecko based browsers and reverse proxy., posted by Andraž 'ruskie' Levstik on Thu Mar 12 08:03:07 2009
|
I have a really odd issue with elog...
My setup:
|
|
Long cookie content is not handled properly., posted by Simon Patton on Tue Apr 14 22:51:15 2009
|
I discovered the infinite loop in 2.7.5 which can happen when a cookie's content is longer that the cookie array
designed to hold it. I also note that this issue has been addressed in 2.7.6, but the solution does not appear
to be correct and it can end up completely confusing the cookie extraction.
|
|
Denial of access after failed import using invalid attributes, posted by soren poulsen on Wed Jun 17 03:46:31 2009
|
Hi,
A user tried to import a CSV file, which caused e-log to add a field called "date" to the list of attributes (and then crash). This caused
the log-book to be blocked until someone (guess who) would go edit the elogd.cfg file and then trigger a reload. |
|
Auto-increment substitutions broken with records for multiple days, posted by Richard Stamper on Wed Jun 24 15:02:49 2009
|
With a logbook defined by
[test]
|
Checks on datetime seconds field generate warning in IE7, posted by Richard Stamper on Wed Jul 1 17:00:30 2009 
|
When adding a log entry containing a datetime field using the IE7 browser a Javascript warning is displayed - see the attachment. This is due to
a change in the naming of the "seconds" field of a datetime entry (made in version 2143) not being propagated to the code that generates the
Javascript that checks the supplied values. |
|
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 |