Hi again,
after I've head good success with OsProcessStarter and friends in WIndows and Linux in a development image, I am now having trouble starting external processes on a headless test machine. I guess I am having a problem somewhere outside of VAST, but am not sure where to look...
This is what gets written to the walkback:
OsProcessesApp class>>#convertPrimErrorArrayToException:then:
receiver = OsProcessesApp
arg1 = (13 'ERROR: posix_spawn() failed. errno: 13
ERROR: posix_spawn() failed. errno: 13
')
arg2 = [] in OsVastSubprocess>>#execute
temp1 = Signal on Exception: (ExOsProcessException) An exception has occurred
OsVastSubprocess>>#execute
receiver = {pid: cmd: ...}
temp1 = (13 'ERROR: posix_spawn() failed. errno: 13
ERROR: posix_spawn() failed. errno: 13
')
- I checked that esproclauncher is in the /bin directory of the server runtime.
- I found that in the /bin directory of the server runtime there is no symbolic link named libc.so, so I created it, just in case this causes troubles (but I guess teh VM wouldn't get very far anyways if that was the problem).
- I checked that the command and arguments are correct and run correctly from the command line
What can I check next? The test system runs the image as root, so I guess there is not much of a chance that this is a file permission issue....
Any ideas?
Joachim