i kicked the service. again. and jenkins seems happy for now. nothing has changed (system config, packages, etc) on the master node. i'll dive in to this tomorrow morning.
On Sun, Mar 17, 2019 at 9:46 AM Sean Owen <sro...@gmail.com> wrote: > It's wedged against since this morning. Something's clearly gone > wrong-er than usual; any recent changes that could be a culprit? > > On Fri, Mar 15, 2019 at 12:08 PM shane knapp <skn...@berkeley.edu> wrote: > > > > well, that box rebooted in record time! we're back up and building. > > > > and as always, i'll keep a close eye on things today... jenkins usually > works great, until it doesn't. :\ > > > > On Fri, Mar 15, 2019 at 9:52 AM shane knapp <skn...@berkeley.edu> wrote: > >> > >> as some of you may have noticed, jenkins got itself in a bad state > multiple times over the past couple of weeks. usually restarting the > service is sufficient, but it appears that i need to hit it w/the reboot > hammer. > >> > >> jenkins will be down for the next 20-30 minutes as the node reboots and > jenkins spins back up. i'll reply here w/any updates. > >> > >> shane > >> -- > >> Shane Knapp > >> UC Berkeley EECS Research / RISELab Staff Technical Lead > >> https://rise.cs.berkeley.edu > > > > > > > > -- > > Shane Knapp > > UC Berkeley EECS Research / RISELab Staff Technical Lead > > https://rise.cs.berkeley.edu > -- Shane Knapp UC Berkeley EECS Research / RISELab Staff Technical Lead https://rise.cs.berkeley.edu
