You are not logged in.
My server updated to this version of samba today and began dumpling core when attempting to start.
After investigating, I found that tevent was updated to 0.9.30 as well.
The problem is with tevent.(seen in the stacktrace) When I rolled it back to 0.9.29, all was well.
I noticed on the gentoo forums that someone had the same issue and the same solution.
Offline
Thank you so much. Spent an hour trying to resolve this.
Offline
https://bugs.archlinux.org/task/50728
Last edited by Alad (2016-09-10 19:38:51)
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
Thank you! I was pulling my hair out.
As an aside, if I'm allowed, ntlm ('sec=ntlm' in fstab or .mount systemd file) was turned off for the sake of security in 4.5. That's something else to fix (remove) if you use it to mount a secure share. Another hair puller.
Last edited by Buddlespit (2016-09-11 02:07:18)
Offline
Same issue after upgrading samba today.
SAMBA — samba crashing on start up INTERNAL ERROR: Signal 11
Now as a new arch and early linux user I will try to roll back a package for the first time. *Done, using downgrader and samba is up and running again.
Last edited by cequalspid (2016-09-10 22:23:27)
Offline
Confirmed. I have been trying to figure out what is happening with my 3 machines that runs samba and have samba shares after upgrading all of them. Could not browse samba shares, see samba shares, even could not see workgroups. It workes for a moment when i manually restarted samba, and than for a moment workgroup was found, and than all was lost. Jeeez, almost half day and wasted...this is the second big bug that is related to samba - later with kio package i could now write to samba shares...
Offline
Despite downgrading tevent which resulted in samba to be run, I had issues accessing files in the share with the WD TV Live home media streamer. The media player stated there are no media files available in the share. Accessing the share was no issue with Windows 10 client.
After downgrading to 4.4.5-2 (packages samba-4.4.5-2-arm, smbclient-4.4.5-2-arm and libwbclient-4.4.5-2-arm), media player found media files again without problems. So it might be that the tevent downgrade in question has issues with such media player OR what could be even worse, the media player has issues with samba 4.5, which remain to be seen.
Offline
Despite downgrading tevent which resulted in samba to be run, I had issues accessing files in the share with the WD TV Live home media streamer. The media player stated there are no media files available in the share. Accessing the share was no issue with Windows 10 client.
After downgrading to 4.4.5-2 (packages samba-4.4.5-2-arm, smbclient-4.4.5-2-arm and libwbclient-4.4.5-2-arm), media player found media files again without problems. So it might be that the tevent downgrade in question has issues with such media player OR what could be even worse, the media player has issues with samba 4.5, which remain to be seen.
Do you know what media player your WD TV Live home media streamer uses/ is based on/ is compiled from? My raspberry pi 3's, running OSMC (Kodi), pick up my media shares just fine. My android phones (VLC and file explorer), Win7&10 (WinExplorer/WMP&VLC) boxes and Linux boxes (Dolphin/VLC) all see the server just fine (now that I downgraded tevent).
Offline
Just in case we have anyone who does not know how to downgrade the commands are as follows:
cd /var/cache/pacman/pkg/
pacman -U tevent-0.9.29-1-x86_64.pkg.tar.xz
The above will work for 64bit arch if you have the previous version installed.
Otherwise the old versions (including 32 bit) can be found at one of the mirrors in your country
Started with Slackware, will run Arch forever.
Offline
Despite downgrading tevent which resulted in samba to be run, I had issues accessing files in the share with the WD TV Live home media streamer. The media player stated there are no media files available in the share. Accessing the share was no issue with Windows 10 client.
After downgrading to 4.4.5-2 (packages samba-4.4.5-2-arm, smbclient-4.4.5-2-arm and libwbclient-4.4.5-2-arm), media player found media files again without problems. So it might be that the tevent downgrade in question has issues with such media player OR what could be even worse, the media player has issues with samba 4.5, which remain to be seen.
From samba 4.5.0 Release notes
http://fossies.org/linux/samba/WHATSNEW.txt
10 UPGRADING
11 =========
12
13 NTLMv1 authentication disabled by default
14 -----------------------------------------
15
16 In order to improve security we have changed
17 the default value for the "ntlm auth" option from
18 "yes" to "no". This may have impact on very old
19 clients which doesn't support NTLMv2 yet.
20
21 The primary user of NTLMv1 is MSCHAPv2 for VPNs and 802.1x.
22
23 By default, Samba will only allow NTLMv2 via NTLMSSP now,
24 as we have the following default "lanman auth = no",
25 "ntlm auth = no" and "raw NTLMv2 auth = no".
perhaps also related to this change ?
Offline
thed0g wrote:Despite downgrading tevent which resulted in samba to be run, I had issues accessing files in the share with the WD TV Live home media streamer. The media player stated there are no media files available in the share. Accessing the share was no issue with Windows 10 client.
After downgrading to 4.4.5-2 (packages samba-4.4.5-2-arm, smbclient-4.4.5-2-arm and libwbclient-4.4.5-2-arm), media player found media files again without problems. So it might be that the tevent downgrade in question has issues with such media player OR what could be even worse, the media player has issues with samba 4.5, which remain to be seen.
From samba 4.5.0 Release notes
http://fossies.org/linux/samba/WHATSNEW.txt
10 UPGRADING 11 ========= 12 13 NTLMv1 authentication disabled by default 14 ----------------------------------------- 15 16 In order to improve security we have changed 17 the default value for the "ntlm auth" option from 18 "yes" to "no". This may have impact on very old 19 clients which doesn't support NTLMv2 yet. 20 21 The primary user of NTLMv1 is MSCHAPv2 for VPNs and 802.1x. 22 23 By default, Samba will only allow NTLMv2 via NTLMSSP now, 24 as we have the following default "lanman auth = no", 25 "ntlm auth = no" and "raw NTLMv2 auth = no".
perhaps also related to this change ?
So far I'm understanding this change, it would result in failing to login to the server. But it logged in fine, it just failed to list any content of the share displaying "No media files" message.
Offline
thed0g wrote:Despite downgrading tevent which resulted in samba to be run, I had issues accessing files in the share with the WD TV Live home media streamer. The media player stated there are no media files available in the share. Accessing the share was no issue with Windows 10 client.
After downgrading to 4.4.5-2 (packages samba-4.4.5-2-arm, smbclient-4.4.5-2-arm and libwbclient-4.4.5-2-arm), media player found media files again without problems. So it might be that the tevent downgrade in question has issues with such media player OR what could be even worse, the media player has issues with samba 4.5, which remain to be seen.
Do you know what media player your WD TV Live home media streamer uses/ is based on/ is compiled from? My raspberry pi 3's, running OSMC (Kodi), pick up my media shares just fine. My android phones (VLC and file explorer), Win7&10 (WinExplorer/WMP&VLC) boxes and Linux boxes (Dolphin/VLC) all see the server just fine (now that I downgraded tevent).
That would be a pain in the ass to figure out, since those are basically black boxes and also without software support since 2012.
Offline
So far I'm understanding this change, it would result in failing to login to the server. But it logged in fine, it just failed to list any content of the share displaying "No media files" message.
You could put smbd in debug mode to figure out what's wrong : smbcontrol smbd debug 3
Offline
Just as an update looks like there was a new build of samba and libs
https://www.archlinux.org/packages/extra/x86_64/samba/
https://www.archlinux.org/packages/extra/x86_64/tevent/
Thanks Tobias!
pacman -Syu and everything is working again.
Started with Slackware, will run Arch forever.
Offline
smbclient-4.5.0-1 installed tevent-0.9.30-1, which gave me no problems, then next -Syu, samba and smbclient-4.5.0-2 upgrade wanted tevent-0.9.29-1 (strange, wanted a regression)
:: Starting full system upgrade...
warning: tevent: local (0.9.30-1) is newer than extra (0.9.29-2)
so smbd and nmbd segfault with samba and smbclient-4.5.0-2 and tevent-0.9.30-1 but work fine with tevent-0.9.29-1 and vs versa, the previous version of samba & smbclient worked fine with the newer version of tevent. Rolling back samba and smbclient continued to segfault, re-upgrading them and then rolling back tevent as others mentioned no more segfaults. and all Windows and Google TV shares and streaming no problem.
∞ hard times make the strong, the strong make good times, good times make the weak, the weak make hard times ∞
Offline
smbclient-4.5.0-1 installed tevent-0.9.30-1, which gave me no problems, then next -Syu, samba and smbclient-4.5.0-2 upgrade wanted tevent-0.9.29-1 (strange, wanted a regression)
:: Starting full system upgrade... warning: tevent: local (0.9.30-1) is newer than extra (0.9.29-2)
so smbd and nmbd segfault with samba and smbclient-4.5.0-2 and tevent-0.9.30-1 but work fine with tevent-0.9.29-1 and vs versa, the previous version of samba & smbclient worked fine with the newer version of tevent. Rolling back samba and smbclient continued to segfault, re-upgrading them and then rolling back tevent as others mentioned no more segfaults. and all Windows and Google TV shares and streaming no problem.
Though my samba is working fine, I'm also getting the tevent warning. Is this some sort of bug in the packaging perhaps?
Offline
Do 'pacman -Syuu' and it should install the version in the repos. The version in the repos was rolled back and as such pacman will not install it automatically since it is an older version. There is a way to make it happen when using only -Syu but I suppose the maintainer of the package decided not to make use of it (or didn't remember).
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
thed0g wrote:So far I'm understanding this change, it would result in failing to login to the server. But it logged in fine, it just failed to list any content of the share displaying "No media files" message.
You could put smbd in debug mode to figure out what's wrong : smbcontrol smbd debug 3
Cheers for the tip, you were correct - it was this change. After updating tevent and samba, I debugged the login.
2016/09/12 16:31:06.900261, 2, pid=14793, effective(0, 0), real(0, 0)] ../libcli/auth/ntlm_check.c:424(ntlm_password_check)
ntlm_password_check: NTLMv1 passwords NOT PERMITTED for user john
But WDTV still logged in somehow, just failed to load the directory content.
[2016/09/12 16:31:06.909002, 3, pid=14793, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth.c:178(auth_check_ntlm_password)
check_ntlm_password: Checking password for unmapped user []\[]@[] with the new password interface
[2016/09/12 16:31:06.909134, 3, pid=14793, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth.c:181(auth_check_ntlm_password)
check_ntlm_password: mapped user is: [POGO]\[]@[]
[2016/09/12 16:31:06.909297, 3, pid=14793, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth.c:249(auth_check_ntlm_password)
check_ntlm_password: guest authentication for user [] succeeded
Which obviously resulted in failing to show any content.
After I've put
ntlm auth = yes
to smb.conf, it was working again.
[2016/09/12 16:36:40.696729, 3, pid=14820, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth.c:178(auth_check_ntlm_p
assword)
check_ntlm_password: Checking password for unmapped user [WORKGROUP]\[john]@[WDTVLIVE] with the new password interface
[2016/09/12 16:36:40.696880, 3, pid=14820, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth.c:181(auth_check_ntlm_p
assword)
check_ntlm_password: mapped user is: [POGO]\[john]@[WDTVLIVE]
[2016/09/12 16:36:40.697958, 3, pid=14820, effective(0, 0), real(0, 0)] ../source3/passdb/lookup_sid.c:1645(get_primary_group_sid)
Forcing Primary Group to 'Domain Users' for john
[2016/09/12 16:36:40.699674, 3, pid=14820, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth.c:249(auth_check_ntlm_password)
check_ntlm_password: sam authentication for user [john] succeeded
[2016/09/12 16:36:40.699896, 2, pid=14820, effective(0, 0), real(0, 0), class=auth] ../source3/auth/auth.c:305(auth_check_ntlm_password)
check_ntlm_password: authentication for user [john] -> [john] -> [john] succeeded
I bet this will confuse quite some users with these kind of older hardware, perhaps adding it to Wiki wouldn't be bad.
Last edited by thed0g (2016-09-12 14:58:18)
Offline