I experienced that a few days ago.

I'm not sure if it's another database error or something else.

Thank you for answering that, Servus and Iuvenalis.

Dear Mater,

Thank you for answering my question.

God Bless you, Mater.

Yours, Sede Catholic.

I wrote a detailed letter to my webhost's tech support, trying to help them track down the problem.

I don't know how much progress they're making, however.

I wrote a detailed letter to my webhost's tech support, trying to help them track down the problem.

I don't know how much progress they're making, however.

Dear Matthew,

Thank you for answering my question.

It does not bother me so much, now that I know other people get it too!!!!!!

I thought it could be just me.

Anyway, hopefully these tech support people will manage to sort it out. If not, it doesn't affect things much anyway.

Thank you Matthew, for putting effort into giving us a smooth-running website.

God Bless you, Matthew.

Yours, Sede Catholic.

I wrote a detailed letter to my webhost's tech support, trying to help them track down the problem.

I don't know how much progress they're making, however.

I've had this happen about 20 times in the past 3 weeks.  My gut feeling is
that it has something to do with the controversies in the SSPX.  Now,
maybe there are a lot of readers checking CI for info and not being members
or whatever, but it might be nice to know if the server is getting too many
hits on other accounts too, or is it too many hits on CI's account specifically?

Because if it's the latter, I would think looking into some means of protection
might be a good idea.  I would not put it past the Menzingen-denizens to
assemble a small army of people with PCs doing coordinated "attacks" on
CI by way of timed hits, which can add up to a distributed-denial-of-service
(DDoS) attack and subsequent reaction from the server.

Maybe some kind of registration, at least for a time, for access to read CI
would stave off the problem.  That way the numerous non-members would
have to establish a username and password, or, at least enter some
characters in a window to prove they are not robots, because one of the
ways attackers cause DDoS problems is by using robots to coordinate
lots of what-looks-like-people trying to enter CI all at the same time.  

The fact that this has been happening a lot makes me wonder, because it
could be either one of two things.  Either just a lot of people are trying to
read CI and sometimes that means there can be spikes quite by chance
from hour to hour or minute to minute, sometimes being spikes that push
the server past its limits and cause "error has been reported to Matthew"
or, it could be that someone is doing selective testing to see what kind
of limits there are, and that once the numbers are found out, then a
very effective DDoS attack can be waged, and that could shut CI down
for a lot more than a few minutes.


It's no secret that
the Menzingen Movement wants CI to disappear.  

First, I saw Incredulous' post --

When I first experienced the error message, the thought crossed my mind that CI had been hacked.




I believe it was St. Thomas Aquinas who said Rash Judgement is acceptable , in fact necessary, when it came to supervising and protecting our children.

This maxim must apply to those who want to protect our Traditional Catholic forums too.

Then, I saw this ad below it - and I thought it was talking about

St. Thomas Aquinas, Doctor of Ministry ------- but, he's Doctor of the Church
not "Doctor of Ministry!"

Online Doctor of Ministry

Doctor of Ministry Degree Online Get Free Info - It's Fast & Easy!

I thought -- "That's a heresy posted there!  Does Matthew know about this???"


Then, I clicked on General Discussion and I got this message instead:

A database error occurred on the server. Matthew has been notified.

That's when I thought -- this must be what happens on CI when a heresy is posted.

He's got software installed that recognizes heresy as "database error!"