smbd crashed with SIGABRT in strlen()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
It occurs randomly. And this was the second time.
$lsb_release -rd
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
$apt-cache policy samba
samba:
Installed: 2:4.3.3+
Candidate: 2:4.3.3+
Version table:
*** 2:4.3.3+
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: samba 2:4.3.3+
Uname: Linux 4.5.0-040500rc5
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
BothFailedConnect: Yes
Date: Tue Mar 8 10:20:06 2016
ExecutablePath: /usr/sbin/smbd
InstallationDate: Installed on 2015-11-06 (122 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
NmbdLog:
Packet send failed to 10.0.3.255(138) ERRNO=Invalid argument
Packet send failed to 10.0.3.255(138) ERRNO=Invalid argument
Packet send failed to 10.0.3.255(138) ERRNO=Invalid argument
Packet send failed to 10.0.3.255(138) ERRNO=Invalid argument
Packet send failed to 10.0.3.255(138) ERRNO=Invalid argument
ProcCmdline: /usr/sbin/smbd -D
ProcEnviron:
LANGUAGE=en_IN:en
PATH=(custom, no user)
LANG=en_IN
SambaServerRegr
Signal: 6
SmbConfIncluded: Yes
SmbLog: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsFailed to delete pidfile /var/run/
SourcePackage: samba
StacktraceTop:
strlen () at ../sysdeps/
push_ucs2_talloc () from /usr/lib/
E_md4hash () from /usr/lib/
create_
?? () from /usr/lib/
Title: smbd crashed with SIGABRT in strlen()
UpgradeStatus: Upgraded to xenial on 2016-03-07 (0 days ago)
UserGroups:
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1514766, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.