Bug Description

Binary package hint: ubuntuone-client

Running Karmic on x86-64.

At least one of the files was copied over to ~/Ubuntu One as root. When syncdaemon tries to hash (prepping for a sync) this file it gets a permission denied error and then continues in a viscous loop trying to hash this same file over and over again (see log in comment #5). Changing the file permissions on this file from root corrects the problem.

After moving ~320mb of versioned software repositories to my Ubuntu One share, I've noticed that the Ubuntu One client is constantly working. Further inspection with top(1) shows the ubuntuone-syncdaemon running at max CPU and continually allocating more memory. This continued until my system slowed to a crawl and I was forced to SIGKILL ubuntuone-syncdaemon ( it didn't respond to SIGTERM ).

When I restarted the ubuntuone-client, the ubuntuone-syncdaemon appeared to get in to its previous state, running at 100% CPU and constantly chewing up more memory.

Cary, thanks for your bug report. Please could you upgrade your ubuntuone packages and let us know if this is still a problem? There have been many fixes recently, so this problem may not exist any more. Please let us know. Thanks.

I'm sorry to hear Ubuntu One is eating up so much of your computer's resources. It would be helpful if you could do the following to help us get to the root cause of this problem:

1) Open Applications->Accessories->Terminal and then:
killall ubuntuone-client-applet ubuntuone-syncdaemon
/usr/lib/ubuntuone-client/ubuntuone-syncdaemon --debug > ~/syncdaemon-debug.log &
top
2) Open Applications->Internet->Ubuntu One
3) Allow Ubuntu One to sync existing files or put some files in your ~/Ubuntu One/ folder to force the problem
4) Attach ~/syncdaemon-debug.log to this bug report and also let us know what the CPU and MEM usage looked like in top for the Ubuntu One python processes
5) Back in a terminal session, run: apport-collect -p apport-collect -p ubuntuone-client 407762

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 506559, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

The easiest solution is to remove files owned by root from the Ubuntu One folder (or to change their owner or permissions). But I don't have any idea if you want to have files owned by root in your Ubuntu One folder.
If suggestions mentioned above doesn't work, look also in comments of Bug #449760.

I am confused here. Between comments #14 and #15 there appears to be 'Fix Released'

If Rubén is genuinely experiencing this bug today (and running the latest software), then it suggest the problem has not been fixed.

@Rubén:
If you could open a terminal and paste the following commands and attach your output then it will help confirm which
version of software you are running:

cat /etc/*release*

dpkg -l | egrep '(ubuntuone|u1sync)'

(If you prefer screenshots then the version number of ubuntu one might be shown in an 'About' section of the
ubuntuone applet and you could attach that screenshot instead)

Suggesting the user check ownership of files within a directory structure to ensure there is no 'root' ownership is
(1) a workaround
(2) unnecessary if the problem is fixed ... ?Fix Released?

Would be nice to have some feedback from a member of the paid canonical staff, regarding whether they
feel that the Ubuntu One product is production ready, if it indeed still contains such a basic fault.

I did use Ubuntu One, but have stayed away for the last six months, hoping that bugs such as
this would be ironed out.

Forget Maverick Meerkat, if Canonical are really pitching these (Ubuntu one) facilities at the enterprise, then bugs like
this need to be truly squashed and thoroughly tested.

Perhaps @Joshua Hoover
or @Facundo Batista
might have some details of whether the bug has a fix or if it is to be given developer time?

I have no interest in a re-reading any workaround (thank you in advance) but I do have some practical suggestions:
(1) give ubuntu one or syncdaemon (whatever) root privileges just temporarily whilst it does it remote hash fetching
( maybe some folks might not like that idea from a network security point of view but can perhaps be mitigated )

or

(2) check file permissions as it traverses directories of files and skip any files it doesn't have authority to hash check
( optional report to the user which files it skipped )

Perhaps if suggestion (1) was felt to be a candidate for a solution then something along the lines of
open network socket, fetch remote hashes, drop network socket, gain root privilege, compare hashes with local, drop root privilege, reopen network socket for syncing
...might be a way of mitigating security concerns, by only having root privilege during non networked mode of the daemon.

I add myself to the list of those affected by this bug, but in... Natty.
To get rid of, i just executed: sudo apt-get remove --purge ubuntuone*
Now, my computer (Acer 5920G) works well, but I do not have the guts to install ubuntuone again.
I arrived here after founding first: https://bugs.launchpad.net/ubuntuone-client/+bug/449760
Before uninstalling, the:
ps auxwww | grep -v S
was showing ubuntuone-syncdaemaon among the offending (always started) processes.

I understand you have already uninstalled the software, but could you please send the archived logs from ~/.cache/ubuntuone/log to <email address hidden> so that we could have a look at what point the system starts malfunctioning?

The "Fix Released" status means that the syncdaemon no longer tries to hash the file it has no permission for.
It writes the following line in the log
"Ignoring path as we don't have enough permissions to track it: '/home/rtg/Ubuntu One/No_hash_me/history.mbox'"
And that's it, it does not try to re-hash the file.

Please find enclosed the archive of my ~/.cache/ubuntuone/log folder. I looked at it, but it shows nothing suspicios (for me).
The output of "uname -a" on my Acer 5920G: Linux fif 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
I should stress that I encountered many times a situation when my processor was at 90-100% for some time (usually until a restart), but I never identified the cause. It was just today that I found about ubunutuone-syncdaemon by following instructions on: http://superuser.com/questions/53673/cpu-mysteriously-being-used-by-nothing (notably the ps auxwww | grep -v S command).
It is just several hours since I uninstalled ubuntuone-syncdaemon, but things seem to be normal, i.e. no more processor at 100%.

I have this or a similar problem, despite apparently haveing the latest version of ubuntuone.
I get a lot of CPU usage on startup, but this settles down, so not a killer. The real problem is a gradual increase in memory usage. Each day it's more. Right now it's using 56% (1.2gig) of memory and no cpu.

We are currently debugging memory and CPU usage to find and solve the problems. This is currently work in progress, being tracked on bug #902166 and bug #913912. You can subscribe to those bugs, and click the link on the top to say that you are affected too.

Sorry for the problems, and thanks for telling us about them.
pura vida.