ELOG Forum

I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

Bad news: I cannot reproduce your problem with the latest elog version 2.9.2 (e7ba466) on scientific linux 6.0

I had to remove some lines in your config, since I don't have your password file.

I'll attach the config file, please have a look if it crashes on your server with the latest elogd version.

Andreas

Thanks for the reply, I tried the very basic cfg and the second one you offered. Running 2.9.2-2475 on a Windows 2008 R2 V.Server, I still crashed on attempt 10 never fail. Windows detects the failure and gives this message:

Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707

Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707

Exception code: 0xc00000fd

Fault offset: 0x00065127

Faulting process id: 0x340

Faulting application start time: 0x01ceefa87fea0aea

Faulting application path: D:\ELOG\elogd.exe

Faulting module path: D:\ELOG\elogd.exe

Report Id: ceccc3da-5b9b-11e3-80f1-5ac95c924b0b

It only happens when propagate is on, I have to be missing some security setting in Windows maybe? Don't know if that helped at all, but I'm out of ideas.

Can you compile elog? Then I would suggest that you download the latest version from GIT an recompile it. You'll find help for that here: https://midas.psi.ch/elog/download.html

I have no experience with compilation on Windows (I try not to touch it, and if I have to I use a long stick ;-)

67633

Mon Dec 2 23:02:45 2013

Re: Crash report involving propagate and replies

Andreas Luedeke wrote:

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

Bad news: I cannot reproduce your problem with the latest elog version 2.9.2 (e7ba466) on scientific linux 6.0

I had to remove some lines in your config, since I don't have your password file.

I'll attach the config file, please have a look if it crashes on your server with the latest elogd version.

Andreas

Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707

Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707

Exception code: 0xc00000fd

Fault offset: 0x00065127

Faulting process id: 0x340

Faulting application start time: 0x01ceefa87fea0aea

Faulting application path: D:\ELOG\elogd.exe

Faulting module path: D:\ELOG\elogd.exe

Report Id: ceccc3da-5b9b-11e3-80f1-5ac95c924b0b

It only happens when propagate is on, I have to be missing some security setting in Windows maybe? Don't know if that helped at all, but I'm out of ideas.

67632

Mon Dec 2 09:58:42 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Bug report

Windows

2.9.2

Re: Crash report involving propagate and replies

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

Bad news: I cannot reproduce your problem with the latest elog version 2.9.2 (e7ba466) on scientific linux 6.0

I had to remove some lines in your config, since I don't have your password file.

I'll attach the config file, please have a look if it crashes on your server with the latest elogd version.

Andreas

67631

Mon Dec 2 09:27:35 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Bug report

Windows

2.9.2

Re: Crash report involving propagate and replies

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

Hi Stephen,

I've just checked that elogd can handle "Propagate Attributes" for more than 10 replies without crashing (I've attached my config, you can see if it works for you.)

Therefore it has to be something else in your configuration that causes this behaviour, or a combination of things.

Could you strip off the configuration further, that it contains the minimal content to cause elogd to crash? Or can you use a debugger on your system?

Cheers

Andreas

67630

Wed Nov 27 15:22:37 2013

Re: Crash report involving propagate and replies

David Pilgram wrote:

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

Hi Stephen,

I see that you don't allow branching in your threads. Why do you need to propagate the Status throughtout the thread? Why not just mark the latest entry and (incase it is necessary) 'collapse to last = 1'

I'm not saying that the bug (if bug it is, rather than a preset limitation) you've found should not be fixed, but I'm puzzled as to why you happen to use the feature. I can see the point if an initial entry provides a whole tree of branches (and a limit of 10 is rather limiting). OK, I know if it is historic, it cannot easily be changed because of other users. Or if some users will primarily be responding to emails rather viewing the logbook via a browser. I'm a single (ab)user elog system myself, so I'm very tolerant of changing how elog works if it offers an improvement.

Thank you for the reply, the not allowing branching was added during the troubleshooting phase of the crashing. Initially I thought the branches caused the issue because crashing only occured on log notes that branched as I only saw the crash on notes that branched, this proved not to be the case. Even with branches the system will crash once there are 10 replies in the note with propagate on.

As for use case, with a few users I needed a way to represent a note as open so that the next person knew work still needed to be done. Once work was completed all notes close, the reason for not using edit is so I have a clear record of what happened (although I may need to change to edit if 10 is the max). I will experiment with the collapse to last to see how it looks. Any other suggestions would be helpful.

67629

Tue Nov 26 21:49:42 2013

David Pilgram

David.Pilgram@epost.org.uk

Bug report

Windows

2.9.2

Re: Crash report involving propagate and replies

Stephen wrote:

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

Hi Stephen,

67628

Tue Nov 26 16:24:39 2013

Crash report involving propagate and replies

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

67627

Tue Nov 26 11:28:39 2013

David Pilgram

David.Pilgram@epost.org.uk

Question

Linux

2.9.2-2455

Re: Problem with space in name of eLog not seeing %20 and "+"

David Pilgram wrote:

Stefan Ritt wrote:

Tom C wrote:

My elog is named "Whatever Elog" so the URL generated is /Whatever+Elog . This works fine but when in the interface certain buttons generate this URL : /Whatever%20Elog ...this URL fails. It seems that elog does not recognize these ( + and %20 ) as the same which I believe they should be as part of HTTP request.

Can you be a bit more specific which buttons you mean? The demo logbook https://midas.psi.ch/elogs/Linux+Demo/ has also a space and I cannot see any problem there.

Years ago I had a similar issue, although I cannot remember the exact details now. The consequence is that I don't leave any spaces in the log book names. However, I did find that '&' was fine, and the ampersand and %26 are interchangeable in a logbook page, so one logbook is ECP&SIW, and using ampersand or '%26' work interchangably when making llinks from other logbooks to ECP&SIW (that is elog:ECP&SIW or elog:ECP%26SIW work equally well).. This is not true of elog.cfg, where only the actual character should be used. This may be true for some other urlencoded characters.

It may be of note that %20 and '+' are not the same urlencode and character - %20 is a space, '+' is %2B, and a brief bit of playing around shows that elog is not so tolerant of those characters as it is with & and %26, and I crashed mine several times but I was only playing, nothing serious was lost.

Having written the above and posted it, I see the links for ECP&SIW I wrote here don't work the same as in my local logbook. I did check! Result is treat the above posting with caution. Although this is not the first time when something works fine on my local logbook but not here on the Mother of all elogs. Different flavour of linux?

Goto page Previous 1, 2, 3 ... 272, 273, 274 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6