Below are the last 10 lines of the message file. Perhaps someone could explain to me what is happening: Jun 9 22:57:35 sytron httpd: PHP Warning: fclose(): supplied argument is not a valid stream resource in /usr/local/apache2/htdocs/www.sytron.ro/html/uploads/images/dispcom.php on line 65 Jun 9 22:57:35 sytron httpd: PHP Warning: fsockopen() [<a href='function.fsockopen'>function.fsockopen</a>]: unable to connect to amazon.co.jp:80 (Connection timed out) in /usr/local/apache2/htdocs/www.sytron.ro/html/uploads/images/dispcom.php on line 57 Jun 9 22:57:35 sytron httpd: PHP Warning: fsockopen() [<a href='function.fsockopen'>function.fsockopen</a>]: unable to connect to http://72.21.210.11:80 (Unable to find the socket transport "http" - did you forget to enable it when you configured PHP?) in /usr/local/apache2/htdocs/www.sytron.ro/html/uploads/images/dispcom.php on line 59 Jun 9 22:57:35 sytron httpd: PHP Warning: fclose(): supplied argument is not a valid stream resource in /usr/local/apache2/htdocs/www.sytron.ro/html/uploads/images/dispcom.php on line 60 Jun 9 22:57:35 sytron httpd: PHP Warning: fputs(): supplied argument is not a valid stream resource in /usr/local/apache2/htdocs/www.sytron.ro/html/uploads/images/dispcom.php on line 61 Jun 9 22:57:35 sytron httpd: PHP Warning: fsockopen() [<a href='function.fsockopen'>function.fsockopen</a>]: unable to connect to http://72.21.210.11:80 (Unable to find the socket transport "http" - did you forget to enable it when you configured PHP?) in /usr/local/apache2/htdocs/www.sytron.ro/html/uploads/images/dispcom.php on line 62 Jun 9 22:57:35 sytron httpd: PHP Warning: fputs(): supplied argument is not a valid stream resource in /usr/local/apache2/htdocs/www.sytron.ro/html/uploads/images/dispcom.php on line 63 Jun 9 22:57:35 sytron httpd: PHP Warning: fclose(): supplied argument is not a valid stream resource in /usr/local/apache2/htdocs/www.sytron.ro/html/uploads/images/dispcom.php on line 64 Jun 9 22:57:35 sytron httpd: PHP Warning: fclose(): supplied argument is not a valid stream resource in /usr/local/apache2/htdocs/www.sytron.ro/html/uploads/images/dispcom.php on line 65 Jun 9 22:57:35 sytron httpd: PHP Warning: fsockopen() [<a href='function.fsockopen'>function.fsockopen</a>]: unable to connect to http://72.21.210.11:80 (Unable to findroot@sytron On Tuesday 10 June 2008 10:09:04 you wrote:

>>> On 10.06.2008 at 09:59, Bogdan Cristea wrote:

...

I have a web server running Slackware on it and yesterday I have experienced a failure due to the saturation of the root partition. After investigating I have found that in /var/log the messages files (message.1, message.2, ..., message.4) were extremely large. After cleaning up, I have freed 2 GB, but today morning I have had the same failure, due to the same reason: the message file was 2GB, eating completely my root partiton. Have you experienced similar behavior? Could you advise how to solve

I'm not sure how you get to the conclusion, that apache is filling this logfile. /var/log/messages is a general log file, normally not involved in logging Apache errors at all.

I'd advise you to actually read that log file to find a pattern what is happening. Then you can either solve the issue, reduce logging (in case you're on debug level) or take steps against it.

Dominique

-- Bogdan Cristea software engineer Sytron Technologies Overseas www.sytron.ro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Bogdan Cristea wrote:

Below are the last 10 lines of the message file. Perhaps someone could explain to me what is happening:

Your webserver at www.sytron.ro is running some buggy code and logging warnings to your syslog. That is odd, but probably just a PHP configuration option. /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, Jun 10, 2008 at 12:25 AM, Bogdan Cristea wrote:

It is odd because it started two days ago with no apparent reason. I have not modified that portion of the server.

Well if you didn't touch /usr/local/apache2/htdocs/www.sytron.ro/html/uploads/images/dispcom.php a few days ago, then perhaps you do have a serious problem, or someone found a way to exploit one of your scripts. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, Jun 10, 2008 at 12:41 PM, Evens Garde wrote:

Bogdan Cristea wrote:

...

I have a web server running Slackware on it and yesterday I have experienced a failure due to the saturation of the root partition. After investigating I have found that in /var/log the messages files (message.1, message.2, ..., message.4) were extremely large. After cleaning up, I have freed 2 GB, but today morning I have had the same failure, due to the same reason: the message file was 2GB, eating completely my root partiton. Have you experienced similar behavior? Could you advise how to solve this issue? regards

A. Put /var on its own partition. B. Read the error logs and find out what is producing the error messages.

And C: Post on the Slackware list? ;-) -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org