Please help with config, posted by Daniel Sajdyk on Mon Sep 2 12:54:12 2024
|
Hello,
I'm trying to create config file for simple incident logbook. It should has 3 attributes:
- source (source of incident) with options:
- email
- jira_id
- ezd_id
- Tactics (from MITRE but for simplicity I wrote only this):
- aaa,
- bbb,
- Technics (also from MITRE but also for simplicity I wrote only this):
- tactics1, tactics2,
- tactics3, tactics4
And this is not working.
For me it looks that choosing first attribute - Source - causes problems, because after that I cannot choose third - Technics - attribute.
When I will start filling attributes from the second - Tactics - then Technics options are avaiable.
Below is config file:
Theme = default
Page Title = ELOG - $Theme
Attributes = Source, Technics, Tactics
Options Source = Email{a}, Jira{b}, EZD{c}
{a} Attributes = Source, Adres_email, Technics, Tactics
{b} Attributes = Source, JIRA_ID, Technics, Tactics
{c} Attributes = Source, EZD_ID, Technics, Tactics
Options Technics = aaa{1}, bbb{2}
{1} Options Tactics = tactics1, tactics2
{2} Options Tactics = tactics3, tactics4
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Source, Technics, Tactics
I will appreciate any help.
Best Regards |
Can Elog make a table?, posted by Walter Reviol on Wed Aug 7 22:54:03 2024
|
Hi!
I like to format an Elog "directory" such that all entries make/occur as a table. Say: 5 columns and a large number of rows. In a sense, make an excel spreadsheet in Elog. Is this possible? How can this be done? Is there perhaps a template?
Thanks in advance.
Walter Reviol
reviol@anl.gov |
Re: Can Elog make a table?, posted by Stefan Ritt on Thu Aug 8 09:07:45 2024
|
I'm not exactly sure what you want to do, but there are two options in elog:
1) Insert directly a table like this one:
Index |
Value |
first |
123 |
second |
432 |
2) Use one ELOG entry as a row in a table. You can try this by clicking on "List" here in the Forum should you not already see the list display, then on "Summary" which give you a spreadsheet like display, where you can specify in the config file which columns of the ELOG entries you want to see. See also the demo here: https://elog.psi.ch/elogs/Linux+Demo/
Best,
Stefan |
Elog on FreeBSD, posted by Truupe on Mon Aug 5 20:45:15 2024
|
Anyone using elog on FreeBSD nowadays? I know it used to be in the ports tree about 10 years ago but seems to be abandoned. Tried to compile from source on 14.1, but no luck there. |
Re: Elog on FreeBSD, posted by Truupe on Mon Aug 5 21:15:08 2024
|
Welp, nevermind, I dug a little more and managed to compile it on 14.1 using cmake.
Truupe wrote: |
Anyone using elog on FreeBSD nowadays? I know it used to be in the ports tree about 10 years ago but seems to be abandoned. Tried to compile from source on 14.1, but no luck there.
|
|
Invalid Content-Length in header when running behind a load balancer, posted by Tamas Gal on Wed Jan 25 14:36:33 2023
|
I am still struggling to get ELOG running behind a load balancer and hope to get some advice here. As already reported in https://elog.psi.ch/elogs/Forum/69542 I observed an infinite loop of redirects when prompted to log in and using a non-empty password file. Without a password, the service worked as expected. This was with version 3.1.3.
With the new version 3.1.4-3, I get another error: "Invalid Content-Length in header" when I click on "submit" of a new post. Viewing the logbooks works fine. The instance is currently live and running here: https://elog.test.km3net.de but I might change it anytime due to debugging etc.
This is a kind of difficult thing to debug (I spent the whole day and no progress). The only thing I've found was this post: https://techcommunity.microsoft.com/t5/iis-support-blog/invalid-content-length/ba-p/3038724 where it seems that some responses are not RFC conform and were rejected in the load-balancer.
The load balancer I use is HAProxy, the same as in my old setup where I got the infinite redirects, and I can't find any setting which would work. To my understanding, the most basic setup should work just fine. The SSL termination is on the load-balancer side so ELOG doesn't even have to know anything about it. The configuration is below. I am running a single instance, so there is not even replication with session keep-alive via cookies or anything fancy.
I also want to mention that I am runnin around 30 different services behind the load balancer and none of them are having any issues with the SSL termination or the load-balancing itself, that's why assume that something in ELOG is either non-conform or buggy.
Any thoughts? I'd really like to use the same infrastructure for the ELOG service as for every other service (automatic certificate renewal via letsencrypt, load-balancing, easy movement to other nodes, SSL termination etc.), to minimise the complexity of our Docker Swarm system.
backend be_elog.km3net.de
mode http
server-template km3net-elog- 1 km3net-elog_elog:8080 check resolvers docker init-addr libc,none
Btw. I am running ELOG with -v but I don't see any error whatsoever in the logs:
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "ios_specific_templates_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_anonymous_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_group_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_group_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_user_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "logged_out_marketing_header_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3437 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3518 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3518 bytes |
Re: Invalid Content-Length in header when running behind a load balancer, posted by Tamas Gal on Wed Jan 25 19:51:29 2023
|
I put the ELOG service behind an Apache reverse proxy which is now sitting behind the HAProxy. It works like this, but it's just a workaround. I am pretty sure that ELOG has problems to communicate with HAProxy correctly and it seems that Apache is more forgiving. So that the chain HAProxy -> Apache -> ELOG and vice versa is working.
If anyone manages to figure out what's wrong, I am happy to get rid of the extra reverse proxy layer!
Tamas Gal wrote: |
I am still struggling to get ELOG running behind a load balancer and hope to get some advice here. As already reported in https://elog.psi.ch/elogs/Forum/69542 I observed an infinite loop of redirects when prompted to log in and using a non-empty password file. Without a password, the service worked as expected. This was with version 3.1.3.
With the new version 3.1.4-3, I get another error: "Invalid Content-Length in header" when I click on "submit" of a new post. Viewing the logbooks works fine. The instance is currently live and running here: https://elog.test.km3net.de but I might change it anytime due to debugging etc.
This is a kind of difficult thing to debug (I spent the whole day and no progress). The only thing I've found was this post: https://techcommunity.microsoft.com/t5/iis-support-blog/invalid-content-length/ba-p/3038724 where it seems that some responses are not RFC conform and were rejected in the load-balancer.
The load balancer I use is HAProxy, the same as in my old setup where I got the infinite redirects, and I can't find any setting which would work. To my understanding, the most basic setup should work just fine. The SSL termination is on the load-balancer side so ELOG doesn't even have to know anything about it. The configuration is below. I am running a single instance, so there is not even replication with session keep-alive via cookies or anything fancy.
I also want to mention that I am runnin around 30 different services behind the load balancer and none of them are having any issues with the SSL termination or the load-balancing itself, that's why assume that something in ELOG is either non-conform or buggy.
Any thoughts? I'd really like to use the same infrastructure for the ELOG service as for every other service (automatic certificate renewal via letsencrypt, load-balancing, easy movement to other nodes, SSL termination etc.), to minimise the complexity of our Docker Swarm system.
backend be_elog.km3net.de
mode http
server-template km3net-elog- 1 km3net-elog_elog:8080 check resolvers docker init-addr libc,none
Btw. I am running ELOG with -v but I don't see any error whatsoever in the logs:
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "ios_specific_templates_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_anonymous_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_group_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_group_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_user_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "logged_out_marketing_header_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3437 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3518 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3518 bytes
|
|
Re: Invalid Content-Length in header when running behind a load balancer, posted by André on Mon Jul 22 16:30:04 2024
|
I have the same problem. I found a temporary solution: https://elog.psi.ch/elogs/Forum/69807
Tamas Gal wrote: |
I put the ELOG service behind an Apache reverse proxy which is now sitting behind the HAProxy. It works like this, but it's just a workaround. I am pretty sure that ELOG has problems to communicate with HAProxy correctly and it seems that Apache is more forgiving. So that the chain HAProxy -> Apache -> ELOG and vice versa is working.
If anyone manages to figure out what's wrong, I am happy to get rid of the extra reverse proxy layer!
Tamas Gal wrote: |
I am still struggling to get ELOG running behind a load balancer and hope to get some advice here. As already reported in https://elog.psi.ch/elogs/Forum/69542 I observed an infinite loop of redirects when prompted to log in and using a non-empty password file. Without a password, the service worked as expected. This was with version 3.1.3.
With the new version 3.1.4-3, I get another error: "Invalid Content-Length in header" when I click on "submit" of a new post. Viewing the logbooks works fine. The instance is currently live and running here: https://elog.test.km3net.de but I might change it anytime due to debugging etc.
This is a kind of difficult thing to debug (I spent the whole day and no progress). The only thing I've found was this post: https://techcommunity.microsoft.com/t5/iis-support-blog/invalid-content-length/ba-p/3038724 where it seems that some responses are not RFC conform and were rejected in the load-balancer.
The load balancer I use is HAProxy, the same as in my old setup where I got the infinite redirects, and I can't find any setting which would work. To my understanding, the most basic setup should work just fine. The SSL termination is on the load-balancer side so ELOG doesn't even have to know anything about it. The configuration is below. I am running a single instance, so there is not even replication with session keep-alive via cookies or anything fancy.
I also want to mention that I am runnin around 30 different services behind the load balancer and none of them are having any issues with the SSL termination or the load-balancing itself, that's why assume that something in ELOG is either non-conform or buggy.
Any thoughts? I'd really like to use the same infrastructure for the ELOG service as for every other service (automatic certificate renewal via letsencrypt, load-balancing, easy movement to other nodes, SSL termination etc.), to minimise the complexity of our Docker Swarm system.
backend be_elog.km3net.de
mode http
server-template km3net-elog- 1 km3net-elog_elog:8080 check resolvers docker init-addr libc,none
Btw. I am running ELOG with -v but I don't see any error whatsoever in the logs:
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "ios_specific_templates_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_anonymous_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_group_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_group_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_user_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "logged_out_marketing_header_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3437 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3518 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3518 bytes
|
|
|
Re: Invalid Content-Length in header when running behind a load balancer, posted by Stefan Ritt on Wed Jul 31 14:22:52 2024
|
I changed elog to interprete the content-length header case in-sensitive and committed the change. Can you try again?
Stefan
André wrote: |
I have the same problem. I found a temporary solution: https://elog.psi.ch/elogs/Forum/69807
Tamas Gal wrote: |
I put the ELOG service behind an Apache reverse proxy which is now sitting behind the HAProxy. It works like this, but it's just a workaround. I am pretty sure that ELOG has problems to communicate with HAProxy correctly and it seems that Apache is more forgiving. So that the chain HAProxy -> Apache -> ELOG and vice versa is working.
If anyone manages to figure out what's wrong, I am happy to get rid of the extra reverse proxy layer!
Tamas Gal wrote: |
I am still struggling to get ELOG running behind a load balancer and hope to get some advice here. As already reported in https://elog.psi.ch/elogs/Forum/69542 I observed an infinite loop of redirects when prompted to log in and using a non-empty password file. Without a password, the service worked as expected. This was with version 3.1.3.
With the new version 3.1.4-3, I get another error: "Invalid Content-Length in header" when I click on "submit" of a new post. Viewing the logbooks works fine. The instance is currently live and running here: https://elog.test.km3net.de but I might change it anytime due to debugging etc.
This is a kind of difficult thing to debug (I spent the whole day and no progress). The only thing I've found was this post: https://techcommunity.microsoft.com/t5/iis-support-blog/invalid-content-length/ba-p/3038724 where it seems that some responses are not RFC conform and were rejected in the load-balancer.
The load balancer I use is HAProxy, the same as in my old setup where I got the infinite redirects, and I can't find any setting which would work. To my understanding, the most basic setup should work just fine. The SSL termination is on the load-balancer side so ELOG doesn't even have to know anything about it. The configuration is below. I am running a single instance, so there is not even replication with session keep-alive via cookies or anything fancy.
I also want to mention that I am runnin around 30 different services behind the load balancer and none of them are having any issues with the SSL termination or the load-balancing itself, that's why assume that something in ELOG is either non-conform or buggy.
Any thoughts? I'd really like to use the same infrastructure for the ELOG service as for every other service (automatic certificate renewal via letsencrypt, load-balancing, easy movement to other nodes, SSL termination etc.), to minimise the complexity of our Docker Swarm system.
backend be_elog.km3net.de
mode http
server-template km3net-elog- 1 km3net-elog_elog:8080 check resolvers docker init-addr libc,none
Btw. I am running ELOG with -v but I don't see any error whatsoever in the logs:
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "ios_specific_templates_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_anonymous_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_group_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_group_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "rl_user_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Received unknown cookie "logged_out_marketing_header_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3437 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3518 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021 | Returned 3518 bytes
|
|
|
|
HTTP headers should be parsed case insensitive, posted by André on Mon Jul 22 16:17:55 2024
|
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. |
Re: HTTP headers should be parsed case insensitive, posted by Stefan Ritt on Wed Jul 31 14:21:21 2024
|
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.
|
|
Old attachments erroneously appearing on new Elog entries., posted by Carl Unsworth on Fri Jul 26 12:53:23 2024 
|
Hi, I'm not sure if this is an Elog bug, something wrong in my configuration/database.
When I create a new article on Elog it always shows an attachment from one of the first entries ever made to this log book made. This is in addition to any attachments which were actually added during article creation.
I just made an example entry to demonstrate. First attachment here shows how the entry looks in the GUI, it has an attached text file called "jail.local", 2nd attachment is how that entry looks in the database file - no attachment.
Does anyone have any idea what's happening? |
Re: Old attachments erroneously appearing on new Elog entries., posted by Stefan Ritt on Fri Jul 26 13:01:54 2024
|
This bug has been fixed in meantime, please upgrade to the current version. |
Re: Old attachments erroneously appearing on new Elog entries., posted by Carl Unsworth on Fri Jul 26 13:14:38 2024
|
Thanks very much for the quick response Stefan. My apologies, I thought I was on the latest version or I would have upgraded before contacting you.
The file I installed from was the rpm "elog-3.1.5-20240226.el9.x86_64.rpm" which still seems to be the latest version on the Dropbox downloads page.
Do I need to use the tar distribution to get the latest?
Stefan Ritt wrote: |
This bug has been fixed in meantime, please upgrade to the current version.
|
|
Re: Old attachments erroneously appearing on new Elog entries., posted by Stefan Ritt on Fri Jul 26 14:09:19 2024
|
I updated the EL9 rpms, so please try again. |
Re: Old attachments erroneously appearing on new Elog entries., posted by Carl Unsworth on Fri Jul 26 14:33:50 2024
|
Great, thank you again. I have now installed the latest and the problem appears to be gone.
Stefan Ritt wrote: |
I updated the EL9 rpms, so please try again.
|
|
Old attachments erroneously appearing on new Elog entries., posted by Carl Unsworth on Fri Jul 26 12:52:54 2024 
|
Hi, I'm not sure if this is an Elog bug, something wrong in my configuration/database.
When I create a new article on Elog it always shows an attachment from one of the first entries ever made to this log book made. This is in addition to any attachments which were actually added during article creation.
I just made an example entry to demonstrate. First attachment here shows how the entry looks in the GUI, it has an attached text file called "jail.local", 2nd attachment is how that entry looks in the database file - no attachment.
Does anyone have any idea what's happening? |
Elog/ImageMagick under windows 11, posted by Aled Isaac on Thu Jul 18 11:38:01 2024
|
I was wondering if anyone would be able to assist me in getting the ImageMagick/figure scaling working on an elog running under windows 11 (Microsoft Windows Version 22H2 (OS Build 22621.3880)). I've followed the installation instructions and checked that $PATH contains the directory for both ImageMagick and GSS. In a 'command prompt' window, when I execute "identify -version" from any directory I get the response:
Version: ImageMagick 7.1.1-35 Q16-HDRI x64 d775d2a:20240714 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Channel-masks(64-bit) Cipher DPC HDRI Modules OpenCL OpenMP(2.0)
Delegates (built-in): bzlib cairo flif freetype gslib heic jng jp2 jpeg jxl lcms lqr lzma openexr pangocairo png ps raqm raw rsvg tiff webp xml zip zlib
Compiler: Visual Studio 2022 (194033811)
which I believe is correct. I've looked through the source-code for the elog and I believe that upon initialisation elogd is looking for a response containing "ImageMagick" somewhere in the response [image_magick_exist = (strstr(str, "ImageMagick") != NULL);] so I'm not sure I understand why this isn't being satisfied. When I run elogd I get the statement "ImageMagick NOT detected. Image scaling will not work.".
I have the feeling that this is some security restriction in windows 11, so was wondering if anyone had seen this problem before and knew of a solution.
Many Thanks
|
Re: Elog/ImageMagick under windows 11, posted by Aled Isaac on Wed Jul 24 17:21:45 2024
|
I've managed to get it working and the problem wasn't what I thought it was. It turns out that ImageMagick v7 doesn't have a "convert.exe" program in the windows version due to some conflict with a disk conversion utility. The "convert.exe" has been replaced with a "magick.exe" and so I made a CONVERT.BAT script within the elog folder with content "magick %*". This workaround appears to have solved the problem.
Aled Isaac wrote: |
I was wondering if anyone would be able to assist me in getting the ImageMagick/figure scaling working on an elog running under windows 11 (Microsoft Windows Version 22H2 (OS Build 22621.3880)). I've followed the installation instructions and checked that $PATH contains the directory for both ImageMagick and GSS. In a 'command prompt' window, when I execute "identify -version" from any directory I get the response:
Version: ImageMagick 7.1.1-35 Q16-HDRI x64 d775d2a:20240714 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Channel-masks(64-bit) Cipher DPC HDRI Modules OpenCL OpenMP(2.0)
Delegates (built-in): bzlib cairo flif freetype gslib heic jng jp2 jpeg jxl lcms lqr lzma openexr pangocairo png ps raqm raw rsvg tiff webp xml zip zlib
Compiler: Visual Studio 2022 (194033811)
which I believe is correct. I've looked through the source-code for the elog and I believe that upon initialisation elogd is looking for a response containing "ImageMagick" somewhere in the response [image_magick_exist = (strstr(str, "ImageMagick") != NULL);] so I'm not sure I understand why this isn't being satisfied. When I run elogd I get the statement "ImageMagick NOT detected. Image scaling will not work.".
I have the feeling that this is some security restriction in windows 11, so was wondering if anyone had seen this problem before and knew of a solution.
Many Thanks
|
|