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! |
|
67638
|
Mon Dec 16 11:16:33 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.2 | Re: How to property install? |
| 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
|
|
67637
|
Sat Dec 14 00:22:52 2013 |
 | Ryan Blakeslee | rb@blakesys.net | Question | Linux | 2.9.2 | How to property install? | 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.) |
|
67636
|
Thu Dec 12 16:03:07 2013 |
| Paulo Moraga | pnmoraga@gmail.com | Question | Windows | V2.9.2-245 | Re: Multiple tab |
| Paulo Moraga wrote: |
|
Hi noob question I was looking for a config but i cant make it, how to i make multitab logbook like this page?
Like in Discussion there are forum,config examples,contribution and vulnerabilities under it
Thanks
|
NVM found it Thanks |
|
67635
|
Thu Dec 12 15:10:43 2013 |
| Paulo Moraga | pnmoraga@gmail.com | Question | Windows | V2.9.2-245 | Multiple tab | Hi noob question I was looking for a config but i cant make it, how to i make multitab logbook like this page?
Like in Discussion there are forum,config examples,contribution and vulnerabilities under it
Thanks
|
| Attachment 1: multitab.JPG
|
|
|
67634
|
Tue Dec 3 11:30:43 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 2.9.2 | Re: Crash report involving propagate and replies |
|
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
|
|
67633
|
Mon Dec 2 23:02:45 2013 |
| Stephen | swgallman@bpa.gov | Bug report | Windows | 2.9.2 | 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.
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. |
|
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.
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?
|
⇄
English (auto-detected) » English
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.
⇄
English (auto-detected) » English
Andreas
⇄
English (auto-detected) » English
⇄
English (auto-detected) » English
|
| Attachment 1: elogd.cfg
|
[global]
SMTP host = mail.psi.ch
Authentication = File
port = 443
SSL = 1
Allow passwordchange = 1
Self Register = 0
Logfile = /usr/local/elog/elog.log
[CSM Log]
; Main settings
Password file = /usr/local/elog/elogPw.txt
Theme = default
List Menu commands = New, Find, List, Config, Change password, Logout, Last Day
; E-mail
; Look and Feel
Use Lock = 1
Fix text = 0
Propagate Attributes = Status
Sort Attribute Options System = 1
Sort Attribute Options Sub-System = 1
List after submit = 1
Display mode = summary
Quote on reply = 1
Entries per page = 30
Refresh = 240
Default Encoding = 1
Quick filter = Date, Type, System, Sub-System, Status, subtext
Time format = %A, %B %d, %Y, %H:%M
Page Title = ELOG - $type
Reverse sort = 1
Restrict edit time = 24
ID Display = $message id
Extendable options = System, Sub-System
Type Time of Event = datetime
Preset Time of Event = $date
List Display = ID, Time of Event, Author, Type, System, Sub-System, Status
Allow branching = 0
Reply String =
Summary lines = 5
Prepend on reply = \nAdded on $date by $long_name\n\n
; Log Header
Preset Author = $long_name
Locked Attributes = Author
Preset on reply Author = $long_name
Required Attributes = Author, Type, System, Status, Time of Event
Preset on reply Time of Event = $date
Preset on edit Author = $long_name
Attributes = Time of Event, Author, Type, System, Sub-System, Status,
;Notification
Options Type = Test1{1}, Test2{2}, Test3{3}, Test4{4}, Test5{5}
Style Type Shift Change = background-color:yellow
{5} Preset Status = Closed
Options Status = Open, Closed
Cell Style Status Closed = background-color:#1f9400
Cell Style Status Open = background-color:#a10000
; Event Time options
; Type Event Time = datetime
; Subst Event Time = $date
; Options
{1} Options System = Test
; Options
{2} Options System = Test
; Options
{3} Options System = Test
; Turnover
{5} MOptions System = Test
{5} MOptions Sub-System = Test
|
| Attachment 2: elog.png
|
|
|