| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69762
|
Fri Mar 15 05:13:42 2024 |
 | Andreas Warburton | andreas.warburton@mcgill.ca | Bug report | Mac OSX | 3.1.5 | Re: Runaway bogus attachment counts in Summary view attachment column |
Thanks a lot Stefan, for fixing this so quickly! I'm now running 3.1.5 fe60aaf0, with the phantom-attachment-count issue in the Summary view now resolved. Cheers, Andreas W.
| Stefan Ritt wrote: |
|
The problem with the attachment paperclips has been fixed in the current version.
Stefan
| Andreas Warburton wrote: |
|
On a new MacBook Pro (Silicon M3), I installed version 3.1.5 build 23df00d9. The application appears to work normally, except that, after a short while, the indicated attachment count (paperclips in the attachment column of the Summary view) starts to increment fairly rapidly with each time that I visit the page. Attachment counts appear even for records that don't have any attachments. When I access records individually, either those with or without real attachments, everything looks OK. Any insights as to what might be causing this, and how to correct?
|
|
|
|
69784
|
Mon Apr 15 18:05:27 2024 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | Mac OSX | 3.1.5 | Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide |
Thanks for the info, I updated the adminguide.
Stefan
| Andreas Warburton wrote: |
|
Here's a more complete/correct set of the updated commands:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl bootout system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd
Cheers,
Andreas
| Andreas Warburton wrote: |
|
The section of the ELOG Administrator's Guide https://elog.psi.ch/elog/adminguide.html describing how to build and install ELOG on a Mac OS X system has worked well for me for several years, even though there have been warnings that the "load" and "unload" subcommands of the "launchctl" command have been deprecated for some time. After trying my luck again on a new Mac with the latest operating system, I encountered errors of the type "Load failed: 5: Input/output error" when attempting to follow these instructions.
After a bit of searching around, I used information at the page https://www.alansiu.net/2023/11/15/launchctl-new-subcommand-basics-for-macos/ to deploy the more current subcommands as follows:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd
Once the above can be verified, perhaps the instructions in the Administrator's Guide can be updated accordingly.
|
|
|
|
69785
|
Tue Apr 16 13:20:01 2024 |
| Andreas Warburton | andreas.warburton@mcgill.ca | Request | Mac OSX | 3.1.5 | Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide |
Hi Stefan, Thanks a lot for implementing the updated commands. I noted that there are a few typos that could cause people confusion if not fixed:
In one case, "launchctl" is misspelled.
Confusingly, I think the two lines containing the 'enable' and 'disable' commands use the contiguous text string "system/ch.psi.elogd" (no space), whereas the two lines containing the 'bootstrap' and 'bootout' commands use the phrase "system /Library/LaunchDaemons/ch.psi.elogd.plist" (note space after 'system').
Many thanks, Andreas W.
|
Stefan Ritt wrote:
|
|
Thanks for the info, I updated the adminguide.
Stefan
| Andreas Warburton wrote: |
|
Here's a more complete/correct set of the updated commands:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl bootout system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd
Cheers,
Andreas
| Andreas Warburton wrote: |
|
The section of the ELOG Administrator's Guide https://elog.psi.ch/elog/adminguide.html describing how to build and install ELOG on a Mac OS X system has worked well for me for several years, even though there have been warnings that the "load" and "unload" subcommands of the "launchctl" command have been deprecated for some time. After trying my luck again on a new Mac with the latest operating system, I encountered errors of the type "Load failed: 5: Input/output error" when attempting to follow these instructions.
After a bit of searching around, I used information at the page https://www.alansiu.net/2023/11/15/launchctl-new-subcommand-basics-for-macos/ to deploy the more current subcommands as follows:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist
sudo launchctl disable system/ch.psi.elogd
Once the above can be verified, perhaps the instructions in the Administrator's Guide can be updated accordingly.
|
|
|
|
|
69786
|
Tue Apr 16 13:31:02 2024 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Mac OSX | 3.1.5 | Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide |
Thanks, fixed.
Stefan
| Andreas Warburton wrote: |
|
Hi Stefan, Thanks a lot for implementing the updated commands. I noted that there are a few typos that could cause people confusion if not fixed:
In one case, "launchctl" is misspelled.
Confusingly, I think the two lines containing the 'enable' and 'disable' commands use the contiguous text string "system/ch.psi.elogd" (no space), whereas the two lines containing the 'bootstrap' and 'bootout' commands use the phrase "system /Library/LaunchDaemons/ch.psi.elogd.plist" (note space after 'system').
Many thanks, Andreas W.
|
|
|
69789
|
Wed Apr 24 12:55:25 2024 |
 | scott | shiva.ps@stfc.ac.uk | Question | Linux | Other | 3.1.5 | Imagemagick not working on Ubuntu |
Hi Team,
I have set up Elog on the Ubuntu server using the compile and install method. I have installed ImageMagick and GhostScript along with that.
You can find "ImageMagick detected" mentioned in the service status provided below:
=======================================================================
● elogd.service - The ELOG Server
Loaded: loaded (/lib/systemd/system/elogd.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2024-04-23 08:59:50 UTC; 1 day 1h ago
Docs: man:elogd(8)
man:elog(8)
Main PID: 858 (elogd)
Tasks: 1 (limit: 9365)
Memory: 163.5M
CPU: 25.825s
CGroup: /system.slice/elogd.service
└─858 /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg
Apr 23 08:59:50 server1.com systemd[1]: Starting The ELOG Server...
Apr 23 08:59:50 server1.com elogd[858]: elogd 3.1.5 built Mar 21 2024, 17:20:15
Apr 23 08:59:50 server1.com systemd[1]: Started The ELOG Server.
Apr 23 08:59:50 server1.com elogd[858]: revision fe60aaf0
Apr 23 08:59:50 server1.com elogd[858]: CKeditor detected
Apr 23 08:59:51 server1.com elogd[858]: ImageMagick detected
Apr 23 09:00:08 server1.com elogd[858]: Server listening on port 8080
=======================================================================
root@server1# identify -version
Version: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
Copyright: (C) 1999-2021 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC Modules OpenMP(4.5)
Delegates (built-in): bzlib djvu fftw fontconfig freetype heic jbig jng jp2 jpeg lcms lqr ltdl lzma openexr pangocairo png tiff webp wmf x xml zlib
=======================================================================
However, the ImageMagick was found to be not working on my logbook. See the below error on the logbook.
Cannot create thumbnail, please check ImageMagick installation
I have attached a screenshot for reference.
Please could someone help me how to solve this?
Many thanks,
Scott
|
| Attachment 1: image.png
|
|
|
69790
|
Thu Apr 25 02:11:08 2024 |
| Konstantin Olchanski | olchansk@triumf.ca | Question | Linux | Other | 3.1.5 | Re: Imagemagick not working on Ubuntu |
Please see https://daq00.triumf.ca/DaqWiki/index.php/Ubuntu#Enable_elog_PDF_preview
see https://stackoverflow.com/questions/52998331/imagemagick-security-policy-pdf-blocking-conversion
xemacs -nw /etc/ImageMagick-6/policy.xml
remove this section at the end:
<!-- disable ghostscript format types -->
<policy domain="coder" rights="none" pattern="PS" />
<policy domain="coder" rights="none" pattern="PS2" />
<policy domain="coder" rights="none" pattern="PS3" />
<policy domain="coder" rights="none" pattern="EPS" />
<policy domain="coder" rights="none" pattern="PDF" />
<policy domain="coder" rights="none" pattern="XPS" />
K.O. |
|
69807
|
Mon Jul 22 16:17:55 2024 |
 | André | andre.althaus@tu-dortmund.de | Bug report | All | 3.1.5 | HTTP headers should be parsed case insensitive |
I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual, haproxy rewrites all headers to lower case.
elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.
For now I'm using the workaround from the manual:
global
h1-case-adjust content-length Content-Length
h1-case-adjust content-type Content-Type
backend elog
option h1-case-adjust-bogus-server
server elog 127.0.0.1:8080
But as the manual states, this should not be used as a permanent solution. |
|
69817
|
Wed Jul 31 14:21:21 2024 |
| Stefan Ritt | I cstefan.ritt@psi.ch | Bug report | All | 3.1.5 | Re: HTTP headers should be parsed case insensitive |
I changed elog to interprete the content-length header case in-sensitive and committed the change. Can you try again?
Stefan
| André wrote: |
|
I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual, haproxy rewrites all headers to lower case.
elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.
For now I'm using the workaround from the manual:
global
h1-case-adjust content-length Content-Length
h1-case-adjust content-type Content-Type
backend elog
option h1-case-adjust-bogus-server
server elog 127.0.0.1:8080
But as the manual states, this should not be used as a permanent solution.
|
|