Client: Can't create a new team without having provisioned a per-user key

[valleybay]

I have tried deleting both the iOS and OS X application, both to no avvail.

When logging in after logging out on OS X, I got:
▶ WARNING loginProvision PerUserKeyUpgrade failed: DB error (error 501)

[maxtaco]

Please do a 'keybase log send' from the terminal prompt.

On Sep 19, 2017 7:51 AM, "Christian Bay" [e-mail] wrote:

I have tried deleting both the iOS and OS X application, both to no avvail.

When logging in after logging out on OS X, I got:
▶ WARNING loginProvision PerUserKeyUpgrade failed: DB error (error 501)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/8528, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05_zqxVA13BZtlQjxQkWlMX93qTwG-ks5sj6rGgaJpZM4PcRbu
.

[maxtaco]

Cc: @mlsteele can you track this issue?

[mlsteele]

Hi @valleybay looks like the server is rejecting your client's attempt to make a PUK. If you do a keybase log send I'll be able to find the corresponding server logs.

[maxtaco]

I fixed your account on the server, we have to look a bit deeper into why you were affected. I know it has something to do with the fact that you revoked your first key.....

[valleybay]

Log submitted with ID be362a7396b11f24ba52de1c

[jwilkins]

same issue for keybase user polyclef

[maxtaco]

@jwilkins I believe it's fixed in master (correct me if I'm wrong @mlsteele), but you can workaround it right now via killall keybase. Or by turning on your mobile phone.

[maxtaco]

@jwilkins actually there's a bug, looking into it.

[maxtaco]

OK, another killall keybase should fix it now (I hope)

[maxtaco]

@jwilkins you should be good; your new key shows up here

[thermistor]

I also have the error message "ERROR can't create a new team without having provisioned a per-user key"

My log id is d7ef46d91f9ed6811108b61c

[maxtaco]

https://keybase.io/thermistor/sigchain#e721bbae1d73646da76943883b1e652f15bcf3792175e025bc09f7201ee6c5560f seems like your should be OK now

[kylemanna]

I have the same issue:

ERROR can't create a new team without having provisioned a per-user key

Log ID: bfefd5d044c9b6fe8e2ce01c

[maxtaco]

@kylemanna you appear to be logged out. Try keybase login?

[kylemanna]

Appears I wasn't logged in, oops. I ran keybase login. I checked my keybase status before but l glazed over the logged in line.

Now seems to work, thanks!

[johannorrman]

Same goes for me.

Log ID: c08024ca18668adadfd0971c

[kadmil]

Hey, guys, I have the same thing. keybase status shows me logged in

[maxtaco]

Do a ‘keybase log send’ and I will take a look.

On Wed, Oct 4, 2017 at 8:34 AM Victor Suzdalev [e-mail]
wrote:

Hey, guys, I have the same thing. keybase status shows me logged in

—
You are receiving this because you commented.

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

[kadmil]

My log is 76d8e6e04288fb611c689d1c

[maxtaco]

@johannorrman seems like when you did log in, it worked, there's just a slight delay.

See here

CC: @mlsteele

[maxtaco]

@kadmil your bug was fixed on the server-side, it should work as soon as you restart your app, or when the next 1hr-timed background event fires.

[austinheap]

@maxtaco if I'm stuck with the same issue should I ping support to do some server side magic? (keybase status shows me logged in, revoked my first key, etc)

[maxtaco]

@austinheap try it again, you should be G2G. I didn't do anything, you client just had to think about it a bit.

https://keybase.io/austinheap/sigchain#4bb6be99afadfdd33002dc7ca4d5ecbb675f152a8190ab74b5202b602878f4840f

[austinheap]

@maxtaco Funny I just noticed that. I quit the desktop client, did a killall keybase, reopened the client, and it worked. Thanks for the super fast response!

[maxtaco]

yeah cool that would have kicked it into action too. I believe our next release has a fix for the lag