You are not logged in.

#1 2020-01-14 11:35:32

makh
Member
Registered: 2011-10-10
Posts: 238

Smb not starting after suspend failure

Hi

After suspend failure, on restart I get this:

systemctl status smb
● smb.service - Samba SMB Daemon
     Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled; vendor preset: disabled)
     Active: inactive (dead)
systemctl status nmb
● nmb.service - Samba NMB Daemon
     Loaded: loaded (/usr/lib/systemd/system/nmb.service; disabled; vendor preset: disabled)
     Active: inactive (dead)

Even after starting both services, now manually; I am unable to access the windows share.

Kindly advise.

Thankyou


OS:  Arch  &  Debian
System: HP Probook 440 G2
WM: Openbox

Offline

#2 2020-01-14 12:28:02

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 9,983

Re: Smb not starting after suspend failure

That doesn't really help, what logs do you get when doing so? Also to be clear, these are for the server side of samba, if you are a client connecting to a Windows share, they have no relevance and you will want to elaborate on which  method you used to connect to said Windows share.

Offline

#3 2020-01-15 04:03:21

makh
Member
Registered: 2011-10-10
Posts: 238

Re: Smb not starting after suspend failure

Hello

Sorry for incomplete information.

I am on Client.

I use Thunar or Nemo to connect.

After starting smb and nmb:

Logs:

systemctl status smb
● smb.service - Samba SMB Daemon
     Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled; vendor preset: disabled)
     Active: active (running) since Wed 2020-01-15 08:58:30 PKT; 49s ago
       Docs: man:smbd(8)
             man:samba(7)
             man:smb.conf(5)
   Main PID: 3343 (smbd)
     Status: "smbd: ready to serve connections..."
      Tasks: 4 (limit: 4557)
     Memory: 13.5M
     CGroup: /system.slice/smb.service
             ├─3343 /usr/bin/smbd --foreground --no-process-group
             ├─3345 /usr/bin/smbd --foreground --no-process-group
             ├─3346 /usr/bin/smbd --foreground --no-process-group
             └─3347 /usr/bin/smbd --foreground --no-process-group

Jan 15 08:58:30 machine1 smbd[3343]:   reopen_one_log: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or direc>
Jan 15 08:58:30 machine1 smbd[3343]: [2020/01/15 08:58:30.258994,  0] ../../lib/util/debug.c:1090(reopen_one_log)
Jan 15 08:58:30 machine1 smbd[3343]:   reopen_one_log: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or direc>
Jan 15 08:58:30 machine1 smbd[3343]: [2020/01/15 08:58:30.259085,  0] ../../lib/util/debug.c:1090(reopen_one_log)
Jan 15 08:58:30 machine1 smbd[3343]:   reopen_one_log: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or direc>
Jan 15 08:58:30 machine1 smbd[3343]: [2020/01/15 08:58:30.622145,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Jan 15 08:58:30 machine1 systemd[1]: Started Samba SMB Daemon.
Jan 15 08:58:30 machine1 smbd[3343]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Jan 15 08:58:30 machine1 smbd[3347]: [2020/01/15 08:58:30.654045,  0] ../../lib/util/debug.c:1090(reopen_one_log)
Jan 15 08:58:30 machine1 smbd[3347]:   reopen_one_log: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or direc>

systemctl status nmb
● nmb.service - Samba NMB Daemon
     Loaded: loaded (/usr/lib/systemd/system/nmb.service; disabled; vendor preset: disabled)
     Active: active (running) since Wed 2020-01-15 09:01:19 PKT; 3s ago
       Docs: man:nmbd(8)
             man:samba(7)
             man:smb.conf(5)
   Main PID: 3514 (nmbd)
     Status: "nmbd: ready to serve connections..."
      Tasks: 1 (limit: 4557)
     Memory: 3.2M
     CGroup: /system.slice/nmb.service
             └─3514 /usr/bin/nmbd --foreground --no-process-group

Jan 15 09:01:19 machine systemd[1]: Starting Samba NMB Daemon...
Jan 15 09:01:19 machine nmbd[3514]: [2020/01/15 09:01:19.924428,  0] ../../lib/util/debug.c:1090(reopen_one_log)
Jan 15 09:01:19 machine nmbd[3514]:   reopen_one_log: Unable to open new log file '/usr/local/samba/var/log.': No such file or directory
Jan 15 09:01:19 machine nmbd[3514]: [2020/01/15 09:01:19.925220,  0] ../../lib/util/debug.c:1090(reopen_one_log)
Jan 15 09:01:19 machine nmbd[3514]:   reopen_one_log: Unable to open new log file '/usr/local/samba/var/log.nmbd': No such file or direc>
Jan 15 09:01:19 machine nmbd[3514]: [2020/01/15 09:01:19.926571,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Jan 15 09:01:19 machine nmbd[3514]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Jan 15 09:01:19 machine systemd[1]: Started Samba NMB Daemon.

I am unable to view shared computers.

Edit 1: nothing traceable on dmesg.

Thankyou

Last edited by makh (2020-01-15 04:06:26)


OS:  Arch  &  Debian
System: HP Probook 440 G2
WM: Openbox

Offline

#4 2020-01-15 08:43:59

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 9,983

Re: Smb not starting after suspend failure

Probably a variant of https://bugs.archlinux.org/task/63899

Do you get a coredump of gvfs (though those should often land in dmesg as well): https://wiki.archlinux.org/index.php/Co … _core_dump

Offline

#5 2020-01-15 09:05:59

seth
Member
Registered: 2012-09-03
Posts: 15,333

Re: Smb not starting after suspend failure

I am on Client.

After starting smb and nmb

You don't need an smb daemon on the client.

Cut out the GUI browsers, can you "view shared computers" with smbclient/smbtree?
https://wiki.archlinux.org/index.php/Samba#Client

Also:

pacman -Qs gvfs-smb

Edit: reminder to self, always F5 before answering. always F5 before answering. always F5 before answering. always F5 before answering.

Last edited by seth (2020-01-15 09:07:04)

Offline

#6 2020-01-16 10:21:01

makh
Member
Registered: 2011-10-10
Posts: 238

Re: Smb not starting after suspend failure

Hi

I tried:

pacman -U /var/cache/pacman/pkg/gvfs-smb-1.42.1-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/gvfs-1.42.1-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/gvfs-mtp-1.42.1-1-x86_64.pkg.tar.xz

It is working for now.

But the actual source of error was suspend failure!

coredumpctl info gvfs
No coredumps found.

Thankyou


OS:  Arch  &  Debian
System: HP Probook 440 G2
WM: Openbox

Offline

#7 2020-01-16 11:32:24

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 9,983

Re: Smb not starting after suspend failure

It isn't guaranteed that gvfs is the name of the process, look at the actual list.

Offline

#8 2020-01-24 12:09:25

makh
Member
Registered: 2011-10-10
Posts: 238

Re: Smb not starting after suspend failure

Hi

I tried to trace, but couldnt find.

Thankyou


OS:  Arch  &  Debian
System: HP Probook 440 G2
WM: Openbox

Offline

Board footer

Powered by FluxBB