The new update works fine! Thank you so much for helping with our very
out-of-date system. We should be upgrading shortly.
** Changed in: s3ql (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
We are indeed using the PPA as the source of the S3QL package. Upon
installation of version 1.15, I encountered this error message:
SyntaxError: ('invalid syntax',
('/usr/lib/pymodules/python2.6/s3ql/mount.py', 251, 50, 'with
tempfile.NamedTemporaryFile() as tmp, \\\n'))
I suspect there'
Public bug reported:
I've been unable to connect to our remote s3ql shares. The error "transport
endpoint is not connected" comes up when trying to ls or cd to the shares. The
issues seems to occur when the mount.s3ql command is called with the
--metadata-upload-interval flag set to 0. The s
An upgrade to s3ql (1.13.2-1~lucid1) was applied yesterday. The ACLs
error no longer appears.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1142452
Title:
rsync throws Invalid argument (22) errors
Public bug reported:
Ubuntu: Lucid 10.04.4
Kernel: 3.0.0-31-server
rsync: 3.0.7-1ubuntu1.1
s3ql: 1.13.1-1~lucid2
Every night we make a backup to a remote s3ql share using rsync. In the
past few days this error started showing up in the logs for every single
file:
rsync: get_acl: sys_acl_get
** Attachment added: "mountall-hack.log"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+attachment/3264218/+files/mountall-hack.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037192
Title:
NFS shares are mounted with wrong clientaddr or not at all
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
** Attachment added: "mountall-net-device.log"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+attachment/3264216/+files/mountall-net-device.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Attachment added: "mountall-flush.log"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+attachment/3264214/+files/mountall-flush.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Attachment added: "mountall-.log"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+attachment/3264213/+files/mountall-.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Attachment removed: "Mounts with 0.0.0.0 for client address"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+attachment/3264211/+files/mountall-.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Hi Steve. I'm working with Niko on the server mountall problem. You're
right that the 0.0.0.0 client address issue occurs because mountall is
able to mount our NFS shares before it should. Initially upon startup,
we run busybox's ipconfig (no tinc) and then rsync with the server to
get system up
12 matches
Mail list logo
