Here's the sequence of events:
- upgrade news server to 4.8PRE
- inn starts throwing errors due to Berkeley DB upgrade from 3.2 to 4.0
- upgrade from inn 2.3.1 to inn 2.3.4, compiling against new Berkeley DB
version
- rebuild OVDB with makehist
- inn runs fine for a while
- had to shutdown news server due to chilled water outage in building
- bring news server back up, innd hangs
- when trying to connect, the connection succeeds temporarily, but no
banner is received back from innd
- after a few minutes, there is no ACK from the machine on that
port in response to a SYN, it appears as if the port is blocked
by a firewall (which it isn't, behavior is the same on localhost)
- ktrace/strace show innd doing nothing but selecting/timing out on
fd 0, but no other useful info (that I can find), although it's
hard to trace due to the fact innd must be started by inndstart,
which is setuid
- tried MAXUSERS=0 and MAXUSERS=512, same behavior
- netstat -m output (with MAXUSERS=512):
74/192/34816 mbufs in use (current/peak/max):
67 mbufs allocated to data
6 mbufs allocated to packet headers
1 mbufs allocated to fragment reassembly queue headers
66/70/8704 mbuf clusters in use (current/peak/max)
188 Kbytes allocated to network (0% of mb_map in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines
- lsof reports 507 open files
Config files available on request.
Any help appreciated.
----------------------------------------------------------------------
| Jim Hranicky, Senior SysAdmin UF/CISE Department |
| E314D CSE Building Phone (352) 392-1499 |
| [EMAIL PROTECTED] http://www.cise.ufl.edu/~jfh |
----------------------------------------------------------------------
"Given a choice between a complex, difficult-to-understand, disconcerting
explanation and a simplistic, comforting one, many prefer simplistic
comfort if it's remotely plausible, especially if it involves blaming
someone else for their problems."
-- Bob Lewis, _Infoworld_
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
