TOS 5.1.123 (X86) is Released for Update

[topo01]

Upgrading from an old model of TOS4 to TOS5 is not easy, and only a portion of users wish to upgrade to TOS5, ...

I would speculate that this particular portion of users is very close to 100%!

[astrolinux]

Have you found a different way to upgrade system partition from 2GB to 8GB without formatting the data partition? I have an F2-221 with two 4GB disks in RAID with version 5.1.41 (and 2GB system partition of course).
Thank you

[TMRyan]

There is no other way, you need to back up the data and then format it.

[XFNeo]

After update TOS from 5.1.103 to 5.1.123 (also I updated docker manager to 2.0.16 version) some of my cron job stop working.
E.g.:

Code: Select all

*/5 * * * * docker exec -u www-data nextcloud-app-1 php cron.php

/var/log/crond.log:

Code: Select all

[Wed Apr 24 13:35:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:36:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:36:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
Apr 24 13:37:01 TNAS-MATI crond: ignoring /var/spool/cron/crontabs/root (non-existent user)
Apr 24 13:37:01 TNAS-MATI crond: no timestamp found (user root job sys-hourly)
Apr 24 13:37:01 TNAS-MATI crond: unable to write timestamp to /var/spool/cron/cronstamps/root.sys-hourly (user root job sys-hourly)
Apr 24 13:37:01 TNAS-MATI crond: no timestamp found (user root job sys-daily)
Apr 24 13:37:01 TNAS-MATI crond: unable to write timestamp to /var/spool/cron/cronstamps/root.sys-daily (user root job sys-daily)
Apr 24 13:37:01 TNAS-MATI crond: no timestamp found (user root job sys-weekly)
Apr 24 13:37:01 TNAS-MATI crond: unable to write timestamp to /var/spool/cron/cronstamps/root.sys-weekly (user root job sys-weekly)
Apr 24 13:37:01 TNAS-MATI crond: no timestamp found (user root job sys-monthly)
Apr 24 13:37:01 TNAS-MATI crond: unable to write timestamp to /var/spool/cron/cronstamps/root.sys-monthly (user root job sys-monthly)
[Wed Apr 24 13:37:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:37:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:38:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:38:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:39:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:39:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
Apr 24 13:40:01 TNAS-MATI crond: failed to get uid for root
Apr 24 13:40:01 TNAS-MATI crond: unable to ChangeUser (user root job sys-hourly)
Apr 24 13:40:01 TNAS-MATI crond: unable to write timestamp to /var/spool/cron/cronstamps/root.sys-hourly (user root job sys-hourly)
Apr 24 13:40:01 TNAS-MATI crond: exit status 1 from user root job sys-hourly
[Wed Apr 24 13:40:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:40:16 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
Apr 24 13:40:16 TNAS-MATI crond: exit status 127 from user user1 docker exec -u www-data nextcloud-app-1 php cron.php
[Wed Apr 24 13:41:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:41:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:42:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:42:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:43:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:43:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:44:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:44:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
Apr 24 13:45:01 TNAS-MATI crond: exit status 127 from user user1 docker exec -u www-data nextcloud-app-1 php cron.php
[Wed Apr 24 13:45:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:45:16 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:46:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:47:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:47:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec

The command "docker exec -u www-data nextcloud-app-1 php cron.php" works when I start it from termainal manually.

When I changed "docker" to "/Volume1/@apps/DockerEngine/dockerd/bin/docker" it starts working again.

Code: Select all

*/5 * * * * /Volume1/@apps/DockerEngine/dockerd/bin/docker exec -u www-data nextcloud-app-1 php cron.php

P.S. In /var/log/crond.log also a lot of strange logs with "exit status 1"

[UncleJohnsBand]

Trying out the Centralized Backup. I noticed that when setting up the schedule I selected 01:15 for the schedule to run. i.e. 1:15 a.m.

After the task was created I noted the time ended up being 13:15 or 1:15 pm.

I edited the task and set the time to be 13:15 and sure enough it then was saved as 1:15 a.m.

However, the folder that is created for the backup showed the 13 hour and not the 01 hour.

2024-05-05-Backup Folder Image.png (2.69 KiB) Viewed 35 times

I am just reporting that the time you set in the backup task is not aligning with what gets saved.... it gets reversed from a.m. to p.m. military time.

The backup I ran was for a Hyper-V on one of the machines on my network and I had no issue (other than needing to activate remote management on the machine) with the backup.

Remote Management Enablement:
https://learn.microsoft.com/en-us/windo ... management

[UncleJohnsBand]

Trying out the Centralized Backup. I noticed that when setting up the schedule I selected 01:15 for the schedule to run. i.e. 1:15 a.m.

After the task was created I noted the time ended up being 13:15 or 1:15 pm.

I edited the task and set the time to be 13:15 and sure enough it then was saved as 1:15 a.m.

However, the folder that is created for the backup showed the 13 hour and not the 01 hour.
2024-05-05-Backup Folder Image.png

I am just reporting that the time you set in the backup task is not aligning with what gets saved.... it gets reversed from a.m. to p.m. military time.

The backup I ran was for a Hyper-V on one of the machines on my network and I had no issue (other than needing to activate remote management on the machine) with the backup.

Remote Management Enablement:
https://learn.microsoft.com/en-us/windo ... management

I now added a Windows backup, same issue on schedule. I did a run now at 12:41 p.m. and this is the folder that was created.... 12:41 a.m.

2024-05-05-Backup Folder Image-Windows.png (2.57 KiB) Viewed 22 times