General discussion about Chef

[chef] Re: Re: 0.9.0 -> 0.9.6 results in eventmachine reporting "no acceptor"


Chronological Thread 
  • From: Ringo De Smet < >
  • To:
  • Subject: [chef] Re: Re: 0.9.0 -> 0.9.6 results in eventmachine reporting "no acceptor"
  • Date: Fri, 16 Jul 2010 17:31:09 +0200
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=jVir78WjmzZNocqp32LLz6Lo91s2ZQEXdGAYpFRhbEWSu7Bdg2RiZd2yNTCPekgvZM o5hUKY58XteLudKM96vuOYpWqva2y/npNYA01yLCjKPGAccm8tsvNsdjkFVW0gdbIDK4 3qZvx+NyFUYGFRoLmB0MSriey7BbwOlXSEkZs=
On 16 July 2010 17:10, Joe Williams 
< >
 wrote:
>
> This is generally because something is already listening on the port. Try 
> "lsof -nP | grep LISTEN" and kill the pid that's listening on the port.
>
> To that end has anyone noticed this happening when starting/stopping with 
> runit? I've seen a couple times where this happens on a runit restart.

Tnx. I did "sv stop chef-XXX" for several chef subsystems before the
upgrade of the gems, but as you mentioned, some of the services didn't
stop at all. All OK now after a *real* restart.

Ringo

Archive powered by MHonArc 2.6.16.

§