search

keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.83k stars 1.22k forks source link

Issue starting KBFS windows app following registration of mobile device #6755

Closed jtsmith0101 closed 7 years ago

jtsmith0101 commented 7 years ago

my workflow:

my log id: ef91f102cfe877cd9b1ea11c

jtsmith0101 commented 7 years ago

I appear able to login from the command line, however the app is still "hung" on "loading"

jtsmith0101 commented 7 years ago

My devices are displayed as they should be from the command line. (keybase device list)

jtsmith0101 commented 7 years ago

could be a coincidence?

jtsmith0101 commented 7 years ago

app starting to "wake up"...

See log: fdb733aaa445633b8eac9c1c

There is an error in my log sending:

The task bar widget displays useful messages, such as folder rekeys, when I open the App, it displays that the app is "Disconnected"

jtsmith0101 commented 7 years ago

hard restart of computer..... still exhibiting same symptoms.

See log: 4152d40fdd3afa8a36f7c41c

jtsmith0101 commented 7 years ago

Output from logout command: C:\Users>keybase logout

MarcoPolo commented 7 years ago

cc @zanderz

cjb commented 7 years ago

CC @maxtaco @patrickxb @zanderz

maxtaco commented 7 years ago

Looks like a bug in the routine that moved home dirs on windows after the reboot.

Not sure why the original problem started.

On Wed, Apr 26, 2017 at 7:42 PM Chris Ball notifications@github.com wrote:

CC @maxtaco https://github.com/maxtaco @patrickxb https://github.com/patrickxb @zanderz https://github.com/zanderz

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-297571582, or mute the thread https://github.com/notifications/unsubscribe-auth/AA05_0QtVxgm6D2RWqs2UUYaNkKL4gJ0ks5rz9ZlgaJpZM4NJhkl .

maxtaco commented 7 years ago

Sorry @jtsmith0101 for your very bad experience. This is highly embarrassing :(

We'll investigate as soon as we can. Thanks for your patience.

jtsmith0101 commented 7 years ago

Happy to test

zanderz commented 7 years ago

The RemoteSettingsRepairman warning is a red herring, since fixed. Updater log shows the target install directory to have been %LOCALAPPDATA%\Keybase since mid December.

With the RPC errors, I am curious whether a mix of versions may be involved? When you run it from c:\Users, which one runs (as per which keybase)?

The installer logs are not present. Maybe your %TEMP% directory got cleaned out?

Does it come back if you reboot?

jtsmith0101 commented 7 years ago

No change I'm afraid.

I do remember the change in installation folders from Appdata\Roaming to Appdata\Local as I had to manually change my path.

I do seem to have fully populated keybase folders in both locations. Perhaps the old pre-December installation wasn't removed when the post-December / current version installed?

I wouldn't expect this to affect performance. Before yesterday, Keybase behaved reliably.

Maybe uninstall, download the fresh version and reinstall?

On Fri, Apr 28, 2017 at 4:31 AM, Steve Sanders notifications@github.com wrote:

The RemoteSettingsRepairman warning is a red herring, since fixed. Updater log shows the target install directory to have been %LOCALAPPDATA%\Keybase since mid December.

With the RPC errors, I am curious whether a mix of versions may be involved? When you run it from c:\Users, which one runs (as per which keybase)?

The installer logs are not present. Maybe your %TEMP% directory got cleaned out?

Does it come back if you reboot?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-297800547, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ9TfAHAya-4UVd3HvqzzxS-L9xCUfPaks5r0N8MgaJpZM4NJhkl .

zanderz commented 7 years ago

What do you get when you type which keybase ?

jtsmith0101 commented 7 years ago

'which' doesn't appear to be a valid Windows command.... ;)

On Fri, Apr 28, 2017 at 9:05 AM, Steve Sanders notifications@github.com wrote:

What do you get when you type which keybase ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-297863115, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ9TfP0LTZavqv0s-BXmMwyCBcBqKmsTks5r0R9KgaJpZM4NJhkl .

maxtaco commented 7 years ago

Mixed versions of the app would not account for that error. We would only see that error if the client started sending non msgpack data down the pipe, or maybe if the pipe became unreliable and started dropping data. It is really hard to know.

It looks like the service is running in auto fork mode. Is that expected? That doesn't seem right on windows.

On Thu, Apr 27, 2017 at 7:09 PM JTS notifications@github.com wrote:

'which' doesn't appear to be a valid Windows command.... ;)

On Fri, Apr 28, 2017 at 9:05 AM, Steve Sanders notifications@github.com wrote:

What do you get when you type which keybase ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-297863115, or mute the thread < https://github.com/notifications/unsubscribe-auth/AJ9TfP0LTZavqv0s-BXmMwyCBcBqKmsTks5r0R9KgaJpZM4NJhkl

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-297863740, or mute the thread https://github.com/notifications/unsubscribe-auth/AA05_xCbrXMtOtRc82gH_f0KHZn6_DQNks5r0SAzgaJpZM4NJhkl .

zanderz commented 7 years ago

Whoops, I meant where keybase - but that probably is not very helpful, as per Max.

jtsmith0101 commented 7 years ago

fair enough.

It displays \AppData\Local\Keybase

On Fri, Apr 28, 2017 at 9:19 AM, Steve Sanders notifications@github.com wrote:

Whoops, I meant where keybase - but that probably is not very helpful, as per Max.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-297865307, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ9TfF_KPcgWviKQpQO31WJFajCrqlyEks5r0SKGgaJpZM4NJhkl .

jtsmith0101 commented 7 years ago

I'm beginning to think something corrupted while I was adding my phone to my devices...

jtsmith0101 commented 7 years ago

logged in from the command prompt. Greeted with a new popup window for entering my passphrase. Logged in....

The taskbar widget, when clicked looks normal. See attached. image

When I select "Open Keybase" from the drop down menu, the application appears stuck here: image

maxtaco commented 7 years ago

@strib / @akalin-keybase there might be a KBFS problem in this dump, the first second one linked: fdb733aaa445633b8eac9c1c

172745 2017-04-26T16:58:21.726300+10:00 - [WARN kbfs journal_server.go:229] ee93 Couldn't enable journal for 026bde44c99940882e6cf65534ab6816: Current UID is empty
172746 github.com/keybase/kbfs/libkbfs.(*JournalServer).enableLocked
172747 C:/Jenkins/workspace/windows-installer_0/src/github.com/keybase/kbfs/libkbfs/journal_server.go:433
172748 github.com/keybase/kbfs/libkbfs.(*JournalServer).Enable
172749 C:/Jenkins/workspace/windows-installer_0/src/github.com/keybase/kbfs/libkbfs/journal_server.go:485
172750 github.com/keybase/kbfs/libkbfs.(*JournalServer).getTLFJournal
172751 C:/Jenkins/workspace/windows-installer_0/src/github.com/keybase/kbfs/libkbfs/journal_server.go:227
172752 github.com/keybase/kbfs/libkbfs.(*JournalServer).JournalStatus
172753 C:/Jenkins/workspace/windows-installer_0/src/github.com/keybase/kbfs/libkbfs/journal_server.go:726
172754 github.com/keybase/kbfs/libkbfs.(*folderBranchOps).getJournalPredecessorRevision
172755 C:/Jenkins/workspace/windows-installer_0/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:613
172756 github.com/keybase/kbfs/libkbfs.(*folderBranchOps).getMostRecentFullyMergedMD
172757 C:/Jenkins/workspace/windows-installer_0/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:1110
172758 github.com/keybase/kbfs/libkbfs.(*folderBlockManager).doReclamation
172759 C:/Jenkins/workspace/windows-installer_0/src/github.com/keybase/kbfs/libkbfs/folder_block_manager.go:1034
172760 github.com/keybase/kbfs/libkbfs.(*folderBlockManager).reclaimQuotaInBackground
172761 C:/Jenkins/workspace/windows-installer_0/src/github.com/keybase/kbfs/libkbfs/folder_block_manager.go:1166
172762 runtime.goexit
172763 C:/Go/src/runtime/asm_386.s:1612
172764 2017-04-26T16:58:22.933255+10:00 - [DEBU kbfs fs.go:565] ee94 => FS CreateFile [tags:DID=XvdNmhOWjFMS-JkFz1vkyA]
strib commented 7 years ago

@maxtaco: that only means KBFS thinks the user isn't logged in. It's normal for logged out users. Sorry it looks scary.

maxtaco commented 7 years ago

K thanks, sorry for the false alarm.

maxtaco commented 7 years ago

@jtsmith0101 are you running any sort of virus protection?

jtsmith0101 commented 7 years ago

yes. I've given explicit network "allow" permission to the following apps: kbfsdokan Keybase Keybase utility upd

All are parked within \AppData\Local

On Fri, Apr 28, 2017 at 10:08 AM, Maxwell Krohn notifications@github.com wrote:

@jtsmith0101 https://github.com/jtsmith0101 are you running any sort of virus protection?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-297872465, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ9TfOOcqfbhO2KYW58Yw0qd86R8h2J6ks5r0S3lgaJpZM4NJhkl .

maxtaco commented 7 years ago

Did you recently change anything here? The issue, at its core, is that the different components of the system can't communicate with each other.

maxtaco commented 7 years ago

In particular, the keybase process runs as a background service and listens for connections on this pipe:

pipe:\\.\pipe\kbservice\Users\jtsmi\AppData\Local\Keybase\keybased.sock

Your background services are failing to connect to it. Is this socket firewalled off by your virus protector?

jtsmith0101 commented 7 years ago

I've not changed anything. Possible poor timing with Norton360 .... should I add another fw exclusion for an unamed application / service?

Or just bite the bullet and and reinstall?

On Fri, Apr 28, 2017 at 10:19 AM, Maxwell Krohn notifications@github.com wrote:

In particular, the keybase process runs as a background service and listens for connections on this pipe:

pipe:\.\pipe\kbservice\Users\jtsmi\AppData\Local\Keybase\keybased.sock

On background servers are failing to connect to it. Is this socket firewalled off by your virus protector?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-297873963, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ9TfGXYYCbqtikioTM8ZxQldnYhihIrks5r0TCcgaJpZM4NJhkl .

maxtaco commented 7 years ago

Can you try to disable norton for a moment and then try again?

zanderz commented 7 years ago

We have made a fix, which unfortunately is merely speculative, since we can't reproduce the problem. We would appreciate it if you would try installing https://s3.amazonaws.com/prerelease.keybase.io/windows/Keybase_1.0.21-20170428134902%2B4280d08.386.exe

Thanks.

jtsmith0101 commented 7 years ago

This had no effect.

On Sat, Apr 29, 2017 at 1:44 AM, Maxwell Krohn notifications@github.com wrote:

Can you try to disable norton for a moment and then try again?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-298033593, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ9TfARvGKx8b167WZjKRMFbvCsVBM06ks5r0glxgaJpZM4NJhkl .

jtsmith0101 commented 7 years ago

My Keybase appears back to normal.

Thanks guys!

On Sat, Apr 29, 2017 at 7:34 AM, Steve Sanders notifications@github.com wrote:

We have made a fix, which unfortunately is merely speculative, since we can't reproduce the problem. We would appreciate it if you would try installing https://s3.amazonaws.com/prerelease.keybase.io/windows/ Keybase_1.0.21-20170428134902%2B4280d08.386.exe

Thanks.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-298112141, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ9TfPyxGk-R0gqXEJqcLrolFzDnhRNsks5r0luDgaJpZM4NJhkl .

zanderz commented 7 years ago

Good news! What fixed it? Was it that new build just linked?

jtsmith0101 commented 7 years ago

new installation file

On Sat, Apr 29, 2017 at 8:27 AM, Steve Sanders notifications@github.com wrote:

Good news! What fixed it?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-298120907, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ9TfI1MMvq15U2GW-_kmvq1kvHwpp7Gks5r0mfkgaJpZM4NJhkl .

jtsmith0101 commented 7 years ago

or pure vodoo magic

On Sat, Apr 29, 2017 at 8:39 AM, James Smith jtsmith0101@gmail.com wrote:

new installation file

On Sat, Apr 29, 2017 at 8:27 AM, Steve Sanders notifications@github.com wrote:

Good news! What fixed it?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-298120907, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ9TfI1MMvq15U2GW-_kmvq1kvHwpp7Gks5r0mfkgaJpZM4NJhkl .

zanderz commented 7 years ago

Thanks for your patience and help.

jtsmith0101 commented 7 years ago

happy to test ;)

On Sat, Apr 29, 2017 at 8:41 AM, Steve Sanders notifications@github.com wrote:

Thanks for your patience and help.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-298122814, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ9TfKZdz-L3I-5srzeIjR7jLr_Mch_9ks5r0mssgaJpZM4NJhkl .

jtsmith0101 commented 7 years ago

And most importantly, thanks for being so responsive

On 29 Apr. 2017 08:43, "James Smith" jtsmith0101@gmail.com wrote:

happy to test ;)

On Sat, Apr 29, 2017 at 8:41 AM, Steve Sanders notifications@github.com wrote:

Thanks for your patience and help.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/6755#issuecomment-298122814, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ9TfKZdz-L3I-5srzeIjR7jLr_Mch_9ks5r0mssgaJpZM4NJhkl .

jtsmith0101 commented 7 years ago

I think this can be closed. Thanks for all your help. I spent some time digging in my AV (following a rummage through the outstanding issues on GH) and discovered that runquiet.exe is being flagged as a trojan and quarantined. After removing the quarantine, restoring the file and rebooting, keybase behaved as I expected. I've whitelisted all of the contents of the \keybase folder... so AV 'shouldn't' impact performance again.