PfSense v2.0.3 Connection reset by peer problem

_igor_ · Feb 17, 2013, 2:29 PM

Since some days the log is getting filled with the following message:

Feb 17 15:23:08	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 15:23:08	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 15:20:52	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 15:20:52	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 15:20:23	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 15:20:23	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 15:14:11	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 15:14:11	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 15:12:35	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 15:12:35	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 15:07:38	lighttpd[31421]: (connections.c.137) (warning) close: 15 Connection reset by peer
Feb 17 15:07:38	lighttpd[31421]: (connections.c.137) (warning) close: 15 Connection reset by peer
Feb 17 15:00:46	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 15:00:46	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 14:59:29	lighttpd[31421]: (connections.c.137) (warning) close: 14 Connection reset by peer
Feb 17 14:59:29	lighttpd[31421]: (connections.c.137) (warning) close: 14 Connection reset by peer
Feb 17 14:56:02	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer
Feb 17 14:56:02	lighttpd[31421]: (connections.c.137) (warning) close: 13 Connection reset by peer

Anyone else having the same problem? Or maybe a solution?
Restart of lighty or the router doesn't help. The webIF works ok, no problems there. Im somewhat confused…

I have a full install 2.0.3-PRERELEASE (amd64) built on Sat Feb 9 21:12:53 EST 2013

jimp · Feb 19, 2013, 5:36 PM

Probably safe to ignore. The lighty logs were going nowhere before, now they go to the system log. Lots of normal things are showing in the log and confusing people. :-)

That just means that the browser or whatever else was talking to lighttpd closed the connection abruptly. Could happen for any number of reasons.

Mr. Jingles · Apr 27, 2013, 8:21 AM

I can confirm I have the same on 2.0.3-RELEASE (X32). Is there perhaps a way to stop these lines from showing up in the logs?

mod3m · May 11, 2013, 3:35 PM

Very many logs of lighttpd[59497]: (connections.c.137) (warning) close: 17 Connection reset by peer
Every second

To turn off the.

Edit file: /etc/inc/system.inc
Find line: server.errorlog-use-syslog="enable" (number line - 850)
replace server.errorlog-use-syslog="disable"
Restart webConfigurator or router

Mr. Jingles · Jul 7, 2013, 5:54 PM

@mod3m:

Very many logs of lighttpd[59497]: (connections.c.137) (warning) close: 17 Connection reset by peer
Every second

To turn off the.

Edit file: /etc/inc/system.inc
Find line: server.errorlog-use-syslog="enable" (number line - 850)
replace server.errorlog-use-syslog="disable"
Restart webConfigurator or router

Thank you ;D

jimp · Jul 9, 2013, 4:13 PM

On 2.1 I added a checkbox to the system log settings to disable the logs from lighttpd. So you won't need to edit the code directly once you move to 2.1, just (un)check the box.

Mr. Jingles · Jul 9, 2013, 5:01 PM

@jimp:

On 2.1 I added a checkbox to the system log settings to disable the logs from lighttpd. So you won't need to edit the code directly once you move to 2.1, just (un)check the box.

It says under your nick that you are a 'Hero member': I can now understand why ;D ;D

Thank you for all you are doing :P