You are not logged in.

Pages: 1

#1 2015-10-04 06:07:26

Mirhawk
Member
Registered: 2015-10-04
Posts: 6

Problems with Samba after update and problems with deluge service

Hi, yesterday I updated my Arch OS using pacman -Syu . Then after rebooting the Arch System, I'm no longer able to access shared folder on My other systems. Checking on the Arch system I found that the smbd.service and nmbd.service were not started and were giving errors whle starting, which are as follows. Please go through them and let Me know what the problem is.

sudo systemctl start smbd.service
Job for smbd.service failed because the control process exited with error code. See "systemctl status smbd.service" and "journalctl -xe" for details.
[mnp@mn ~]$ sudo systemctl status smbd.service
* smbd.service - Samba SMB/CIFS server
   Loaded: loaded (/usr/lib/systemd/system/smbd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2015-10-04 16:54:33 IST; 6s ago
  Process: 3269 ExecStart=/usr/bin/smbd -D (code=exited, status=1/FAILURE)
^C[mnp@mn ~]$ sudo systemctl status smbd.service -l
* smbd.service - Samba SMB/CIFS server
   Loaded: loaded (/usr/lib/systemd/system/smbd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2015-10-04 16:54:33 IST; 14s ago
  Process: 3269 ExecStart=/usr/bin/smbd -D (code=exited, status=1/FAILURE)
^C[mnp@mn ~]$ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
--
-- Kernel start-up required KERNEL_USEC microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 170330 microseconds.
Oct 04 16:44:38 mn systemd[1059]: deluged.service: Failed at step EXEC spawning
-- Subject: Process /usr/bin/deluged could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/bin/deluged could not be executed and failed.
--
-- The error number returned by this process is 2.
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Main process exited, code=exi
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Unit entered failed state.
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Failed with result 'exit-code
Oct 04 16:45:06 mn polkit-agent-helper-1[1168]: pam_unix(polkit-1:auth): authent

[mnp@mn ~]$ journalctl -r
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
-- Logs begin at Sun 2012-01-01 11:00:53 IST, end at Sun 2015-10-04 16:45:06 IST
Oct 04 16:45:06 mn polkit-agent-helper-1[1168]: pam_unix(polkit-1:auth): authent
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Failed with result 'exit-code
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Unit entered failed state.
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Main process exited, code=exi
Oct 04 16:44:38 mn systemd[1059]: deluged.service: Failed at step EXEC spawning
Oct 04 16:44:38 mn systemd[1055]: Startup finished in 170ms.
Oct 04 16:44:38 mn systemd[1055]: Reached target Default.
Oct 04 16:44:38 mn systemd[1055]: Started Deluge Daemon.
Oct 04 16:44:38 mn systemd[1055]: Reached target Basic System.
Oct 04 16:44:38 mn systemd[1055]: Reached target Sockets.
Oct 04 16:44:38 mn systemd[1055]: Reached target Timers.
Oct 04 16:44:38 mn systemd[1055]: Listening on D-Bus User Message Bus Socket.
Oct 04 16:44:38 mn systemd[1055]: Reached target Paths.
-- Reboot --
Oct 04 16:41:37 mn bash[8429]: rtorrent still running...
Oct 04 16:41:37 mn bash[8429]: rtorrent still running...
Oct 04 16:41:36 mn bash[8429]: rtorrent still running...
Oct 04 16:41:36 mn bash[8429]: rtorrent still running...
Oct 04 16:41:35 mn bash[8429]: rtorrent still running...
Oct 04 16:41:35 mn systemd[472]: Received SIGRTMIN+24 from PID 8438 (kill).
Oct 04 16:41:34 mn systemd[472]: Stopped target Timers.
Oct 04 16:41:34 mn systemd[472]: Starting Exit the Session...

nmbd.service

sudo systemctl start nmbd.service -l
Job for nmbd.service failed because the control process exited with error code. See "systemctl status nmbd.service" and "journalctl -xe" for details.
[mnp@mn ~]$ sudo systemctl status nmbd.service -l
* nmbd.service - Samba NetBIOS name server
   Loaded: loaded (/usr/lib/systemd/system/nmbd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2015-10-04 16:56:25 IST; 7s ago
  Process: 3677 ExecStart=/usr/bin/nmbd -D (code=exited, status=1/FAILURE)
[mnp@mn ~]$ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
--
-- Kernel start-up required KERNEL_USEC microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 170330 microseconds.
Oct 04 16:44:38 mn systemd[1059]: deluged.service: Failed at step EXEC spawning
-- Subject: Process /usr/bin/deluged could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/bin/deluged could not be executed and failed.
--
-- The error number returned by this process is 2.
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Main process exited, code=exi
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Unit entered failed state.
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Failed with result 'exit-code
Oct 04 16:45:06 mn polkit-agent-helper-1[1168]: pam_unix(polkit-1:auth): authent

[mnp@mn ~]$ journalctl -r
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
-- Logs begin at Sun 2012-01-01 11:00:53 IST, end at Sun 2015-10-04 16:45:06 IST
Oct 04 16:45:06 mn polkit-agent-helper-1[1168]: pam_unix(polkit-1:auth): authent
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Failed with result 'exit-code
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Unit entered failed state.
Oct 04 16:44:38 mn systemd[1055]: deluged.service: Main process exited, code=exi
Oct 04 16:44:38 mn systemd[1059]: deluged.service: Failed at step EXEC spawning
Oct 04 16:44:38 mn systemd[1055]: Startup finished in 170ms.
Oct 04 16:44:38 mn systemd[1055]: Reached target Default.
Oct 04 16:44:38 mn systemd[1055]: Started Deluge Daemon.
Oct 04 16:44:38 mn systemd[1055]: Reached target Basic System.
Oct 04 16:44:38 mn systemd[1055]: Reached target Sockets.
Oct 04 16:44:38 mn systemd[1055]: Reached target Timers.
Oct 04 16:44:38 mn systemd[1055]: Listening on D-Bus User Message Bus Socket.
Oct 04 16:44:38 mn systemd[1055]: Reached target Paths.
-- Reboot --
Oct 04 16:41:37 mn bash[8429]: rtorrent still running...
Oct 04 16:41:37 mn bash[8429]: rtorrent still running...
Oct 04 16:41:36 mn bash[8429]: rtorrent still running...
Oct 04 16:41:36 mn bash[8429]: rtorrent still running...
Oct 04 16:41:35 mn bash[8429]: rtorrent still running...
Oct 04 16:41:35 mn systemd[472]: Received SIGRTMIN+24 from PID 8438 (kill).
Oct 04 16:41:34 mn systemd[472]: Stopped target Timers.
Oct 04 16:41:34 mn systemd[472]: Starting Exit the Session...

I tried removing (pacman -R samba )and re installing samba(pacman -S samba) and using the default configuration as smb.conf(cp smb.conf.default smb.conf), yet nothing works.

About deluge, I have removed deluge since I don't need it using pacman -R deluge. Yet it shows up the systemctl services. How do I remove it completely?

Offline

#2 2015-10-04 06:15:57

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,598

Re: Problems with Samba after update and problems with deluge service

https://bbs.archlinux.org/viewtopic.php?id=202204 ?

Oh, to get rid of deluge, try disabling the service.

Last edited by Scimmia (2015-10-04 06:16:55)

Online

#3 2015-10-04 08:46:24

Mirhawk
Member
Registered: 2015-10-04
Posts: 6

Re: Problems with Samba after update and problems with deluge service

Scimmia wrote:

https://bbs.archlinux.org/viewtopic.php?id=202204 ?

Oh, to get rid of deluge, try disabling the service.

Thanks a lot, guess should have searched more extensively! Also, just disabling the process would work? Is there no way to remove it permanently?

Offline

Pages: 1

Board footer

Powered by FluxBB