Samba broken after update to openvix 6.0.01

[ccs]

No, it is commented out.
https://github.com/OpenViX/vix-core/...450R1179-R1180

Yes, backupmanager no longer puts it in settings even if /etc/samba exists, but it's already in the settings file so stays there.

I've just tried it and the whole of /etc/samba still gets backed up.

root@et10000:~# grep samba /etc/enigma2/settings
config.backupmanager.backupdirs=['/etc/enigma2/', '/etc/fstab', '/etc/hostname', '/etc/network/interfaces', '/etc/passwd', '/etc/shadow', '/etc/etc/shadow', 
'/etc/resolv.conf', '/etc/ushare.conf', '/etc/inadyn.conf', '/etc/tuxbox/config/', '/etc/wpa_supplicant.conf', '/usr/softcams/', '/etc/auto.network', '/usr/crossepg/providers', 
'/etc/samba', '/usr/keys', '/opt', '/usr/script', '/usr/sundtek', '/etc/rc3.d/S99tuner.sh', '/etc/wpa_supplicant.wlan0.conf', 
'/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/providers/terrestrial_finder.xml', '/etc/samba/smb-user.conf', '/etc/samba/private']
root@et10000:~#

[Huevos]

Yes, backupmanager no longer puts it in settings even if /etc/samba exists, but it's already in the settings file so stays there.

I've just tried it and the whole of /etc/samba still gets backed up.

root@et10000:~# grep samba /etc/enigma2/settings
config.backupmanager.backupdirs=['/etc/enigma2/', '/etc/fstab', '/etc/hostname', '/etc/network/interfaces', '/etc/passwd', '/etc/shadow', '/etc/etc/shadow', 
'/etc/resolv.conf', '/etc/ushare.conf', '/etc/inadyn.conf', '/etc/tuxbox/config/', '/etc/wpa_supplicant.conf', '/usr/softcams/', '/etc/auto.network', '/usr/crossepg/providers', 
'/etc/samba', '/usr/keys', '/opt', '/usr/script', '/usr/sundtek', '/etc/rc3.d/S99tuner.sh', '/etc/wpa_supplicant.wlan0.conf', 
'/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/providers/terrestrial_finder.xml', '/etc/samba/smb-user.conf', '/etc/samba/private']
root@et10000:~#

Read post #9 again.

[ccs]

Read post #9 again.

I have done, it won't work.

So easier... Flash 6.0. Restore 5.4 backup. Make a 6.0 backup. Flash 6.0 again. Restore 6.0 backup.

Make a 6.0 backup includes /etc/samba from the 5.4 backup.

tar.jpg

[Huevos]

I have done, it won't work.



Make a 6.0 backup includes /etc/samba from the 5.4 backup.

tar.jpg

How? It is commented out.

[ccs]

I've just taken a few backups on 6.0.001 (Release), here is what I get in the latest....

root@et10000:/media/hdd/ccs/etc# ls -l
-rwxr--r--    1 root     root           254 Jul 15 12:54 auto.network
drwxr-xr-x    2 root     root          4096 Nov  9 19:51 enigma2
-rwxr--r--    1 root     root           217 Jul 15 12:48 fstab
-rwxr--r--    1 root     root             8 Jan 12  2018 hostname
drwxr-xr-x    2 root     root          4096 Nov  9 19:51 network
-rwxr--r--    1 root     root           974 Jan 21  2021 passwd
drwxr-xr-x    2 root     root          4096 Nov  9 19:51 rc3.d
-rwxr--r--    1 root     root            93 Nov  9 18:29 resolv.conf
drwxr-xr-x    4 root     root          4096 Nov  9 19:51 samba
-rwxr--r--    1 root     root           730 Jan 21  2021 shadow
drwxr-xr-x    3 root     root          4096 Nov  9 19:51 tuxbox
-rwxr--r--    1 root     root           113 Nov 15  2017 wpa_supplicant.conf
-rwxr--r--    1 root     root           244 Feb 12  2021 wpa_supplicant.wlan0.conf
root@et10000:/media/hdd/ccs/etc# ls -lR samba
samba:
drwxr-xr-x    2 root     root          4096 Nov  9 19:51 distro
-rwxr--r--    1 root     root            20 Dec 31  2020 lmhosts
drwxr-xr-x    2 root     root          4096 Nov  9 19:51 private
-rwxr--r--    1 root     root           772 Dec 31  2020 smb-user.conf
-rwxr--r--    1 root     root           744 Dec 31  2020 smb-user.conf.orig
-rwxr--r--    1 root     root            95 Dec 31  2020 smb.conf

samba/distro:
-rwxr--r--    1 root     root            61 Dec 31  2020 smb-branding.conf
-rwxr--r--    1 root     root          1457 Dec 31  2020 smb-global.conf
-rwxr--r--    1 root     root           586 Dec 31  2020 smb-shares.conf
-rwxr--r--    1 root     root             0 Nov  9 19:45 smb-vmc.conf
-rwxr--r--    1 root     root            29 Dec 31  2020 smb-vmc.samba

samba/private:
-rwxr--r--    1 root     root        430080 Dec 31  2020 secrets.tdb
-rwxr--r--    1 root     root           204 Dec 31  2020 smbpasswd
-rwxr--r--    1 root     root            80 Dec 31  2020 users.map
root@et10000:/media/hdd/ccs/etc#

The commit is definitely in there, I thought it just appended entries to /etc/enigma2/settings, and that is then used to select which files to backup??

root@et10000:/media/hdd/ccs/etc# grep samba /etc/enigma2/settings
config.backupmanager.backupdirs=['/etc/enigma2/', '/etc/fstab', '/etc/hostname', '/etc/network/interfaces', '/etc/passwd', '/etc/shadow', '/etc/etc/shadow', '/etc/resolv.conf', '/etc/ushare.conf', '/etc/inadyn.conf', 
'/etc/tuxbox/config/', '/etc/wpa_supplicant.conf', '/usr/softcams/', '/etc/auto.network', '/usr/crossepg/providers', '/etc/samba', '/usr/keys', '/opt', '/usr/script', '/usr/sundtek', '/etc/rc3.d/S99tuner.sh', 
'/etc/wpa_supplicant.wlan0.conf', '/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/providers/terrestrial_finder.xml', '/etc/samba/smb-user.conf', '/etc/samba/private']
root@et10000:/media/hdd/ccs/etc#

You don't even need to install samba, everyone will have a copy of /etc/samba in their backups.

[Huevos]

init 4 ... remove "config.backupmanager.backupdirs" from settings file... init 3... make a backup.

[ccs]

init 4 ... remove "config.backupmanager.backupdirs" from settings file... init 3... make a backup.

That works (although a bit of an overkill if you've added some yourself), I removed /etc/samba from settings on my ultimo4k/py3 when the commit first came out.

The next flash and restore then leaves you the latest /etc/samba from the distro, plus the user maintained /etc/samba/smb-user.conf and /etc/samba/private.

[Huevos]

So lets purge it from settings when users make a backup.
https://github.com/OpenViX/vix-core/...4657cee7c47351

[adm]

So easier... Flash 6.0. Restore 5.4 backup. Make a 6.0 backup. Flash 6.0 again. Restore 6.0 backup.

Doesn't work for me.

If I don't restore settings (5.4 or 6.0) I can install Samba and it will run in 6.0.001
Without a settings/plug-in restore I have to telnet into the box and "opkg update" before a samba install will work correctly - otherwise it goes into the loop when selecting samba - every time it asks if you want to install then goes away for a while and requires a reboot to finish - repeating endlessly if the samba menu is selected again.
If I subsequently restore settings (5.4 or 6.0) then Samba will be stopped and I cannot start it. The autostart can still be changed between enabled and disabled but the manual start (green button) does nothing and when autostart is enabled a reboot will not get it running. The network is OK - I can FTP and Telnet to the box.

[ccs]

So lets purge it from settings when users make a backup.
https://github.com/OpenViX/vix-core/...4657cee7c47351

Yes, that works, backup no longer includes /etc/samba, just the 2 files/folder that are needed.

[adm]

I've got it working but strange....

I removed "etc/samba" from the backup settings/plugin file and re-tared and re-gzipped it.
Re-flashed 6.0.001, installed samba to a working state (having said yes to a reboot to finish the install) but it failed to start again after restoring my modified back settings/plugin file.

Re-flashed 6.0.001, restored my modified backup setting file and then installed samba and said yes to the reboot to finish installing samba - after the reboot samba failed to start.

Re-flashed 6.0.001, restored my modified backup setting file and then installed samba and said NO to the reboot. Samba working. I then put the box into deep standby, waited until it closed down and switched it back on - samba still working. Gave the box a reboot - samba still working.

[widar]

Hello, have same problem on my zgemma 9s but not on my zgemma h7, both upgraded to 6.0.002, the other thing on both is that the cccam webpage info cant be found. Cccam works still. I have tested the hints above, that I am able to, as I am not a experienced user. Nothing get the samba to work, most important to me iis the samba thing. Thank you for any help.

[Tkr001]

Samba didn't work on any of the 5 boxes I upgraded. I found it easiest to flash and set up from scratch. No problems with Samba that way. You can copy timers, softcam configs etc before flashing and just copy the files back afterwards.

[adm]

Hello, have same problem on my zgemma 9s but not on my zgemma h7, both upgraded to 6.0.002, the other thing on both is that the cccam webpage info cant be found. Cccam works still. I have tested the hints above, that I am able to, as I am not a experienced user. Nothing get the samba to work, most important to me iis the samba thing. Thank you for any help.

The same solutions worked for me on my zgemma 9S which also had the same problem - although I did have to add a opkg udate via telnet.

Try telnetting into your box and doing a "opkg update" before trying to install samba
You wil need the IP of your box 192.168.xxx.xx (menu -> information -> network -> IP = ???.???.???.??)
You will need your box's user (name) and the password you have set-up
See post 2 in the following thread
https://www.world-of-satellite.com/s...X-5-4-released
Your username is probably root

Assuming windows 10 on the PC
In the windows search box type telnet
the search should come up with "telnet run command"
click on the search result and a window should open

type open xxx.xxx.xxx.xx and press return (where xxx.xxx.xxx.xx is the IP number of your box)
you should then get a prompt for login
type root and press return (assuming that you haven't changed the user on your box)
you should then get a prompt for password
type your password and press return
at the next prompt type opkg update
A lot of files should be downloaded to your box

Close down the telnet window and go back to your box and see if smaba will install.

[capistrano]

You can get around the problem by enforcing password protected access: just uncomment the line with "include = /etc/samba/distro/smb-secure.conf" in /etc/samba/smb-user.conf. Samba will now start without error. You will now need to authenticate when mounting the share but I guess that's better anyway.