SuperContainer Server fails to start after OSX Security update 2013-01

[Tony Hill]

I am running a MacBook Pro with Lion (10.7.5).

I am running the latest Java JDK 7_17

 

I run a development version of SuperContainer server on this computer for use with FileMaker Pro 11.

This has been error free for 4 years under various versions of SC

 

I am now on 2.864 of SuperContainer and have been for several months.

 

Yesterday I updated my OSX with Safari 6.0.3 and the latest Security update.

 

Now the SC server will not start, I get this error

 

Problem starting server: mymacname: maymacname: nodename nor servname provided, or not known

 

NB: I have replaced my real Mac name by the text mymacname for security purposes.

 

I have traced similar errors reported on Apache servers with other apps but they were of no help.

I did re-install the latest Java again but this made no difference.

 

Is this one for 360Works or do I have to sit it out until Apple fix whatever they unfixed.

Any ideas?

 

Tony

[Joe Pampalon]

This error comes from SC not being able to resolve the machine name. The fix for this is to go into System Preferences --> Sharing and change the name of your machine there. After the change SC will be able to recognize your machine, and you can freely change the machine back to it's original name (or any other name).