[Bug 388483] Re: smbd panic action with yield_connection name=0x0

[Darren]

I'm also having this problem.
Samba is running on Ubuntu 8.04, and I when either of two windows XP clients connects it sends me this email:
  The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 9866 ().
  This means there was a problem with the program, such as a segfault. However, the executable could not be found for process 9866. It may have died unexpectedly, or you may not have permission to debug the process.

Connecting to the samba share from another Ubuntu machine does not cause
the problem.

It is just a simple read/write file share, with guest users allowed. No
printer sharing yet.

I've done a bit of experimentation and just booting windows doesn't
cause it (I have the file share set to mount automatically). But opening
My Computer (i.e. so I can see the share, and can see free disk space)
does. I.e. I do not need to double-click the share and actually see the
files inside to trigger the alert.

The alert just appears to be noise - once I open the folder I can see
and use all the files without any problem.

The problem is consistent and repeatable. I set "log level = 3" and my /var/log/samba directory is full of various log files, some of them rather large (e.g. 600K). I seem to have one log file per client machine, as well as log.smbd, log.nmbd, a couple of log.winbind* files, and a couple of log.wb-* files.
Which of those do you want to see? I'd rather send it directly to an interested developer rather than post them here, as I'm not knowledgeable about what privacy issues there may be.
Or if you give me a hint of what to look for, I'm happy to trawl through them a bit.

-- 
smbd panic action with yield_connection name=0x0
https://bugs.launchpad.net/bugs/388483
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.