Deployment and management tools for an entire streaming platform that can reside on a server (local, remote, hosted, VPS) with media files stored on cloud services like Google Drive or Dropbox.
Sync between uploadcache and cloud seems to be broken.
When TurboSync does it's thing, it leaves these logs and the files remain in the uploadcache directory, instead of being pushed to the cloud and removed locally.
I notice there is some grep action going on that appears it might be interpreting -'s as an indication to expect a range of data.
Since this has been working fine without issue until last night, I am curious if there was an update that may have changed something in TurboSync?
Thanks!
omniplex@server2:~/mnt/cloud/uploadcache/Media/TVShows2$ tail -f /home/omniplex/OmniStream/logs/turbosync.log
Starting sync at Wed Jun 5 15:16:02 CDT 2024
Nothing to queue
Finished at Wed Jun 5 15:16:02 CDT 2024
---------------------------------------------------
tail: /home/omniplex/OmniStream/logs/turbosync.log: file truncated
Starting sync at Wed Jun 5 15:24:01 CDT 2024
grep: Invalid range end
Queuing /Media/TVShows2/Show Name (2013) {tvdbid-000000}/Season 11/Show Name (2013) - S00E00 - [WEBDL-1080P][EAC3 2.0][H264]-NTB.mkv of size 3.5G
{
"jobid": 200
}
Finished at Wed Jun 5 15:24:01 CDT 2024
---------------------------------------------------
tail: /home/omniplex/OmniStream/logs/turbosync.log: file truncated
Starting sync at Wed Jun 5 15:32:01 CDT 2024
grep: Invalid range end
Queuing /Media/TVShows2/Another Show Name (2006) {tvdbid-111111}/Season 888/Another Show Name (2006) - S888E08 - [WEBDL-1080P][AAC 2.0][H264]-REALITYTV.mkv of size 1.2G
{
"jobid": 203
}
grep: Invalid range end
Queuing /Media/TVShows2/Show Name (2013) {tvdbid-000000}/Season 11/Show Name (2013) - S00E00 - [WEBDL-1080P][EAC3 2.0][H264]-NTB.mkv of size 3.5G
{
"jobid": 205
}
Finished at Wed Jun 5 15:32:01 CDT 2024
---------------------------------------------------
Sync between uploadcache and cloud seems to be broken.
When TurboSync does it's thing, it leaves these logs and the files remain in the uploadcache directory, instead of being pushed to the cloud and removed locally.
I notice there is some grep action going on that appears it might be interpreting -'s as an indication to expect a range of data.
Since this has been working fine without issue until last night, I am curious if there was an update that may have changed something in TurboSync?
Thanks!