Traceback (most recent call last):
File "/opt/rockstor/src/rockstor/smart_manager/views/samba_service.py", line 107, in post
systemctl('nmb', command)
File "/opt/rockstor/src/rockstor/system/services.py", line 64, in systemctl
return run_command([SYSTEMCTL_BIN, switch, service_name])
File "/opt/rockstor/src/rockstor/system/osi.py", line 109, in run_command
raise CommandException(cmd, out, err, rc)
CommandException: Error running a command. cmd = ['/usr/bin/systemctl', 'start', 'nmb']. rc = 1. stdout = ['']. stderr = ['Job for nmb.service failed because the control process exited with error code. See "systemctl status nmb.service" and "journalctl -xe" for details.', '']
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.
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.
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.
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
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
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?
