Discussion:
[urbit] Exploded Planet
Nik Black
2015-09-26 17:30:36 UTC
Permalink
Howdy. My planet exploded. I'm fairly sure I didn't try to run it
concurrently with itself. I ^\'d because I needed port 8080 temporarily,
and when I tried to bring ~mocsyl-locfel back up, I got this error:

~
urbit: home is mocsyl-locfel
loom: mapped 2048MB
protected loom
live: loaded: MB/132.726.784
boot: installed 229 jets
arvo: time: ~2015.9.26..17.26.19..1410
rest: checkpoint to event 30.705
rest: old 0vl.7jc11, new 0v1t.q9n89
loaded passcode from mocsyl-locfel/.urb/code.~harfep-lagtyr
record (mocsyl-locfel/.urb/egz.hope) is corrupt (j)
​​

I've sent the corpse of ~mocsyl-locfel to Curtis.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Philip Monk
2015-09-26 18:34:38 UTC
Permalink
Your event log is corrupted, so your planet is definitely exploded. This
happens very rarely, but it does seem to still happen occasionally. The
general solution is probably something more industrial-strength than a hard
drive (there's some Kafka code written that supposedly works, but isn't on
master). It seems like our hard drive code should work a little better
than it does, though.
Post by Nik Black
Howdy. My planet exploded. I'm fairly sure I didn't try to run it
concurrently with itself. I ^\'d because I needed port 8080 temporarily,
~
urbit: home is mocsyl-locfel
loom: mapped 2048MB
protected loom
live: loaded: MB/132.726.784
boot: installed 229 jets
arvo: time: ~2015.9.26..17.26.19..1410
rest: checkpoint to event 30.705
rest: old 0vl.7jc11, new 0v1t.q9n89
loaded passcode from mocsyl-locfel/.urb/code.~harfep-lagtyr
record (mocsyl-locfel/.urb/egz.hope) is corrupt (j)
​​
I've sent the corpse of ~mocsyl-locfel to Curtis.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Curtis Yarvin
2015-09-26 18:36:13 UTC
Permalink
Yup, let us know if you need another. Sorry. Getting fsync right is hard! What platform was this on?

Sent from my iPhone
Your event log is corrupted, so your planet is definitely exploded. This happens very rarely, but it does seem to still happen occasionally. The general solution is probably something more industrial-strength than a hard drive (there's some Kafka code written that supposedly works, but isn't on master). It seems like our hard drive code should work a little better than it does, though.
Post by Nik Black
~
urbit: home is mocsyl-locfel
loom: mapped 2048MB
protected loom
live: loaded: MB/132.726.784
boot: installed 229 jets
arvo: time: ~2015.9.26..17.26.19..1410
rest: checkpoint to event 30.705
rest: old 0vl.7jc11, new 0v1t.q9n89
loaded passcode from mocsyl-locfel/.urb/code.~harfep-lagtyr
record (mocsyl-locfel/.urb/egz.hope) is corrupt (j)
​​
I've sent the corpse of ~mocsyl-locfel to Curtis.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Nik Black
2015-09-26 19:01:17 UTC
Permalink
I don't need any more tickets. I still have some extras. This was on a
linux machine (Gentoo specifically).
Post by Curtis Yarvin
Yup, let us know if you need another. Sorry. Getting fsync right is
hard! What platform was this on?
Sent from my iPhone
Your event log is corrupted, so your planet is definitely exploded. This
happens very rarely, but it does seem to still happen occasionally. The
general solution is probably something more industrial-strength than a hard
drive (there's some Kafka code written that supposedly works, but isn't on
master). It seems like our hard drive code should work a little better
than it does, though.
Post by Nik Black
Howdy. My planet exploded. I'm fairly sure I didn't try to run it
concurrently with itself. I ^\'d because I needed port 8080 temporarily,
~
urbit: home is mocsyl-locfel
loom: mapped 2048MB
protected loom
live: loaded: MB/132.726.784
boot: installed 229 jets
arvo: time: ~2015.9.26..17.26.19..1410
rest: checkpoint to event 30.705
rest: old 0vl.7jc11, new 0v1t.q9n89
loaded passcode from mocsyl-locfel/.urb/code.~harfep-lagtyr
record (mocsyl-locfel/.urb/egz.hope) is corrupt (j)
​​
I've sent the corpse of ~mocsyl-locfel to Curtis.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to urbit-dev+***@googlegroups.com.
To post to this group, send email to urbit-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...