SourceForge.net

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

Per our email thread, the issue looks to be related to the DNS for your
vhost. Please let us know by new ticket if the problem persists once the
DNS has been corrected.

Thank you,

Jacob Moorman
Director of Operations, SourceForge.net

It seems the problem may be caused by the aolserver.com DNS pointing at the
old VHOST IP. (See support ticket #2119831.)

Help. I'm really at a loss for what to try and do here to fix things.
I've made sure it's connecting to "mysql-a" and not the FQDN, checked and
double-checked the username and password ... Is someone looking into this?

Has anyone looked into this further? Can someone at least confirm that
there's a real problem here?

FYI: http://sourceforge.net/project/admin/database.php?group_id=3152

Still shows "mysql4-a" as the hostname.

So, I changed the hostname to just 'mysql-a' and I still get the database
connection failure.

Any other suggestions?

FYI:
http://sourceforge.net/community/forum/topic.php?id=3496&page&replies=1

Hello,

The issue is that you're using a FQDN for the database server hostname.
Were you using mysql4-a (without the .sourceforge.net), it would have
worked. We'll look in to adding temporary support for the old mysql4-X
hostnames with FQDN, though that's not supported right now.

Project database changes were announced previously as: "The hostname used
to access project DB service will change to mysql-X from its current
mysql4-X (where X is the first letter of the project name). The old
hostname scheme will be supported through the migration, but will be
deprecated in the future. NOTE: The proper server name is mysql-X not
mysql-X.sourceforge.net."

We would encourage you to go ahead and update your application config to
use the new hostnames.

Thank you,

Jacob Moorman
Director of Operations, SourceForge.net

I ran into this today too. It turns out the new server name is "mysql-a"
without the "4" and without ".sourceforge.net" at the end. Hope this
helps.

Hello - as a SF.net subscriber, I'm supposed to get "priority support" -
it's been a few hours since I've submitted this ticket and it's not even
_assigned_ to anyone, yet.

Exactly how does SF define "priority"?

Hello - as a SF.net subscriber, I'm supposed to get "priority support" -
it's been a few hours since I've submitted this ticket and it's not even
_assigned_ to anyone, yet.

Exactly how does SF define "priority"?