The Forum Is Wonky

[Jerod Broussard]

Testing

[Jerod Broussard]

Gotta come back to see posting. Page cancels out when you post.

[Panhead John]

This is the worst I’ve ever seen the forum. It takes many attempts to try and see anything. And when you can, it takes forever to see the page.

[DaveD]

Totally hosed for me all day. This is the first time I have had any page respond instead the "the server is too busy, try later" message.

[Alan Brice]

I got this msg several times trying to post my "mea culpa" at 3:30am ish, so I knew it was the BBQ gods trying to change my mind.

[Panhead John]

I’ve been getting this also…..

[DaveD]

Got one of those as well.

[RiverJeff]

I got that

[Alan Brice]

Me thinks you need more mammary.

[JCBBQ]

Back in business!! Phew!

[DaveD]

I lol'd!

[RichieB]

Dare I say it's back to operational?

[RiverJeff]

I was so worried I thought the mother was coming for me!

[Carolyn]

Same here. Obviously, I can post now, since I am posting right now. 😁

[DaveD]

Ah, a fellow member of the Deparment of Redundancy Department, I see.

[Ace]

I fell asleep waiting for it to load... When I woke up it was still broke. I must have been dreaming.

[ComfortablyNumb]

I was in Spokane yesterday. I would have let you know, but, well, the server was busy.

[DavidNorcross]

I had the message this morning. Seems to be working fine now.

[SheilaAnn]

7:58 pm pst and it’s all good here. Granted, this is the first time I’ve been in the pit all day.

[RAYMBO]

I have checked the server. It is working fine as of now. But it was overloaded for at least 14 hours yesterday.

8a to midnight. CPU, Disk, and Network all heavily loaded.



I have more than a few alert systems and did not get a single notification. I will have to double check the alert systems. As this started before 8a (central) and I am still up at that time (8p for me).

Since the network (IPv4) was also high, this was some kind of DOS attack. If it were an internal issue (server or the forums scripts), the IPv4 would not also match the heavy loading.

[Panhead John]

You need to give us your phone number so we can just call you next time…..🥸

[Smoker_Boy]

Seems like it's only on the paid log in side. I went to the free side and that seems to be working. Maybe a backup in progress?

Glad we pay for this.

[RAYMBO]

Seems like it's only on the paid log in side. I went to the free side and that seems to be working. Maybe a backup in progress?

Good call. That was exactly it. But with a catch.

I recently tweaked the caching settings on the forum (to try to fix another issue).

That cause the cache table to explode to 72GB. Normally the database dump is 3GB.

So, the server got overloaded trying to dump and compress a 75GB db dump file.

I have restored the cache settings. I will be keeping an eye on the backups and the cache table.

[Alan Brice]

Ray J you are the whip that drives the team, thanks.

[Huskee]

I was gonna suggest exactly that. (Lol, no I wasn't )

[Michael_in_TX]

I have a web app background. 72 GB cache table? Ouchy! I've had cache tables go haywire on some sites from time to time....but I don't think I ever had one more than 10 GB (which is still ridiculous)!

[Ace]

Good call. That was exactly it. But with a catch.

I recently tweaked the caching settings on the forum (to try to fix another issue).

That cause the cache table to explode to 72GB. Normally the database dump is 3GB.

So, the server got overloaded trying to dump and compress a 75GB db dump file.

I have restored the cache settings. I will be keeping an eye on the backups and the cache table.

@raywjohnson Thank you for all you do and for keeping this site on the rails.