Hi Jules, > [...] > 2020-12-24 01:01:40.302 747066:Thread-1 > s3ql.backends.gs._parse_error_response: Server response not JSON - > intermediate proxy failure? > 2020-12-24 01:01:40.303 747066:MainThread > s3ql.block_cache.with_event_loop: upload of 86350 failed > NoneType: None > 2020-12-24 01:01:40.320 747066:Thread-1 s3ql.mount.exchook: recording > exception <RequestError, code=401, reason='Unauthorized', with body data> > [...] I do not know why you do not get any exception backtrace information but S3QL did raise an exception (and the last resort exception hook logs that). It might be that your trio version is too old or new for S3QL. (I am using 0.15.0 and this version works good with S3QL)
That might be the same issue as https://github.com/s3ql/s3ql/issues/224 It might be that the Google Storage Backend with OAuth2 authentication is currently not working as expected anymore. Does the crash happens to be approx. 1 hour after you mounted the file system? That's the expiration time of an access token of the Google Backend as far as I know. Could you try to use ADC instead of OAuth for authentication? https://www.rath.org/s3ql-docs/backends.html#google-storage You could also try to change this line: https://github.com/s3ql/s3ql/blob/release-3.6.0/src/s3ql/backends/gs.py#L443 if exc.message == 'Invalid Credentials': to if exc.message == 'Invalid Credentials' or exc.code == 401: This change is a little bit to broad as it handles any HTTP 401 status code as an access token expiration – but since at this point you needed to have done several successful requests already that might be OK. I do not use Google Storage as backend so sorry for these rather unspecific suggestions. -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/c9c56d99-f640-538a-82d1-88b9463f16fc%40jagszent.de.
