Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 209 of 729  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject
  67527   Tue Jun 4 13:26:02 2013 Reply Martin Rongenmartin.rongen@rwth-aachen.deQuestionLinux2.9.2Re: Daemonizing vs. shell execution

Stefan Ritt wrote:

Martin Rongen wrote:

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

Usually the problem comes from the fact that a daemon runs from the root directory ('/') by definition. I might not find your scripts if they are not in the path. Try to call them explicitly with the ful path like "/usr/local/elog/script.sh".

/Stefan 

 I didn't know that. Thanks for the quick response. I have it working now :)

  67526   Tue Jun 4 12:38:01 2013 Reply Stefan Rittstefan.ritt@psi.chBug fixAll2.9.2-2481Re: Export entries to XLS or CSV?

Andreas Luedeke wrote:

Jim Tinlin wrote:

Andreas Luedeke wrote:

scogordo wrote:

I've been asked to export one of our logbooks to xls or csv. Doable?

Thanks,
Scott

Hi Scott,

yes, every user can export entries using the "find" command.
Just select the export format in the first line

Export to:  

 
Detect language » English
 
 
Detect language » English
 
 
Detect language » English
 
 
Detect language » English
 
 
Detect language » English
 

I often use the XML Format, but CSV is fine if you just want to import the entries to some spreadsheet program.

I was shocked to find out that this feature has not yet made it into the documentation?!? But it is that simple to use that there is not much to document.

There is even an "Import" command, to reimport entries from a file. But this is tricky to use: if you have fields of type date or datetime, then you have to convert those fields in the proper format.

I tried EXPORTING logbooks as .csv but have not been fully successful.  Elog seems to only export the data entered for various fields with the exception of the text field.

Here is an example export from my logbook (used to track simulator problems), I would like to also export the TEXT field so it can be used by my managers in excel...but as you can see there is no entry for "TEXT" fields...

Thanks in advance!

"Message ID","Date","Author","Type","Status","Priority"

107,Thu  30 May 2013 11:28:57 -0700,"Jim Tinlin","Graphic Display","Evaluated","Low"

106,Thu  30 May 2013 10:02:24 -0700,"Jim Tinlin","Graphic Display","Identified","Low"

105,Thu  30 May 2013 08:07:27 -0700,"Jim Tinlin","Problem ID","Identified","Medium"

104,Thu  30 May 2013 08:04:30 -0700,"Jim Tinlin","Problem ID","Identified","Medium"

103,Wed  29 May 2013 09:36:11 -0700,"Jim Tinlin","Problem ID","Evaluated","High"

102,Wed  29 May 2013 08:58:02 -0700,"Jim Tinlin","Problem ID","Evaluated","High"

Yes, you're right: the text field is only exported in XML and Raw mode.
It is questionable how EXCEL should cope with HTML or ELCode output from the text fields.
But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.
 
I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'.
(This string has not yet been added to the localization.)
As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text.
Of course the spreadsheet programs just display the HTML source.
 
Stefan, do you think this should be added to the official branch?

 

 
Detect language » English
 
 
Detect language » English
 

Hi Jim, can you confirm that this works for you? If so, I'm willing to incorporate the patch into the distribution. 

  67525   Tue Jun 4 12:03:18 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2-2475Re: Sorting by numeric attribute (not entry ID).
> By default, elog enties are sorted by their ID number.  When viewing a logbook in Full or Summary, they are
> shown in strict order of ID.  In Threaded, entries are shown in strict order of ID for the latest entry of each
> thread, and then previous entries (in reply to) back from the latest one.  
> 
> In collapsed mode, it is only the starting entry of each thread is shown (or the latest one if "collapse to
> last" chosen, but that's a detail).
> 
> I have a couple of logbooks where I'd like the default sorting to be by another numeric attribute that I enter. 
> 
> Now this works fine in Full or Summary mode.  In threaded mode (e.g. default for this forum, where every entry
> is shown but are grouped by thread), it works in as much as all the entres are there and in order, but it
> doesn't quite look the same as when sorting by ID - the replies are not each offset further right beneath the
> entry it is in reply to, but all just slightly offset to the first entry.  
> 
> If you try to [completely] collapse the threaded mode to just one line per threaded topic - it doesn't.  Looks
> (almost) the same as threaded.
> 
> I was hoping to get the list of entries collapsed to one line per thread, in order of the numeric attribute, but
> I cannot seem to get this to happen.   Have I missed something here?  Or is it possible at all?

This is not possible at the moment, but I will add it to the wish list.
  67524   Mon Jun 3 20:02:38 2013 Question David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.9.2-2475Sorting by numeric attribute (not entry ID).
By default, elog enties are sorted by their ID number.  When viewing a logbook in Full or Summary, they are
shown in strict order of ID.  In Threaded, entries are shown in strict order of ID for the latest entry of each
thread, and then previous entries (in reply to) back from the latest one.  

In collapsed mode, it is only the starting entry of each thread is shown (or the latest one if "collapse to
last" chosen, but that's a detail).

I have a couple of logbooks where I'd like the default sorting to be by another numeric attribute that I enter. 

Now this works fine in Full or Summary mode.  In threaded mode (e.g. default for this forum, where every entry
is shown but are grouped by thread), it works in as much as all the entres are there and in order, but it
doesn't quite look the same as when sorting by ID - the replies are not each offset further right beneath the
entry it is in reply to, but all just slightly offset to the first entry.  

If you try to [completely] collapse the threaded mode to just one line per threaded topic - it doesn't.  Looks
(almost) the same as threaded.

I was hoping to get the list of entries collapsed to one line per thread, in order of the numeric attribute, but
I cannot seem to get this to happen.   Have I missed something here?  Or is it possible at all?
  67523   Mon Jun 3 15:53:22 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2Re: Daemonizing vs. shell execution

Martin Rongen wrote:

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

Usually the problem comes from the fact that a daemon runs from the root directory ('/') by definition. I might not find your scripts if they are not in the path. Try to call them explicitly with the ful path like "/usr/local/elog/script.sh".

/Stefan 

  67522   Mon Jun 3 15:49:33 2013 Reply Martin Rongenmartin.rongen@rwth-aachen.deInfoLinux2.6.0Re: "full" only changes color

Kees Bol wrote:
Hi,
I have the strange problem that when changing to "full"-diplaymode the output looks the same as with "summary", only the color is different. The texts don't appear.
Any idea what can cause this behaviour?

thanks
Kees Bol



I now have the same problem in 2.9.2. Attached please find the elogd.cfg

Best regards
Martin
Attachment 1: elogd.cfg
[global]
port = 8080
Logbook Tabs=0 ;this is the only logbook here

[EDM beamtime logbook]
Theme = default
Title image URL = http://lx3b58:8888/EDM+beamtime+logbook/
Password file = passwd
Self register = 0
Admin user = jedi_admin

Menu commands = New, Reply, Find, Login, Config
Guest menu commands = New, Reply, Find, Login
List Menu commands = New, Find, Help, Logout, Config
Guest List Menu commands = New, Find, Last Day, Help, Login

Attributes = entry type, run number , Start, Stop,  run type, operators, shift, COSY state, DAQ state, comments
List display =Date, entry type, comments, run number, run type, operators, shift, COSY state, DAQ state
Guest List display =Date, entry type, comments, run number, run type, operators, shift, COSY state, DAQ state

Options entry type = run{1}, comment{2}, shift summary{3}, reply{4}
Preset entry type = run
Preset on reply Entry type = reply
Subst on reply comments = Re: $comments
{1,2,3} Options entry type = run{1}, comment{2}, shift summary{3}
{4} Options entry type =  reply
	
Cell Style entry type run = background-color:#b9ca67
Cell Style entry type comment = background-color:#bd9c73
Cell Style entry type shift summary = background-color:#d6b6e6
Cell Style entry type reply = background-color:#5cb8ff

Required Attributes = entry type

{1} Show Attributes Edit= entry type, run number , Start, Stop,  run type, operators, shift, COSY state, DAQ state, comments
{1} Required Attributes = operators, shift, run number, run type, COSY state, DAQ state

{2} Show Attributes Edit= entry type, operators, shift, COSY state, DAQ state, comments
{2} Required Attributes = operators, shift, COSY state, DAQ state

{3} Show Attributes Edit= entry type, operators, shift, COSY state, DAQ state, comments
{3} Required Attributes = operators, shift, COSY state, DAQ state

{4} Show Attributes Edit= entry type, operators, comments, run number, run type
{4} Required Attributes = operators

Options Shift = Morning, Day, Night
Options run type = Test entry, ED SCT
Options COSY state = Problem, Maintenance, Running
Options DAQ state = OK, Faulty

Cell Style COSY state Problem = background-color:red
Cell Style COSY state Maintenance =  background-color:yellow 
Cell Style COSY state Running = background-color:green
Cell Style DAQ state OK = background-color:green
Cell Style DAQ state Faulty = background-color:red

Extendable options = run type

Fixed Attributes Edit = run type, COSY state, DAQ state, entry type, run number, Start, Stop, shift 
Fixed Attributes Reply = entry type, run type, COSY state, DAQ state, entry type, run number, Start, Stop, shift, comments

Page Title = EDM beamtime logbook
Reverse sort = 1
Quick filter = run number

{1} Preset run number = $shell(bash preset_run.sh 2>/dev/null)
;looks up last run number in logbook folder and increments


;Type run number = numeric
Type Start  = datetime
Type Stop = datetime
{1} Preset Start =  $utcdate
{1} Preset Stop =   $utcdate

Thumbnail size=500

Summary lines = 0 ;so it doesnt appear on front page

Search all logbooks = 0

Default encoding = 2 ; html-necessary for latex
Allowed encoding = 4 ; only html allowed

Time format = %A, %B %d, %Y, %H:%M 
{1} Execute new = bash append_root.sh $run number
 ; adds link to root-file

RSS Title = run $comment, posted by $operators on $entry time

; No Email notification
Suppress Email to users = 1

  67521   Mon Jun 3 15:44:46 2013 Entry Martin Rongenmartin.rongen@rwth-aachen.deQuestionLinux2.9.2Daemonizing vs. shell execution

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

  67520   Mon Jun 3 13:56:35 2013 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportWindowsUnknownRe: Application failed to initialize properly

Norm wrote:

Andreas Luedeke wrote:

Norm wrote:

I attempted to install the newest version of elog on our site elog server from an old old version.  Around 2008 I believe.  I then received an application failed to initialize properly 0xc0150002 after installing the newest version.  I then tried installing the Feb 2013 version and received the same message.  Panicked, I rolled back our server to its state yesterday.  I would like to update our elog software, anyone know why I am receiving this error??

 Hi Norm. I have not much experience with windows, but I can give you my two cent on how to proceed:

  • Check the old elogd version. It is shown at the bottom of your elog web page (this forum shows ELOG V2.9.2-2475).
  • Copy your logbook data to a different PC, maybe your office PC.
  • Then compile the latest elog on your office PC, run it with the copied data and access it as http://localhost:8080 (or whatever port number you are using)
  • If it is still crashing: re-compile it using "make debug" and run it from a debugger (I don't know any C-debugger for Windows). Post the precise error message.
 
Detect language » English
 

Good luck!

Andreas,

We do not have the current revision at the bottom of any of the pages.  Is there another way I can find out the current revision I'm using?

Thanks!

Try:

/usr/local/sbin/elogd -h

 
Detect language » English
 

This is the path for Linux, it is likely different on Windows. But you could just run "elogd -h" in the directory where you compile elogd.

It should print out the version in the first line.

ELOG V3.1.4-80633ba