Re: Crash report involving propagate and replies, posted by Hung Dao on Fri Jan 3 21:33:40 2014 
|
| Andreas Luedeke wrote: |
|
|
Stephen wrote:
|
|
|
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.
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 ;-)
⇄
English (auto-detected) » English
|
I have been able to compile Elogd successfully in Windows with Visual Studio 2010 but not with Elog. Attached are errors, it complaint about buffer[i] type char * being assigned type void *. If anyone has been successful compile the elog, please give me a hint. Thanks. |
|
Re: Crash report involving propagate and replies, posted by Hung Dao on Sun Jan 12 04:48:12 2014
|
| Andreas Luedeke wrote: |
|
| Hung Dao wrote: |
|
| Andreas Luedeke wrote: |
|
|
Stephen wrote:
|
|
|
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.
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 ;-)
⇄
English (auto-detected) » English
|
I have been able to compile Elogd successfully in Windows with Visual Studio 2010 but not with Elog. Attached are errors, it complaint about buffer[i] type char * being assigned type void *. If anyone has been successful compile the elog, please give me a hint. Thanks.
|
You don't need "elog" to run the logbook, the executable "elog" is only needed to create entries without the web interface. Stefan should adapt "elog.c" some day to be compatible with the default switches of modern, paranoid compilers; but for the moment you can ignore this.
⇄
English (auto-detected) » English
If you use the newly created "elogd", does that reproduce the former problem?
|
I don't see it has crashed when testing your cfg. However, one thing I must do is to comment out the alarm_handler function in order to compile the elogd successfully. Otherwise, it shows an undefined alarm, see in the 2nd attachment. Although it did not crash as tested with your cfg, I have experienced the new version sometimes crashed on our system but then it self restarted (different scenario since my cfg does not use Propagate. I have not been able to narrow down yet. |
|
Re: Crash report involving propagate and replies, posted by Hung Dao on Mon Feb 3 22:45:10 2014
|
| Stephen wrote: |
|
| Stefan Ritt wrote: |
|
| Stephen wrote: |
|
Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
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?
|
Was a tricky problem. When you use "Propagate Attributes", a routine is called inside elogd which recursively goes through all replies. It uses quite some memory for temporary storage of attributes and attachments. So after a certain time you get a stack overflow since you run out of memory. Since the stack size is different under different operating systems, it was hard for me to reproduce it initially. Now I use some different memory (dynamic heap instead stack) which should fix the problem. Can you pull from GIT and give it a try?
/Stefan
|
Unfortunately, I am a little outside of my element when trying to compile it. I will ask around and see if someone here could give me a hand. Thanks for looking into this for me.
PS. If anyone else has managed to compile this could you give me a hand =)
|
I was able to manage and compile the latest code from GIT. It runs fine so far. Just a hint, in order to compile successfully, there are some steps that you may need to modify your header file depend on how you store your mxml, krb5, OpenSSL files and directories. |
cell style bug?, posted by ch huet on Thu May 6 17:40:47 2010
|
hello
i've tried to change the color of a cell with "cell style"
it doesn't works
by removiving "cell" in the line ,just to get "style" the color of all cell of the row change (so it works for that...)
regards |
|
Re: cell style bug?, posted by ch huet on Fri May 7 15:35:12 2010
|
| Stefan Ritt wrote: |
|
| ch huet wrote: |
|
hello
i've tried to change the color of a cell with "cell style"
it doesn't works
by removiving "cell" in the line ,just to get "style" the color of all cell of the row change (so it works for that...)
regards
|
As written here: https://midas.psi.ch/elogs/Forum/66807 you need to upgrade to version 2.7.8-5 of ELOG to get this functionality.
|
You're right my verssion was the previous one |
|
large attachment seems to hang elogd?, posted by Haitao Yu on Tue Mar 7 21:41:28 2006
|
Hello,
I am trying to attach somewhat large file (4-15MB files tested) with my messages but it seems to hang the elogd server for a really long time (30-100minutes). The file upload was done pretty soon (within a few seconds), then the elogd process seems to be busy doing something, using around 50MB of memory and 95% of CPU time, and stop respond to the requests. I can read the logbook with another copy of elogd running on another port, and I can see (and download) the uploaded file. I am wondering what could cause the problem --- and could it be related to the problem of not setting up the SMTP server right? Thanks for any suggestion!
Haitao
P.S. I read in some old message that if we want to upload very large files, we have to change the WEB_BUFFER_SIZE in elogd.c, however this parameter is no longer in v2.6.1. Is there something similiar I have to change? |
|
Allow password change ???, posted by Hal Proctor on Fri Apr 10 17:41:25 2009
|
How do you allow users to change password for a given logbook when the user keeps getting prompted for admin password to enter the change password feature?
I have Allow password change = 1 set global and at each logbook hoping that would work.
It allows them to change the password when and only when the user gets past the admin login when clicking CONFIG.
help
|
|
Re: Allow password change ???, posted by Hal Proctor on Fri Apr 10 19:32:33 2009
|
| Hal Proctor wrote: |
|
How do you allow users to change password for a given logbook when the user keeps getting prompted for admin password to enter the change password feature?
I have Allow password change = 1 set global and at each logbook hoping that would work.
It allows them to change the password when and only when the user gets past the admin login when clicking CONFIG.
help
|
Thats what we get for having two people working on the install and configuration. LOL
When first creating and setting up the configs, we had Admin Password = xxxxx entered in each logbook config. Once we created a password list we no longer needed that entry.
This was why each user who had login credentials was being asked to provide the admin password when trying to change their password.  |
|