Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[ET10x00] box invisible on network

Not done the init thing yet,ahh with you now samba needs an update/adjustment.
 
I've reflashed my ET10K with 5.4.003, no settings restore, started Samba (needed an opkg update to get it to load ok.)

PC could see ET10K (asked for login credentials).

With browse network neighbourhood, ET10K could see Ultimo4k, but not itself. Ultimo4k could not see the ET10K.

The mounts I have on the Ultimo4k include the parameter vers=2.0 I couldn't work out how to force this onto browse network, so.......

Took a copy of /etc/samba from the working version of 5.4.003, and copied it into the non-working version. Now works ok (needed a yellow button rescan in browser.)

(To copy, I stopped enigma (telnet init 4), renamed /etc/samba to /etc/samba.orig, copied over the "old" version of /etc/samba, restarted with init 3, and then rebooted.)

Are you able to copy /etc/samba.orig and /etc/samba to a PC and compare the contents?
And/or ZIP them and upload so others can compare and experiment?
 
Are you able to copy /etc/samba.orig and /etc/samba to a PC and compare the contents?
And/or ZIP them and upload so others can compare and experiment?

I did a bit of checking after I'd finished, but found no differences, probably because I was rushing and mixed up the versions.

I'll have another look tomorrow.
 
I have not done anything as recording a load of things again or fell asleep:rolleyes:
 
I had an idea, unusual I know, more surprising - it worked.

Flashed ET10K with 5.4.003, no settings restore. Started Samba (after opkg update) and network browser exhibited the documented problems.

Did a settings restore and then restored settings+plugins - Samba now working as expected.:)

There is one subtle difference with the samba directory before and after the settings restore.......

Code:
root@et10000:~# ls -lR /etc/samba*
/etc/samba.flash.orig:
drwxr-xr-x    2 root     root           528 Dec 28 09:02 distro
-rw-r--r--    1 root     root            20 Dec 28 09:02 lmhosts
drwxr-xr-x    2 root     root           376 Dec 28 09:02 private
-rw-r--r--    1 root     root           744 Dec 28 09:02 smb-user.conf
-rw-r--r--    1 root     root            95 Dec 28 09:02 smb.conf

/etc/samba.flash.orig/distro:
-rw-r--r--    1 root     root            61 Dec 28 09:02 smb-branding.conf
-rw-r--r--    1 root     root          1457 Dec 28 09:02 smb-global.conf
-rw-r--r--    1 root     root           586 Dec 28 09:02 smb-shares.conf
[COLOR="#FF0000"]-rw-r--r--    1 root     root            29 Dec 28 09:02 smb-vmc.conf[/COLOR]
-rw-r--r--    1 root     root            29 Dec 28 09:02 smb-vmc.samba

/etc/samba.flash.orig/private:
-rw-r--r--    1 root     root        430080 Dec 28 09:02 secrets.tdb
-rw-r--r--    1 root     root           204 Dec 28 09:02 smbpasswd
-rw-r--r--    1 root     root            80 Dec 28 09:02 users.map
root@et10000:~#

after settings restore.....

root@et10000:~# ls -lR /etc/samba
/etc/samba:
drwxr-xr-x    2 root     root           528 Dec 28 09:06 distro
-rw-r--r--    1 root     root            20 Oct  8 05:12 lmhosts
drwxr-xr-x    2 root     root           376 Dec 28 09:06 private
-rw-r--r--    1 root     root           744 Oct  8 05:12 smb-user.conf
-rw-r--r--    1 root     root            95 Oct  8 05:12 smb.conf

/etc/samba/distro:
-rw-r--r--    1 root     root            61 Oct  8 05:12 smb-branding.conf
-rw-r--r--    1 root     root          1457 Oct  8 05:12 smb-global.conf
-rw-r--r--    1 root     root           586 Oct  8 05:12 smb-shares.conf
[COLOR="#FF0000"]lrwxrwxrwx    1 root     root            13 Dec 28 09:06 smb-vmc.conf -> smb-vmc.samba[/COLOR]
-rw-r--r--    1 root     root            29 Oct  8 05:12 smb-vmc.samba

/etc/samba/private:
-rw-------    1 root     root        430080 Dec 28 08:57 secrets.tdb
-rw-------    1 root     root           204 Dec 28 08:57 smbpasswd
-rw-r--r--    1 root     root            80 Oct  8 05:12 users.map
root@et10000:~#
So restoring the plugin produces the desired result, no need to use an old working copy of /etc/samba (although the effect is the same).

Anything else needed before I get back to the full image?
 
Last edited:
My vhannibal has thrown a wobbly reset my sat tuners and not listed bouquets and and throwing up an erno warning .
Need to start again as cant remember with all the restores which one was used.
 
I had an idea, unusual I know, more surprising - it worked.

Flashed ET10K with 5.4.003, no settings restore. Started Samba (after opkg update) and network browser exhibited the documented problems.

Did a settings restore and then restored settings+plugins - Samba now working as expected.:)

There is one subtle difference with the samba directory before and after the settings restore.......

Code:
root@et10000:~# ls -lR /etc/samba*
/etc/samba.flash.orig:
drwxr-xr-x    2 root     root           528 Dec 28 09:02 distro
-rw-r--r--    1 root     root            20 Dec 28 09:02 lmhosts
drwxr-xr-x    2 root     root           376 Dec 28 09:02 private
-rw-r--r--    1 root     root           744 Dec 28 09:02 smb-user.conf
-rw-r--r--    1 root     root            95 Dec 28 09:02 smb.conf

/etc/samba.flash.orig/distro:
-rw-r--r--    1 root     root            61 Dec 28 09:02 smb-branding.conf
-rw-r--r--    1 root     root          1457 Dec 28 09:02 smb-global.conf
-rw-r--r--    1 root     root           586 Dec 28 09:02 smb-shares.conf
[COLOR="#FF0000"]-rw-r--r--    1 root     root            29 Dec 28 09:02 smb-vmc.conf[/COLOR]
-rw-r--r--    1 root     root            29 Dec 28 09:02 smb-vmc.samba

/etc/samba.flash.orig/private:
-rw-r--r--    1 root     root        430080 Dec 28 09:02 secrets.tdb
-rw-r--r--    1 root     root           204 Dec 28 09:02 smbpasswd
-rw-r--r--    1 root     root            80 Dec 28 09:02 users.map
root@et10000:~#

after settings restore.....

root@et10000:~# ls -lR /etc/samba
/etc/samba:
drwxr-xr-x    2 root     root           528 Dec 28 09:06 distro
-rw-r--r--    1 root     root            20 Oct  8 05:12 lmhosts
drwxr-xr-x    2 root     root           376 Dec 28 09:06 private
-rw-r--r--    1 root     root           744 Oct  8 05:12 smb-user.conf
-rw-r--r--    1 root     root            95 Oct  8 05:12 smb.conf

/etc/samba/distro:
-rw-r--r--    1 root     root            61 Oct  8 05:12 smb-branding.conf
-rw-r--r--    1 root     root          1457 Oct  8 05:12 smb-global.conf
-rw-r--r--    1 root     root           586 Oct  8 05:12 smb-shares.conf
[COLOR="#FF0000"]lrwxrwxrwx    1 root     root            13 Dec 28 09:06 smb-vmc.conf -> smb-vmc.samba[/COLOR]
-rw-r--r--    1 root     root            29 Oct  8 05:12 smb-vmc.samba

/etc/samba/private:
-rw-------    1 root     root        430080 Dec 28 08:57 secrets.tdb
-rw-------    1 root     root           204 Dec 28 08:57 smbpasswd
-rw-r--r--    1 root     root            80 Oct  8 05:12 users.map
root@et10000:~#
So restoring the plugin produces the desired result, no need to use an old working copy of /etc/samba (although the effect is the same).

Anything else needed before I get back to the full image?

I tried
Code:
root@et10000:~# opkg list | grep -e [COLOR="#0000CD"]smb [/COLOR]-e [COLOR="#0000CD"]samba[/COLOR]
before and after the settings restore, the results were identical.

I'm assuming all samba packages include the text smb or samba.
 
I'm giving up, I can no longer get the simple sequence in post #45 to work.

I started again from scratch with debug logs on, after that I couldn't get network browser to work as expected.

The exception file straight after the flash and samba install now shows as a symbolic link, not as it did in #45....

Code:
-rw-r--r--    1 root     root            29 Dec 28 09:02 smb-vmc.conf

There's nothing I could have done to make that happen.

Taking a settings backup and restoring it no longer did what it achieved in #45.

I restored settings+plugins from a working backup and network browser works ok.
 
One final thought.
Could it be that nmbd stops running for some unknown reason?
This command should show the smbd and nmbd processes that are running.
Code:
ps -AFH | grep -e [sn]mbd
There should be an smbd (and it's child smbd processes) and an nmbd process.
On by Zgemma H7 I got this:
Code:
root@zgemmah7:~#
root@zgemmah7:~# ps -AFH | grep -e [sn]mbd
root      2061     1  0  7251  2992   1 Dec27 ?        00:00:00   /usr/sbin/smbd
root      2065  2061  0  6600  1960   1 Dec27 ?        00:00:00     /usr/sbin/smbd
root      2066  2061  0  6601  2228   0 Dec27 ?        00:00:00     /usr/sbin/smbd
root      2068     1  0  4355  1468   0 Dec27 ?        00:00:03   /usr/sbin/nmbd
root@zgemmah7:~#
As I understand it the important thing is that both smbd and nmbd are running.
The number of extra child smbd processes varies depending on, I presume, present (and past?) connections that have been made to samba.
 
I found during my last attempt(s) samba had sometimes stopped and I had to restart it via the gui.

This is my current "live" working version on the et10k...

Code:
root@et10000:~# ps -AFH | grep -e [sn]mbd
root       604     1  0  8012  7864   0 13:27 ?        00:00:00   /usr/sbin/smbd
root       608   604  0  7293  2876   0 13:27 ?        00:00:00     /usr/sbin/smbd
root       609   604  0  7291  2580   0 13:27 ?        00:00:00     /usr/sbin/smbd
root       611     1  0  4794  2952   0 13:27 ?        00:00:00   /usr/sbin/nmbd
root@et10000:~#

Maybe I'll have one last go, I must be mad.
 
As I understand it the important thing is that both smbd and nmbd are running.
The number of extra child smbd processes varies depending on, I presume, present (and past?) connections that have been made to samba.
If I kill nmbd, I still see 3 other assorted boxes, but not the et10k.
Restart nmbd and the et10k comes back.
 
If I kill nmbd, I still see 3 other assorted boxes, but not the et10k.
Restart nmbd and the et10k comes back.

Back to square one, reflashed 5.4.003, no settings restore, start samba, no /usr/sbin/nmbd running.

Start /usr/sbin/nmbd by hand, network browser working fine.

So need to find out what autostarts /usr/sbin/nmbd (and now samba has been in the stopped state after 3 reboots, so probably part of the same rc file).

There's a startup script in /etc/rc0_to_6.d. I'm assuming they're all similar, named either K20samba or S20samba.
Code:
#! /bin/sh
### BEGIN INIT INFO
# Provides:          Samba
# Required-Start:    $network $local_fs $remote_fs
# Required-Stop:     $network $local_fs $remote_fs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Should-Start:      slapd cups
# Should-Stop:       slapd cups
# Short-Description: start Samba SMB daemons (smbd/wsdd/nmbd)
### END INIT INFO

WSDD_DISABLED="Yes"
smbd=/usr/sbin/smbd
test -x "$smbd" || exit 0
nmbd=/usr/sbin/nmbd
test -x "$nmbd" || exit 0
wsdd=/usr/sbin/wsdd
test -x "$wsdd" && WSDD_DISABLED="No"


case "$1" in
  start)
    echo -n "Starting Samba: smbd"
    $smbd
    NMBD_DISABLED=`testparm -s --parameter-name='disable netbios' 2>/dev/null || true`
    if [ "$NMBD_DISABLED" != "Yes" ]; then
      echo -n " nmbd"
      $nmbd
    fi
    if [ "$WSDD_DISABLED" != "Yes" ]; then
      echo -n " wsdd"
      start-stop-daemon --start --quiet --exec $wsdd
    fi
    echo "."
    ;;
  stop)
    echo -n "Stopping Samba: smbd"
    start-stop-daemon --stop --quiet --pidfile /var/run/samba/smbd.pid
    echo -n " nmbd"
    start-stop-daemon --stop --quiet --pidfile /var/run/samba/nmbd.pid
    echo -n " wsdd"
    start-stop-daemon --stop --quiet --pidfile /var/run/wsdd.pid
    echo "."
    ;;
  reload|force-reload)
    if [ "$WSDD_DISABLED" != "Yes" ]; then
      start-stop-daemon --stop --quiet --pidfile /var/run/wsdd.pid
    fi
    start-stop-daemon --stop --quiet --signal 1 --exec $smbd
    start-stop-daemon --stop --quiet --signal 1 --exec $nmbd
    if [ "$WSDD_DISABLED" != "Yes" ]; then
      sleep 1
      start-stop-daemon --start --quiet --exec $wsdd
    fi
    ;;
  restart)
    echo -n "Stopping Samba: smbd"
    start-stop-daemon --stop --quiet --pidfile /var/run/samba/smbd.pid
    echo -n " nmbd"
    start-stop-daemon --stop --quiet --pidfile /var/run/samba/nmbd.pid
    echo -n " wsdd"
    start-stop-daemon --stop --quiet --pidfile /var/run/wsdd.pid
    echo ""
    echo -n "Waiting for samba processes to die off"
    for i in 1 2 3 ;
    do
        sleep 1
        echo -n "."
    done
    echo ""
    echo -n "Starting Samba: smbd"
    start-stop-daemon --start --quiet --exec $smbd
    NMBD_DISABLED=`testparm -s --parameter-name='disable netbios' 2>/dev/null || true`
    if [ "$NMBD_DISABLED" != "Yes" ]; then
      echo -n " nmbd"
      start-stop-daemon --start --quiet --exec $nmbd
    fi
    if [ "$WSDD_DISABLED" != "Yes" ]; then
      echo -n " wsdd"
      start-stop-daemon --start --quiet --exec $wsdd
    fi
    echo "."
    ;;
  *)
    echo "Usage: /etc/init.d/samba {start|stop|reload|restart|force-reload}"
    exit 1
esac

exit 0

root@et10000:/etc/rc0.d#
 
Last edited:
Went back to 5.4.0.001 and no restores and using the wizard on lan 2 it states no internet connection,and vlan locked out until i go up and use remote to change it back to lan 2 and wondering if its the same on yours.

Back on with lan 2 no restores and guess what no et on browser scan
 
Last edited:
@ccs
Oh I'd forgotten about wsdd.
I think it's just to help make samba visible to browse from Windows, possibly mainly Windows 10.
 
Last edited:
@ccs
If you find nmbd isn't running it might be worth checking nmbd's log file, which on my Zgemma H7 is /var/log/samba/log.nmbd.
It's date/time and it's contents should help work out if nmbd has never started or if it started up and then crashed or halted for some reason.
Code:
root@zgemmah7:~#
root@zgemmah7:~#
root@zgemmah7:~# ps -AFH | grep -e "[sn]mbd\|wsd\d"
root      2061     1  0  7248 11092   0 21:41 ?        00:00:00   /usr/sbin/smbd
root      2065  2061  0  6600  3472   0 21:41 ?        00:00:00     /usr/sbin/smbd
root      2066  2061  0  6598  2260   0 21:41 ?        00:00:00     /usr/sbin/smbd
root      2068     1  0  4355  3340   0 21:41 ?        00:00:00   /usr/sbin/nmbd
root      2075     1  0   427    72   0 21:41 ?        00:00:00   /usr/sbin/wsdd
root@zgemmah7:~#
root@zgemmah7:~#
root@zgemmah7:~# ls -l /var/log/samba/log.nmbd
-rw-r--r--    1 root     root           544 Dec 28 21:42 /var/log/samba/log.nmbd
root@zgemmah7:~#
root@zgemmah7:~#
root@zgemmah7:~# cat /var/log/samba/log.nmbd
[2020/12/28 21:41:22.386397,  0] ../source3/nmbd/nmbd.c:907(main)
  nmbd version 4.9.15 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2018
[2020/12/28 21:41:22.398134,  0] ../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
[2020/12/28 21:42:03.476868,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
  *****

  Samba name server ZGEMMAH7 is now a local master browser for workgroup WORKGROUP on subnet 192.168.13.126

  *****
root@zgemmah7:~#
root@zgemmah7:~#
 
@ccs
Oh I'd forgotten about wsdd.
I think it's just to help make samba visible to browse from Windows, possibly mainly Windows 10.

Thanks, wsdd is running on the working system, I can see the ET10K from windows 10, and I think I could earlier today when the network browser wasn't working.

.... having said that, it's also running on the ultimo4k, but windows can't see it. :eek:
 
Last edited:
Back to square one, reflashed 5.4.003, no settings restore, start samba, no /usr/sbin/nmbd running.

Start /usr/sbin/nmbd by hand, network browser working fine.

So need to find out what autostarts /usr/sbin/nmbd (and now samba has been in the stopped state after 3 reboots, so probably part of the same rc file).

There's a startup script in /etc/rc0_to_6.d. I'm assuming they're all similar, named either K20samba or S20samba.

From those startup scripts it looks like nmbd wouldn't start if the samba configuration files had
Code:
disable netbios = yes
in them.
But as far as I can see on my Zgemma H7 only one of the sample files that aren't used has it, namely /etc/samba/distro/smb-secure.conf
 

OpenViX Feeds Status

Back
Top