Discussion:
source.squeak.org down [EOM]
(too old to reply)
Fabio Niephaus
2016-10-26 13:11:14 UTC
Permalink
Chris Muller
2016-10-26 15:49:35 UTC
Permalink
Just saw this and checked, it's up. Nothing in the logs, however,
daemontools says its only been up for 9200 seconds, which corresponds
to the time of your mail. Very strange.. Not sure if someone shut it
down or something else..

On Wed, Oct 26, 2016 at 8:11 AM, Fabio Niephaus <***@fniephaus.com> wrote:
Fabio Niephaus
2016-10-26 16:00:22 UTC
Permalink
Post by Chris Muller
Just saw this and checked, it's up. Nothing in the logs, however,
daemontools says its only been up for 9200 seconds, which corresponds
to the time of your mail. Very strange.. Not sure if someone shut it
down or something else..
Tobias apparently logged into the machine and saw the process hanging at
100% CPU. He decided to kill it after a few minutes and then it must have
restarted automatically.
But thanks for looking into this.
Chris Muller
2016-10-26 17:08:57 UTC
Permalink
Whoa, please don't kill the process! It isn't hung, its building the
historical index. It will be using 100% CPU for the next few weeks.
Performance will be slightly degraded until then but the system should
be accessible. Thanks for your patience, it will be worth it -- at
the end we'll finally have a permanently integrated MC history for
every method and class definition.
Post by Fabio Niephaus
Post by Chris Muller
Just saw this and checked, it's up. Nothing in the logs, however,
daemontools says its only been up for 9200 seconds, which corresponds
to the time of your mail. Very strange.. Not sure if someone shut it
down or something else..
Tobias apparently logged into the machine and saw the process hanging at
100% CPU. He decided to kill it after a few minutes and then it must have
restarted automatically.
But thanks for looking into this.
Tobias Pape
2016-10-26 18:45:54 UTC
Permalink
Post by Chris Muller
Whoa, please don't kill the process!
mkay.
Tobias Pape
2016-10-26 18:51:57 UTC
Permalink
Post by Chris Muller
Whoa, please don't kill the process! It isn't hung, its building the
historical index. It will be using 100% CPU for the next few weeks.
Performance will be slightly degraded until then but the system should
be accessible. Thanks for your patience, it will be worth it -- at
the end we'll finally have a permanently integrated MC history for
every method and class definition.
please note that the machine(s) need a restart very soon to upgrade its kernel
(viz. patch a recent severe security hole)

Best regards
-Tobias
Post by Chris Muller
Post by Fabio Niephaus
Post by Chris Muller
Just saw this and checked, it's up. Nothing in the logs, however,
daemontools says its only been up for 9200 seconds, which corresponds
to the time of your mail. Very strange.. Not sure if someone shut it
down or something else..
Tobias apparently logged into the machine and saw the process hanging at
100% CPU. He decided to kill it after a few minutes and then it must have
restarted automatically.
But thanks for looking into this.
Chris Muller
2016-10-26 18:55:39 UTC
Permalink
Okay, it shoudn't be a problem, thanks for the note.
Post by Tobias Pape
Post by Chris Muller
Whoa, please don't kill the process! It isn't hung, its building the
historical index. It will be using 100% CPU for the next few weeks.
Performance will be slightly degraded until then but the system should
be accessible. Thanks for your patience, it will be worth it -- at
the end we'll finally have a permanently integrated MC history for
every method and class definition.
please note that the machine(s) need a restart very soon to upgrade its kernel
(viz. patch a recent severe security hole)
Best regards
-Tobias
Post by Chris Muller
Post by Fabio Niephaus
Post by Chris Muller
Just saw this and checked, it's up. Nothing in the logs, however,
daemontools says its only been up for 9200 seconds, which corresponds
to the time of your mail. Very strange.. Not sure if someone shut it
down or something else..
Tobias apparently logged into the machine and saw the process hanging at
100% CPU. He decided to kill it after a few minutes and then it must have
restarted automatically.
But thanks for looking into this.
Continue reading on narkive:
Loading...