Re: Defunct daemons, posted by David Pilgram on Sat Mar 29 13:14:44 2014
|
Further work suggests that the type of pdf file might matter, as I have now seen the defunct daemon after
adding the first pdf file in an entry.
However, I have also found that image manipulation (rotation, size) generates a defunct daemon.
> Hi Stefan and Andreas
>
> Yesterday I reported I had some issues with the latest elog: but now I can reproduce one.
> elog 2.9.2-a738232
>
> I started a new entry, and attached three pdf files. I did not get the problem of not seeing the png thumnbnail
> this time, although that is annoying if you want/need to adjust the thumbnail image before submitting.
>
> However, if I then look at the running processes, I have the following listed (ps -A)
>
> 23677 tty1 00:00:04 elogd
> 23809 tty1 00:00:00 elogd <defunct>
> 23825 tty1 00:00:00 elogd <defunct>
> 23847 pts/0 00:00:00 ps
>
> 23677 was when I started the elogd daemon, having killed off the previous daemon etc for test purposes.
>
> 23809 and 23825 appeared after a couple of pdfs were added (second and third ones to be precise). They can only
> be killed off by killing off the original running daemon. It appears that attaching a second and further pdf
> attachments to any entry generates an elogd <defunct> in the processes list, although attaching a jpg in the
> middle of a list of pdfs didn't (but the next pdf did). This is happening while adding attachments, that is the
> Submit button has yet to be pressed, so it seems to be generated when the pdf file is being processed for some
> reason.
>
> You can end up with quite a stack of these in the process list!
>
> I never saw this behaviour with the previous version I was running, SVN2475 I think.
>
>
> By the way, I still cannot send an attachment over to this server (showing a screenshot) without the 502 error. |
Re: error message "Command Config is not allowed" after registering, posted by Mark Bergman on Wed Apr 2 19:17:31 2014
|
Mark Bergman wrote: |
After registering, elog displays a page with the message:
Error: Command "Config" is not allowed for user ""
However, the registration is successful. This causes confusion, and results in users registering multiple times.
In the elogd.conf file, I have the directive:
Allow Config = bergman
Any suggestions?
|
Is anyone else seeing this? It's very confusing to new users.
|
Passing html code for table using elog command, posted by Remington Tyler Thornton on Thu May 22 21:39:55 2014
|
Hey,
I am testing out automated entries using elog on the command line. The file I pass has html code for a table; the resulting entry shows the html code for the table instead of generating the table. Is there a way to make elog parse the code to show a formatted table?
Thanks in advance. |
Re: Passing html code for table using elog command, posted by Andreas Luedeke on Mon May 26 09:55:06 2014
|
Remington Tyler Thornton wrote: |
Hey,
I am testing out automated entries using elog on the command line. The file I pass has html code for a table; the resulting entry shows the html code for the table instead of generating the table. Is there a way to make elog parse the code to show a formatted table?
Thanks in advance.
|
⇄
English (auto-detected) » English
The elog command has the option "-n <n>" to tell elog, what type of text it should expect.
[-n 0|1|2] Encoding: 0:ELcode,1:plain,2:HTML
⇄
English (auto-detected) » English
You'll find it explained in the documentation https://midas.psi.ch/elog/userguide.html#misc
It is necessary for elog to know the type of encoding, otherwise it would not show non-html content correctly. |
Re: Unable to resize images in browser, posted by Matt Deller on Thu Jun 19 09:35:20 2014
|
Stefan Ritt wrote: |
Matthew Deller wrote: | I am unable to resize/ manipulate images in browser. Image Magick detected Version: ImageMagick 6.6.9-7 2012-08-17.
Output when running elog with verbose option shows buffer overflow when resize attempted:
[[Going to execute: /bin/sh -c "identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png'" > /tmp/elog-shell 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
*** buffer overflow detected ***: elogd terminated
Any ideas how to fix this? I'm not sure if this is a problem with the elog / Ubuntu / Image Magick? |
What happens if you execute the command manually, like
$ identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png
The "identify" command just checks the size in pixels of your image and expects something like 800x600. Let me know if this command returns something completely different.
/Stefan |
Sorry for very late reply. I recently rebuilt our server. Elog 2-9-2, new machine, new OS (Ubuntu 14.04), new version of ImageMagick (6.7.7-10), but I'm having the same unresolved problem. identify -format from the command line returns 645x860 (as it should). Any ideas?
-Matt |
New entries remotely?, posted by Daniel Roldan on Tue Jul 29 16:20:16 2014
|
Hi all,
I would like to create a new entry remotely.
I would like that when the macro run, the macro automatically create a new entry in my Elog.
I was searching, but i don't saw any thing about this.
Is possible to do a new entry remotely?
Thanks for all. |
Re: New entries remotely?, posted by Stefan Ritt on Tue Jul 29 16:53:18 2014
|
Daniel Roldan wrote: |
Hi all,
I would like to create a new entry remotely.
I would like that when the macro run, the macro automatically create a new entry in my Elog.
I was searching, but i don't saw any thing about this.
Is possible to do a new entry remotely?
Thanks for all.
|
Use the "elog" command line utility as described here under tips & tricks: http://midas.psi.ch/elog/userguide.html |
Re: Preset Text, posted by Andreas Luedeke on Sat Aug 9 06:40:35 2014
|
mike cianci wrote: |
Sorry for the novice question, but can anyone tell me where the ".txt" document is suppose to reside for the "Preset text" statement to find it? I have a "test.txt" document in the "Template" file but all "Preset text = test.txt" does is print "test.txt" in the comment section.
Thanks, Mike
|
I always chose the safe solution: I provide the full path to the document. For example (under Linux):
Preset text = /usr/local/elog/logbooks/inc/test.txt
⇄
English (auto-detected) » English
⇄
English (auto-detected) » English
|