ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67523
|
Mon Jun 3 15:53:22 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.2 | Re: 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 |
| Martin Rongen | martin.rongen@rwth-aachen.de | Info | Linux | 2.6.0 | Re: "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 |
| Martin Rongen | martin.rongen@rwth-aachen.de | Question | Linux | 2.9.2 | Daemonizing 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 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | Unknown | Re: 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. |
67519
|
Sat Jun 1 20:20:03 2013 |
| Norm | normthompson@yahoo.com | Bug report | Windows | Unknown | Re: Application failed to initialize properly |
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! |
67518
|
Fri May 31 11:41:48 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug fix | All | 2.9.2-2481 | Re: Export entries to XLS or CSV? |
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
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
|
Attachment 1: diff.txt
|
11645,11650d11644
< if (strieq(mode, "CSV3"))
< rsprintf("<input type=radio id=\"CSV3\" name=\"mode\" value=\"CSV3\" checked>");
< else
< rsprintf("<input type=radio id=\"CSV3\" name=\"mode\" value=\"CSV3\">");
< rsprintf("<label for=\"CSV3\">%s </label>\n", loc("CSV (\";\" separated) + Text"));
<
19535c19529
< csv = strieq(mode, "CSV1") || strieq(mode, "CSV2") || strieq(mode, "CSV3");
---
> csv = strieq(mode, "CSV1") || strieq(mode, "CSV2");
20266,20268c20260
< } else {
< if (strieq(mode, "CSV3"))
< rsprintf(";\"Text\"");
---
> } else
20270d20261
< }
20973,20987c20964
< } else {
< if (strlen(text)>0 && strieq(mode, "CSV3")) {
< rsprintf(";");
< strlcpy(str, text, sizeof(str));
< rsputs("\"");
< pt1 = str;
< while ((pt2 = strchr(pt1, '"')) != NULL) {
< *pt2 = 0;
< rsputs(pt1);
< rsputs("\"\"");
< pt1 = pt2 + 1;
< }
< rsputs(pt1);
< rsputs("\"");
< }
---
> } else
20989d20965
< }
|
67517
|
Thu May 30 22:52:51 2013 |
| Jim Tinlin | jim@tinlin.net | Question | Windows | ELOG V2.7. | Re: Export entries to XLS or CSV? |
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
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" |
67516
|
Wed May 29 14:57:23 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | 2.8-2350 | Re: hyperlink other elog posts |
Remington Tyler Thornton wrote: |
I am on an experiment that used ELOG for all documentation and meeting notes. In our meeting notes we link to elog posts that had been discussed during the meeting. We had done this by hyperlinking the URL to the entry. Recently we had to move our logbook to another machine and so none of our hyperlinks work since the URLs have changed. I noticed that when one creates a new entry in the subject they can reference another post. Is there a way to link another elog in the body of the elog by using its logbook name and id number without having to use a URL?
Thanks in advance
|
This is one of the rare cases where it helps to read the manual: https://midas.psi.ch/elog/userguide.html#add (You may need to upgrade to elog 2.9)
If you want to replace the old URLs with the new ones, you can edit the logbook files with the entries. The attached script allows you to do so easily. But be careful, try it on a copy of your data first.
 ⇄
Detect language » English
⇄
Detect language » English
Using:
regreplace "<old-url>" "<new-url>" *a.log
I hope this helps.
Andreas |
Attachment 1: regreplace
|
#!/bin/bash
if [ $# -lt 3 ]
then
echo "using: $0 <search-for> <replace-with> <file-list>"
exit
fi
if [ "$1" = "-f" ]
then
flag="-f"
shift 1
else
flag="-i"
fi
search="$(echo "$1"|awk '{gsub("\\","\\\\");gsub("/","\\/");print $0}')"
replace="$(echo "$2"|awk '{gsub("\\","\\\\");gsub("[$]","\\$");gsub("/","\\/");print $0}')"
shift 2
echo "replace \"$search\" with \"$replace\" in the files "
bold=`tput smso`
offbold=`tput rmso`
for file in $(grep -l "$search" "$@")
do
tmp=/tmp/regreplace_$(basename $file)
sed "s/${search}/${replace}/g" $file >$tmp
echo "${bold}diffs of $file$offbold ('<' = before, '>' = after)"
diff $file $tmp
cp $flag $tmp $file
rm -f $tmp
done
|
|