TOS 6.0.555 (X86) is Released for Update

[ORION]

updated from 5.1.145 to 6.0.530 and immediately he found a new update to 6.0.555 everything went without problems! the IP has not changed, the files are all in place, I just re-configured some system settings, the total time is no more than 40 minutes.

[mrslother]

Active Directory problem after upgrading from 6.0.535.

My Active Directory domain was not enabled (checkbox in Settings--> Domain --> Join Domain option is not checked).
.......
What has changed since 6.0.535??

I modified the /etc/samba/smb-ads.conf file with

Code: Select all

workgroup = MYDOMAIN

but while trying to rejoin the domain TOS keeps rewriting that line to

Code: Select all

workgroup = INTRA

It looks like TOS is pulling my configured AD domain ("intra.mydomain.com") and just extracting the "intra" from it.
That would be a regression from 6.0.535.
Why is this happening?

[redbad]

F5-221 updated without issues

[ColaChen]

Hi.
Did you only change the value of "workgroup=MYDOMAIN" on 6.0.535? Are there any other configurations? Our lab will verify whether the situation you described exists. Thank you.

[mrslother]

Did you only change the value of "workgroup=MYDOMAIN" on 6.0.535?
Are there any other configurations? Our lab will verify whether the situation you described exists. Thank you.

I don't know what the contents of smb-ads.conf was back in 535 but the NAS was properly joined to the domain and reflected the "MYDOMAIN" workgroup. After updating to 555:

• The Network Services --> SMB File Service config still showed workgroup/domain as: "MYDOMAIN"

• The Privileges --> Domain join checkbox was no longer checked. When manually checking the config options were already present in the edit fields; the domain showed "intra.mydomain.com" as expected. And the advanced settings showed workgroup of "MYDOMAIN" as expected.

I only noticed that /etc/samba/smb-ads.conf contains "INTRA" only after the domain re-join failure. I don't know what it had before I tried re-joining the domain.
If I change it to "MYDOMAIN" and try re-joining it always is rewritten to say "INTRA".

[TMlinda]

This issue has been verified in our laboratory and is being resolved. Please wait for the release of the next system version.

[mrslother]

Thank you for your fast response to this issue.

[Digit]

Hi,
I have an issue everyday after scheduled reboot.
I am using rsync service only and the latest is not restarting properly.
The /etc/rsyncd.conf is not rebuilt correctly... when I go in the UI and define the rsync service, I get this rsyncd.conf:

Code: Select all

log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
lock file = /var/lock/rsync.lock
use chroot = no
max connections = 5
read only = no
write only = no
list = no
ignore errors = yes
#motd file = /etc/rsyncd.motd
#exclude =
uid          = david
gid          = david
port         = 873
auth users   = nas_backup
secrets file = /etc/rsyncd.passwd

        [backup_VM]
        path = /Volume1/backup_VM
        list = yes

        [backup_homes]
        path = /Volume1/backup_homes
        list = yes

        [backup_scans]
        path = /Volume1/backup_scans
        list = yes

However, after a scheduled reboot, it looks invalid (uid empty, git instead of gid and empty):

Code: Select all

log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
lock file = /var/lock/rsync.lock
use chroot = no
max connections = 5
read only = no
write only = no
list = no
ignore errors = yes
#motd file = /etc/rsyncd.motd
#exclude =
uid = 
git = 
port         = 873
auth users   = nas_backup
secrets file = /etc/rsyncd.passwd

        [backup_VM]
        path = /Volume1/backup_VM
        list = yes

        [backup_homes]
        path = /Volume1/backup_homes
        list = yes

        [backup_scans]
        path = /Volume1/backup_scans
        list = yes

Could you please fix this asap as it's the only reason for me to have bought this nas (backup my primary nas through rsync)

[TMlinda]

Thanks for your feedback, we will verify whether this issue exists in our lab.

[addx972]

thank you for your message i made the update and everything is working for me