I'll go do that here is just a few minutes.
Not sure what the results will be since the report was 2 months ago.
And yes, if I go across the LAN to the Ubuntu server and store and retrieve
files across the LAN, I can repeat the Panic.
Bill
At 04:16 PM 04/02/14, you wrote:
Thanks for
apport information
** Tags added: apport-collected precise running-unity
** Description changed:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 8302 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is
apport information
** Attachment added: SMBConf.txt
https://bugs.launchpad.net/bugs/1276414/+attachment/4061925/+files/SMBConf.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
apport information
** Attachment added: SambaInstalledVersions.txt
https://bugs.launchpad.net/bugs/1276414/+attachment/4061926/+files/SambaInstalledVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
I have apport already installed.
I issued the following command as root apport-bug
/var/crash/_usr_sbin_smbd.0.crash
Just to make sure, I will attach a text file with the contents.
Thank you,
Wm Lewis
** Attachment added: Crash Report
https://bugs.launchpad.net/ubuntu/+source/samba/+bug
apport was already installed.
Submission made as requested.
Wm Lewis
At 06:38 PM 3/5/2014, you wrote:
Thanks for reporting this bug.
If it is possible to install apport on the system, let apport get a
/var/crash/ report for this failure, and then report that with 'apport-
bug /var/crash
if you need more information.
Wm Lewis
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
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/1287408
Title:
Panic
And another Panic action today. Details below.
-
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 24852 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this
Ok... Done.
At 10:01 PM 2/10/2014, you wrote:
Hello,
So we need some more information. Please run from a terminal window:
apport-collect 1278635
and then change the status of the bug to 'Confirmed'.
Jörg
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
You received this
apport information
** Tags added: apport-collected precise running-unity
** Description changed:
Panic email supplied this:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 19000 (/usr/sbin/smbd).
apport information
** Attachment added: SambaInstalledVersions.txt
https://bugs.launchpad.net/bugs/1278635/+attachment/3977468/+files/SambaInstalledVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
apport information
** Attachment added: SMBConf.txt
https://bugs.launchpad.net/bugs/1278635/+attachment/3977467/+files/SMBConf.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Sorry. When I ran it the first time, it was from a 'remote' terminal window.
Re-ran from the machine in question.
Bill
--
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/1278635
Title:
** Changed in: samba (Ubuntu)
Status: Incomplete = Confirmed
--
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/1278635
Title:
Panic or segfault in Samba
To manage notifications
Another panic or segfault in Samba
This one just occurred right after a reboot of the machine
==
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
0x7f85d6d89c8e in waitpid ()
Public bug reported:
Panic email supplied this:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 19000 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace
Public bug reported:
This is now a routine panic email from Samba.
The samba-dbg package is now installed for debugging future panics. Will
send that information when the next panic hits.
Hope the non-debugged info below might help.
Here is system info
Public bug reported:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 8302 (/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
18 matches
Mail list logo
