| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67639
|
Tue Dec 17 21:00:33 2013 |
 | Ryan Blakeslee | rb@blakesys.net | Question | Linux | 2.9.2 | Re: How to property install? |
| Andreas Luedeke wrote: |
|
| Ryan Blakeslee wrote: |
|
Hello,
I have followed the very simple steps on the Download page for checking out and compiling from GIT. That works perfect and there is no issue.
The problem I have is-- it is not clear to me where to put the 'elog' dir that I have after I 'make' and 'make install'. Or, is there an installer script afterwards that I run? I'm installing on Debian 7 and trying to upgrade from 2.5.2 (which was installed using apt-get.)
|
Hi Ryan,
as far as I remember the Debian package is not supported any more. The "make install" assumes Red-hat style installation directories (you can see it in elog/Makefile, all the installation directories are installed there).
I have no idea where Debian is supposed to install the binaries. But you should be able to use GNU "locate" to find the old files: "locate elog" and "locate elogd" should tell you where the old binaries had been installed.
Kind Regards, Andreas
⇄
English (auto-detected) » English
|
Hi Andreas,
Thank you so much for the reply and info; Much appreciated! I turned up a CentOS 6 VM and the installation, using the RPM's provided on the 'downloads' page here, worked perfectly and was very straight-forward and easy.
The D/L page includes the Debian repositories (which is how I installed on Debian in the first place) but only installed v2.5.2. I needed to get to the newest version (ELOG V2.9.2-2455) so I can setup authentication and SSH. (And also so that when I am reading the manuals and documentation online, provided at this site, that is makes sense to the version I am running.) I also want to add that it seems that I am able to bring over my older 2.5.2 logbooks to 2.9.2 without any problem. To do that, I just rsync'd the logbooks from old to new. They seem to work just fine under the newest version.
I'm good to go. Anyone looking for an easy deployment of ELOG, especially in a production environment, I can attest that the RPM's provided here make it very simple to deploy on Cent6.
Thanks! |
|
67643
|
Fri Jan 3 21:33:40 2014 |
| Hung Dao | hungtdao@yahoo.com | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
| 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. |
| Attachment 1: error1.jpg
|
|
| Attachment 2: error2.jpg
|
|
| Attachment 3: error3.jpg
|
|
|
67644
|
Mon Jan 6 10:25:03 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
| Hung Dao wrote: |
|
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.
|
Just put (char *) in front of all malloc(). I will include the fix in the next official version.
/Stefan |
|
67645
|
Mon Jan 6 10:32:43 2014 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
| 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? |
|
67646
|
Tue Jan 7 04:28:28 2014 |
 | John Haggerty | haggerty@bnl.gov | Bug report | Mac OSX | 2.9.2 | Due to Evernote web clipper | | I investigated a little further the problem with fckedit in Chrome with the hints in the Chrome Developer Javascript window for debugging, and it seems the problem occurs when I have the Evernote web clipper extension enabled. If I disable it, I am able to make entries on any server, otherwise the cursor is missing and there is no way to enter text as reported in an earlier thread that I inadvertently failed to reply to. |
|
67647
|
Sun Jan 12 04:48:12 2014 |
| Hung Dao | hungtdao@yahoo.com | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
| 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. |
| Attachment 1: test.jpg
|
|
| Attachment 2: test2.jpg
|
|
|
67648
|
Mon Jan 13 09:01:31 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
|
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.
|
Yes, the alarm() function is wrong here. I removed it from the Windows version and committed the code to GIT. |
|
67649
|
Mon Jan 13 09:30:09 2014 |
| Stefan Ritt | stefan.ritt@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.
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 |
|