It's difficult to do anything about this without the crash file, or
steps to reproduce it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778456
Title:
Panic in gencache_stabilize
To manage notific
Hum,
Date: Wed, 22 Aug 2018 07:40:05 +0200 (CEST)
From: root
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 2004 (/usr/sbin/winbindd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gd
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778456
T
Hi Andreas,
My /var/crash was empty (and still is; I got a new crash mail
yesterday).
Regards
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778456
Title:
Panic in gencache_stabilize
To manage no
Thanks
Could you check if there is a crash file in /var/crash about samba, and
then attach it to this bug? Note that it may contain sensitive
information.
Alternatively you may install the debug symbols packages (see
https://wiki.ubuntu.com/Debug%20Symbol%20Packages) and extract the core
dump fro
I've also this in log.winbindd:
[2018/06/24 23:32:21.438678, 0]
../source3/winbindd/winbindd.c:243(winbindd_sig_term_handler)
Got sig[15] terminate (is_parent=1)
[2018/06/25 06:33:59.854508, 0]
../source3/winbindd/winbindd_cache.c:3170(initialize_winbindd_cache)
initialize_winbindd_cache:
