No TOS GUI access

[Fusor]

Good day,
I've been tinkering around with my new (and first) F8 SSD Plus and after a week of "tinkering" I've hit a brick wall. So after a lot of stuff on upgrading packages, installing newer Python versions etc. etc. after restarting the system the last time (A LOT of changes done between the last two restarts) I can't enter the TOS GUI. Eveerything else works just fine, Sonarr, Radarr, Bazarr, Prowlarr, Plex, Shoko, Stash, SABnzbd, qBittorrent, SSH, EVERYTHING but the TOS GUI. Also, in my network, the link it tries to open now is IP:8181 instead of 5443, that it used to try to open. It won't open on port 80 (cause it was remapped with the checkbox in the GUI), it won't open on any port. Please help, I'm sure thing aren't for a total restart, since everything else works, it's just something messes up the GUI. And as I've said, I have access through SSH with root rights (cause I can't access with non root even if I wanted to, and it would have been better if I don't do all those things as root!).
Help!
Thanks in advance.

[TMeric]

Hello! Since your other services are working normally and only the TOS graphical interface is not accessible, I believe the system is functioning properly. Please first check that your access address and port are correct. If you haven't modified the HTTP and HTTPS ports, you should be able to access the NAS using the following addresses: http://ip:8181 or https://ip:5443.

If you still cannot access it, you can connect to the NAS backend via SSH and enter the following commands to check the status of TOSDaemon and Nginx:

systemctl status TOSDaemon.service
systemctl status nginx.service

If the status is not active (running), you can try restarting them with the following commands:

systemctl restart TOSDaemon.service
systemctl restart nginx.service

If the issue persists, please use the command df -h to check if the /dev/md9 usage has reached 100%. Please try the steps above to resolve the issue. Thank you!

[Fusor]

https://gist.github.com/Feredzhanov/d6e ... 2b50e01249
https://gist.github.com/Feredzhanov/012 ... 3df52bd061
https://gist.github.com/Feredzhanov/074 ... a3a4bc0cbe
https://gist.github.com/Feredzhanov/e83 ... a5cb257f77

This is what I get as a feedback from the commands.

[TMeric]

Hello,Based on your records, it seems that there is an issue with the Nginx service. I also noticed that the /tmp directory is currently 100% utilized. I recommend visiting our website at www.terra-master.com and contacting the online customer service in the bottom right corner. Please send her the link to this post so she can assist you in scheduling an engineer for remote troubleshooting.

[Fusor]

Here's what

Code: Select all

journalctl -xeu nginx.service

gave as answer, just for the record.
https://gist.github.com/Feredzhanov/d73 ... 3018517c65

Also I've cleaned the /tmp folder

[TMeric]

Based on the information you provided, the failure to start Nginx is due to the missing /var/log/nginx/error.log file or directory, which prevents Nginx from writing the error log. Please follow the method I mentioned earlier to schedule an engineer for remote assistance. Alternatively, you may also choose to reinitialize the system.

[Fusor]

Ok, I've managed to fix it, some how.
It wasn't the first time the /tmp dir was full, so I've read to make rm -rf * on it, apparently it broke the api, log and spool links in the /var dir, so I've recreated the 3 folders in /tmp and the links started working again, made a reboot and TOS is now working. However, right before that, the /tmp folder was again full, so any solution to that, I haven't been making installs for the past 1-2 days, cause of the TOS issue (didn't want to bug it more) and still the folder was full. Also it seems like if it gets full I can't connect to the NAS through SMB, don't exactly know if that's the issue, but seems to happen, when the /tmp gets full. Any suggestions, what to do when /tmp gets full?

[CursaYang]

The tmp directory is located in the system partition. If the system partition is full, it will cause inability to access. Please confirm whether the installation application data path is in the system partition. As a temporary solution, you can monitor the usage of the tmp directory through a script and automatically clean it up.

[Fusor]

I really don't know what is eating my /tmp folder
https://gist.github.com/Feredzhanov/ed9 ... 4e983d2faa

[Gremlin]

I really don't know what is eating my /tmp folder
https://gist.github.com/Feredzhanov/ed9 ... 4e983d2faa

Iirc the issue of /tmp filling was a bug inone version of Tos and was fixed. Maybe some research needed.