full tmp dir prevents server from reading server.env during startup #4132
Labels
in:Kernel/Bootstrap
Needs member attention
release bug
This bug is present in a released version of Open Liberty
release-18.0.0.4
If /tmp directory is full and you want to start a server, the server starts but with wrong environment vars. during startup you see exceptions like this:
wlp/bin/server: line 161: cannot create temp file for here document: No space left on device
According to the return code server started successfully which is almost true (according to messages.log) and "server status" command also says "server is running". However, the server initializes without the given server.env which could result in a wrong behaviour of the application. Think what happens if you put db-connection-urls / usernames etc. in the server.env and they aren't available. In the worst case the application switches to some default "developer environment" behaviour in production ...
You could easily recreate this problem just with a full /tmp directory.
open-liberty/dev/com.ibm.ws.kernel.boot.ws-server/publish/bin/server
Line 159 in 29aa36b
The text was updated successfully, but these errors were encountered: