ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
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
|
|
67515
|
Wed May 29 08:38:04 2013 |
 | UlfO | ulf.olsson@dynamate.se | Question | Windows | 2.9.2-2455 | Filter and sorting | Hi,
We have a fire preventive team at our company doing periodic inspections of our various corporate buildings.
If they find a deviation they want to register this somewhere.
So I thought E-log would be nice to use in this case.
The way the fire preventive team inspection works is building by building.
All the buildings has numbers.
So they want to be able to select a buildingnumber in E-log and filter on open,ongoing and closed records when they do their inspections.
And they also wants the filtering to stay on that choosen buildingnumber despite if they delete or add new entries.
I know that you can have a default startview in E-log but this view is static.
Is it possible to do this in E-log?
|
|
67514
|
Tue May 28 19:01:42 2013 |
| Remington Tyler Thornton | rtthornt@indiana.edu | Info | Linux | 2.8-2350 | hyperlink other elog posts | 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 |
|
67513
|
Tue May 28 09:16:18 2013 |
| Razvan Gornea | gornea@zoho.com | Question | Linux | 2.9.2-2455 | Elog command line problem | I'm trying to use the command line to post automatically entries from a web based calendar. I run elogd behind SSL with user/pass configuration. I created an account for the calendar and used the following command line.
[gornea@lheppc63 ~]
$ elog -v -s -a Subject=Test -a Type=Notice -a Category=Planning -h svn.lhep.unibe.ch -p 443 -l "LHEP EXO General" -u calendar ******** "SORRY for SPAMMING! Testing automated posts from command line"
It seems like all parameters are OK but for some reason the connection gets closed. Anybody has an idea why? The SSL certificate is not valid and on the web page users have first to accept it. Can this explain the problem? Is there a flag for elog command line to instruct it to ignore SSL warnings? Thanks a lot!
Command line output:
Successfully connected to host svn.lhep.unibe.ch, port 443
Request sent to host:
POST /LHEP+EXO+General/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------16B1637A4CDBB4E6448003F4
Host: lheppc63.lhep.unibe.ch
User-Agent: ELOG
Content-Length: 1105
Content sent to host:
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="cmd"
Submit
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="unm"
calendar
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="upwd"
Z28yQjUyIQ==
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="exp"
LHEP EXO General
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="encoding"
ELCode
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Subject"
Test
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Type"
Notice
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Category"
Planning
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Text"
SORRY for SPAMMING! Testing automated posts from command line
---------------------------16B1637A4CDBB4E6448003F4
Response received:
HTTP/1.1 302 Found
Server: ELOG HTTP 2.9.2-2455
Location: https://svn.lhep.unibe.ch/LHEP+EXO+General/
Connection: Close
<html>redir</html>
Message successfully transmitted, ID=
[gornea@lheppc63 ~]
$
|
|