ARGH! I get this screen everytime...

[kumquatq3]

 

I get the above screen, note the "Hello Revan Solo" that is in the code for some reason (not my doing) , whenever the new thread is created, but I get this screen.

 

I get it everytime or almost everytime.

[Gorth]

First it insults you in german, then it apologises in english.

 

You are doomed

[metadigital]

It is just a database error, when there are too many simultaneous requests for the server to handle, it bounces some out without knowing the exact state of the write transaction (whether it succeeded or not).

 

In my experience, it has succeeded. The server just isn't sure.

 

You can either post topics when the fora are less busy, send off a check to Obsidian to upgrade their server farm and forum software, or ignore it.

 

[kumquatq3]

It is just a database error, when there are too many simultaneous requests for the server to handle, it bounces some out without knowing the exact state of the write transaction (whether it succeeded or not).

 

In my experience, it has succeeded. The server just isn't sure.

 

You can either post topics when the fora are less busy, send off a check to Obsidian to upgrade their server farm and forum software, or ignore it.

 

<{POST_SNAPBACK}>

 

 

all well and good, but I can't remember NOT getting it. Hence, It's not a "peak hours" thing.

[metadigital]

So it happens every time you post a reply?

[Hydrogen]

It is just a database error, when there are too many simultaneous requests for the server to handle, it bounces some out without knowing the exact state of the write transaction (whether it succeeded or not).

 

In my experience, it has succeeded. The server just isn't sure.

 

You can either post topics when the fora are less busy, send off a check to Obsidian to upgrade their server farm and forum software, or ignore it.

 

<{POST_SNAPBACK}>

 

Obsidian is aware of it. I know this because Fionavar and I have pointed it out to Admin. We both get it from time to time, but we have found that our posts go through even when we get it.

 

Also, we tend to get that at strange times, so I don't think it is a peak hour thing.

 

If other people are getting it, make sure to let us know. For a while, Fionavar and I thought it was only the mods who were getting that error.

 

Also, I haven't noticed it to happen consistantly. If someone gets it everytime, then we probably have something else to look into.

[Krookie]

I think it just happens when he makes a new thread.

[Hydrogen]

If it keeps happening, just comment here. Hopefully, we can figure out what is going on. I looked at a note that I had from before when Fionavar and I were getting them at least once a day and we were told that the database passed all the tests.

[kumquatq3]

I think it just happens when he makes a new thread.

<{POST_SNAPBACK}>

 

Right

 

I can't remember getting when I post just normal

 

 

I've also been getting this thing on longish posts where my "commands" like quotes, img, size and color stop functioning all together for that post. Example:

 

I type:

Hi[/quote.] (without the periods)

 

and when I hit post it doesn't follow the command, it just displays it as above. This is on every command in that post.

 

It is also a frequent occurance

[Magena]

I saw Guildmaster on earlier, so hopefully he is looking into this... or scratching his head and saying "huh?"

[kumquatq3]

I saw Guildmaster on earlier, so hopefully he is looking into this... or scratching his head and saying "huh?"

<{POST_SNAPBACK}>

 

Maybe "Revan Solo" can fix it.

[Krookie]

I just got the screen too...

[Cantousent]

This often happens to me, also. The topic still posts, though, so I haven't worried about it.

[Magena]

I just got it at 11:14 pm PDT, so it isn't a rush hour thing. My post did go through though , so it is more annoyance than true issue --- at this point.

[Musopticon?]

I have got maybe 5 times. Each time when posting a new topic.

[Archmonarch]

I get it whenever I post a new topic as well. In fact, I seem to remember having gotten it (though less frequently) last year also.

 

Also, Im guessing the reason for the Revan Solo item is that was the first topic (You will notice the error message references a topic named 'Hallo Revan Solo.') to cause a problem, and has been a holdover for every similar error message since. I would suggest looking into the above topic, and see if any problems can be discovered there.

[Magena]

I get it whenever I post a new topic as well. In fact, I seem to remember having gotten it (though less frequently) last year also.

 

Also, Im guessing the reason for the Revan Solo item is that was the first topic  (You will notice the error message references a topic named 'Hallo Revan Solo.') to cause a problem, and has been a holdover for every similar error message since. I would suggest looking into the above topic, and see if any problems can be discovered there.

<{POST_SNAPBACK}>

 

At least we are narrowing the issue down to being when people start new threads. - that is probably why they mods don't get it frequently - since they close threads more than start them.

[Jediphile]

Yeah, when the computer begins to talk to you in german, you know it's bad... <_<

[Carnage]

yeah I have also had this screen, I think I saw it twice last week sometime.......

[Kor Qel Droma]

I had the same screen, minus the German.

[Calax]

I saw it every time I have made a new topic in the past three days.

[The Guildmaster]

At first glance it looks like the mail system is having problems sending e-mail post notifications to a user. I've analyzed and repaired the SQL tables, but no errors were found. It may be something else which we're looking in to.

 

Thanks,

TG

[metadigital]

At first glance it looks like the mail system is having problems sending e-mail post notifications to a user.  I've analyzed and repaired the SQL tables, but no errors were found.  It may be something else which we're looking in to.

<{POST_SNAPBACK}>

If they are new topics, then there shouldn't be too many people being sent emails, as there are no posts to which this new post is a reply to, so the email notification should be triggered for mods / devs (those who want to know about new topics). If the index of the table was corrupt, then that would cause the error, so re-indexing would solve that (hopefully: might have to discard the index and create a new one from scratch).

 

Secondly, I get the error infrequently (I got it today), but not always when starting a new topic, sometimes when replying, too. And not always when posting a new topic, sometimes it posts normally.

 

[Kor Qel Droma]

Today I started two new topics. The first went through okay, but on the second one the error screen popped up again.

[metadigital]

Try and get a copy of the error message. I say this because I think it is always the same, but someone earlier suggested it changed. (Just copy and paste into Notepad, or similar, then paste it here.)