View Full Version : Technical difficulties: Private Messages (Resolved)
Marcus-SanDiego
12-22-2010, 07:08 AM
Looking into it.
Problem: cannot open private messages from the notifications button. Getting MySQL error from database.
ETA for fix: unknown.
Who is affected: unknown. Feel free to let me know, in this thread, if you're able to access PMs via "notifications" button.
az3579
12-22-2010, 07:12 AM
I am able.
danewilson77
12-22-2010, 07:20 AM
I'm good. No problems. Seems like there was a glitch on the site this morning....though.
Marcus-SanDiego
12-22-2010, 07:21 AM
Thanks, guys.
az3579
12-22-2010, 07:24 AM
Thanks, guys.
Anything for the Godfather.
Marcus-SanDiego
12-22-2010, 07:25 AM
Grateful to you guys. :praise
Marcus-SanDiego
12-22-2010, 07:44 AM
Update: MySQL will likely be rebooted shortly. Site may go down for a moment (or not).
az3579
12-22-2010, 08:05 AM
Still up... (obviously) :p
MrMaico
12-22-2010, 08:26 AM
I had a different issue the other day when I was trying to edit an old post. Instead of taking me to the edit screen it took me to Paypal to make a donation to the site. That's one way to get donations....LOL j/k Marcus. I will say that it did work though, made a small donation.:-) I'd planned on waiting till after payday so I could give a little more but I can still do that too.
Marcus-SanDiego
12-22-2010, 08:42 AM
Barry, that was me the other day. I miscoded something, so it created that Paypal problem. Of course, at that time, someone donated to the site. So maybe I need to try that again! Haha.
Marcus-SanDiego
12-22-2010, 08:53 AM
We were having memory issues. Specifically, we were bumping on limitations because of the parameters that were set for the container. When I tried to open private messages this morning, I got a notice saying that there was not enough memory to complete my request. Those memory parameters have now been increased so that we don't get these issues on a regular basis.
Additionally, we're looking into general slowdown issues that most often happen during the morning.
The issue that is the subject of this thread, though, has been resolved.
Therefore, I am closing it.
Powered by vBulletin® Version 4.2.2 Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.