Server launched but failed initialization - WebSphere

I tried the innocent action of starting the WebSphere Application Server on the machine with zOS and I got the following problem:

ADMU0128I: Starting tool with the ProcSrvBG profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3011E: Server launched but failed initialization. Server log files
> should contain failure information


I wasted almost a day trying to figure out what happened, among the possible reasons and solutions there were:
1. another process is already using the port that the Applcation Server wants to use(see here)
2. reinitializing the configuration by running "osgiCfgInit.bat" from ./profiles/profilename/bin (see here)
3. host name changes

None of these worked in my case. The reason was there was not enough space on disk. An it was that bad, that we couldn't even start the servers even worse it could not be logged anymore and the only thing that could be found was some output in native_stderr.log under ./websphere_location/profiles/profilename/logs/servername/native_stderr.log:

An exception occurred while writing to the platform log:
java.io.IOException: There is not enough space in the file system.
at java.io.FileOutputStream.write(FileOutputStream.java:290)
at sun.nio.cs.StreamEncoder$ConverterSE.implFlushBuffer(StreamEncoder.java:285)
at sun.nio.cs.StreamEncoder$ConverterSE.implFlush(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:202)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:236)
at java.io.BufferedWriter.flush(BufferedWriter.java:257)
at org.eclipse.core.runtime.adaptor.EclipseLog.log(EclipseLog.java:309)
at org.eclipse.core.runtime.adaptor.EclipseLog.log(EclipseLog.java:295)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveBundleDatas(BaseStorage.java:520)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveAllData(BaseStorage.java:372)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.access$1(BaseStorage.java:362)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage$StateSaver.run(BaseStorage.java:1081)
at java.lang.Thread.run(Thread.java:811)
Logging to the console instead.

!ENTRY system.bundle 4 0 2010-08-25 14:54:16.265
!MESSAGE FrameworkEvent.ERROR
!STACK 0

java.io.IOException: There is not enough spa


(Please notice how abrupt he error message had to end - it might not look funny to you but when I saw it I laughed for 10 minutes...in the bathroom).


While trying to figure out the problem I got to the conclusion that I don't like the netstat command under zOS at least - just a personal attitude.