TOS 7.0.0616 Beta (X86) is Released for Update

[star]

updated to 7.0.0706
all data erased on volume1 includeing all vms and docker. and apps.
everything was erased....

[usersky]

With the help from the support guys i managed to go back to TOS6, have all the data, will stay on 6 for a while. I hope the recent blunders aren't because of Claude or another AI coding tools

[Phil]

updated to 7.0.0706
all data erased on volume1 includeing all vms and docker. and apps.
everything was erased....

Our system update package will not affect your data. Your situation may be somewhat unique and may be caused by some unknown reasons. Please schedule remote technical support through our online chat window on our official website(https://salesiq.zohopublic.com/signatur ... 97d0be8892), and we will help you troubleshoot the problem.

[rfbjr]

From syslog:
Will these commands be removed when TOS 7 is released? It seems excessive and besides in my case I don't have Docker installed

Code: Select all

Jun 17 08:59:50 Forge application[3134]: message repeated 37 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 09:00:20 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:00:20 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:00:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:04:50 Forge application[3134]: message repeated 17 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 09:05:20 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:08:50 Forge application[3134]: message repeated 15 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 09:09:20 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:10:20 Forge application[3134]: message repeated 5 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 09:10:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:19:20 Forge application[3134]: message repeated 35 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 09:19:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:20:20 Forge application[3134]: message repeated 3 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 09:20:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:30:20 Forge application[3134]: message repeated 39 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 09:30:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:36:20 Forge application[3134]: message repeated 23 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 09:36:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:40:20 Forge application[3134]: message repeated 15 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 09:40:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:49:20 Forge application[3134]: message repeated 35 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 09:49:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:50:20 Forge application[3134]: message repeated 3 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 09:50:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 09:59:50 Forge application[3134]: message repeated 37 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 10:00:20 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 10:00:20 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 10:00:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 10:03:20 Forge application[3134]: message repeated 11 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 10:03:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 10:09:50 Forge application[3134]: message repeated 25 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 10:10:10 Forge TOSDaemon[3633]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 10:10:10 Forge TOSDaemon[3633]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 10:10:10 Forge TOSDaemon[3633]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 10:10:20 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 10:10:20 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 10:10:50 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 10:11:50 Forge application[3134]: message repeated 5 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]
Jun 17 10:12:20 Forge application[3134]: DEBUG /bin/bash -c systemctl status DockerEngine.service
Jun 17 10:14:20 Forge application[3134]: message repeated 9 times: [ DEBUG /bin/bash -c systemctl status DockerEngine.service]

[Felix]

The entries showing:
systemctl status DockerEngine.service

do not necessarily indicate that the Docker application has been installed or actively used.

In TOS, some system services or background components may periodically check the status of optional services (such as DockerEngine) as part of system service monitoring or health-check routines. This can happen even if the Docker app package is not installed

[rfbjr]

Fair enough, I was also just wondering with the entries labeled DEBUG if they were only there while TOS 7 is still beta. I didn't have DEBUG mode turned on that NAS.