*** This bug is a duplicate of bug 388483 ***
https://bugs.launchpad.net/bugs/388483
** This bug has been marked a duplicate of bug 388483
smbd panic action with yield_connection name=0x0
--
Panic or segfault in Samba
https://bugs.launchpad.net/bugs/281188
You received this bug
*** This bug is a duplicate of bug 388483 ***
https://bugs.launchpad.net/bugs/388483
** This bug has been marked a duplicate of bug 388483
smbd panic action with yield_connection name=0x0
--
Panic or segfault in Samba
https://bugs.launchpad.net/bugs/281188
You received this bug
The problem is those are different crashes, all ending in smb-panic, but
most certainly coming from very different causes. Some of those Intrepid
issues were fixed in Jaunty, so I would be interested in knowing if any
of you can still reproduce their crash after an upgrade to Jaunty. If
yes,
The problem is those are different crashes, all ending in smb-panic, but
most certainly coming from very different causes. Some of those Intrepid
issues were fixed in Jaunty, so I would be interested in knowing if any
of you can still reproduce their crash after an upgrade to Jaunty. If
yes,
I'm on intrepid and I get this maybe once a week. I'm not sure if this
is the same issue, since the stack trace looks slightly different:
[Thread debugging using libthread_db enabled]
[New Thread 0x7fbc9b551710 (LWP 20441)]
0x7fbc981058f5 in waitpid () from /lib/libc.so.6
#0
I'm on intrepid and I get this maybe once a week. I'm not sure if this
is the same issue, since the stack trace looks slightly different:
[Thread debugging using libthread_db enabled]
[New Thread 0x7fbc9b551710 (LWP 20441)]
0x7fbc981058f5 in waitpid () from /lib/libc.so.6
#0
I'm on Intrepid (plan to upgrade to Jaunty soon) and I have literally
thousands of these messages in my dmesg and logs after an uptime of a
few days:
[215799.967346] type=1502 audit(1243006362.717:7274):
operation=inode_permission requested_mask=rw:: denied_mask=w::
fsuid=0
I'm on Intrepid (plan to upgrade to Jaunty soon) and I have literally
thousands of these messages in my dmesg and logs after an uptime of a
few days:
[215799.967346] type=1502 audit(1243006362.717:7274):
operation=inode_permission requested_mask=rw:: denied_mask=w::
fsuid=0
I have the same problem in hardy (64bit) since 7.5.09. All patches are
installed. After installing the debugging symbols, I get this stack
trace:
[Thread debugging using libthread_db enabled]
[New Thread 0x7f1873834700 (LWP 26480)]
0x7f1870a3b4a5 in waitpid () from /lib/libc.so.6
#0
I have the same problem in hardy (64bit) since 7.5.09. All patches are
installed. After installing the debugging symbols, I get this stack
trace:
[Thread debugging using libthread_db enabled]
[New Thread 0x7f1873834700 (LWP 26480)]
0x7f1870a3b4a5 in waitpid () from /lib/libc.so.6
#0
This has started happening to me with Jaunty, however I get the same as
Ali above: it's not able to give a backtrace of any sort.
--
Panic or segfault in Samba
https://bugs.launchpad.net/bugs/281188
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This has started happening to me with Jaunty, however I get the same as
Ali above: it's not able to give a backtrace of any sort.
--
Panic or segfault in Samba
https://bugs.launchpad.net/bugs/281188
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm being affected by this one for ~9 month(s)
Still no fix or workaround on this bug ?
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 15316 ().
This means there was a problem with the program, such as a segfault.
However, the executable could not be
I'm being affected by this one for ~9 month(s)
Still no fix or workaround on this bug ?
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 15316 ().
This means there was a problem with the program, such as a segfault.
However, the executable could not be
I also have same problems like above.
---
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 30746 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this
I also have same problems like above.
---
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 30746 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this
I have the same problem on latest Jaunty/amd64. I also saw these lines
in dmesg:
[ 50.337015] type=1502 audit(1235553386.815:23): operation=inode_permission
requested_mask=r:: denied_mask=r:: fsuid=0
name=/usr/share/samba/upcase.dat.samba3 pid=4542 profile=/usr/sbin/nmbd
[ 50.337028]
I have the same problem on latest Jaunty/amd64. I also saw these lines
in dmesg:
[ 50.337015] type=1502 audit(1235553386.815:23): operation=inode_permission
requested_mask=r:: denied_mask=r:: fsuid=0
name=/usr/share/samba/upcase.dat.samba3 pid=4542 profile=/usr/sbin/nmbd
[ 50.337028]
I've been experiencing the same problem since upgrading from Intrepid to
Jaunty Development. Crash occurs on reboot.
==
sc...@baka:~$ lsb_release -a
LSB Version:
I've been experiencing the same problem since upgrading from Intrepid to
Jaunty Development. Crash occurs on reboot.
==
sc...@baka:~$ lsb_release -a
LSB Version:
I am attaching the report self-generated by samba after installing
samba-dbg.
** Attachment added: new file
http://launchpadlibrarian.net/22417358/new%20file
--
Panic or segfault in Samba
https://bugs.launchpad.net/bugs/281188
You received this bug notification because you are a member of
Same problem here. I have just copied some files from a read only samba
share to a Windows 2000 client.
[Thread debugging using libthread_db enabled]
[New Thread 0x7f42848f9700 (LWP 9676)]
0x7f42816b3f15 in waitpid () from /lib/libc.so.6
#0 0x7f42816b3f15 in waitpid () from
I am attaching the report self-generated by samba after installing
samba-dbg.
** Attachment added: new file
http://launchpadlibrarian.net/22417358/new%20file
--
Panic or segfault in Samba
https://bugs.launchpad.net/bugs/281188
You received this bug notification because you are a member of
Same problem here. I have just copied some files from a read only samba
share to a Windows 2000 client.
[Thread debugging using libthread_db enabled]
[New Thread 0x7f42848f9700 (LWP 9676)]
0x7f42816b3f15 in waitpid () from /lib/libc.so.6
#0 0x7f42816b3f15 in waitpid () from
Same here:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 16283 (/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
Same here:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 16283 (/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
I'm also having this problem with a new install of Ubuntu 8.10 LAMP Server
(+ubuntu desktop) on a mixed Win/OSX network.
[New Thread 0xb74946d0 (LWP 7227)]
0xb79bb424 in __kernel_vsyscall ()
#0 0xb79bb424 in __kernel_vsyscall ()
#1 0xb75d85e3 in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2
I'm also having this problem with a new install of Ubuntu 8.10 LAMP Server
(+ubuntu desktop) on a mixed Win/OSX network.
[New Thread 0xb74946d0 (LWP 7227)]
0xb79bb424 in __kernel_vsyscall ()
#0 0xb79bb424 in __kernel_vsyscall ()
#1 0xb75d85e3 in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2
shan...@shankhs-desktop:~$ lsb_release -rd
Description:Ubuntu 8.10
Release:8.10
shan...@shankhs-desktop:~$ uname -a
Linux shankhs-desktop 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686
GNU/Linux
shan...@shankhs-desktop:~$ apt-cache policy samba
samba:
Installed:
I am having the same problem.I am attaching the mail I am getting .
** Attachment added: samba.txt
http://launchpadlibrarian.net/20838959/samba.txt
--
Panic or segfault in Samba
https://bugs.launchpad.net/bugs/281188
You received this bug notification because you are a member of Ubuntu
shan...@shankhs-desktop:~$ lsb_release -rd
Description:Ubuntu 8.10
Release:8.10
shan...@shankhs-desktop:~$ uname -a
Linux shankhs-desktop 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686
GNU/Linux
shan...@shankhs-desktop:~$ apt-cache policy samba
samba:
Installed:
I have the same problem
[Thread debugging using libthread_db enabled]
[New Thread 0x7f92bf9af700 (LWP 1925)]
0x7f92bc774f15 in waitpid () from /lib/libc.so.6
#0 0x7f92bc774f15 in waitpid () from /lib/libc.so.6
#1 0x7f92bc70d461 in ?? () from /lib/libc.so.6
#2 0x7f92bfbbbe38 in
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 6015 (/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 6015 (/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
** Attachment added: panic
http://launchpadlibrarian.net/18390962/panic
--
Panic or segfault in Samba
https://bugs.launchpad.net/bugs/281188
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
35 matches
Mail list logo
