Project

General

Profile

Actions

Bug #812

closed

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

Added by Anonymous over 18 years ago. Updated over 16 years ago.

Status:
Invalid
Priority:
Urgent
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

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
Actions #1

Updated by Anonymous over 18 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

Actions #2

Updated by Anonymous over 18 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?

Actions #3

Updated by Anonymous over 18 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.

Actions #4

Updated by stbuehler about 17 years ago

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

Looks like the original problem is solved.

Actions #5

Updated by stbuehler over 16 years ago

  • Status changed from Fixed to Invalid
Actions

Also available in: Atom