[Big Mac]

For the first time in, I think, years, we've seen the return of the dreaded MacNN database error. I figured I'd create this thread to save someone else the trouble.

[Dakar V]

I was seeing that and server too busys for the past week, maybe more.

[sek929]

Today a post I made was apparently a duplicate, and I was sent back to the thread.

I only clicked submit once though.

[Dakar V]

That usually indicates time-traveling posts.

[brassplayersrock²]

bump

[imitchellg5]

I've been getting this error a lot today.

[Simon]

Originally Posted by Dakar V 

I was seeing that and server too busys for the past week, maybe more.

I can confirm that.

[Mastrap]

Same here.

[Dakar V]

Only saw one, maybe two this week.

[Dakar V]

I've seeing stuff like this with some regularity recently:

Fatal error: Unable to connect to memcache server in [path]/includes/class_datastore.php on line 224

[mkbhatia]

I just addressed the memcache issue (we are using a new server) and have asked our admins to look into the db issues.

[seanc]

I've got a new one for you

[seanc]

I've got a new one for you

[seanc]

test

I got an error on this post telling me it was a duplicate of one I'd posted already.

I also can't do anything with it apart from edit.

[brassplayersrock²]

something's ****ed up

[imitchellg5]

Oh yay. I haven't had any issues lately, but then about two minutes ago I started getting errors.

[seanc]

I'm still getting the above error in the screenshot and the board is telling me some of my posts are duplicates - it'd be right, some of them are, but not the ones it's telling me about.

Well we can be thankful that it's not swallowing posts.

[seanc]

I'm still getting the above error in the screenshot and the board is telling me some of my posts are duplicates - it'd be right, some of them are, but not the ones it's telling me about.

Well we can be thankful that it's not swallowing posts.

Edit: It really doesn't like me These dupes were a result of the above error.

[seanc]

Bump. Still thought iMitchellG5 was the last poster.

[reader50]

It looks like vB did something dodgy with the memcache code, or we're using a configuration they don't expect. Going to the new memcache server fixed the memcache errors, but almost immediately created problems for staff members, as can be seen by seanc's posts right after the server change.

We started making dupe posts, lost most moderation powers, couldn't do infractions, and sometimes couldn't even log in. All we'd get is that new bitfield error instead.

We've gone back to the old memcache server as of 11 hours ago, and expect to work up a bug report for the vBulletin people.

[Dakar V]

*cue besson*