Cloudron time vs App time mismatch
-
Jan 07 19:20:42 2021-01-07 17:20:42,223 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Jan 07 19:20:42 2021-01-07 17:20:42,223 INFO success: teamspeak entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)why the 2h difference?
Funny enough it shows two different times there already, one is 2h off, the other is 4h off
See the backup times and their time stamp file name - it is consistent there
Here's the backup list from WinSCP
Compare the file names and the file date. System time is correctWould that cause DB to fail a reconnect in TS?
-
Jan 07 19:20:42 2021-01-07 17:20:42,223 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Jan 07 19:20:42 2021-01-07 17:20:42,223 INFO success: teamspeak entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)why the 2h difference?
Funny enough it shows two different times there already, one is 2h off, the other is 4h off
See the backup times and their time stamp file name - it is consistent there
Here's the backup list from WinSCP
Compare the file names and the file date. System time is correctWould that cause DB to fail a reconnect in TS?
@robi for the first logviewer mismatch, this is because the first time shown is from the logservice itself and is translated into the local time of your browser, whereas the second comes from the app itself and is just treated as a plain string. Apps normally run in UTC.
For the winscp part, I am not sure how winSCP translates timestamps. The folder names are set from server time.
I don't think any of this will have anything to do with DB reconnection, if you have any issue there, please make a new entry in the TS forum section with some more info.
