Apache vlogger Bug reintroduced?

Hi all,

I was running latest ISPConfig 3.5.0.3 quite nice on a Ubuntu 12.04 setup via Howto. Since Sep30 I'm getting problems with vlogger/apache2. After searching around the bugtracker and forums, it seems the problem was known in 2012 and fixed by a new vlogger call in ispconfig.conf and a cron at night. I checked the workaround and solutions of that old thread and all mentioned additions etc. are already in place (as they belonged to 3.4.x and have possibly been worked into 3.5 from the start).

So I'm quite at loss where that problems come from. Here's the log:

Code:

Use of uninitialized value $reqsize in pattern match (m//) at /usr/local/ispconfig/server/scripts/vlogger line 468, <STDIN> line 1.
Use of uninitialized value $reqsize in numeric gt (>) at /usr/local/ispconfig/server/scripts/vlogger line 468, <STDIN> line 1.
Use of uninitialized value $reqsize in pattern match (m//) at /usr/local/ispconfig/server/scripts/vlogger line 468, <STDIN> line 2.
Use of uninitialized value $reqsize in numeric gt (>) at /usr/local/ispconfig/server/scripts/vlogger line 468, <STDIN> line 2.
Use of uninitialized value $reqsize in pattern match (m//) at /usr/local/ispconfig/server/scripts/vlogger line 468, <STDIN> line 3.
Use of uninitialized value $reqsize in numeric gt (>) at /usr/local/ispconfig/server/scripts/vlogger line 468, <STDIN> line 3.
...

Those lines popup every time a VHost is called.

Anything I can post from the configs to help get this sorted? I have multiple of hundreds of those lines in the error.log!

Greets
Grey

 

You say "since Sept 30". Have you done any updates there? Ubuntu upgrade maybe?

 

Of course. The system is doing autonomous security updates and a normal update may very well be the case. BUT: The original problem was because of some logging mechanism and perl problems (vlogger etc.) and the solution is already implemented in this version of ISPConfig. So the question remains: what triggered that (re-?)appearance and how to get rid of it ASAP, as this system is going to be live soon and was running smoothly until a few weeks ago when those log entries occured. And they are written every single time a page is called on any vhost. You can do the math yourself how the log file size is exploding...

I'm happy to assist any debugging, but I assume I'll need someone to look into that deeper. Falko perhaps?

Greets
Jens

 

Hi Till,

thanks for jumping in. Mine are only slightly different (one addition):

Code:

LogFormat "%v %h %l %u %t \"%r\" %>s %B \"%{Referer}i\" \"%{User-Agent}i\"" combined_ispconfig
CustomLog "| /usr/local/ispconfig/server/scripts/vlogger -s access.log -t \"%Y%m%d-access.log\" /var/log/ispconfig/httpd" combined_ispconfig env=!dontlog

so the only difference I spot is the "env=!dontlog" after the LogFormat "combined_ispconfig" and that is because of an SetEnvIf declaration for the URL "/monit/token" to not show in logs every few minutes.

Greets