Open mmattimoe opened 6 years ago
cc: @songgao @jzila
If you do a keybase log send
, and post the resulting ID here, I can take a look.
This is the RPC for getting journal status. EOF almost sounds like kbfsfuse crashed?
Yeah a log send would help!
Thanks! I tried to send a log but I must have done it incorrectly. I’ll try again.
Sincerely,
Megan K. Mattimoe, J.D. Executive Director Advocating Opportunity 1119 Adams Street, Second Floor Toledo, Ohio 43604
Phone 855-855-1945, ext. 700 Fax 855-855-1945 Mobile 419-260-4217
Email mm@advocatingopportunity.com (mailto:mm@advocatingopportunity.com) Website www.advocatingopportunity.com (http://www.advocatingopportunity.com) Facebook www.facebook.com/advocatingopportunity (http://www.facebook.com/advocatingopportunity) Twitter https://twitter.com/AOAdvocate
Confidentiality Statement: This electronic message contains information from the law firm of Megan K. Mattimoe, Esq., and may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this message is prohibited. If you have received this electronic message in error, please notify the sender immediately by reply e-mail.
On Saturday, Jul 14, 2018 at 8:44 PM, Song Gao <notifications@github.com (mailto:notifications@github.com)> wrote:
This is the RPC for getting journal status. EOF almost sounds like kbfsfuse crashed?
Yeah a log send would help!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub (https://github.com/keybase/client/issues/12817#issuecomment-405059313), or mute the thread (https://github.com/notifications/unsubscribe-auth/AkjzEZRYrzty8vBpdXD-ru_n7n_Q39uLks5uGpBhgaJpZM4VP-Fq).
Sent - I don’t have an ID it looks like.
Sincerely,
Megan K. Mattimoe, J.D. Executive Director Advocating Opportunity 1119 Adams Street, Second Floor Toledo, Ohio 43604
Phone 855-855-1945, ext. 700 Fax 855-855-1945 Mobile 419-260-4217
Email mm@advocatingopportunity.com (mailto:mm@advocatingopportunity.com) Website www.advocatingopportunity.com (http://www.advocatingopportunity.com) Facebook www.facebook.com/advocatingopportunity (http://www.facebook.com/advocatingopportunity) Twitter https://twitter.com/AOAdvocate
Confidentiality Statement: This electronic message contains information from the law firm of Megan K. Mattimoe, Esq., and may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this message is prohibited. If you have received this electronic message in error, please notify the sender immediately by reply e-mail.
On Saturday, Jul 14, 2018 at 8:56 PM, Megan Mattimoe <megan.mattimoe@gmail.com (mailto:megan.mattimoe@gmail.com)> wrote: Thanks! I tried to send a log but I must have done it incorrectly. I’ll try again.
Sincerely,
Megan K. Mattimoe, J.D. Executive Director Advocating Opportunity 1119 Adams Street, Second Floor Toledo, Ohio 43604
Phone 855-855-1945, ext. 700 Fax 855-855-1945 Mobile 419-260-4217
Email mm@advocatingopportunity.com (mailto:mm@advocatingopportunity.com) Website www.advocatingopportunity.com (http://www.advocatingopportunity.com) Facebook www.facebook.com/advocatingopportunity (http://www.facebook.com/advocatingopportunity) Twitter https://twitter.com/AOAdvocate
Confidentiality Statement: This electronic message contains information from the law firm of Megan K. Mattimoe, Esq., and may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this message is prohibited. If you have received this electronic message in error, please notify the sender immediately by reply e-mail.
On Saturday, Jul 14, 2018 at 8:44 PM, Song Gao <notifications@github.com (mailto:notifications@github.com)> wrote:
This is the RPC for getting journal status. EOF almost sounds like kbfsfuse crashed?
Yeah a log send would help!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub (https://github.com/keybase/client/issues/12817#issuecomment-405059313), or mute the thread (https://github.com/notifications/unsubscribe-auth/AkjzEZRYrzty8vBpdXD-ru_n7n_Q39uLks5uGpBhgaJpZM4VP-Fq).
Logs: 89f5439ec19bb61528ab5c1c
Yeah looks like kbfsfuse is crashing. Definitely my fault:
panic: Unknown ID suffix 0
goroutine 281 [running]:
github.com/keybase/kbfs/tlf.ID.Type(0x0, 0x0, 0x0)
/Users/build/go/src/github.com/keybase/kbfs/tlf/id.go:252 +0x65
github.com/keybase/kbfs/libkbfs.buildCanonicalPathForTlf(0x0, 0x0, 0xc422dcb4f0, 0x1, 0x1, 0x1, 0x1)
/Users/build/go/src/github.com/keybase/kbfs/libkbfs/path.go:72 +0x2b
github.com/keybase/kbfs/libkbfs.path.CanonicalPathString(0x0, 0x0, 0x0, 0x0, 0xc42032a2a0, 0x1, 0x1, 0x0, 0x172650a)
/Users/build/go/src/github.com/keybase/kbfs/libkbfs/path.go:162 +0x92
github.com/keybase/kbfs/libkbfs.(*rmOp).ToEditNotification(0xc42309fba0, 0x238d, 0x2081227c, 0xed2dc9060, 0x5c57b60, 0xc42011c460, 0x46, 0xc420cfb0a0, 0x20, 0xe2408d0a017dd5e1, ...)
/Users/build/go/src/github.com/keybase/kbfs/libkbfs/ops.go:641 +0x604
github.com/keybase/kbfs/libkbfs.(*folderBranchOps).makeEditNotifications(0xc42008d400, 0x535df80, 0xc422a2a740, 0xc4202cb600, 0xc4202cccc0, 0x21, 0xc42011c460, 0x46, 0x205277f0, 0xed2dc9060, ...)
/Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:2390 +0x79f
github.com/keybase/kbfs/libkbfs.(*folderBranchOps).handleEditNotifications(0xc42008d400, 0x535df80, 0xc422a2a740, 0xc4202cb600, 0xc4202cccc0, 0x21, 0xc42011c460, 0x46, 0x205277f0, 0xed2dc9060, ...)
/Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:2406 +0xcf
github.com/keybase/kbfs/libkbfs.(*folderBranchOps).handleMDFlush(0xc42008d400, 0x535df80, 0xc422a2a740, 0x0, 0x0, 0x238d)
/Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:6576 +0x45a
github.com/keybase/kbfs/libkbfs.(*folderBranchOps).onMDFlush.func1(0xc42008d400, 0x0, 0x0, 0x238d)
/Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:6614 +0x25a
created by github.com/keybase/kbfs/libkbfs.(*folderBranchOps).onMDFlush
/Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:6603 +0x73
I'll look into it fixing it as soon as I can, Monday at the latest.
Thank you! :) I appreciate it.
Sincerely,
Megan K. Mattimoe, J.D. Executive Director Advocating Opportunity 1119 Adams Street, Second Floor Toledo, Ohio 43604
Phone 855-855-1945, ext. 700 Fax 855-855-1945 Mobile 419-260-4217
Email mm@advocatingopportunity.com (mailto:mm@advocatingopportunity.com) Website www.advocatingopportunity.com (http://www.advocatingopportunity.com) Facebook www.facebook.com/advocatingopportunity (http://www.facebook.com/advocatingopportunity) Twitter https://twitter.com/AOAdvocate
Confidentiality Statement: This electronic message contains information from the law firm of Megan K. Mattimoe, Esq., and may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this message is prohibited. If you have received this electronic message in error, please notify the sender immediately by reply e-mail.
On Saturday, Jul 14, 2018 at 9:03 PM, Jeremy Stribling <notifications@github.com (mailto:notifications@github.com)> wrote:
Yeah looks like kbfsfuse is crashing. Definitely my fault:
panic: Unknown ID suffix 0 goroutine 281 [running]: github.com/keybase/kbfs/tlf.ID.Type(0x0, 0x0, 0x0) /Users/build/go/src/github.com/keybase/kbfs/tlf/id.go:252 +0x65 github.com/keybase/kbfs/libkbfs.buildCanonicalPathForTlf(0x0, 0x0, 0xc422dcb4f0, 0x1, 0x1, 0x1, 0x1) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/path.go:72 +0x2b github.com/keybase/kbfs/libkbfs.path.CanonicalPathString(0x0, 0x0, 0x0, 0x0, 0xc42032a2a0, 0x1, 0x1, 0x0, 0x172650a) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/path.go:162 +0x92 github.com/keybase/kbfs/libkbfs.(rmOp).ToEditNotification(0xc42309fba0, 0x238d, 0x2081227c, 0xed2dc9060, 0x5c57b60, 0xc42011c460, 0x46, 0xc420cfb0a0, 0x20, 0xe2408d0a017dd5e1, ...) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/ops.go:641 +0x604 github.com/keybase/kbfs/libkbfs.(folderBranchOps).makeEditNotifications(0xc42008d400, 0x535df80, 0xc422a2a740, 0xc4202cb600, 0xc4202cccc0, 0x21, 0xc42011c460, 0x46, 0x205277f0, 0xed2dc9060, ...) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:2390 +0x79f github.com/keybase/kbfs/libkbfs.(folderBranchOps).handleEditNotifications(0xc42008d400, 0x535df80, 0xc422a2a740, 0xc4202cb600, 0xc4202cccc0, 0x21, 0xc42011c460, 0x46, 0x205277f0, 0xed2dc9060, ...) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:2406 +0xcf github.com/keybase/kbfs/libkbfs.(folderBranchOps).handleMDFlush(0xc42008d400, 0x535df80, 0xc422a2a740, 0x0, 0x0, 0x238d) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:6576 +0x45a github.com/keybase/kbfs/libkbfs.(folderBranchOps).onMDFlush.func1(0xc42008d400, 0x0, 0x0, 0x238d) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:6614 +0x25a created by github.com/keybase/kbfs/libkbfs.(folderBranchOps).onMDFlush /Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:6603 +0x73
I'll look into it fixing it as soon as I can, Monday at the latest.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub (https://github.com/keybase/client/issues/12817#issuecomment-405059953), or mute the thread (https://github.com/notifications/unsubscribe-auth/AkjzEX3ZTMvLAlDjfg5Zb6CBsavhqpPxks5uGpTOgaJpZM4VP-Fq).
I tracked this down to a bug that triggers when you remove some files and their parent directory all at once. It was possible to crash this way before, but the release this week made it more likely.
It's interesting because I think a few restarts would fix this automatically, depending on how much data was deleted. macOS restarts automatically when kbfs crashes, so it might just start working on its own eventually. But I made a build with the fix in keybase/kbfs#1677 if anyone wants to try it:
We'll have a linux release with the fix tomorrow morning.
having the same issue on Windows 10 ... log 4004979b3c52850093c4841c
thank you.
@zanderz any way we can make a Windows build available that includes KBFS commit 54e61767d0c300478925713f06c9842c8da7457a? Doesn't have to be an official release, just downloadable from somewhere.
coming here from #12845.
Installed "2.4.0-20180715192547+3ed23a5741" now. kbfs still refuses to work:
2018-07-19T16:13:01.227256+02:00 ▶ [DEBU kbfs block_retrieval_queue.go:238] 0ea Block 01765ad73a1daa1e86a9da567fc83d013273c7cd67b56a8ea1c72557009fbdbaa1 missing for disk block cache metadata update 2018-07-19T16:13:01.227327+02:00 ▶ [WARN kbfs(PRE) prefetcher.go:683] 0eb error prefetching block 01765ad73a1daa1e86a9da567fc83d013273c7cd67b56a8ea1c72557009fbdbaa1: Couldn't get block 01765ad73a1daa1e86a9da567fc83d013273c7cd67b56a8ea1c72557009fbdbaa1, canceling 2018-07-19T16:13:01.227411+02:00 ▶ [DEBU kbfs(PRE) prefetcher.go:485] 0ec nothing to cancel for block 01765ad73a1daa1e86a9da567fc83d013273c7cd67b56a8ea1c72557009fbdbaa1 2018-07-19T16:13:01.232540+02:00 ▶ [DEBU kbfs(FBO 300c6fb9) folder_branch_ops.go:1085] 0ed Identify finished successfully 2018-07-19T16:13:01.232624+02:00 ▶ [DEBU kbfs(FBO 300c6fb9) folder_branch_ops.go:759] 0ee Setting head revision to 14 2018-07-19T16:13:01.232721+02:00 ▶ [DEBU kbfs(FBO 300c6fb9) folder_branch_ops.go:5296] 0ef Updated latestMergedRevision to 11. 2018-07-19T16:13:01.239651+02:00 ▶ [DEBU kbfs(FBO 300c6fb9) folder_block_ops.go:3180] 0f0 Root node BlockPointer{ID: 015cc31d85193b16688837aea2074a9b7e0312a2d4d71fc5fb99169f3f9b54d168, KeyGen: 1, DataVer: 1, Context: Context{Creator: d35948ced477173ae615ef3fe974c000}, DirectType: direct} doesn't exist in the node cache; using a throwaway node cache instead panic: Unknown ID suffix 0
goroutine 334 [running]: github.com/keybase/kbfs/tlf.ID.Type(0x0, 0x0, 0x0) /Users/build/go/src/github.com/keybase/kbfs/tlf/id.go:252 +0x65 github.com/keybase/kbfs/libkbfs.buildCanonicalPathForTlf(0x0, 0x0, 0xc423de8e28, 0x1, 0x1, 0x1, 0x1) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/path.go:72 +0x2b github.com/keybase/kbfs/libkbfs.path.CanonicalPathString(0x0, 0x0, 0x0, 0x0, 0xc4202e64d0, 0x1, 0x1, 0x0, 0x46) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/path.go:162 +0x92 github.com/keybase/kbfs/libkbfs.(renameOp).ToEditNotification(0xc42056d200, 0xc, 0xb8ebb2d, 0xed2e03565, 0x5c60b60, 0xc4202d8460, 0x46, 0xc42019fee0, 0x20, 0x28926154b96f0c30, ...) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/ops.go:789 +0xa57 github.com/keybase/kbfs/libkbfs.(folderBranchOps).makeEditNotifications(0xc420248c00, 0x5364a80, 0xc420d5a840, 0xc420786c00, 0xc423ddeba0, 0x21, 0xc4202d8460, 0x46, 0xb7812cc, 0xed2e03565, ...) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:2389 +0x6e6 github.com/keybase/kbfs/libkbfs.(folderBranchOps).handleUnflushedEditNotifications(0xc420248c00, 0x5364a80, 0xc420d5a840, 0xc420786c00, 0xc423ddeba0, 0x21, 0xc4202d8460, 0x46, 0xb7812cc, 0xed2e03565, ...) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:2426 +0xca github.com/keybase/kbfs/libkbfs.(folderBranchOps).setHeadLocked(0xc420248c00, 0x5364a80, 0xc420d5a840, 0xc42047de50, 0xc42380e200, 0xc42002aba0, 0x21, 0xc4202d8460, 0x46, 0x1d0570d3, ...) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:817 +0xb0d github.com/keybase/kbfs/libkbfs.(folderBranchOps).setInitialHeadTrustedLocked(0xc420248c00, 0x5364a80, 0xc420d5a840, 0xc420c5fe50, 0xc42380e200, 0xc42002aba0, 0x21, 0xc4202d8460, 0x46, 0x1d0570d3, ...) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:924 +0x16f github.com/keybase/kbfs/libkbfs.(folderBranchOps).SetInitialHeadFromServer.func2(0x0, 0x0) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/folder_branch_ops.go:1763 +0x5d8 github.com/keybase/kbfs/libkbfs.runUnlessCanceled.func1(0xc420624000, 0xc42051a680) /Users/build/go/src/github.com/keybase/kbfs/libkbfs/util.go:28 +0x27 created by github.com/keybase/kbfs/libkbfs.runUnlessCanceled /Users/build/go/src/github.com/keybase/kbfs/libkbfs/util.go:27 +0x77
Full log uploaded to log id f3e69569511d7debeeb5301c
@leitmedium thanks, your crash looks slightly different. I will find time later today to debug it and get a new fix out. Sorry for the trouble.
@leitmedium I have a new test build up that should fix your problem: https://s3.amazonaws.com/prerelease.keybase.io/darwin-test/Keybase-2.4.0-20180719225238%2B67ef6ce70a.dmg
If you're willing to try another experiment build, let me know whether it helps. Thanks!
@k2s There is now a Windows test build containing proposed fixes, if you would care to try: https://prerelease.keybase.io/windows/Keybase_2.4.0-20180719162747%2B67ef6ce70a.386.msi
@zanderz I installed the test version on Windows. keybase status
shows now that service is running and disk should be available at k:.
But it is not and I see in kbfs error log message panic: Unknown ID suffix 0
.
log: 0fc806a85735321142110a1c
@k2s ugh this is a slightly different crash from the other ones I've seen in this issue. I'll work on a fix, but probably not until Monday, sorry.
@strib this is first time I have any issue with Keybase. hope you will find fix, but no stress. thank you.
What is the solution to this problem, as the first steps are correct? git commit -m "moe atext file" The identity of the author is unknown
*** Please tell me who you are.
He runs
git config - global user.email "you@example.com"
git config --global user.name "your name"
To set the default identity for your account. delete -global to set the identity only in this repository.
Fatal: Unable to automatically detect email address (I got "madyy2010@DESKTOP-5NT0ESD. (None)")
Me? This was fixed in 2018 Also, idk what you mean who am I? My name is in my email and in my username. While I suppose I could answer existentially, we just met - it’s a bit early for that.
On Sun, Mar 6, 2022 at 3:02 PM mod2010 @.***> wrote:
What is the solution to this problem, as the first steps are correct? git commit -m "moe atext file" The identity of the author is unknown
*** Please tell me who you are.
He runs
git config - global user.email @.***" git config --global user.name "your name"
To set the default identity for your account. delete -global to set the identity only in this repository.
Fatal: Unable to automatically detect email address (I got @.*** (None)")
— Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/12817#issuecomment-1060029767, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJEPGEOFQ33OYPMIKFMZ5KLU6UFPBANCNFSM4FJ74FVA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
-- Sincerely,
Megan K. Mattimoe, J.D. Executive Director Advocating Opportunity 1119 Adams Street, Second Floor Toledo, Ohio 43604
Pronouns: She/Her/Hers
Phone 855-855-1945, ext. 700 Fax 855-855-1945 Mobile 419-260-4217
Email @.*** Website www.advocatingopportunity.com Facebook www.facebook.com/advocatingopportunity Twitter https://twitter.com/AOAdvocate
The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message and any copy of it from your computer system.
What is the solution to this problem, as the first steps are correct?
remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead. remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information. fatal: Authentication failed for 'https://github.com/mod2010/mm1.git/'
Keybase GUI Version: 2.3.0-20180710171051+64615d6258
I keep getting error messages and cannot delete files