The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 11874 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 24005 ().
This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 24005.
It may have died unexpectedly, or you may not have permission to debug
[Expired for samba (Ubuntu) because there has been no activity for 60
days.]
** Changed in: samba (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Sorry, I meant to mention that I'm running Lucid Server 64-bit.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/657972
Title:
Panic or segfault in Samba
--
Ubuntu-server-bugs
I'm having this error, too. Most of mine contained a backtrace nearly
identical to Edson Manners', but a few had the executable could not be
found message. I think this might be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/388483
This bug is definitely still around. The
** This bug has been flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/657972
Title:
Panic or segfault in Samba
--
Ubuntu-server-bugs mailing list
I have the same problem:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 1293 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the program
Le 01/02/2011 19:27, Chuck Short a écrit :
Can you install the samba-dbg package and try to reproduce this?
Thanks
chuck
Samba-dbg IS installed :
patrice@grosbill:~$ dpkg -s samba-dbg
Package: samba-dbg
Status: install ok installed
Priority: extra
Section: debug
Installed-Size: 129132
Can you install the samba-dbg package and try to reproduce this?
Thanks
chuck
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
https://bugs.launchpad.net/bugs/657972
Title:
Panic or segfault in Samba
--
I am not getting this anymore. I think if I remember correctly I opened
another port but it's been a while since I looked into this problem.
On Tue, Feb 1, 2011 at 10:27 AM, Chuck Short
chuck.sh...@canonical.comwrote:
Can you install the samba-dbg package and try to reproduce this?
Thanks
I don't know if this log helps but I get this too. 10.04 upgraded
to 10.10 (also have 3 multiple keyring sign-ons at startup)
---
Date: Thu, 09 Dec 2010 19:27:56 -0500
To: root
Subject: Panic or segfault in Samba
User-Agent: Heirloom mailx
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: samba
I get the following message in the root mailbox :
-
The Samba 'panic action' script,
That is THE problem :
1- I just noticed a delay when connecting my Win XP PC to the samba share.
(maybe , no sure)
2- the connection was OK after that
At the end of the day I checked my mailbox and found the panic
message, with NO backtrace.
Nothing in syslog.
What can I do now to get more
Thank you for opening this bug and helping make Ubuntu better.
Unfortunately, there is nothing we can do until we actually know what
happened.
You can try to add more data here by running ´apport-collect 657972',
which will attach a series of logs to this bug.
** Changed in: samba (Ubuntu)
14 matches
Mail list logo
