In case it helps - here's info from .s3ql/mount.log:
2018-12-28 21:45:58.438 9468:MainThread s3ql.mount.determine_threads: Using
8 upload threads.
2018-12-28 21:45:58.440 9468:MainThread s3ql.mount.main: Autodetected 4040
file descriptors available for cache entries
2018-12-28 21:45:59.442 9468:MainThread s3ql.mount.get_metadata: Using
cached metadata.
2018-12-28 21:45:59.448 9468:MainThread s3ql.mount.main: Setting cache size
to 47196 MB
2018-12-28 21:45:59.451 9468:MainThread s3ql.block_cache.__init__: Loaded 0
entries from cache
2018-12-28 21:45:59.452 9468:MainThread s3ql.mount.main: Mounting
s3c://XXXX:443/YYYY/ at /home/sqlbackup/s3ql_mount...
2018-12-28 21:45:59.461 9468:MainThread s3ql.mount.unmount: Unmounting file
system...
2018-12-28 21:45:59.463 9468:MainThread root.excepthook: Uncaught top-level
exception:
Traceback (most recent call last):
File "/bin/mount.s3ql", line 9, in <module>
load_entry_point('s3ql==2.33', 'console_scripts', 'mount.s3ql')()
File
"/usr/lib64/python3.4/site-packages/s3ql-2.33-py3.4-linux-x86_64.egg/s3ql/mount.py",
line 189, in main
faulthandler.enable(crit_log_fd)
AttributeError: 'int' object has no attribute 'fileno'
On Friday, December 28, 2018 at 9:41:27 PM UTC-5, Matthew Dent wrote:
>
> Greetings!
>
> Thanks for all your hard work!
>
> I just upgraded to 2.33 - ran the s3qladmin upgrade - and thought
> everything was fine. But when I mount the filesystem, it seems to crash.
> Mounting it in the foreground with logging turned on seems to work fine,
> but mounting normally mount.s3ql <endpoint> <mountpoint> seems to cause the
> crash.
>
> Any hints, pointers, suggestions, or thoughts are more than welcome! I
> had been using 2.31 - skipped the 2.32 upgrade as I saw that 2.33 was out.
>
> Thanks in advance!
>
> -- Matt
>
--
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].
For more options, visit https://groups.google.com/d/optout.
