From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 136: Calamaris proxy reports stay empty
Date: Mon, 11 Nov 2019 13:14:14 +0000 [thread overview]
Message-ID: <DEE096B0-CA08-4737-B4E7-41C5B66DB27E@ipfire.org> (raw)
In-Reply-To: <954d9b87-69f6-9513-e6a6-874c3ad4db60@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
Hi,
> On 10 Nov 2019, at 14:47, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> after not using the "Proxy Reports" for a while, I wanted to try the
> again today.
>
> But no matter what I try, 'Calamaris' only creates *empty* logs with 0
> Bytes, like '/var/ipfire/proxy/calamaris/reports/calamaris-1573395239.log'.
>
> And the "Proxy Reports" GUI keeps telling me "No reports available".
>
> Tested on Core 134 (Worked!), a running Core 136 installation
> (Productive) and a fresh Core 136 installation. Both Core 136
> installations won't work. Not at all!
>
> I tested on console and got the following error:
>
> ...
> root(a)ipfire: ~ # /usr/bin/perl /var/ipfire/proxy/calamaris/bin/mkreport
> 1 0 2019 8 10 2019 -d 10 -P 30 -t 10 -D 2 -u -r -1 -R 100 -s
> Can't use 'defined(%hash)' (Maybe you should just omit the defined()?)
> at /var/ipfire/proxy/calamaris/bin/calamaris line 2609.
Did you try changing this line as suggested?
It is probably a regression from the Perl upgrade.
> ...
>
> Before I file a bug report: can anyone confirm?
>
> Best,
> Matthias
next prev parent reply other threads:[~2019-11-11 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 14:47 Matthias Fischer
2019-11-11 13:14 ` Michael Tremer [this message]
[not found] <18eb03fa-0045-4565-d889-e910c1ff4670@ipfire.org>
2019-11-13 16:58 ` Michael Tremer
2019-11-13 17:30 ` Matthias Fischer
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=DEE096B0-CA08-4737-B4E7-41C5B66DB27E@ipfire.org \
--to=michael.tremer@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