22.11.2014, 12:21
While I'm not certain this is a direct cause of your problems, please keep in mind I'm going through a pretty substantial upgrade process and your server may be exhibiting this behavior because of that. Part of this upgrade process involves moving tables from the old game CP database to the new DB, and then updating that info into a new structure.
I have noticed that one downside of this upgrade involves some silly behavior with services using a custom IP address. I _believe_ (I'd have to check) that your server uses a unique IP and might be one of the systems showing odd behavior. You, myself, and only one other person are rocking the custom IP so this problem only encompasses 4 services (2 of them being my own). I know this info is likely no help to you, however I just wanted you to know the issue is relatively unique and is one of the primary issues I'm working at the very moment I'm typing this.
Again, this may not be the root cause of your issues but I wanted to relay this info in the hopes it may give you some insight.
Sit tight, hopefully in a few hours your service will be back to normal. If it turns out that the DB migration isn't causing this, I will address your looping issue the instant I have a stopping point in the upgrades I'm performing.
I have noticed that one downside of this upgrade involves some silly behavior with services using a custom IP address. I _believe_ (I'd have to check) that your server uses a unique IP and might be one of the systems showing odd behavior. You, myself, and only one other person are rocking the custom IP so this problem only encompasses 4 services (2 of them being my own). I know this info is likely no help to you, however I just wanted you to know the issue is relatively unique and is one of the primary issues I'm working at the very moment I'm typing this.
Again, this may not be the root cause of your issues but I wanted to relay this info in the hopes it may give you some insight.
Sit tight, hopefully in a few hours your service will be back to normal. If it turns out that the DB migration isn't causing this, I will address your looping issue the instant I have a stopping point in the upgrades I'm performing.