From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Testing Issues with core165 Development Build: next/cad86575
Date: Mon, 07 Mar 2022 17:51:00 +0100 [thread overview]
Message-ID: <db3fd3c7d884c8572ee9c15876644bbc5afd9023.camel@ipfire.org> (raw)
In-Reply-To: <16a1fbd2-c1fc-50a5-8c58-5a85a0528f5c@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
Hello Charles,
a big thanks for pointing this regression out. I've introduced this by
one of my latest IDS related fixes :(
I'll send a patch to the list to fix this issue.
Best regards,
-Stefan
> Hi Stefan,
>
> In case you had not noticed ... after fresh install of latest
> next/cad86575
> ...
>
> Web page ids.cgi stops loading after header.
> The page header down through "Intrusion Prevention System <?>" is
> displayed and then stops -- nothing else on the page
>
> Log in httpd error shows as:
>
> "Unable to read file /var/ipfire/suricata/ignored at
> /var/ipfire/general-functions.pl line 883."
>
> I went to the directory and touched "ignored" file and chowned it to
> nobody:nobody.
> That allowed the page to complete loading
>
> I don't know if the chown was necessary -- I didn't try reloading the
> page before doing it.
>
>
> Cheers,
> Charles Brown
>
next parent reply other threads:[~2022-03-07 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16a1fbd2-c1fc-50a5-8c58-5a85a0528f5c@yahoo.com>
2022-03-07 16:51 ` Stefan Schantl [this message]
2022-03-07 16:52 ` [PATCH] ids.cgi: Only read-in ignored hosts, if the ignore file exists Stefan Schantl
[not found] <06172f89-90ad-7851-ad93-25cd8d390c38.ref@yahoo.com>
2022-03-07 12:26 ` Testing Issues with core165 Development Build: next/cad86575 Charles Brown
2022-03-08 15:47 ` Michael Tremer
2022-03-08 20:13 ` Charles Brown
2022-03-11 16:28 ` Michael Tremer
2022-03-11 23:40 ` Charles Brown
2022-03-17 15:52 ` Michael Tremer
2022-03-17 19:34 ` Charles Brown
2022-03-18 9:14 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=db3fd3c7d884c8572ee9c15876644bbc5afd9023.camel@ipfire.org \
--to=stefan.schantl@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox