Housepets!

Ah, no wonder then. Noted, and thanks for the heads up

Fixed! The server ran out of disk space due to a 80GB log file. Oops. Fixed log rotation so that won't happen again!

how in the world does a single file get that large?

Ah, dealing with SQL errors.

Bane of my existence.

So, now that it's fixed, what does an SQL error do, fail to load a page or send the message?

D-Rock wrote:So, now that it's fixed, what does an SQL error do, fail to load a page or send the message?

To pack a year's worth of classes into a short-ish explanation, a Server Query Language error can be any number of things - after all, it is just a programming language; in this case the one primarily used to build databases. I couldn't tell you for certain without looking at it myself, but given what Inaki said, log files are used to track changes in the database. Given that it was affecting the User CP and the PM system, I would speculate that any time there was a change to a user's profile or when a message was sent/read/sorted et cetera, the log file would be updated to keep track of the change, so that in case of a catastrophic breakdown in that particular database, you can figure out what change caused the whole thing to go kablooey. However, the constant updates to the log files from a large cadre of users over a period of time will make the log file grow larger and larger, until well... you have a giant file eating 80 gigs of memory. Without space to add changes to the log file, the system would prevent any changes being made - thus throwing up the error everyone saw.

Again, all speculation - Inaki could explain better, he actually saw the files. But that'd be my (relatively educated?) guess.

CosmicCoyote wrote:

D-Rock wrote:So, now that it's fixed, what does an SQL error do, fail to load a page or send the message?

To pack a year's worth of classes into a short-ish explanation, a Server Query Language error can be any number of things - after all, it is just a programming language; in this case the one primarily used to build databases. I couldn't tell you for certain without looking at it myself, but given what Inaki said, log files are used to track changes in the database. Given that it was affecting the User CP and the PM system, I would speculate that any time there was a change to a user's profile or when a message was sent/read/sorted et cetera, the log file would be updated to keep track of the change, so that in case of a catastrophic breakdown in that particular database, you can figure out what change caused the whole thing to go kablooey. However, the constant updates to the log files from a large cadre of users over a period of time will make the log file grow larger and larger, until well... you have a giant file eating 80 gigs of memory. Without space to add changes to the log file, the system would prevent any changes being made - thus throwing up the error everyone saw.

Again, all speculation - Inaki could explain better, he actually saw the files. But that'd be my (relatively educated?) guess.

Man you gave me a headache...but I think I understand now

Thanks for the quick fix! I don't really get it either, but yeah.

On another note, in my 4 years here, I think this is the first time I've seen a post by inaki :3

Well, I mean, I suppose I could throw more examples at you if you wanted, but they are called programming languages for a reason. They sound nonsensical if you don't know what you're talking about.

kurowolfe wrote:Thanks for the quick fix! I don't really get it either, but yeah.

On another note, in my 4 years here, I think this is the first time I've seen a post by inaki :3

I've seen one before.

Where he says he doesn't have admin duties, he just makes the server keep working.

CosmicCoyote wrote:-snip-

One part of the forum software that kept track of who sent PMs to whom, when avvies were changed, etc. ran out of memory. It threw up an error to stop recording that stuff, before Inaki assigned free sectors of space for archiving user activities.

That sums it up? :3

Liam wrote:

CosmicCoyote wrote:-snip-

One part of the forum software that kept track of who sent PMs to whom, when avvies were changed, etc. ran out of memory. It threw up an error to stop recording that stuff, before Inaki assigned free sectors of space for archiving user activities.

That sums it up? :3

More or less. Why can't I make it that simple? >_>

Because what is simple to people who know some programming is like Semidefinite Optimization math to people who don't know how to program.

Xane wrote:Just call them SQRRL errors. Easier to imagine SQRRLs eating the wires.

So we shifting the blame to the errors on Diss's uncontrolled squirrel minions now?

Amazee Dayzee wrote:So we shifting the blame to the errors on Diss's uncontrolled squirrel minions now?

No on Diss! he is the 300lb Devil Skirrl in the room?

Yeah but he has thousands of minions he can't always keep his eyes on.

Thanks for the explanations. Yes, programming languages is Greek to me, but nothing wrong with learning a bit more about it. Though there are times when I realize the "for dummies" version is the one to stick to for the moment.

Amazee Dayzee wrote:Because what is simple to people who know some programming is like Semidefinite Optimization math to people who don't know how to program.

I am assuming this has something to do with convex optimizations?

CosmicCoyote wrote:
To pack a year's worth of classes into a short-ish explanation, ⚙...you have a giant file eating 80 gigs of memory... 80 gigs of memory

HOLY CARP! How many people are here?!?

enough to break a server, apparently.

Keep it up, and Diss will have you assassinated.

Database log or error log?