So we're upgrading from Flash Comms Server to Flash Media Server 2.

We run on Debian, so that in itself wasn't as simple as you might think, had
to all this to get it to wok
apt-get install libstdc++2.10-glibc2.2 libnspr4
cd /usr/lib
ln -s libcrypto.so.0.9.7 libcrypto.so.4
ln -s libssl.so.0.9.7 libssl.so.4

But after doing that it did indeed do so, but our apps still weren't working.
Build a minimal test-app to narrow the problem down, made a directory for a
"testApp" in the applications directory and put this code in the main.asc
inside there:
application.onAppStart = function(){
trace("Test App Starting");
}

application.onConnect = function(client){
trace("Connecting Client");
}
Nothing too complicated as you can see. Testing that connection with this
amazingly simple bit of client-side code:

stop();
client_nc = new NetConnection();

// Trace the connection status when it changes
client_nc.onStatus = function(info) {
trace("Level: " + info.level + newline + "Code: " + info.code);
};

var res=client_nc.connect("rtmp://test.server.com/testApp");
trace("Connected:"+res);

//Quick counter to check the connection status every 50 frames
var tim=0;
var count=0;
onEnterFrame = function(){
if(tim++>50){
tim=0;
count++;
trace("After "+count+" status is "+client_nc.isConnected);
}
}


When the URL to connect to here is wrong (like it is here) we get the expected
error printed quite quickly, yet when we point it at the actual FMS install it
instead pauses, waits, until number 77 in the trace count there to give the
same NetConnection.Connect.Failed error.

The App is started, the app shows the "Test App Starting" message in the log,
but it doesn't show any attempt to actually connect at all.

There's no firewall problems blocking the connection, I'm able to telnet into
port 1935 and get a reply, though having no idea what the protocol is I can't
send any sensible message.

So anyone have any idea what might be wrong? Can't find anything to indicate
even a connection attempt in any of the logs at all.

Hummm. Found someone saying a 2.4 kernel wasn't gonna do the trick so upgrade
the kernel to a 2.6 kernel which I'd never done remotely before, glad the
machine came back up!

But it's still doing the same even with the 2.6 kernel :( Boo!

Okay, figured it out. Mostly it was the kernel version problem, needed 2.6

Strangely, it seems I had to hit the Reload Application button on the
fms2_console before it statrted to work - even after a complete reboot. Seems
odd.

But all is working now. Thanks anyway.