Hi,
On 11 Nov 2019, at 17:17, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
On 11.11.2019 14:14, Michael Tremer wrote:
Hi,
Hi,
On 10 Nov 2019, at 14:47, Matthias Fischer <matthias.fischer@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@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?
No, because I'm not that familiar with Perl. How would I do this?
Line 2609ff reads:
...
if ( defined(%tcp_content) ) {
I think this line should just be:
if (%tcp_content) {
You might have more of those in the file, but I am sure the interpreter will tell you when you try to run it.
As far as I know this whole calamaris thing is not maintained upstream any more. If this isn’t easily fixable we will just have to remove the feature. Not sure how many users this has.
outstart(11);
if ( $tcp == 0 ) {
outline( 11, 'no matching requests' );
} else {
...
It is probably a regression from the Perl upgrade.
I suppose so, too.
Best,
Matthias