Connection issues on Solaris 10 (Accept failed: Bad file number)

Jim Hayter jhayter at
Tue Jan 5 17:33:09 CET 2010

Thanks for the link

Following the points there:
1) I am running 2.0.6, which either has or I had already made the edit
for ticket 547.
2) I set connect_timeout to 0 and turned off keep alive in apache.
3) Starting varnishd with "-p waiter=poll" did not work for me (waiter
not recognized), so I rebuilt Varnish using 
	./configure --disable-kqueue --disable-epoll --disable-ports
4) FYI, varnishd will not run in the background for me, it always fails
to start the child process.  It works running with the -F flag.

One note about,
where it refers to /etc/projects, it should be /etc/project (not

At this point it appears to be working fine. I left a test running
overnight and it is still going.  The previous tests I did all dumped
core long before this amount of time.

Thank you very much for your help and the link.  I had gone on to look
at using Apache2 as a caching front end to Apache1 but I believe that
Varnish will be the preferred solution.


-----Original Message-----
From: varnish-misc-bounces at
[mailto:varnish-misc-bounces at] On Behalf Of Tollef Fog
Sent: Monday, January 04, 2010 4:43 AM
To: varnish-misc at
Subject: Re: Connection issues on Solaris 10 (Accept failed: Bad file

]] "Jim Hayter" 

| I've tried running both 2.0.5 and 2.0.6 on a Sun intel box running
| Solaris 10.
| Varnish works for a while and then starts generating log output like
| examples below, reporting nothing but " Accept failed: Bad file
| I raised the process file descriptor limit, but that did not help.
| Is anyone using Varnish 2.0.x on a Sun intel box running Solaris 10?
| so, do you have any suggestions?

Can you try some of the suggestions on ?  If they help,
please tell us so we can try to find out what's wrong with the ports

Tollef Fog Heen 
Redpill Linpro -- Changing the game!
t: +47 21 54 41 73
varnish-misc mailing list
varnish-misc at

More information about the varnish-misc mailing list