| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67081
|
Fri Jun 3 12:06:20 2011 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | 2.9.0-2414 | Re: elogd crashes when running mirror cron with SSL and KRB5 | > When I run a mirror server and both logbooks using SSL/KRB5 then the cron job causes a segmentation fault.
>
> I haven't tried to check it with a simple configuration yet.
> My set-up: two elogd on same server, one running "german" on port 444, the other "english" on port 445.
> Both are behind an apache webserver configured reverse proxy, to hide the ports for external access.
> I'll try to reproduce the fault with a "minimal configuration" soon and report again.
>
I've tried to test a simpler configuration on my local PC but failed:
all simple set-ups I've tried worked fine.
I found that the mirror cron synchronization works fine in my production set-up when I remove the line:
Mirror user = luedeke
But I can have this line in my simple test set-up and it still works fine.
Anyway: bugs closed for me. |
|
67095
|
Fri Jul 22 10:31:27 2011 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Info | All | 2.9.0 | Re: Elog client usage |
| Alan Grant wrote: |
|
I have searched the Elog forum and docs at length for actual examples of how to use the Elog client and I apologize if I missed it somehwere but could someone please provide some actual examples of how the parmeters are used? I haven't had much success setting it up just going by the Elog command syntax quide.
What I intend to do is load a raw text file into an active logbook directly, either one line at at time or batched from a text file ("m" option).
Also, I saw a Perl script contribution somewhere on the site which appears to offer the same functionality as the above util. Just wondering why there would be two methods, and which might be the best for me to use? Thank you.
|
I suppose you have your demon "elogd" running and you can connect to your logbook via the web interface?
Then you can use the "elog" command to upload a text file as one entry.
If you want to split the text file to one-entry-per-line, you need to write a batch script to do that.
The usage of the "elog" command is descibed in the ELOG User's Guide: https://midas.psi.ch/elog/userguide.html#misc
The command line for "elog" has to define all "Required attributes" with "-a ..."
elog -h <host> -p <port> -l <logbook> -u <user> <password> -a <attribute>=<value> -n 1 -m <text-file>
<port> can be omitted if port 80 is used, "-u <user> <password>" can be omitted if anonymous entry creation is allowed.
Here's an example to write to the demo logbook at midas (local text file /tmp/hello.txt contains "hello world")
elog -h midas.psi.ch -l Linux+Demo -d elogs -a Author=nobody -a Type=Other -a Category=test -a "Subject=hello" -m /tmp/hello.txt
I hope this helps.
PS: please never refer to a location as "somewhere on the site". |
|
67097
|
Wed Jul 27 04:36:40 2011 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | All | 2.9.0 | Re: Elog client usage |
| Alan Grant wrote: |
|
| Andreas Luedeke wrote: |
|
| Alan Grant wrote: |
|
What I intend to do is load a raw text file into an active logbook directly, either one line at at time or batched from a text file ("m" option). [...]
|
[...] The usage of the "elog" command is descibed in the ELOG User's Guide: https://midas.psi.ch/elog/userguide.html#misc |
[...] I typed the following, observing case sensitivity, then press enter and at this point it just hangs:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11"
|
You wrote you want to upload a text file, then you need to add at the end "-m <file>". E.g. if the text-file is named "C:text.txt", then write:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11" -n 1 -m C:text.txt
The "-n 1" is just to tell elog to upload plain text. If you do not specify "-m <file>" then it expects input from a pipe and therefore hangs. If you don't know what "input from a pipe" means then ALWAYS use the "-m <file>" option.
PS: if "Ticket date" is of the format "date" then it is sensitive to the formatting of the date string. "Jul26/11" is likely not a legal date format. Better do not specify it for the first test. Write instead:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -n 1 -m C:text.txt
PPS: do you really use a sub-directory "elog" instead of the default location "logbooks" for your ELOG logbook files? If not, then leave out this option, too.
elog -h localhost -p 8080 -l Tartan+Tow+Log -n 1 -m C:text.txt
|
|
67360
|
Mon Oct 29 07:52:07 2012 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | Windows | latest | Re: Comment avoir elog en français II |
| Philippe Rousselot wrote: |
|
Bonjour,
tout est dans le titre.
Merci
For those who speak strange languages, I asked how to get a french version of elog.
By the way, this is my second mail because I forgot to give an icon to the first mail, and when I hit Back to do so, my text was erased. Bug or normal obnoxious attitude of my browser ?
Thanks in advance
Philippe
|
ELOG comes "internationalised": you just need to set your desired language in the configuration files.
Language = french
in the configuration file elogd.cfg does the trick.
If you are capable to read the English language (which I suppose  ), then I would recommend reading the manual, e.g. https://midas.psi.ch/elog/config.html#global  ⇄
Detect language » English
PS: I happened to have the same problem (text erased after "back") when I had javascript disabled in the browser. If you have it enabled, you'll get a popup window that tells you what mandatory fields are missing in your post. Then you'll not need to use the back button. |
|
67364
|
Mon Oct 29 17:27:12 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Windows | latest | Re: Comment avoir elog en français II [solved almost] |
| David Pilgram wrote: |
|
May I make a suggestion here? Something I do for other reasons. I run two separate elog daemons, each with their own configuration files. In this case you could have one configuration file tout en française, and the other in English. This gets around the language setting being in the Global section of the configuration file elog.cfg
Of course this needs a little planning, for example a small script/batch file to start up each daemon with the correct config file. - so on my linux system, I start one with
/usr/local/sbin/elogd -p 8080 -c /home/logbooks/elogd0.cfg -d /home/logbooks
and the other with
/usr/local/sbin/elogd -p 8081 -c /home/logbooks/elogd1.cfg -d /home/logbooks
The disadvantage is that you cannot click between French and English by the tabs along the top of the elog page, you'd have to switch between browser windows.
Hope this helps.
David.
|
Does this work nice and stable for you? I've tried at the beginning to run two server on one host, one in German and the other in English.
I experienced occasional server crashes (every few days) and assumed that they were related to two mirrors running on the same host.
A mirror server just for a second language was not of big importance to me, therefore I did shut down the mirror server.
And the server stopped crashing then. Was that just coincidence?
I recognised that you are not running a mirror, you let both logbook processes access the same data. Is that save?
Did you ever see data corruption from two processes modifying the same data? Or is one of the ELOG servers not used much?
Thanks for sharing your experience!
Andreas
⇄
Detect language » English
|
|
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
|
|
67705
|
Wed Sep 17 17:45:18 2014 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Info | All | V2.9.2-24 | Re: Sort by date prior to 2002 |
| Chris Jennings wrote: |
|
| Chris Jennings wrote: |
|
I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old?
Thanks in advance,
Chris
|
Sorry, my mistake. The cutoff date is anything before September 9th 2001 does not sort.
|
I think I remember that this has been discussed earlier: it is a little bug in elogd.
You can see where it comes from if you type in the little command 'date -d "9-Sep-2001 3:46:40" +%s'
Converted to "seconds of the epoche" (seconds since 1970-01-01 00:00:00 UTC) the date "9-Sep-2001 3:46:40" has one digit more than "9-Sep-2001 3:46:39".
Since elog makes a string comparison, suddenly 1'000'000'000 is less than 999'999'999; therefore the wrong sorting.
Workaround: you can modify your old entries and add a leading zero to all entries where your specific date field starts with a '9'.
Stefan: you should fix it at least well before 20-Nov-2286 18:46:40, when the same bug strikes again! |
|
67960
|
Fri Jun 5 19:01:05 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | All | 3.1.0+ | Re: Different way CSS files are handled | Hi Stefan,
there is a little problem with the Makefile (on SL5 and SL6): the following line:
@$(INSTALL) -m 0644 themes/default/* $(ELOGDIR)/themes/default/
/usr/bin/install: omitting directory `themes/default/icons'
make: *** [install] Error 1
When I go back to the old Makefile construct:
@$(INSTALL) -m 0644 themes/default/icons/* $(ELOGDIR)/themes/default/icons/
@for file in `find themes/default -type f` ;\
do \
if [ ! -f $(ELOGDIR)/themes/default/`basename $$file` ]; then \
$(INSTALL) -m 0644 $$file $(ELOGDIR)/themes/default/`basename $$file` ; \
fi; \
done
then it seems to work again.
Cheers
Andreas
| Stefan Ritt wrote: |
|
Hi,
I just implemented a different way CSS files are handled in ELOG. Previously, we had the default.css, which could be adjusted for specific needs. Some people did that (like myself). So I changed a few colors etc. When I now implement a new feature in elog, it might need a new CSS class which I put in default.css. But this means that people who have modified this file get it either overwritten, or do not get the new styles.
In order to fix this, the default.css is now called elog.css and is always inluded in any ELOG page. If one specifies a CSS file with "CSS = <file.css>", then this CSS file is loaded in addition to elog.css. So one can put only the modifications into that file and inherits all the rest from elog.css. If new features come in elog.css, the installation with the personalized CSS file will then get the new features from the new elog.css automatically, and just overwrite a few settings in the personalized file. Here is an example:
elog.css:
td {
color:black;
font-size:12px;
}
Personalized file special.css, activated with "CSS = special.css" in the elogd.cfg file:
td {
font-size:18px;
}
This personalized file now overwrites the font size from elog.css to 18 pixel, while maintaining all the rest from elogd.css.
The modification is committed to GIT and will be contained in the next release of elog.
/Stefan
|
|
|