🚀 go-pugleaf

We are getting some strange errors on one of our (busy) AUFS servers:

09:29:03 12/21/92  New session 16 started on server socket 0, count 104
09:29:03 12/21/92  Session 16 from [Network 56.146, node 30, socket 250]
09:29:03 12/21/92  Login requested for anthonyh (we are running as root)
09:29:03 12/21/92  pid 10537 starting for session 16
09:29:03 12/21/92  Woops, no more sessions
09:29:03 12/21/92  Login: user anthonyh, home directory /home/fennel/isops/anthonyh
09:29:03 12/21/92  Using protocol 'AFPVersion 2.0'
09:40:03 12/21/92  Session (12) closed
09:40:03 12/21/92  Recorded terminated inferior Aufs PID 10018
09:40:03 12/21/92  process 10018, session 12 terminated with exit code 0
09:40:03 12/21/92  1616 messages out, 2649 in, CPU 3.50 user 20.61 system
09:40:03 12/21/92  Process 10018 terminated
09:40:03 12/21/92  Okay, sessions should be available
09:40:03 12/21/92  Waiting for session 12 to activate
09:40:05 12/21/92  New session 12 started on server socket 0, count 105
09:40:05 12/21/92  Session 12 from [Network 56.147, node 28, socket 248]
09:40:05 12/21/92  Login requested for markr (we are running as root)
09:40:05 12/21/92  pid 10751 starting for session 12
09:40:05 12/21/92  Woops, no more sessions

It looks to us as though the tickle/idle timout code is not clearing the ASPSkt
entry correctly - or in time to cope with the session number allocation
requests?

Has anyone seen this before or shall we start to dig deeper?

-- 

phil 
   ___/   /
   /_/)  /       Phil Male, Director, Information Systems Engineering
  / /_ '/  Computer Newspaper Services, The Bishops Manor, Howden, DN14 7BL
 / / ///

Feel disillusioned?  I've got some great new illusions ...