[SOLVED]Failed to start samba due to a system error - SELinux related

Alan_A · January 9, 2017, 10:14am

Sure, output is below. Thanks!

nmb.service - Samba NMB Daemon
Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2017-01-09 19:56:01 AEDT; 4min 40s ago
Main PID: 13178 (code=exited, status=1/FAILURE)

Jan 09 19:56:01 chopsstorage3 systemd[1]: Starting Samba NMB Daemon…
Jan 09 19:56:01 chopsstorage3 systemd[1]: nmb.service: main process exited, code=exited, status=1/FAILU RE
Jan 09 19:56:01 chopsstorage3 systemd[1]: Failed to start Samba NMB Daemon.
Jan 09 19:56:01 chopsstorage3 systemd[1]: Unit nmb.service entered failed state.
Jan 09 19:56:01 chopsstorage3 systemd[1]: nmb.service failed.

Flyer · January 9, 2017, 11:08am

Hi @Alan_A, this doesn’t help us

We can try this
journalctl -xe | grep nmb
journalctl -xe | grep smb

then reading some log:
tail -n 100 /var/log/samba/log.nmbd
tail -n 100 /var/log/samba/log.smbd

Alan_A · January 10, 2017, 8:51am

I only got output from the journalctl -xe | grep nmb. The other three commands returned nothing. Checking the /var/log/samba directory, and the two log files are 0 size.

– Subject: Unit nmb.service has begun start-up
– Unit nmb.service has begun starting up.
Jan 10 19:42:22 chopsstorage3 systemd[1]: nmb.service: main process exited, code=exited, status=1/FAILURE
– Subject: Unit nmb.service has failed
– Unit nmb.service has failed.
Jan 10 19:42:22 chopsstorage3 systemd[1]: Unit nmb.service entered failed state.
Jan 10 19:42:22 chopsstorage3 systemd[1]: nmb.service failed.

Flyer · January 10, 2017, 10:47am

Hi @Alan_A this doesn’t help us

Can you please check with journactl -r if you find something about nmb or smb??

Meanwhile, can you try to ping www.google.com (just to check another net issue)

M.

Alan_A · January 10, 2017, 11:16am

Sorry, I dont see anything in there that is related

I can ping google and other sites ok. Im able to install Rock-Ons so network access is good

Flyer · January 10, 2017, 11:21am

Ok, next step:
can you post your smb.conf file?
M.

Alan_A · January 11, 2017, 7:29am

[global]
log level = 3
map to guest = Bad User
cups options = raw
log file = /var/log/samba/log.%m
printcap name = /dev/null
load printers = no

####BEGIN: Rockstor SAMBA GLOBAL CUSTOM####
workgroup = CHOPSNET
####END: Rockstor SAMBA GLOBAL CUSTOM####

Flyer · January 11, 2017, 8:26am

Hi @Alan_A,
your smb.conf is simple and ok too, so this unfortunately doesn’t help us

Let’s start over: can you describe steps you to raise that error?

M.

Alan_A · January 11, 2017, 9:19am

Sure. It’s a fresh install on a new machine, clean drive. I’ve booted up after install, accepted the license, created admin account etc.Created a pool, then installed a couple of RockOns (OwnCloud and OpenVPN) but not configured them yet.
Subscribe to stable updates and do an update.

I want to start creating some shares, and notice that Samba isnt running, try to start the service (System > Services > Click slider to on) and it fails. Click the spanner icon against Samba to see what options therre are (not many!) and enter my local Workgroup name. Click submit - get error.

Flyer · January 11, 2017, 10:39am

Uhmmm, stupid question of the day:

did you performed a reboot?

M.

Alan_A · January 11, 2017, 11:13am

Not a stupid question, but I have rebooted. I’ve just done another one to be 100% sure, and still same issue.

Flyer · January 11, 2017, 11:36am

Ok, we must at least have some logs so please add here (or upload online and provide links) for
/var/log/samba/log.nmbd and /var/log/samba/log.smbd

Mirko

Flyer · January 11, 2017, 12:05pm

Ok, Hagakure mode on:

systemctl restart nmb +
dmesg

Alan_A · January 11, 2017, 8:46pm

Both log files are still empty
Output from dmesg is

gist.github.com

https://gist.github.com/alanarthur/94f7fc766dd19c81c4e37ad92686175d

dmesg output

[    0.000000] Linux version 4.8.7-1.el7.elrepo.x86_64 (mockbuild@Build64R7) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Thu Nov 10 20:47:24 EST 2016
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.8.7-1.el7.elrepo.x86_64 root=UUID=6e678a9d-b56a-464b-b461-e61bc0f43a4a ro rootflags=subvol=root crashkernel=auto rhgb quiet LANG=en_AU.UTF-8
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format.
[    0.000000] x86/fpu: Using 'eager' FPU context switches.
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009bbff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009bc00-0x000000000009bfff] reserved
[    0.000000] BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved

This file has been truncated. show original

Flyer · January 11, 2017, 11:18pm

Hi @Alan_A can you start other services like ntp??
First thing i noticed is that eth0 renaming and SELinux:

can you check current SELinux status with sestatus -v ?

Another question: are you running Rockstor in a VM or on bare metal?

M.

Alan_A · January 12, 2017, 1:54am

I’m running on bare metal, and yes, I seem to be able to start ntp, nfs etc.

I dont know why the eth0 would be getting renamed - should I try disabling ipv6 perhaps? There are 2 NICs in this box, but only using one, and I just accepted the default config

sestatus output is

SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 30

Process contexts:
Current context: unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
Init context: system_u:system_r:init_t:s0
/usr/sbin/sshd system_u:system_r:sshd_t:s0-s0:c0.c1023

File contexts:
Controlling terminal: unconfined_u:object_r:user_devpts_t:s0
/etc/passwd system_u:object_r:passwd_file_t:s0
/etc/shadow system_u:object_r:shadow_t:s0
/bin/bash system_u:object_r:shell_exec_t:s0
/bin/login system_u:object_r:login_exec_t:s0
/bin/sh system_u:object_r:bin_t:s0 -> system_u:object_r:shell_exec_t:s0
/sbin/agetty system_u:object_r:getty_exec_t:s0
/sbin/init system_u:object_r:bin_t:s0 -> system_u:object_r:init_exec_t:s0
/usr/sbin/sshd system_u:object_r:sshd_exec_t:s0

Flyer · January 12, 2017, 8:45am

Hi @Alan_A, actually some Rockstors get SELinux while Rockstor default has SELinux disabled.

Good reading about this (how to disable it or have it permissive, thanks to @magicalyak howto!) : SELinux and SMB shares unavailable after upgrade to 3.8.15 - #16 by magicalyak

Pls update us
Mirko

Alan_A · January 12, 2017, 8:56am

Bingo. The man’s a genius, thanks very much. I didnt even know what SELinux was, so had to go and do a bit of googling. Looking through the post you linked to, i set it to permissive mode and straight away I was able to start Samba.

I’ve edited the config file to set it to permissive (presumably this makes it permanent rather than just for the current boot cycle) One comment on the linked post recommended not disabling it, any thoughts? Im guessing if it’s not supposed to be on by default, it’s not an issue to disable it?

Flyer · January 12, 2017, 10:30am

Happy to read you’re running your Samba! (and hope you won’t have same issues I’m testing with new Centos 7 1611: bad samba linking stopping ntpd, ping, etc)

Talking about SELinux: @phillxnet & @suman any idea about it supposed to be disabled on Rockstor but sometime ON??

M.

Alan_A · January 12, 2017, 10:38am

In the thread you linked to (or one linked from there), I think I noted that someone had had the same situation when manually adjusting parameters at install to force BTRFS. I had to do the same thing, as my first attempt at install somehow managed to set it to LVM instead. Could be a common cause meaning that the wrong config is getting picked up somewhere at install time??