Samba share issue after a reboot

General
1

I have noticed the share is not accessible after a power up from shutdown state.
I can ssh or use the web gui but don’t have access anymore from my linux or windows pc.
The workaround for me is to delete the share and re-create.

My NAS is a Intel® Pentium® CPU G3420 @ 3.20GHz with 8 gig of RAM, Architecture: x86_64.
Let me know if there’s some other info needed.

2

@meazz1, are you on the latest version or still on 3.9.1-16 as I saw in an earlier post of yours? That information might help to pinpoint, what’s going on.

Did you check the system and/or Samba logs for any clues why during the reboot there seems to be an issue?

2 Likes
3

An update.
I have had the NAS running for last 4+ days. Today noticed the shares are not accessible any more.
I’m on 3.9.1-16 / Linux: 4.12.4-1.el7.clrepo.x86_64.

Screenshot%20from%202020-03-15%2015-16-25

I checked /var/log/samba

log.smbd shows

[2020/03/15 14:41:09.804169, 3] …/source3/printing/pcap.c:140(pcap_cache_reload)
reloading printcap cache
[2020/03/15 14:41:09.804322, 3] …/source3/printing/pcap.c:189(pcap_cache_reload)
reload status: ok
[2020/03/15 14:48:39.009629, 2] …/source3/smbd/server.c:807(remove_child_pid)
Could not find child 7046 – ignoring
[2020/03/15 14:53:39.853056, 3] …/source3/printing/pcap.c:140(pcap_cache_reload)
reloading printcap cache
[2020/03/15 14:53:39.853213, 3] …/source3/printing/pcap.c:189(pcap_cache_reload)
reload status: ok
[2020/03/15 15:03:39.050672, 2] …/source3/smbd/server.c:807(remove_child_pid)
Could not find child 7707 – ignoring
(END)

log.nmbd shows

[2020/03/15 11:30:38.369961,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.4.80 on subnet 192.168.4.5 for name ^A^B__MSBROWSE__^B<01>
[2020/03/15 11:30:38.370020,  3] ../source3/nmbd/nmbd_incomingrequests.c:574(process_name_query_request)
  OK
[2020/03/15 11:30:38.372974,  3] ../source3/nmbd/nmbd_incomingrequests.c:323(process_node_status_request)
  process_node_status_request: status request for name ^A^B__MSBROWSE__^B<01> from IP 192.168.4.80 on subnet UNICAST_SUBNET.
[2020/03/15 11:30:38.373219,  3] ../source3/nmbd/nmbd_incomingrequests.c:323(process_node_status_request)
  process_node_status_request: status request for name ^A^B__MSBROWSE__^B<01> from IP 192.168.4.80 on subnet UNICAST_SUBNET.
[2020/03/15 11:31:22.340298,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.4.80 on subnet 192.168.4.5 for name HOME<1d>
[2020/03/15 11:31:22.340406,  3] ../source3/nmbd/nmbd_incomingrequests.c:574(process_name_query_request)
  OK
[2020/03/15 11:31:22.340593,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.4.80 on subnet 192.168.4.5 for name HOME<1d>
[2020/03/15 11:31:22.340650,  3] ../source3/nmbd/nmbd_incomingrequests.c:574(process_name_query_request)
  OK
[2020/03/15 11:31:22.344688,  3] ../source3/nmbd/nmbd_incomingdgrams.c:660(process_get_backup_list_request)
  process_get_backup_list_request: request from MACBOOKPRO-22F5<00> IP 192.168.4.80 to HOME<1d>.
[2020/03/15 11:31:22.344779,  3] ../source3/nmbd/nmbd_incomingdgrams.c:558(send_backup_list_response)
  send_backup_list_response: sending backup list for workgroup HOME to MACBOOKPRO-22F5<00> IP 192.168.4.80
[2020/03/15 11:31:22.344923,  3] ../source3/nmbd/nmbd_incomingdgrams.c:660(process_get_backup_list_request)
  process_get_backup_list_request: request from MACBOOKPRO-22F5<00> IP 192.168.4.80 to HOME<1d>.
[2020/03/15 11:31:22.345020,  3] ../source3/nmbd/nmbd_incomingdgrams.c:558(send_backup_list_response)
  send_backup_list_response: sending backup list for workgroup HOME to MACBOOKPRO-22F5<00> IP 192.168.4.80
[2020/03/15 11:31:22.345979,  3] ../source3/nmbd/nmbd_incomingrequests.c:323(process_node_status_request)
  process_node_status_request: status request for name NAS-RS<20> from IP 192.168.4.80 on subnet UNICAST_SUBNET.
[2020/03/15 11:31:54.449663,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request:

Not sure why so many name query from different LAN devices. I can access the web gui just fine.
If I turn off and on the samba service, I can access the shares.

Since this setup up for my home use only I would be ok if I can have a cron job to stop and start samba denom once a day.

4

Hi @meazz1,

Thanks for the additional information. We recently made several improvements to our implementation of Samba, but I unfortunately do not see much problem in the logs you provided. It thus seem we may need to dig in a little further. In case you haven’t seen, I would point you towards a recent post of mine in which I detail some of the ways to troubleshoot samba:

While these were on a thread regarding our upcoming “Built on openSUSE” release, the information therein might be helpful to better figure out what is happening. Of particular importance, we recently made several improvements to our Samba implementation so you might want to start by looking at /etc/samba/smb.conf and make sure it is as it is supposed to be.

I’m sorry I don’t have a straight answer yet, but hopefully the details in the post I linked will help point you in the right direction. Let us know how it goes!

Of note, I can see you have a mac on your LAN. Do the other machines have issues connecting to your Samba share(s)? If you have multiple shares exported via Samba, is the issue affecting all shares or just one? Could you provide some details on the client with which you’re seeing this error (it appears to be a linux-based client)?

Let us know how it goes, and I hope this helps.

1 Like