Major Site Upgrade

[Mike Bobbitt]

I know it's been a frustrating few [days|weeks|months] however we are making progress, slowly. I'm optimistic that early this morning we managed another improvement, hopefully folks will be able to get on as a general rule instead of having to wait for the server load to go down.

 

[Edward Campbell]

Mike, we are all damned grateful for all that you do for us. 

 

[GAP]

Mike, we are all damned grateful for all that you do for us. 

:ditto:

 

[Scott]

<another reminder that subscriptions, swag purchases, and donations help>

 

[Mike Bobbitt]

System Load is High: 30.07

Back to the drawing board I guess...

 

[Scott]

Maybe you changed permissions? I am not seeing the warning. Though the reply screen is taking a bit longer to load...

FYI, I did notice a difference once you took down the goddamned Christmas lights ;D

 

[Mike Bobbitt]

It spiked up to 30 and is now back down to <1 (where it should be). Sill seems an improvement, where we were often sitting around 15-30 and frequently spiking to 100+ which triggered a site cooldown (shut down until we got back down to a load of 3 or less).

 

[Edward Campbell]

All that being said, I like the new NEW buttons.

 

[Mike Bobbitt]

All that being said, I like the new NEW buttons.

Now that the server crisis is behind us*, I figured it was time to tackle some of the long-standing critical items.

Chat is also working better (and green), with more site changes on the way.

* One more change this morning to help, overall server performance is much improved.

 

[Mike Bobbitt]

As an addendum, I almost went with the icon below, to make it clear that clicking on the "NEW" image brings you to the first unread post.  ^-^

 

[Loachman]

Right now, I can get into Navy.ca, but not Army.ca - and I do not particularly care for bodies of water bigger or colder than a hot tub.

 

[Mike Bobbitt]

Try https://army.ca instead of http://army.ca

The secure site works fine, I'll check into why the plaintext version is freaking out

 

[Loachman]

It does, yes. Thanks, Mike.

 

[Mike Bobbitt]

I've also redirected http to https for now, to reduce the impact to users. There may be a few brief outages while I try to track the source.

 

[Loachman]

https Army.ca no longer works for me, http Navy.ca still does.

Do you still have any hair left, Mike?

 

[dapaterson]

Same here - Navy.ca works - though I get a certificate error; army.ca presents a blank screen - not even an error.

 

[Mike Bobbitt]

https Army.ca no longer works for me, http Navy.ca still does.

Do you still have any hair left, Mike?

Still do, somehow, but it's turning 'arctic blonde' rapidly.

Because I jinxed it by saying "the server crisis is behind us" this morning, the server wanted my attention for the evening. Not being game for that, I decided that a good old fashioned database rebuild, software wipe and cold shutdown was a fitting response.

And here we are, so server 0, Mike 1.

It's your move, server.

 

[dapaterson]

And here we are, so server 0, Mike 1.

It's your move, server.

I know!  Let's start a discussion that gets put on the front page of Slashdot!

 

[Loachman]

I see soothing green again...

Danke.

 

[George Wallace]

Try https://army.ca instead of http://army.ca

The secure site works fine, I'll check into why the plaintext version is freaking out

I am finding that the opposite is true for all my pages, except:

https://army.ca/forums/index.php?action=recent;start=0

Even when I delete the "s" in the https, it automatically resets to https and I can not access the first page of the recent posts.

If I go to    http://army.ca/forums/index.php?action=recent    I have no problem.