That did it. Thanks!
On Wednesday, August 17, 2016 at 10:50:48 PM UTC-7, curtis wrote:
>
> Did you delete the ~silmud-rampel directory completely before running
> with the correct ticket? I would try that. I don't think you have a
> planet at all here.
>
> On Thu, Aug 18, 2016 at 12:48 AM, Nathan <frogo...@gmail.com <javascript:>>
> wrote:
> > After doing `git pull && curl -o … && make clean && make distclean &&
> make`
> > (although not all in one go) I got a working comet that's able to
> connect to
> > ~binzod/urbit-meta, but my planet is still not right yet. Here's what it
> > says this time:
> >
> > $ bin/urbit silmud-rampel/
> >
> > ~
> >
> > urbit: home is silmud-rampel
> >
> > loom: mapped 2048MB
> >
> > _ce_patch_apply
> >
> > _ce_image_sync
> >
> > _ce_patch_delete
> >
> > _ce_patch_free
> >
> > protected loom
> >
> > live: loaded: MB/68.534.272
> >
> > boot: installed 237 jets
> >
> > arvo: time: ~2016.8.18..04.29.42..91ce
> >
> > rest: checkpoint to event 2.000
> >
> > rest: old 0v16.42if7, new 0va.5l7ei
> >
> > loaded passcode from silmud-rampel/.urb/code.~novser-motnup
> >
> >
> > ---------------- playback complete----------------
> >
> > ames: on localhost, UDP 61670.
> >
> > http: live (insecure, public) on 8082
> >
> > http: live ("secure", public) on 8444
> >
> > http: live (insecure, loopback) on 12322
> >
> > ames: czar zod.urbit.org: ip .104.197.214.171
> >
> >
> > This one might be a little weird, though — when I first tried to use the
> > ticket I forgot the -t:
> >
> >
> > $ bin/urbit -w silmud-rampel zugzug-zugzug-zugzug-zugzug
> >
> > your ticket: ~zugzug-zugzug-zugzug-zugzug
> >
> > ~
> >
> > urbit: home is zugzug-zugzug-zugzug-zugzug
> >
> > loom: mapped 2048MB
> >
> > boot: installed 216 jets
> >
> > boot: loading ./urbit.pill
> >
> > arvo: time: ~2016.8.17..18.25.28..f712
> >
> > generating 2048-bit RSA pair...
> >
> > cp ./urbit.pill zugzug-zugzug-zugzug-zugzug/.urb
> >
> > saving passcode in zugzug-zugzug-zugzug-zugzug/.urb/code.~ropryp-dilnut
> >
> > (for real security, write it down and delete the file...)
> >
> > ames: czar zod.urbit.org: ip .104.197.214.171
> >
> > ames: on localhost, UDP 49878.
> >
> > http: live (insecure, public) on 8081
> >
> > http: live ("secure", public) on 8443
> >
> > http: live (insecure, loopback) on 12321
> >
> >>> [%mo-not-running %hood %poke]
> >
> > ; ~zod not responding still trying
> >
> > <awaiting hood, this may take a few minutes>
> >
> > interrupt
> >
> >
> > I've since run bin/urbit -w silmud-rampel -t
> zugzug-zugzug-zugzug-zugzug,
> > but now after doing the remake and pill curl a session looks like:
> >
> >
> > $ bin/urbit silmud-rampel/
> >
> > ~
> >
> > urbit: home is silmud-rampel
> >
> > loom: mapped 2048MB
> >
> > _ce_patch_apply
> >
> > _ce_image_sync
> >
> > _ce_patch_delete
> >
> > _ce_patch_free
> >
> > protected loom
> >
> > live: loaded: MB/68.534.272
> >
> > boot: installed 237 jets
> >
> > arvo: time: ~2016.8.18..04.29.42..91ce
> >
> > rest: checkpoint to event 2.000
> >
> > rest: old 0v16.42if7, new 0va.5l7ei
> >
> > loaded passcode from silmud-rampel/.urb/code.~novser-motnup
> >
> >
> > ---------------- playback complete----------------
> >
> > ames: on localhost, UDP 61670.
> >
> > http: live (insecure, public) on 8082
> >
> > http: live ("secure", public) on 8444
> >
> > http: live (insecure, loopback) on 12322
> >
> > ames: czar zod.urbit.org: ip .104.197.214.171
> >
> >
> > Activity Monitor says this urbit process is using teeny amounts of CPU
> time
> > and occasionally sending packets — unlike my comet that I created just
> now
> > that connected to urbit-meta.
> >
> >
> > What should I do now?
> >
> >
> >
> > On Tuesday, August 16, 2016 at 9:13:10 PM UTC-7, Galen Wolfe-Pauly
> wrote:
> >>
> >> Network is up, and people seem to be able to join.
> >>
> >> Do you have a fresh pill and fresh build?
> >>
> >>
> >> On Aug 16, 2016, at 8:51 PM, Silas Snider <swsn...@gmail.com> wrote:
> >>
> >> This is happening for me right now. Is the network still down?
> >>
> >> On Sunday, August 14, 2016 at 9:28:43 AM UTC-7, philip.monk wrote:
> >>>
> >>> Sorry, I'm on mobile.
> >>>
> >>> I was planning on not restarting, though we might reset the womb
> state. I
> >>> suspect we won't do that either, though.
> >>>
> >>>
> >>> On Aug 14, 2016 9:26 AM, "Raymond Pasco" <r...@the.ug> wrote:
> >>>>
> >>>> Ah, I assume it’s actually https://bootstrap.urbit.org/staging3.pill
> :)
> >>>> - and not yet! Do you plan on changing the protocol version,
> restarting with
> >>>> the same protocol version, or not restarting?
> >>>> >
> >>>> > On Aug 14, 2016, at 12:23 PM, Philip Monk <phili...@tlon.io>
> wrote:
> >>>> >
> >>>> > That's actually https://bootstrap.urbit.org/stahing3.pill. Also,
> did
> >>>> > we merge the staging branches into master yet?
> >>>> >
> >>>> >
> >>>> > On Aug 14, 2016 9:10 AM, "Raymond Pasco" <r...@the.ug> wrote:
> >>>> > If you want to help us with some last-minute testing, you can boot
> a
> >>>> > comet or fakezod if you use
> https://bootstrap.urbit.org/staging-3.pill
> >>>> > rather than latest. Let us know how it works!
> >>>> >
> >>>> > On August 14, 2016 3:38:55 AM EDT, Zach Gotsch <orbi...@gmail.com>
> >>>> > wrote:
> >>>> > Ack I saw that restart was delayed until Monday but I thought
> things
> >>>> > were up in the meantime. My bad.
> >>>> >
> >>>> > On Saturday, August 13, 2016 at 9:53:32 PM UTC-7, curtis wrote:
> >>>> > Sorry, the network is off until Monday -- we're upgrading the
> servers
> >>>> > to the new crypto and no one is around to keep it on.
> >>>> >
> >>>> > On Sat, Aug 13, 2016 at 11:33 PM, Zach Gotsch <orbi...@gmail.com>
> >>>> > wrote:
> >>>> > > I can see UDP packets going out but nothing coming back.
> >>>> > >
> >>>> > > zod.urbit.org web server seems to be up.
> >>>> > >
> >>>> > > If I tcpdump on my router, I don't see anything from ~zod, so I
> >>>> > > don't think
> >>>> > > it is some sort of NAT issue.
> >>>> > >
> >>>> > > Any debug tips?
> >>>> > >
> >>>> > > -Zach (hopefully soon ~noclec-talren)
> >>>> > >
> >>>> > > --
> >>>> > > 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 urbi...@googlegroups.com.
> >>>> > > For more options, visit https://groups.google.com/d/optout.
> >>>> >
> >>>> >
> >>>> > --
> >>>> > Sent from my Android device with K-9 Mail. Please excuse my
> brevity.
> >>>> >
> >>>> > --
> >>>> > 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 urbi...@googlegroups.com.
> >>>> > 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 urbi...@googlegroups.com.
> >> 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 <javascript:>.
> > To post to this group, send email to urbi...@googlegroups.com
> <javascript:>.
> > 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+unsubscr...@googlegroups.com.
To post to this group, send email to urbit-dev@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
