Error message when posting

[Janis]

I wonder if anyone can explain this?
Each time I've posted a thread today it's taken ages to update, then the web page goes blank apart from this message:
Couldn't get mail server response codesDatabase Error: MySQL server has gone away
File: /home/arillas/public_html/forum/Sources/Load.php
Line: 2035
When I retrieve the page, my post has actually appeared on the page.

Has anyone else had this problem? Or is it just me?
Janis x

[Janis]

but would you believe it - this post went through perfectly!!!
Sod's law I suppose ?

[Sandy x]

Yes Janis. I often get that message when my computer is on a go slow.....but always when I go back to check, it has actually been posted.

[Sara]

It's not you Janis. I just got the same message, but my reply is showing.

Sara....x

[justphil]

Can't sleep after tonight's "excitement." So anorak is back.

It is to do with the server, but as you might guess, I have found a workaround. If your post seems to take a long time, preview it. The preview display appears above your post, so scroll up to see it. You will be warned that someone else has posted, but if you scroll down, it is you. Your post was already saved. Just don't hit Post again or you will post twice. Just go to Unread Posts or whatever you do next.

Phil

[Sandy x]

Phil, so does that mean it only does this when someone else has posted at the same time? Useful to know because I have lost messages like that many a time......

[TerryW]

Janice, sit down and make yourself comfortable as I want to tell you a story.

In 1984 I was in the office at work and this lovely IBM PC came in and I was smitten. I immediately new then that a computer was female. I couldn't get enough of her and I would often dream about having one at home. Over the next few years many more PC's came to work and they seemed to get even more beautiful. The drawing office had one that had two of the most amazing big screens you have ever seen and all the engineers would stare at them all day. You would  have a problem  if you  became too adventurous and the PC would beep very loudly and tell you  that input was inhibited.

I eventually got one at home and I was on it day and night. She was a lovely machine and even had a sound card that made the most amazing noises. But these did become monotonous after a while. I did try many more PC,s over the passing years and some were very fruity, Apricots, Apples and Blackberries and when you touched them their skins were micro soft.

But, I found I couldn't do without one and they became an obsession. There was one big problem though due to their requirement for monthly updates. If one was missed panic would set in. Some friends of ours missed an update and they ended up with a little netbook.

So Janice your problems are down to your PC being female. You will find more evidence here .....


•      They can multi-task, but .............

•   No one but their creator understands their internal logic.
•   They hear what you say, but not what you mean.
•   Beauty is only shell deep.
•   When you ask what's wrong, they say "nothing".
•   Can produce incorrect results with alarming speed.
•   Always turning simple statements into big productions.
•   Smalltalk is important.
•   You do the same thing for years, and suddenly it's wrong.
•   They make you take the rubbish out to the recycling bin.
•   The native language they use to communicate with other computers is       incomprehensible to anyone else.
•   Even your smallest mistakes are stored in long-term memory for later retrieval.
•   As soon as you make a commitment to one, you find yourself spending half your paycheck on accessories for it.
•   The message "bad command or file name" is about as informative as "If you don't know what is wrong, then I'm not going to tell you."
•       The computer needs the EXACT words from you
•        You're spending 70% of your time trying to understand how it works.
•        Anyway... you have to admit the fact once you've had one you wouldn't like to live without.

[Janis]

Oh, Terry - I'm still laughing at that - thank you ever so much!  I particular like the quote

The message "bad command or file name" is about as informative as "If you don't know what is wrong, then I'm not going to tell you."

(not sure if I've inserted properly there - it's the first time I've used the quote icon)

Absolutely fantastic explanation, though

Janis x

[Janis]

Yup - the quote thingy worked! I'll try that again...

[justphil]

Sandy, I don't think so. It is true sometimes - you hit post and miss the red warning so go back to unread etc. You will definitely lose it then unless you hit post again before moving on. On my screen the red warning is often out of sight and if I rush and forget to check by scrolling up, I have lost posts.

This other situation described by Janis is after you hit post, when the whole thing seems to sit and wait for ages then "times out" with the error message  MySQL server has gone away. Before that happens you can force it to post by previewing, but you then get the red warning message, except it is your own post that has just gone through. If you hit post again in this situation, you wil post twice.

Hope it helps
love
Phil

[justphil]

Terry, you rascal. Justloved it.

Phil

[justlynn]

When I've hit Post and got the red warning, I haven't found that I need to go back to Unread at all - the new post the warning refers to has now appeared directly under the message you have just typed.  Try it 

Loved your explanation, Terry! 

lynn xx

[riggers]

Yes Terrys explanation says it all  

[justlynn]

At least it never asks if its bum looks big in this!! 

[Janis]

Neither does my computer, Lynn - it's very "pc" (groan) !!!

Janis x