Issue: Forum slow, database errors

[teylyn]

Again!
........................

[arlu1201]

Teylyn,

Did you face this issue again? If the issue didnt recur, please mark it solved.

[Domski]

It happened again. I just got a database error when trying to ask someone to change their thread title.

Not solved.

Dom

[FDibbins]

For what its worth, I had a problem too...I replied to a threat, but when I tried to post, it took ages and then just times out with an error msg with something aboutthe forum was experiencing problems. This was about 30-45 minds ago. It seems ok now tho

[teylyn]

Did you face this issue again? If the issue didnt recur, please mark it solved.

Well, we could all file individual threads and mark them solved ten minutes later if the error did not occur in that time span, couldn't we, Arlette?

Were you asking because you hope it will just go away, magically? Or were you asking because the tech team did something towards actively addressing the issue?

[arlu1201]

Teylyn,

You will know this very well, that there are certain issues which need to be addressed right at the time when they occur, like parse errors, database errors, etc. They cant be worked on later as it wont be possible to find the root cause of such an issue. When there are no parse errors cropping up, how do you expect the tech team to find out why that error occurred say 3 hrs ago?

For this same reason, i asked you if the issue recurred at your end. We are not waiting out on these issues to check if they might just vanish automatically. The team is working hard at their end to check into each issue.

[Domski]

Well there's errors happening at the moment so it's probably a good time for them to get on it. I do fail to see how we are expected to conjure errors up as you request when we have no real idea what is causing them.

[arlu1201]

Thanks Dom. I did see the posts and have asked the tech team for an update. Though most of them will be off since its a Sunday, i have asked their lead to check things up.

[shg]

When there are no parse errors cropping up, how do you expect the tech team to find out why that error occurred say 3 hrs ago?

The guy had a leaky roof that he never fixed. When asked why, he said, "Well, ya cain't fix it when it's rainin, and when it ain't rainin, it don't leak."

[Mordred]

I find it interesting that the "team" is working hard at these issues. If they were, the issues would be resolved wouldn't they? I think that if I or anyone else in the professional world had the success rate that the "team" is having, we would have been fired 2 months ago. During the lowest peak times (the weekends) seems to be when I either receive database errors or at the very least, long load times between forums and threads. How is that even logical? I think the "team" is way over their heads on these issues and the proof is in the reliability of the forum. I received 2 database errors last night but didn't report them because it doesn't seem to be worth the wait times to post. This is almost funny.

[Domski]

I received 2 database errors last night but didn't report them because it doesn't seem to be worth the wait times to post. This is almost funny.

Took me a couple of attempts but I was bored. Wonder if this thread will still be going this time next year?

[Mordred]

Took me a couple of attempts but I was bored. Wonder if this thread will still be going this time next year?

LoL, if this site is having these issues in a year from now, there won't be many people using it I don't think.

[NBVC]

LoL, if this site is having these issues in a year from now, there won't be many people using it I don't think.

The sad part is that there probably will be... a whole new set of guinea pigs will have spawned on the site... while us old ones have long died out!

[Fotis1991]

I received the ...message...Two(2) more times, again....Now.

[arlu1201]

The routine backup process was running on the server during the weekend and hence the database errors, server too busy errors popped up. The tech team is currently discussing with the server guys on how to best do this without causing the errors to crop up. More updates on this coming soon....

[teylyn]

Arlette, I don't really care about your geek speak. I really don't care what exactly the tech team do or how hard they try.

I'm not really impressed by "effort". I've read Ayn Rand and I live in New Zealand. Whenever I hear/read that somebody is "working hard" on something or has put in "tremendous effort", it just means that they have delivered a complete failure because they don't know what they're doing, but are all frantically working overtime to make up for lack of expertise.

The result of such a framework is exactly what we have seen at EF for the last three months.

Keep on working overtime, if you want. Put in effort, try hard. Even try to try harder.

Unless you seriously upskill your tech team, the situation won't improve.

Of course, the trial-and-error type dudes working on the system at the moment don't seem to have much of a clue, so if we users and contributors expect any significant positive changes to the forum, we'll need to accommodate their learning curve (i.e. wait for another couple of years or so). We may do that. Or we may not. As stated before, you need _us_, not the other way around.

In the mean time, you'll proudly report major step changes, like no more gray rep icons (as if anyone but 3 members care), while at the same time we still can't copy and paste forum content to a spreadsheet without annoying formatting (give that a go, will you?) or easily copy code from a code tag (which has been on the to-do-list for two years now).

I'm sure you'll find wordy rationales and explanations why the team will (not) solve certain things and proudly report that another issue has been solved (or not, but they have maybe disappeared, but nobody knows why). The truth is that the tech team have accidentally stumbled upon a setting, found a switch, or a tick box and tried it.

This does not mean that they are anywhere near the technical skills required to run a vBulletin forum in the current version.

With 5 days without any other obligations I'm sure I'd be able to turn this forum upside down. Unfortunately, I'm not available for freelance work. Others may be. In fact, others have offered their expertise, but forum politics and petty gripes have prevented the benefits this forum could have gained. Be proud of that. </irony>

Face up to it and biff the tech team you currently employ. Despite the meagre "success" and "solved" messages of the last days, let's face it: they don't have a clue and everybody here knows it. Keep on stabbing in the dark. Yes, hit a few solutions accidentally, every week or so, but please don't try to tell us that Vai's team are even remotely capable of running this show, because the experience of the last two years has shown that they are not.

And please, stop pestering us to close issues. We will if we are certain that they've been solved. But as the exchanges in this forum show, many a promise of an issue solved proved to be wrong. Therefore, I take the liberty of waiting it out to see if the issue returns. It may take some time until I close the thread I opened. However long it takes, it will still be more responsive than the tech team is.

regards,

[arlu1201]

The error that has been popping up - "You need to wait for 30 secs between posts, please wait for 15 secs" has not occurred for the last 2-3 days. The settings at the backend have been checked and has been fixed. However, the tech team is going to monitor this for the next 1-2 days. If you do get this error again, please report it immediately with the time at which it occurred.