[QUOTE=mdettweiler;278486]Everything's working fine for me right now--I can load all of the web pages, and my clients on ports 9000, 1400, and 13000 are getting through as well. :huh:[/QUOTE]


Yes it seems to work now. :smile: Strange but good.


Lennart

[QUOTE=Lennart;278485]Is it only me who can't reach any servers ?[/QUOTE]
Don't feel too bad.
From where I am sitting I can barely reach my own server.
stretching ... stretching ... got it.
j/k

That was just me being incredibly lazy. My chair is on castors. :smile:

[url]http://noprimeleftbehind.net:1400/all.html[/url] does not respond for me, but [url]http://nplb-gb1.no-ip.org:1400/all.html[/url] does. Is something wrong with the NPLB domain?

Seconded to Mini-Geek (ie. it's not just him.)

Ah yes...it seems Gary's IP address changed again. I went into the DNS settings and updated the IP--should be all set within an hour or so when the changes farm out to various DNS servers worldwide. :smile:

The server has been down for the past hour.

[QUOTE=Oddball;280992]The server has been down for the past hour.[/QUOTE]

And it's still down. Not just the NPLB domain either, this time. :yucky:
Unfortunately, all of my fallback servers were hosted at NPLB, as well, so I've got 6+ hours of idle time. Are there any active public PRPnet servers hosted elsewhere for such an occasion?

I'm very sorry guys. My buddy knocked the downstairs plug out of the wall that controls the internet, phone, and cable when bringing up the XMAS tree early this afternoon. Unfortunately I've been out all day and just now noticed it. Needless to say, it's plugged back in now.

Santa's little helper has been a very naughty boy.
1 lump of charcoal for him.
Ho! Ho! Ho!
:razz:

j/k.
The holiday season involves a lot of activities that do not occur throughout the rest of the year.
In terms of process analysis, control and quality, Deming called these Uncontrolled Factors 'special causes'.
In simpler terms, 'Stuff happens that you can't control' ... AND ... your buddy is 'special' :P
Situation normal. No big deal. :)

Max contacted me about the database using much more CPU than usual.
I investigated and found a mysql maintenance process was thrashing the database, RAM and HDD, and it had been doing so for quite some time.
The system was in such a tight loop that we could not get a lock on the mysql log file.

The maintenance process is the database log file rotate process and it was creating a new log file every millisecond or so pushing HDD I/O to about 97% and causing a couple of other system logs to fill up.

I have executed the mysql restart command but it is taking some time to bring the database down before it can be restarted.

I'll keep you informed.

The database is restarted.
The rogue process is gone.
The HDD i/o is back to normal.
The database is responding to PRPNet requests.