Bug #812

(network_freebsd_sendfile.c.96) writev failed: Permission denied

Added by Anonymous about 4 years ago. Updated almost 2 years ago.

Status:Invalid Start:
Priority:Urgent Due date:
Assigned to:- % Done:

0%

Category:core
Target version:-
Missing in 1.5.x:

Description

When this happend, my FreeBSD server will going to down.
This will happen 1-2 times per day.

here is the log file
--------------------


2006-08-17 11:40:24: (network_freebsd_sendfile.c.96) writev failed: Permission denied 2490 
2006-08-17 11:40:24: (connections.c.538) connection closed: write failed on fd 2490 
...
2006-08-17 11:40:46: (network_freebsd_sendfile.c.96) writev failed: Permission denied 2298 
2006-08-17 11:40:46: (connections.c.538) connection closed: write failed on fd 2298 
2006-08-17 11:49:23: (log.c.75) server started

History

Updated by Anonymous almost 4 years ago

I saw something similar last night:

2006-09006 19:43:00: (network_freebsd_sendfile.c.96) writev failed: Socket is not connected 7

The application stopped serving entirely, I had to restart it when I woke up 4 hours later. Please check this out.

-- lightty

Updated by Anonymous almost 4 years ago

Replying to anonymous:

When this happend, my FreeBSD server will going to down. This will happen 1-2 times per day.

here is the log file
{{{ 2006-08-17 11:40:24: (network_freebsd_sendfile.c.96) writev failed: Permission denied 2490 2006-08-17 11:40:24: (connections.c.538) connection closed: write failed on fd 2490 ... 2006-08-17 11:40:46: (network_freebsd_sendfile.c.96) writev failed: Permission denied 2298 2006-08-17 11:40:46: (connections.c.538) connection closed: write failed on fd 2298 2006-08-17 11:49:23: (log.c.75) server started }}}

I'm alsow having this problem with FreeBSD 6.1, what to do?

Updated by Anonymous almost 4 years ago

I tracked the problem down to being PF firewall that kept states of every connection resolving in too many entries for any new connections, adding a QUICK rule resolved it.

Updated by stbuehler over 2 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

Looks like the original problem is solved.

Updated by stbuehler almost 2 years ago

  • Status changed from Fixed to Invalid

Also available in: Atom