Urbit: code 32000

[custom-jonathan]

Just received this amongst a slew of "still trying/ok" messages:

[%error-results i=[id='logs by hash' code='-32000' message='unknown block'] t=~]

[custom-jonathan]

Including this screen shot in case it's all related:

[custom-jonathan]

And my ship has been randomly becoming unresponsive. Can't switch between dojo or chat. I'll only be aware of it when I try to refresh my landscape and it sits on "thinking." I'll ssh into my droplet, and I can't do anything after reattaching to my screen. I'll ctl+z 2x to slam the ship down, and restart it.

Don't know if these should all go in separate issues, or if they're multiple symptoms of the same problem.

[philipcmonk]

The error-results printf is harmless, silenced on master, will go out in the next OTA (probably tonight ?).

The not-responding/is ok is probably #2071, which should also go out in the next OTA.  I had this on ~wicdev and deployed that and it fixed it.

The hanging is one @joemfb is tracking down.  The first step is getting debug symbols into the build, which is... you guessed it, in the next update (not OTA because it's an update to the interpreter, so it'll be 0.10.2).

On Thu, Dec 12, 2019 at 11:47 AM, custom-jonathan < [email protected] > wrote:

And my ship has been randomly becoming unresponsive. Can't switch between
dojo or chat. I'll only be aware of it when I try to refresh my landscape
and it sits on "thinking." I'll ssh into my droplet, and I can't do
anything after reattaching to my screen. I'll ctl+z 2x to slam the ship
down, and restart it.

Don't know if these should all go in separate issues, or if they're
multiple symptoms of the same problem.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (
https://github.com/urbit/urbit/issues/2088?email_source=notifications&email_token=ABKLYGH6QQAG36HALUXSLHDQYKINHA5CNFSM4J2C6BVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGXZ4QY#issuecomment-565157443
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/ABKLYGA5TNMWWPQHZ6ZBOQLQYKINHANCNFSM4J2C6BVA
).

[joemfb]

The hanging (or at least some of it) should be fixed by #2069, which will be in the next update.

[custom-jonathan]

Trying intensifies.

[philipcmonk]

Hasn't gone out yet, I'm hoping to push it out tonight

On Fri, Dec 13, 2019 at 10:13 AM, custom-jonathan < [email protected] > wrote:

Still getting the slew of ok/still trying. Did the OTA go out and I'm
missing it from my star?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (
https://github.com/urbit/urbit/issues/2088?email_source=notifications&email_token=ABKLYGF63BTVA7GWMW4XDALQYPGF5A5CNFSM4J2C6BVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG2ZMXA#issuecomment-565548636
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/ABKLYGAC4M7M357C2IRKVKDQYPGF5ANCNFSM4J2C6BVA
).

[custom-jonathan]

Got the update on ~minder-folden & ~talleg-botsug. Both have the .of4bg hash but ~minder is still getting this kind of stuff after I turned it off & back on again:

[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
; ~talleg-botsug not responding still trying
; ~talleg-botsug is ok
; ~novlud-padtyv not responding still trying
; ~novlud-padtyv is ok
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
ames: strange wake queue, expected 47, got [message-num=46 fragment-num=406]
; ~talleg-botsug not responding still trying
; ~talleg-botsug is ok

[philipcmonk]

The %received-event error is unusual, but just means there's a garbage subscription still around.  Harmless.

The "strange wake" notification indicates we still had something in our packet queue after it had already been acknowledged.  @belisarius, we need to isolate what causes this.  Regardless, that printf indicates it's repairing the state, so it shouldn't be a problem.

On Fri, Dec 13, 2019 at 7:42 PM, custom-jonathan < [email protected] > wrote:

Got the update on ~minder-folden & ~talleg-botsug. Both have the .of4bg
hash but ~minder is still getting this kind of stuff:

[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e'] ;
~talleg-botsug not responding still trying ; ~talleg-botsug is ok ;
~novlud-padtyv not responding still trying ; ~novlud-padtyv is ok
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e']
[%received-event-for-nonexistent-channel '1575514789219-0aa53e'] ames:
strange wake queue, expected 47, got [message-num=46 fragment-num=406] ;
~talleg-botsug not responding still trying ; ~talleg-botsug is ok

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (
https://github.com/urbit/urbit/issues/2088?email_source=notifications&email_token=ABKLYGBGBCX26P7ERZTJPWTQYRI2VA5CNFSM4J2C6BVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG3ZEWQ#issuecomment-565678682
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/ABKLYGES2N4UKNCSLBBN6ODQYRI2VANCNFSM4J2C6BVA
).

[custom-jonathan]

With #2098 we can turn off the %received-event notifications with |knob? Do we have to %hush the whole alert? Or just use %received-event? I've tried 'em both and I'm still getting alert after alert in my client.

[philipcmonk]

With #2098, you will be able to run |knob %eyre-no-channel %hush to silence it. However, it hasn't been deployed yet.