Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.

View Entry Info: Samba broken after update to openvix 6.0.01

Category:
Possible Bug
What ViX Image build number are you using?
Please provide your ViX Team image build number. Menu > Information > About > Build number > ENTER THIS NUMBER e.g. 4.2.028
6.0.001
Have you tried a flash WITHOUT settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
No
Have you tried a flash WITH settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
Yes
Attachments
Page 1 of 2 12 LastLast
Results 1 to 15 of 29

Thread: Samba broken after update to openvix 6.0.01

  1. #1
    Junior Member

    Join Date
    Oct 2019
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Samba broken after update to openvix 6.0.01

    Hi Guys.

    Upgraded Solo SE II from 5.4.016 using GUI.
    After upgrade the samba server dies with error in logs.
    smbd errors:

    From log.smbd

    [2021/11/09 10:33:21.601275, 0] ../../source3/smbd/server.c:1738(main)
    smbd version 4.15.0 started.
    Copyright Andrew Tridgell and the Samba Team 1992-2021
    [2021/11/09 10:33:21.749531, 0] ../../source3/auth/auth_util.c:1410(make_new_session_info_guest)
    make_server_info_info3 failed with NT_STATUS_NO_SUCH_USER
    [2021/11/09 10:33:21.750340, 0] ../../source3/smbd/server.c:2015(main)
    ERROR: failed to setup guest info.

    From system log messages

    Nov 9 10:33:21 vusolose daemon.err smbd[712]: [2021/11/09 10:33:21.601275, 0] ../../source3/smbd/server.c:1738(main)
    Nov 9 10:33:21 vusolose daemon.err smbd[712]: smbd version 4.15.0 started.
    Nov 9 10:33:21 vusolose daemon.err smbd[712]: Copyright Andrew Tridgell and the Samba Team 1992-2021
    Nov 9 10:33:21 vusolose daemon.err smbd[713]: [2021/11/09 10:33:21.749531, 0] ../../source3/auth/auth_util.c:1410(make_new_session_info_guest)
    Nov 9 10:33:21 vusolose daemon.err smbd[713]: make_server_info_info3 failed with NT_STATUS_NO_SUCH_USER
    Nov 9 10:33:21 vusolose daemon.err smbd[713]: [2021/11/09 10:33:21.750340, 0] ../../source3/smbd/server.c:2015(main)
    Nov 9 10:33:21 vusolose daemon.err smbd[713]: ERROR: failed to setup guest info.
    Nov 9 10:33:22 vusolose daemon.err nmbd[719]: [2021/11/09 10:33:22.344934, 0] ../../source3/nmbd/nmbd.c:902(main)
    Nov 9 10:33:22 vusolose daemon.err nmbd[719]: nmbd version 4.15.0 started.
    Nov 9 10:33:22 vusolose daemon.err nmbd[719]: Copyright Andrew Tridgell and the Samba Team 1992-2021
    Nov 9 10:33:22 vusolose daemon.err nmbd[720]: [2021/11/09 10:33:22.354354, 0] ../../lib/util/pidfile.c:217(pidfile_create)]

    Flashing back to to VIX 5.4.016 restores samba functionality.

    Best regards
    Kar in Sweden.
    Last edited by kalel-2; 09-11-21 at 11:09. Reason: Typos in post

  2. #2
    Forum Supporter
    Donated Member
    adm's Avatar

    Join Date
    Sep 2014
    Location
    Southend on Sea, UK
    Posts
    1,282
    Thanks
    46
    Thanked 477 Times in 374 Posts
    Xtrend ET10000 runing 6.0.001

    I cannot get SAMBA to start.

    I've tried.
    menu -> setup -> network -> utilities -> samba -> remove service
    then automatic reboot
    then telnet into the box and "opkg update"
    then reboot
    then menu -> setup -> network -> utilities -> samba -> which installs smb
    then automatic reboot

    Samba remains at "stopped" - autostart or manual start have no effect.
    No Samba logs are produced
    Last edited by adm; 09-11-21 at 16:51.
    Xtrend ET10K, 2 x satellite tuners 28.2 (Sky FTA), 2 x hybrid (UK Freeview), Zgemma H9S (satellite)

  3. #3
    ViX Beta Tester ccs's Avatar

    Join Date
    Sep 2014
    Posts
    5,097
    Thanks
    512
    Thanked 1,172 Times in 1,001 Posts
    ... it was working for me last night after a settings restore, but I can't check again at the moment.

    EDIT: re-flashed with a settings restore and all ok.
    Last edited by ccs; 09-11-21 at 17:02.

  4. #4
    Moderator Huevos's Avatar

    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    10,864
    Thanks
    1,826
    Thanked 3,988 Times in 2,626 Posts
    @ccs, they are restoring the config files in their 5.4 backup, right? Remember we changed it so that did not happen?

    Can you post some virgin config files?

  5. #5
    ViX Beta Tester ccs's Avatar

    Join Date
    Sep 2014
    Posts
    5,097
    Thanks
    512
    Thanked 1,172 Times in 1,001 Posts
    Quote Originally Posted by Huevos View Post
    @ccs, they are restoring the config files in their 5.4 backup, right? Remember we changed it so that did not happen?

    Can you post some virgin config files?
    A settings restore will bring back /etc/samba because it's in there by default for everyone.

    Any updated configs from later releases of samba will be overwritten, although in practice it's very unlikely to cause any problems as reported in this thread.

    /etc/samba/smb-user.conf and /etc/samba/private are the only 2 config files which user should change, and so were added to the settings backup.

    /etc/samba should really be removed as it's not needed.

    I'll dig out some configs later.
    Last edited by ccs; 09-11-21 at 17:58.

  6. #6
    Forum Supporter
    Donated Member
    adm's Avatar

    Join Date
    Sep 2014
    Location
    Southend on Sea, UK
    Posts
    1,282
    Thanks
    46
    Thanked 477 Times in 374 Posts
    Quote Originally Posted by ccs View Post
    A settings restore will bring back /etc/samba because it's in there by default for everyone.

    Any updated configs from later releases of samba will be overwritten, although in practice it's very unlikely to cause any problems as reported in this thread.

    /etc/samba/smb-user.conf and /etc/samba/private are the only 2 config files which user should change, and so were added to the settings backup.

    /etc/samba should really be removed as it's not needed.

    I'll dig out some configs later.
    A re-flash of 6.0.001 without a settings or plug-in restore (and with a telnet “opkg update”) got Samba working again but an immediate follow-up with a settings and plug-in restore caused it to fail again.

    I then reloaded 5.4.016 (from the backup including settings and plugins) and removed Samba
    Then made a new settings backup for 5.4.016
    Then re-flashed 6.0.001 and without restoring settings or plug-ins
    Then telnet “opkg update”
    Then reinstall Samba from the network GUI/menu

    Samba running

    The settings update from the 5.4.016 backup with Samba removed was re-installed followed by an automatic reboot.

    Samba fails to start!

    So it looks that if there is something in the settings backup that is “corrupting” Samba
    Xtrend ET10K, 2 x satellite tuners 28.2 (Sky FTA), 2 x hybrid (UK Freeview), Zgemma H9S (satellite)

  7. #7
    ViX Beta Tester ccs's Avatar

    Join Date
    Sep 2014
    Posts
    5,097
    Thanks
    512
    Thanked 1,172 Times in 1,001 Posts
    /etc/samba is in the image release, removing samba will still leave /etc/samba in a settings restore.

    Have a look at it before and after the settings restore.

    This is my current /etc/samba (on ultimo4k 6.0.001) (/etc/samba is not in the backup, just the files/folders mentioned earlier.)

    Code:
    root@vuultimo4k:~# ls -lR /etc/samba
    /etc/samba:
    drwxr-xr-x    2 root     root          4096 Nov  9 17:02 distro
    -rw-r--r--    1 root     root            20 Nov  3 00:34 lmhosts
    drwxr-xr-x    2 root     root          4096 Nov  9 17:02 private
    -rw-r--r--    1 root     root           772 Dec 31  2020 smb-user.conf
    -rw-r--r--    1 root     root            95 Nov  3 00:34 smb.conf
    
    /etc/samba/distro:
    -rw-r--r--    1 root     root            61 Nov  3 00:34 smb-branding.conf
    -rw-r--r--    1 root     root          1516 Nov  3 00:34 smb-global.conf
    -rw-r--r--    1 root     root           586 Nov  3 00:34 smb-shares.conf
    lrwxrwxrwx    1 root     root            13 Nov  9 17:02 smb-vmc.conf -> smb-vmc.samba
    -rw-r--r--    1 root     root            29 Nov  3 00:34 smb-vmc.samba
    
    /etc/samba/private:
    -rw-------    1 root     root        430080 Dec 31  2020 secrets.tdb
    -rw-------    1 root     root           204 Jan 18  2021 smbpasswd
    -rw-r--r--    1 root     root            80 Dec 31  2020 users.map
    root@vuultimo4k:

    This is 5.4.016 et10k which restored ok on 6.0.001. /etc/samba is in the backup.

    Code:
    root@et10000:~# ls -lR /etc/samba
    /etc/samba:
    drwxr-xr-x    2 root     root           528 Oct 13 10:56 distro
    -rw-r--r--    1 root     root            20 Dec 31  2020 lmhosts
    drwxr-xr-x    2 root     root           376 Oct 13 10:56 private
    -rw-r--r--    1 root     root           772 Dec 31  2020 smb-user.conf
    -rw-r--r--    1 root     root           744 Dec 31  2020 smb-user.conf.orig
    -rw-r--r--    1 root     root            95 Dec 31  2020 smb.conf
    
    /etc/samba/distro:
    -rw-r--r--    1 root     root            61 Dec 31  2020 smb-branding.conf
    -rw-r--r--    1 root     root          1457 Dec 31  2020 smb-global.conf
    -rw-r--r--    1 root     root           586 Dec 31  2020 smb-shares.conf
    lrwxrwxrwx    1 root     root            13 Oct 13 10:56 smb-vmc.conf -> smb-vmc.samba
    -rw-r--r--    1 root     root            29 Dec 31  2020 smb-vmc.samba
    
    /etc/samba/private:
    -rw-------    1 root     root        430080 Dec 31  2020 secrets.tdb
    -rw-------    1 root     root           204 Dec 31  2020 smbpasswd
    -rw-r--r--    1 root     root            80 Dec 31  2020 users.map
    root@et10000:~#
    Last edited by ccs; 09-11-21 at 18:25.

  8. #8
    Forum Supporter
    Donated Member
    adm's Avatar

    Join Date
    Sep 2014
    Location
    Southend on Sea, UK
    Posts
    1,282
    Thanks
    46
    Thanked 477 Times in 374 Posts
    Quote Originally Posted by adm View Post
    A re-flash of 6.0.001 without a settings or plug-in restore (and with a telnet “opkg update”) got Samba working again but an immediate follow-up with a settings and plug-in restore caused it to fail again.

    I then reloaded 5.4.016 (from the backup including settings and plugins) and removed Samba
    Then made a new settings backup for 5.4.016
    Then re-flashed 6.0.001 and without restoring settings or plug-ins
    Then telnet “opkg update”
    Then reinstall Samba from the network GUI/menu

    Samba running

    The settings update from the 5.4.016 backup with Samba removed was re-installed followed by an automatic reboot.

    Samba fails to start!

    So it looks that if there is something in the settings backup that is “corrupting” Samba
    I've just updated my Zgemma H9S to 6.0.001 - same problem.
    Xtrend ET10K, 2 x satellite tuners 28.2 (Sky FTA), 2 x hybrid (UK Freeview), Zgemma H9S (satellite)

  9. #9
    Moderator Huevos's Avatar

    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    10,864
    Thanks
    1,826
    Thanked 3,988 Times in 2,626 Posts
    Quote Originally Posted by adm View Post
    I've just updated my Zgemma H9S to 6.0.001 - same problem.
    So easier... Flash 6.0. Restore 5.4 backup. Make a 6.0 backup. Flash 6.0 again. Restore 6.0 backup.

  10. #10
    Moderator twol's Avatar

    Join Date
    Apr 2012
    Posts
    7,010
    Thanks
    861
    Thanked 2,480 Times in 1,894 Posts
    Quote Originally Posted by adm View Post
    I've just updated my Zgemma H9S to 6.0.001 - same problem.
    Yes an old backup wil likely restore invalid settings - so get it working and run a new settings backup, as BackupManager has now been changed to not save the “ bad settings“ for samba
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
    ------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 using Legacy ports on multiswitches
    Zgemma H9 C/S into Giga4K

  11. #11
    Forum Supporter
    Donated Member
    adm's Avatar

    Join Date
    Sep 2014
    Location
    Southend on Sea, UK
    Posts
    1,282
    Thanks
    46
    Thanked 477 Times in 374 Posts
    Quote Originally Posted by ccs View Post
    /etc/samba is in the image release, removing samba will still leave /etc/samba in a settings restore.

    Have a look at it before and after the settings restore.

    This is my current /etc/samba (on ultimo4k 6.0.001) (/etc/samba is not in the backup, just the files/folders mentioned earlier.)

    Code:
    root@vuultimo4k:~# ls -lR /etc/samba
    /etc/samba:
    drwxr-xr-x    2 root     root          4096 Nov  9 17:02 distro
    -rw-r--r--    1 root     root            20 Nov  3 00:34 lmhosts
    drwxr-xr-x    2 root     root          4096 Nov  9 17:02 private
    -rw-r--r--    1 root     root           772 Dec 31  2020 smb-user.conf
    -rw-r--r--    1 root     root            95 Nov  3 00:34 smb.conf
    
    /etc/samba/distro:
    -rw-r--r--    1 root     root            61 Nov  3 00:34 smb-branding.conf
    -rw-r--r--    1 root     root          1516 Nov  3 00:34 smb-global.conf
    -rw-r--r--    1 root     root           586 Nov  3 00:34 smb-shares.conf
    lrwxrwxrwx    1 root     root            13 Nov  9 17:02 smb-vmc.conf -> smb-vmc.samba
    -rw-r--r--    1 root     root            29 Nov  3 00:34 smb-vmc.samba
    
    /etc/samba/private:
    -rw-------    1 root     root        430080 Dec 31  2020 secrets.tdb
    -rw-------    1 root     root           204 Jan 18  2021 smbpasswd
    -rw-r--r--    1 root     root            80 Dec 31  2020 users.map
    root@vuultimo4k:

    This is 5.4.016 et10k which restored ok on 6.0.001. /etc/samba is in the backup.

    Code:
    root@et10000:~# ls -lR /etc/samba
    /etc/samba:
    drwxr-xr-x    2 root     root           528 Oct 13 10:56 distro
    -rw-r--r--    1 root     root            20 Dec 31  2020 lmhosts
    drwxr-xr-x    2 root     root           376 Oct 13 10:56 private
    -rw-r--r--    1 root     root           772 Dec 31  2020 smb-user.conf
    -rw-r--r--    1 root     root           744 Dec 31  2020 smb-user.conf.orig
    -rw-r--r--    1 root     root            95 Dec 31  2020 smb.conf
    
    /etc/samba/distro:
    -rw-r--r--    1 root     root            61 Dec 31  2020 smb-branding.conf
    -rw-r--r--    1 root     root          1457 Dec 31  2020 smb-global.conf
    -rw-r--r--    1 root     root           586 Dec 31  2020 smb-shares.conf
    lrwxrwxrwx    1 root     root            13 Oct 13 10:56 smb-vmc.conf -> smb-vmc.samba
    -rw-r--r--    1 root     root            29 Dec 31  2020 smb-vmc.samba
    
    /etc/samba/private:
    -rw-------    1 root     root        430080 Dec 31  2020 secrets.tdb
    -rw-------    1 root     root           204 Dec 31  2020 smbpasswd
    -rw-r--r--    1 root     root            80 Dec 31  2020 users.map
    root@et10000:~#
    My files on ET10000 V6.0.001 after a 5.4.016 settings restore.

    smb1.jpg

    smb2.jpg

    smb3.jpg
    Xtrend ET10K, 2 x satellite tuners 28.2 (Sky FTA), 2 x hybrid (UK Freeview), Zgemma H9S (satellite)

  12. #12
    ViX Beta Tester ccs's Avatar

    Join Date
    Sep 2014
    Posts
    5,097
    Thanks
    512
    Thanked 1,172 Times in 1,001 Posts
    Quote Originally Posted by twol View Post
    Yes an old backup wil likely restore invalid settings - so get it working and run a new settings backup, as BackupManager has now been changed to not save the “ bad settings“ for samba
    It's not as easy as that, /etc/samba will still be in everyone's backup, the specific new samba file and folder have been added.

    I moved from 5.4.016 with a settings restore (which included just /etc/samba) onto 6.0.001, ET10K, and there were no problems.

  13. #13
    ViX Beta Tester ccs's Avatar

    Join Date
    Sep 2014
    Posts
    5,097
    Thanks
    512
    Thanked 1,172 Times in 1,001 Posts
    Quote Originally Posted by Huevos View Post
    So easier... Flash 6.0. Restore 5.4 backup. Make a 6.0 backup. Flash 6.0 again. Restore 6.0 backup.
    The 6.0 backup will still have /etc/samba.

  14. #14
    ViX Beta Tester ccs's Avatar

    Join Date
    Sep 2014
    Posts
    5,097
    Thanks
    512
    Thanked 1,172 Times in 1,001 Posts
    Quote Originally Posted by adm View Post
    A re-flash of 6.0.001 without a settings or plug-in restore (and with a telnet “opkg update”) got Samba working again but an immediate follow-up with a settings and plug-in restore caused it to fail again.
    I've just tried that and it worked, restoring /etc/samba from about a year ago.

    Your /etc/samba is older, but should be ok. The following will not work if you use wifi........

    This will get you the latest /etc/samba, but you will initially lose any changes you may have made in the past.

    Flash 6.0, and then (before restoring settings when you're prompted), telnet into the box and rename /etc/samba to /etc/samba.new

    Then restore settings and plugins, telnet into the box again and init 4 to stop enigma, rename /etc/samba to /etc/samba.old

    Then rename /etc/samba.new to /etc/samba and then init 3 to start up.

    That should leave you with the latest samba configs. See if you can start samba.

  15. #15
    Moderator Huevos's Avatar

    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    10,864
    Thanks
    1,826
    Thanked 3,988 Times in 2,626 Posts
    Quote Originally Posted by ccs View Post
    The 6.0 backup will still have /etc/samba.
    No, it is commented out.
    https://github.com/OpenViX/vix-core/...450R1179-R1180

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.