U1 does not connect or connects erratically

Besides, on the "Computers connected to this account"

https://one.ubuntu.com/account/machines/

one can only remove, but not add computers. Why?

Despite ps aux shows

sergei 10389 0.1 0.1 244752 30420 ? SL 11:21 0:01 /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-login

no login prompt pops up

Sergei,
Sorry to hear Ubuntu One is not working for you as expected. Looking at your logs it looks like you need to reauthorize(add) your computer. Sometimes Tokens get stuck in the keyring preventing the process to add your computer. Could you please try the following:

   1. Quit the Ubuntu One Preferences (if open)
   2. Open Applications->Accessories->Passwords and Encryption Keys
   3. Click on the arrow next to "Passwords"
   4. Right-click on the Ubuntu One token and select "Delete"
   5. Go to https://one.ubuntu.com/account/machines/
   6. Click on the checkbox next to your computer
   7. Click the "Remove selected computers" button
   8. Open a Terminal and run:
       u1sdtool -q; killall ubuntuone-login; u1sdtool -c
   9. a web page should open, prompting you to add your computer to your Ubuntu One account
  10. Add your computer

You should be connected after you follow these steps. If you are not connected, can you please attach the following files to this bug report?

~/.cache/ubuntuone/log/oauth-login.log
~/.cache/ubuntuone/log/syncdaemon-exceptions.log
 ~/.cache/ubuntuone/log/syncdaemon.log

Thank you,
duanedesign

Thank you, Duanedesign!

I will try your recipe as soon as I get to that (remote) computer and send you the requested logs.

Meanwhile, U1 started to behave erratically even on this computer (I am communicating from),
which worked flawlessly before. The sync daemon eats up a lot of CPU cycles:

sergei@tp:~$ top

top - 22:17:45 up 1 day, 23:51, 8 users, load average: 0.88, 0.80, 0.74
Tasks: 233 total, 2 running, 231 sleeping, 0 stopped, 0 zombie
Cpu(s): 49.3%us, 5.8%sy, 0.0%ni, 45.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 3089872k total, 2927768k used, 162104k free, 217788k buffers
Swap: 6023164k total, 1972k used, 6021192k free, 1185684k cached

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 2104 sergei 20 0 214m 45m 5260 R 113 1.5 92:16.89 ubuntuone-syncd

sergei@tp:~$ ps aux | grep ubuntu
sergei 2104 3.3 1.5 219424 46568 ? Rl Sep16 94:57 /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
sergei 2124 0.1 1.0 236492 31364 ? SL Sep16 3:38 /usr/bin/python /usr/lib/ubuntu-sso-client/ubuntu-sso-login

I am attaching the files you requested, for this computer.

[Another bug just popped up: when I try to upload the files .cache/... from a dotted directory using the Attachment button on this launchpad bug reporting site, it DOES NOT SEE any dotted directories!]

Yet another bug: it only allows for attaching just one file

This is the third file attached

Ubuntu seems to become a real MS competitor: I wonder how it is possible to make so many errors in
just 3 lines: one cron and two rsync commands

Duanedesign,

I did as you suggested, several times, all 10 steps successfully.
But it still does not connect (sync failed in Tomboy, without any explanations)

I am attaching the required files.

On Thu, Sep 16, 2010 at 6:07 PM, duanedesign <email address hidden> wrote:
> Sergei,
> Sorry to hear Ubuntu One is not working for you as expected. Looking at your logs it looks like you need to reauthorize(add) your computer. Sometimes Tokens get stuck in the keyring preventing the process to add your computer. Could you please try the following:
>
>   1. Quit the Ubuntu One Preferences (if open)
>   2. Open Applications->Accessories->Passwords and Encryption Keys
>   3. Click on the arrow next to "Passwords"
>   4. Right-click on the Ubuntu One token and select "Delete"
>   5. Go to https://one.ubuntu.com/account/machines/
>   6. Click on the checkbox next to your computer
>   7. Click the "Remove selected computers" button
>   8. Open a Terminal and run:
>       u1sdtool -q; killall ubuntuone-login; u1sdtool -c
>   9. a web page should open, prompting you to add your computer to your Ubuntu One account
>  10. Add your computer
>
> You should be connected after you follow these steps. If you are not
> connected, can you please attach the following files to this bug report?
>
> ~/.cache/ubuntuone/log/oauth-login.log
> ~/.cache/ubuntuone/log/syncdaemon-exceptions.log
>  ~/.cache/ubuntuone/log/syncdaemon.log
>
> Thank you,
> duanedesign
>
> --
> U1 does not connect or connects erratically
> https://bugs.launchpad.net/bugs/638858
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “ubuntuone-client” package in Ubuntu: New
>
> Bug description:
> Binary package hint: ubuntuone-client
>
> 1) Ubuntu release and 2) U1 package version were collected autonmatically by ubuntu-bug.
>
> 3) I have been expecting U1 to start working, for a few months.
>
> 4) It does not.
>
> I have several computers connected to U1, most of them work, somehow, but the connection/synchronization
> mechanism is very nondeterministic and erratic. You are never sure whether you are connected and synchronized,
> except clicking on the "tools", "synchronize" in Tomboy notes. Then it chooses between "failed", "synchronized",
> or remembers you still have to provide credentials on your U1 account, all at random.
>
> Besides,
>
> A) I cannot connect *this* computer, from which I am filing this bug, to U1 at all, although I am logged
> on my account, and have attempted to connect and synchronize many times.
>
> B) I do not see any U1 notification icons (on any computer), which would inform me of my current U1 status.
>
> Here what I see:
>
> sergei@thor:~$ ps aux | grep ubuntu
> sergei   10343  0.1  0.2 389852 40948 ?        SL   11:21   0:01 /usr/bin/python /usr/bin/ubuntuone-preferences
> sergei   10389  0.1  0.1 244752 30420 ?        SL   11:21   0:01 /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-login
> sergei   11026 87.9  0.2 202328 43640 ?        Sl   11:36   0:43 /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
>
> Killing them all, restarting U1, opening Tomboy, synchronizing reports "Failed" with no details pr...

Sergei,
Looking at the logs from comment #9 it looks like that computer is connecting to U1 file sync server.

2010-09-27 16:38:51,138 - ubuntuone.SyncDaemon.Main - NOTE - ---- MARK (state: <State: 'QUEUE_MANAGER' (queues IDLE connection 'With User With Network')>; queues: metadata: 0; content: 0; hash: 0, fsm-cache: hit=9022 miss=13697) ----

'With User With Network' means you are connected. You can get this status by running the following command in a Terminal:

u1sdtool -s

queues:IDLE means it currently has no files to sync. You should be able to drop a test file into your Ubuntu One folder and it should sync to the cloud and appear at https://one.ubuntu.com/files

Tomboy Notes Sync works separately from the Ubuntu One file sync. So File Sync can work while Note Sync does not, and vice-versa. To debug the note sync, first lets make sure you have followed these steps to authorize the note sync.
https://wiki.ubuntu.com/UbuntuOne/Tutorials/Notes

NOTE: Even though you may have done this already for setting up file sync you need to do this again for Tomboy. It's helpful to put "Tomboy" in the name in order to identify this entry as being for notes sync.

If you have followed those steps and Tomboy still will not sync you can get debug info with the following steps.
1. Quit Tomboy
2. Applications->Accessories->Terminal, and run:

     tomboy --debug > ~/tomboy_debug.log

3.Try to reproduce the bug and then attach ~/tomboy_debug.log to a bug report

On the second computer that started to spike the CPU, is this computer also running Ubuntu(Lucid) 10.04?
Some things to look for:

1. check the permissions of the file and make sure you are the group:owner and not root:

ls -la Ubuntu\ One/Java/examples/ch06/fig06_09_10/.CrapsTest.java~.XuCZs6

2.check whether /tmp has enough space...

3. Copy and paste the contents of the file to another file and remove it

Let us know how it goes.

thank you,
duanedesign

[Expired for ubuntuone-client (Ubuntu) because there has been no activity for 60 days.]