[Samba] Samba in Opensuse Leap 42.1

Orbb orbb1 at centrum.cz
Tue Apr 19 19:19:39 UTC 2016


Hi all, I use Samba for production enviroment happily from version I think 4.0.2 and it worked really well. I started on OpenSuse 12.3, than upgraded to 13.1. I installing upgrades nonfrequently, sometimes I recompile samba to newer version. Everything worked fine until some update on Opensuse. Than my servers started freezing (most of it is virtualized on VMWare esxi 5.5). Sometimes happen total "freeze", no respond to ping, when I open console its frozen on Login dialog but I cant write anything and only way is reboot. Sometimes its just reboot server completely (I have encrypted LVM volumes so I know when its happen). So I decided to reinstall everything from scratch on latest Leap 42.1. I install only basic system without GUI, than I compile samba (prepare this packades: openldap2 openldap2-devel krb5-client libgnutls-devel libacl-devel python-devel cups cups-devel) and everything worked well, I restore backup from old machine and go sleep. Everything worked like a charm,
  but after two days, server rebooted ... Problem is, there is nothing related in logs, I read everytime journalctl but now hint here :(. I decided problem is in samba-opensuse, because I use more virtual machines for different purposes (webserver, mailserver with Kerio connect, ftp server ect) and they dont have any problems. Can you give me any advices ? Its happen on diferent physical servers, in diferent companies ... Same problems :(. Thanks for your time :)

I use Samba as DC, nothing special in smb.conf, here is what I use:
[global]
<------>workgroup = AVAX
<------>realm = AVAX.LOC
<------>netbios name = DC-01
<------>server role = active directory domain controller
<------>dns forwarder = 192.168.1.254
<------>allow dns updates = nonsecure
<------>load printers = yes

nothing more.

krb5 configured, DNS worked fine, replication between servers worked fine ... everything worked great expect sometimes server hangs, reboots itself or freeze :(. After restart it worked fine again. It does on two years old installation same think like on new only two days old :(


in journalctl is after each restart about 40 of this lines
dub 09 15:00:48 linux-52z0 systemd-udevd[265]: maximum number (136) of children reached
its red-colored but I think its just informational message, but not sure


some other lines related to samba, I thonk its OK but I am not expert :)
dub 15 10:10:51 dc-01 samba[2268]: [2016/04/15 10:10:50.997847,  0] ../source4/smbd/server.c:373(binary_smbd_main)
dub 15 10:10:51 dc-01 samba[2268]: samba version 4.4.0 started.
dub 15 10:10:51 dc-01 samba[2268]: Copyright Andrew Tridgell and the Samba Team 1992-2016
dub 15 10:10:51 dc-01 samba[2270]: [2016/04/15 10:10:51.814636,  0] ../source4/smbd/server.c:485(binary_smbd_main)
dub 15 10:10:51 dc-01 samba[2270]: samba: using 'standard' process model
dub 15 10:10:51 dc-01 samba[2270]: [2016/04/15 10:10:51.831253,  0] ../lib/util/become_daemon.c:124(daemon_ready)
dub 15 10:10:51 dc-01 samba[2270]: STATUS=daemon 'samba' finished starting up and ready to serve connections
dub 15 10:10:52 dc-01 winbindd[2285]: [2016/04/15 10:10:52.198716,  0] ../source3/winbindd/winbindd_cache.c:3245(initialize_winbindd_cache)
dub 15 10:10:52 dc-01 winbindd[2285]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
dub 15 10:10:52 dc-01 smbd[2274]: [2016/04/15 10:10:52.725014,  0] ../lib/util/become_daemon.c:124(daemon_ready)
dub 15 10:10:52 dc-01 smbd[2274]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
dub 15 10:10:52 dc-01 winbindd[2285]: [2016/04/15 10:10:52.978657,  0] ../lib/util/become_daemon.c:124(daemon_ready)
dub 15 10:10:52 dc-01 winbindd[2285]: STATUS=daemon 'winbindd' finished starting up and ready to serve connections


Thanks for your time ... 


Best Regards from Czech Republic
Michal Suk



More information about the samba mailing list