Re: Mysterious Emboldened lines in threaded (collapsed) mode, posted by Andreas Luedeke on Tue Sep 18 10:05:27 2012
|
> I upgraded my system, including the version of Firefox.
> [...]
> Sorry this is a bit rambling, but its very hard to describe!
A picture can say more than thousand words.
Can you reproduce this with a simple configuration?
If yes, can you attach the configuration, the *a.log files,
a description of what firefox version you're using and please:
some screenshots of "before" and "after"?
Thanks!
Andreas |
Re: Importing XML, posted by Andreas Luedeke on Thu Oct 4 11:35:12 2012
|
| David Chastain wrote: |
|
[...] Basically, I am trying to take spreadsheet data, convert it into XML and upload it as a logbook so I don't have to perform lots of data entry. I also tried .CSV but have had no luck. Any thoughts or ideas?
|
I've successfully imported a large amount of entries from old non-ELOG logbooks via XML.
The only problem that I did run into was the date format: ELOG is very restrictive on the imported format; it has to be either "MM/DD/YY(YY) (HH:MM:SS)" or "DD.MM.YY(YY) (HH:MM:SS)".
When you export entries ELOG honours the "Date format" that you've specified in your elogd.cfg, therefore you cannot import the exported file until you reformat the date in the file.
Andreas |
|
Re: Comment avoir elog en français II, posted by Andreas Luedeke on Mon Oct 29 07:52:07 2012
|
| 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. |
|
Re: Comment avoir elog en français II [solved almost], posted by Andreas Luedeke on Mon Oct 29 17:27:12 2012
|
| 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
|
|
Re: Elogd hangs while uploading bmp attachment, posted by Andreas Luedeke on Wed Oct 31 17:20:14 2012
|
| David Wallis wrote: |
|
I'm running elog 2.9.2 on a Red Hat 6.3 server. This installation has been running for some time on a Solaris server, and was recently moved to the RHEL server.
When a user tries to upload a .bmp attachment, the upload never completes, eventually timing out with a proxy error. At that point, the elogd process stops responding to requests and needs to be restarted. Nothing is in the log file other than a "Listening" message when elogd starts up. Png and pdf attachments seem to work fine. I was able to convert an image from .bmp to .png and upload, but that's not practical for my user.
ImageMagick 6.5.4-7 is installed on the server. Everything else seems to be working normally.
Is this a known problem, or have I missed something that needs to be installed on the RHEL server?
|
Hi David,
I've just tested it on my server running ELOG V2.9.0-2414, Scientific Linux 5.7 (RHEL 5.?) with ImageMagick 6.2.8: the attachment is uploaded but no preview is generated. No problem with the server.
What was the behaviour of your Solaris system? Did it upload? Did it create a preview?
BMP files are - in my experience - often very large. Could it be a file size problem? Did you try with a small BMP image?
Kind Regards
Andreas
⇄
Detect language » English
|
ELOG crash related to Kerberos, SSL and Login users, posted by Andreas Luedeke on Mon Nov 26 15:57:49 2012 
|
I'm using Kerberos and SSL and experience problems with individual setting of "Login user =" for different logbooks.
Sometimes (not every time, but most times) the server crashes under the following condition:
When I login at one logbook and then change to a logbook, that has a restricted "Login user" list with my login
name not in it. It created the following GDB output:
Program received signal SIGSEGV, Segmentation fault.
show_elog_list (lbs=0x916b768, past_n=0, last_n=0, page_n=0, default_page=1, info=0x0) at src/elogd.c:19793
19793 message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;
Expected behaviour would be to show me the login page with the error message:
"you don't have access to this logbook".
This message is never shown for the attached configuration file.
If I remove the "Guest" commands for logbook "TestB" then elogd behaves properly.
For the moment I've just disabled "Login user" settings.
Regards
Andreas |
|
Re: ELOG crash related to Kerberos, SSL and Login users, posted by Andreas Luedeke on Mon Nov 26 17:12:32 2012
|
Forget the previous post:
I cannot reproduce the problem with the latest version of elogd (2.9.2-2475). |
|
Re: Error 554 MailTransferAgentServer ESMTP not accepting messages, posted by Andreas Luedeke on Tue Dec 11 09:00:36 2012
|
Just my 2 cent: did you try to reproduce the problem with the latest ELOG version 2.9.2?
Kind Regards
Andreas |