Re: editor dosn't work, posted by David Pilgram on Thu Jun 2 20:20:19 2011
|
Sara Vanini wrote:
|
segmentation fault when "restrict edit" is used and "new" is allowed for anonymous users, posted by Andreas Luedeke on Mon Jun 20 05:31:31 2011
|
The simple config file below produces a segmentation fault when elogd is started,
http://localhost/Test/?cmd=New
is opened in the browser and then e.g. "Entry" is switched to "Problem".
|
Re: segmentation fault when "restrict edit" is used and "new" is allowed for anonymous users, posted by Stefan Ritt on Mon Jun 20 17:53:58 2011
|
You are the first one allowing guests to enter new entries, so this probes a code path which was never used before. I fixed the crash in SVN revision 2416,
but it might be that there are more issues with that. Just keep reporting. |
Re: ELOG deamon stuck in find_thread_head(), posted by Soren Poulsen on Wed Jul 6 12:06:01 2011
|
Soren Poulsen wrote:
|
Re: ELOG deamon stuck in find_thread_head(), posted by David Pilgram on Wed Jul 6 12:36:33 2011
|
Soren Poulsen wrote:
|
SEGV after upgrade from 2.7.8 to 2.9.0, posted by Kester Habermann on Mon Aug 15 11:36:02 2011
|
Hello,
We've been using ELOG 2.6.5 to 2.7.8 for 4 years without any major problems.
Recently we upgraded to version 2.9.0 and since we've had the daemon frequently crash with SEGV. |
Elog crashes with URL find npp=0, posted by Andreas Luedeke on Tue Sep 13 11:54:16 2011
|
Some user wanted to modify the URL by hand and succeeded to crash the elogd process with npp=now
It appears that npp=0 crashes elogd with the following error message:
|
Memory Leak in V2.9.0-2411 (Mirroring Related), posted by Ryan on Tue Sep 20 04:46:55 2011
|
I have two identical servers (IBM X337) setup on the same LAN with Ubuntu Linux 10.04 LTS with ELOGD running (Compiled from tarbell) with the same exact
package install base. (Only difference between the two servers is the hostname, and the ELOGD.CFG global section)
I noticed after setting these servers up today that ELOGD crashed on the server configured to mirror. It looks like |