I'm running ELOG V2.9.2-2455. 

The elogd process continues to run, but no longer responds to requests.If, for example, I open a new browser tab and try to load the logbook, I eventually get a timeout. There is no ImageMagick "convert" process running.

 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?

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

 Hi David,

Which svn version of elog are you running - what does it say at the very bottom of the page (this forum says ELOG V2.9.0-2435); there *is* and issue about loading files and thumbnails with svn 2473, but it may also be in one or two prior to that (I found it with 2473, anyway).  Also, is elog running (taking CPU time) and not responding to anything after you try this (and you have to kill the daemon and restart), or crashing out at that point? I've had both behaviours at one time or another, for reasons I now understand, not related (I think) to this one, but the more evidence, the better chance that someone will find the problem.

David.

 Thanks for the info, David.

I do not see any *.bmp files in the logbook directory when this happens. The hang happens when the "Upload" button is hit, so there is no logbook entry yet either.

When I saw this problem come in, I was reminded of problems I have of elog crashing.  So I tried attaching a .bmp file to an entry.  In my case it did not crash, but it did not run ImageMagick either - it just gave a link as it it were a zip or tar file - that is to say no .png image had been generated and shown.   As I've never attached a .bmp file before, I don't know whether elog allows for them to be processed and a thumbnail made, a quick look in the documentation didn't enlighten me, but then I didn't look for that long either.  (I'm running 2.9.2 svn 2475, under Slackware 13 which is a version post some image processing issues I reported to Stefan - might that explain why in my case?). 

I have found that sometimes elog will crash, but effectively after it has done the action - so if it crashes when asked to move files from one logbook to another, you find the entries have been moved.  In my case, I believe the crashes are due to memory issues, nothing I can state for certain.

It would possibly help Stefan and Andreas if you can tell whether the .bmp file appears in the relivent logbook directory (usually a subdirectory of ....../logbooks) - it will have been renamed as yymmdd_hhmmss_{filename}.bmp - except, of course, the date and time will be showing not these symbols - and if the entry with which you have tried to attach this .bmp file been written - using a text viewer on the file yymmdda.log (obviously the day will be today, i.e. the one just updated as you tried the entry.   I have come across orphan attachment files in directories in my time, possibly from when elog crashed part way through an action.

(If I am stating the obvious, apologies, I don't know your level of experience with elog or linux, so trying to cover all possible levels)

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?

Andreas Luedeke wrote:

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   Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English

 I'd better put some caveats in here, then!

The two daemons on my host were never accessing the same subdirectories of /home/logbooks (this is my location, for ease of data backups (*)), and they were running with owner 'nobody', i.e. that's the owner of each directory.  In that sense they were independant, and as I was the only user, only one daemon would be working on files at any one moment. 

Next is that my system is never running for so many days uninterrupted.  The computer sometimes has to be booted into Windoze to use the CAD program, or even was just shut down and switched off.

I realise now that my earlier reply may have lead people to think they could work on the same data with two separate daemons (so as to work in their own language, but the data would be in both....) but I never meant to give that impresssion.  I've simply not tried it.  It might work on a stand-alone system, but I don't know how elog copes with multiple users accessing data at the same time - lock files?  check to see if data has been altered before allowing a submission is probably not done (it would make a branch if branches were allowed, I think) - I don't have the experience of using elog under these circumstances.  I thought Philippe Rousselot wanted a French language logbook and a separate English language one.  If I'm wrong there, sorry to raise his hopes.

Make a nice little project for someone to explore the limits, and maybe find what changes are needed.  Not necessarily to impliment it, though.

As for data corruption, never seen any, but I suppose the general warning of keep the backups well up-to-date.  I have had trouble with data, in particular moving data between logbooks, and this is one reason I have experience of how to make an elog entry using a text editor, as well as how to modify entries - to assemble scattered entries into a thread, or split a long thread into two shorter ones for ease of handling.  But I don't think those were ever connected to having two deamons running on one host, it happens when just one is running.

(*) In principle, all my data can be put on a memory stick - currently 16GB - and then I can run any linux box with full access to all my data, with the memory stick mounted on /home.