-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FUSE mount stops working after some time #290
Comments
I experienced this for 3 consecutive days and have reverted to a commit I think I was on before, 8997b8c |
I was about to post the same issue. I'm not sure yet of what's going on, but I randomly need to unmount and mount again my acd folder. |
@maximegaillard no - it would just not work (bad address error iirc) |
same problem here, bad address error. After remounting everything works again for a few hours :( how can I revert to the commit you're talking about @msh100 ? |
thanks, it seems to work again :) I think the write speed is not the same as with the newest commit, but it's stable again. |
spoke too soon, after an hour of being mounted: |
Yes same here it appears
Same issue as latest commit, I have absolutely no idea how to proceed. |
@yadayada is there anything we can do now to improve logging for this? I am fairly sure that the logs I have already handed over are quite unhelpful. |
I experience the same problems as Maximegaillard. Ls takes very long and in Cyberduck I receive timeout errors. I am using acd_cli on two Debian systems one works great so far and the other produces these occasional errors time by time, but at least once a day. How do I find out which commit I use on the machine that works great so far? |
Are these excerpts from the log file? If so, could you please mount in debug+foreground mode; you should get the |
Sure, will do. Will update you asap. |
I am experiencing this issue too. Only updated today and didn't notice this issue. Has anyone found a stable commit? |
I am still monitoring this and it has not happened again however has got me thinking - My suspicion at the moment is a malformed API response from Amazon. In the meantime I will keep logging and if there's nothing in a few days I guess this issue should be closed assuming Amazon is the cause of the issue. |
Did you do anything specific to fix it? Mine seems to be happening every night |
Short update: Issue of non-working fuse mount is still there and suddenly appeared on my second box as well. acd_cli on this second box was not touched or updated since september 2015, because I never had any issues. Is there anythign I can do to improve logs? |
I have the feeling that this issue is something similar as this issue: I always get this output when I try to umount my acd mount again. fusermount: failed to unmount /mount/directory: Device or resource busy Only killing the process helps... |
This just started for me today, but only on a single box. An older box with an older acd_cli is fine :/ |
Can anyone experiencing this also provide logs as mentioned above? The data I have been able to get so far is not very informative. |
So mount with |
eh, You may want to make it log somewhere all the output |
I did a --debug mount and got the same messages as @msh100 spammed over and over. I have re-pulled from the 1.3.0 master release and it seems a lot more settled - then again -i0 helped too. |
Ok, here's my rsync errors: Here's a link to my log file: https://dl.dropboxusercontent.com/u/83188234/acd_cli.log yadayada here. This is an unrelated issue with rsync's error handling. |
Hi,
|
@Niklasmaximilian See #283. Please contact Amazon's support. |
I am finding that mine is getting unmounted every night. At first I thought it was related to #283 like @yadayada suggested. I found a few files that were 'corrupted' or had been lost (they couldn't be downloaded via web interface nor acd_cli). I have deleted those files and I still find I get unmounted. I find I get these two entries a LOT
When it was a corrupted file I would find an "Internal Failure" near an attempted access of a file, since removing all those corrupted files I can't find "Internal Failure" anywhere in the logs. I notice that it gets unmounted when uploading to ACD. I am assuming the issue is relating to something in these lines here:
But I can't see why, as the file This morning I have had it unmount several times on me. Here is a link to the log: Hopefully this helps. |
I'm having the same issue as @hjone72 It's getting unmounted while uploading files with acd_cli upload. |
That may line up with the issues I had and sounds plausible. However I have not encountered it since and have been uploading 😕 |
I believe d enables debug logging so just watch your log files as not sure On Friday, 18 March 2016, hjone72 [email protected] wrote:
|
After doing some trail and error I have found that I am also getting a similar result as @geekcroft. I have started using RClone to upload files to ACD. Making this change has prevented the mount from unmounting overnight however once I run ACDCLI Sync it unmounts. Here is my latest log from when it has unmounted. I am going to try and get that foreground log again tonight. EDIT: |
I also had this problem with having to unmount and mount my acd folder daily, sometimes multiple times, and |
I am now running acd_cli using foreground and byobu (screen) and have not had the issue since. I have also stopped using acdcli upload and started using rclone. |
After upgrading to the latest repo last week, my fuse read mount started breaking every few days. This never happened with a previous build (from Feb) Here are my mount point script that runs on boot #!/bin/bash |
Update:I tried removing the acdcli sync command from both my nightly upload script and mount script as it seems like others were having overlapping syncing issues, but i'm still have the same issue. @yadayada , any logs you want me to provide? |
First off, I have deleted quite a few unrelated comments in this thread. To everyone who experiences unmounting issues and wants to provide a log, please apply the following small patch: diff --git a/acd_cli.py b/acd_cli.py
index ac3370d..68c0006 100755
--- a/acd_cli.py
+++ b/acd_cli.py
@@ -38,6 +38,8 @@ for plug_mod in iter_entry_points(group='acdcli.plugins', name=None):
_app_name = 'acd_cli'
+sys.stderr = open('acd_cli.log', 'w')
+
logger = logging.getLogger(_app_name)
# path settings And then mount in debug mode without setting the |
I manually updated acd_cli.py as i couldn't figure out how to patch it, and i've launched the mount in debug mode. Waiting for unmount patiently ;) |
I get these unhandled exceptions on
|
i haven't had a fuse unmount ever since i enabled debug logging... strange. |
I too am experiencing this issue after upgrading to the latest stable version of api 0.8.9. |
the fusemount just errored out again. Attached debug logs. |
I'm still having this issue on a new server, anything I can provide to help diagnose? |
@yadayada Forgive me for being ignorant, but am I literally just running that patch as a script and if so, where do I want/need to be to run it? I'm on Ubuntu 15.10 and installed via "pip3 install --upgrade git+https://github.com/yadayada/acd_cli.git |
@yadayada I'm still getting this error a lot, it seems to occur after running the sync command a 2nd time since mount and reading files. I've added the code in comment #290 with no luck in the logs:
Although here's what I got when I added this to class LoggingMixIn in acd_fuse.py
unmounted, sync and remount it worked again. synced 2 more times and got below
Please let me know if I can be of assistance in debugging this and thank you for all your great work. |
Removing ~/.cache/acd_cli/nodes.db and then re-syncing and re-mounting appears to fix this, at least temporarily. I'll report back if it breaks again. |
I am getting this issue again after switching to own oauth handler. I did not have it since March so I find it unlikely the two are not related. Going to update to latest master now and see if it keeps happening. |
In my experience, this normally happens when you force a sync and either the mount is being used or uploaded to. The easiest way I have found to combat this is to have a script poll every so often to ensure there is an issue. Here is what I use on my linux boxes to keep the mount running. I simply have a cronjob that checks every minute to see if everything is ok. This also takes care of the database corruption that can occur by deleting the DB and resyncing when it is found.
|
Hah. The cause may be what you say but it has been months and issues only occurred when I switched back to my own oauth handler. |
I’ve been using my own OAuth handler for many months without a problem, but I run the acdcli mount in a seperate screen window in the foreground.
|
new user of acd_cli (cheers!) and have also run into these issues where the mount frequently crashes after doing a 'acd_cli sync' straight after a rclone transfer. I have just attempted to run the mount in the foreground using screen to see if this makes any difference. Debian 8 here if it matters. |
I am not too sure what's going on here, I recently updated to the version of
acd_cli
from master, and have issues with the FUSE read mount. This has happened more than once now.The last two lines of this log just loop thousands and thousands of times.
The text was updated successfully, but these errors were encountered: