[SOLVED]Samba has stopped working on my Mageia 7

This forum is dedicated to testing early releases and cauldron : Howtos, tips, tricks and user global feedback and thoughts...

Helpful tip :
For bugs tracking we use : https://bugs.mageia.org = The Mageia Bug Tracker
In this bug tracker you'll find already reported bugs and you'll be able to report those you have found....

[SOLVED]Samba has stopped working on my Mageia 7

Postby banjo » May 17th, '19, 20:36

I have a shared drive on Samba that has been set up and working for months on this Mageia 7 system. I have changed nothing in the setup, /etc/samba/smb.conf, but samba appears to be not reachable recently. When I attempt to open the shared drive from a client machine, the client says that it has timed out trying to connect to the server.

I have not opened the shared directory for a while, so I do not know exactly when it stopped working. Samba is set up to log for specific machines:

Code: Select all
# --------------------------- Logging Options -----------------------------
#
# log file = specify where log files are written to and how they are split.
#
# max log size = specify the maximum size log files are allowed to reach. Log
# files are rotated when they reach the size specified with "max log size".
#

   # log files split per-machine:
   log file = /var/log/samba/log.%m
   # maximum size of 50KB per log file, then rotate:
   max log size = 50



The most recent log file for my client machine is from April 25.

I am trying to connect from my Mint system and from an Android tablet. Both fail, so I think the problem is on the Mageia 7 server side.

The smbd is running.

Code: Select all
# systemctl status smb
● smb.service - Samba SMB Daemon
   Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2019-05-17 13:19:07 EDT; 58min ago
     Docs: man:smbd(8)
           man:samba(7)
           man:smb.conf(5)
 Main PID: 15187 (smbd)
   Status: "smbd: ready to serve connections..."
   Memory: 8.8M
   CGroup: /system.slice/smb.service
           ├─15187 /usr/sbin/smbd --foreground --no-process-group
           ├─15189 /usr/sbin/smbd --foreground --no-process-group
           ├─15190 /usr/sbin/smbd --foreground --no-process-group
           └─15214 /usr/sbin/smbd --foreground --no-process-group

May 17 13:19:07 localhost systemd[1]: Starting Samba SMB Daemon...
May 17 13:19:07 localhost smbd[15187]: [2019/05/17 13:19:07.811351,  0] ../../lib/util/become_daemon.c:136(daemon>
May 17 13:19:07 localhost systemd[1]: Started Samba SMB Daemon.
May 17 13:19:07 localhost smbd[15187]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve conn>


The shared folder permissions are wide open, 0777.

Code: Select all
$ ls -ld SysInfo/
drwxrwxrwx 53 poobah poobah 4096 May 17 07:39 SysInfo//


The Samba permissions on the folder are wide open:

Code: Select all
[SysInfo]
   path = /home/poobah/SysInfo
   valid users = poobah
   available = yes
   read only = no
   browseable = yes
   public = yes
   writable = yes
   create mask = 0777
   directory mask = 0777


The firewall on the Mageia 7 system is turned off.

Code: Select all
# systemctl status iptables
● iptables.service - iptables Firewall for IPv4
   Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled; vendor preset: disabled)
   Active: inactive (dead)


I can ping the Mageia 7 system from the client. I can ssh log into the Mageia 7 system from the client. The Mageia 7 system can access the internet via its wifi connection. So the network connection is good.

Testparm reports no problems with the config file.

Code: Select all
[root@localhost samba]# testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

# Global parameters
[global]
        log file = /var/log/samba/log.%m
        max log size = 50
        security = USER
        server string = Samba Server Version %v
        workgroup = MYGROUP
        idmap config * : backend = tdb
        cups options = raw


[homes]
        browseable = No
        comment = Home Directories
        read only = No


[printers]
        browseable = No
        comment = All Printers
        path = /var/spool/samba
        printable = Yes


[SysInfo]
        create mask = 0777
        directory mask = 0777
        guest ok = Yes
        path = /home/poobah/SysInfo
        read only = No
        valid users = poobah root


What else can I look at to find out why the smbd is not answering the request?

Thanks,
Banjo
(_)=='=~
Last edited by banjo on May 18th, '19, 23:42, edited 1 time in total.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Samba has stopped working on my Mageia 7

Postby banjo » May 18th, '19, 21:41

Trying to figure out what ports samba is listening on.

Code: Select all
[root@localhost poobah]# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      3710/sshd           
tcp        0      0 0.0.0.0:631             0.0.0.0:*               LISTEN      3702/cupsd         
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      5330/master         
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      3707/smbd           
tcp        0      0 127.0.0.1:10026         0.0.0.0:*               LISTEN      5330/master         
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      3707/smbd           
tcp6       0      0 :::22                   :::*                    LISTEN      3710/sshd           
tcp6       0      0 :::631                  :::*                    LISTEN      3702/cupsd         
tcp6       0      0 ::1:25                  :::*                    LISTEN      5330/master         
tcp6       0      0 :::445                  :::*                    LISTEN      3707/smbd           
tcp6       0      0 :::139                  :::*                    LISTEN      3707/smbd           
udp        0      0 0.0.0.0:68              0.0.0.0:*                           3491/dhclient       
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           27913/chrome --type
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           27821/chrome       
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           1094/avahi-daemon: 
udp        0      0 0.0.0.0:42302           0.0.0.0:*                           1094/avahi-daemon: 
udp6       0      0 :::42616                :::*                                1094/avahi-daemon: 
udp6       0      0 :::5353                 :::*                                1094/avahi-daemon: 
[root@localhost poobah]#


So it looks like smbd is alive and listening on some ports, but I do not see anything on 192.168.1.8, which is the IP of this computer. There are some tcp6 ports listening on what looks like wildcards. Tcp6? Is that an issue?

I can open the share on this computer using localhost. It even asks for my credentials before giving me access to my own share.... as it should. So at that level, samba is working.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Samba has stopped working on my Mageia 7

Postby banjo » May 18th, '19, 22:39

Here is another random attempt to get some information.

Code: Select all
brian@LinuxMain ~ $ nmap 192.168.1.8

Starting Nmap 7.01 ( https://nmap.org ) at 2019-05-18 16:29 EDT
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.04 seconds
brian@LinuxMain ~ $ nmap -Pn 192.168.1.8

Starting Nmap 7.01 ( https://nmap.org ) at 2019-05-18 16:30 EDT
Nmap scan report for 192.168.1.8
Host is up (0.0027s latency).
Not shown: 993 filtered ports
PORT     STATE  SERVICE
22/tcp   open   ssh
111/tcp  closed rpcbind
2049/tcp closed nfs
4001/tcp closed newoak
4002/tcp closed mlchat-proxy
4003/tcp closed pxc-splr-ft
4004/tcp closed pxc-roid

Nmap done: 1 IP address (1 host up) scanned in 4.63 seconds


I can ping the IP myself. Why would nmap claim that pings are being blocked?

Code: Select all
brian@LinuxMain ~ $ ping 192.168.1.8
PING 192.168.1.8 (192.168.1.8) 56(84) bytes of data.
64 bytes from 192.168.1.8: icmp_seq=1 ttl=64 time=2.61 ms
64 bytes from 192.168.1.8: icmp_seq=2 ttl=64 time=1.11 ms
64 bytes from 192.168.1.8: icmp_seq=3 ttl=64 time=1.13 ms
64 bytes from 192.168.1.8: icmp_seq=4 ttl=64 time=1.17 ms
64 bytes from 192.168.1.8: icmp_seq=5 ttl=64 time=1.14 ms
64 bytes from 192.168.1.8: icmp_seq=6 ttl=64 time=1.93 ms
64 bytes from 192.168.1.8: icmp_seq=7 ttl=64 time=2.39 ms
^C
--- 192.168.1.8 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6008ms
rtt min/avg/max/mdev = 1.113/1.646/2.619/0.611 ms
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Samba has stopped working on my Mageia 7

Postby banjo » May 18th, '19, 23:42

I fixed it.

On a WAG, I went to MCC=>Security=>Set Up your Personal Firewall to see what it thought was going on with the firewall.

Turns out that it somehow thought that it was supposed to block Windows shares. The box that allows Windows shares was not checked. I did not make that change as far as I can remember. I have been using the share for a while.

I checked the Windows Share box, said OK and tried again and it worked.

So, WRT the firewall, what the heck does the following mean?

Code: Select all
[root@BSKMageia poobah]# systemctl status iptables
● iptables.service - iptables Firewall for IPv4
   Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled; vendor preset: disabled)
   Active: inactive (dead)


Doesn't that mean that the firewall is disabled? If the service is disabled, what is blocking access to the ports? I am missing something here.

Anyway, it works again, so I am marking this solved.

Banjo
(_)=='=~
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: [SOLVED]Samba has stopped working on my Mageia 7

Postby martinw » May 23rd, '19, 19:38

There are two alternatives for controlling the firewall: iptables.service and shorewall.service. Mageia uses shorewall by default.
martinw
 
Posts: 609
Joined: May 14th, '11, 10:59

Re: [SOLVED]Samba has stopped working on my Mageia 7

Postby banjo » May 24th, '19, 01:31

OK. Thanks. I guess that is why iptables was disabled. Still learning the ropes.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts


Return to Testing : Alpha, Beta, RC and Cauldron

Who is online

Users browsing this forum: No registered users and 1 guest

cron