Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Between 9:40am and 10:02am eastern this morning, the site was mostly down. I was sleeping in and not around.
There was a database and PHP error, which is still lingering. It eventually resolved itself by nuking all the connections.
This is the 2nd time this particular error has happened in the last year, I do not have a solution other than to reboot the server due to the way memory corruption occurs.
After the webinar today, I will bounce the server and futures.io (formerly BMT) will be down for about 5 minutes during this time.
Also, I forgot to post that the webinars went offline this morning during the server problem, and they were offline most of the day because it wasn't reported to me until a couple of hours ago. Has been fixed now, but they (and entire site) will be down for a few minutes when I reboot the server.
Hey Mike not sure if it is relevent or not or anything at all... I was trying to see ninja stuff last night using spy ++ and noticed two windows messages in chinese , I opened em to take a look and was non stop message after message streaming , it said something like flash place holder , they were coming from here cause I closed the page and they went away ... but again I have no idea what I was looking at ....
"Successful trading is one long journey, not a destination" Peter Borish Former Head of Research for Paul Tudor Jones speaking on conversations with John F. Carter
Made a couple of mysql changes, and wrote some code tonight to wrap around the default vBulletin error handler. End result is hopefully what happened yesterday morning won't happen again, and if there is a mysql hiccup or restart, vBulletin will now retry the connection a few times before giving up and throwing an error.