Adam Grare

@Fryguy I did but that was najdorf

Those errors are normal on startup

@kTipSSIoYv can you check `ps aux | grep MIQ` ?

That's very weird there are no workers or MIQ Server, can you upload as much of the evm.log as you can?

@kTipSSIoYv can you try running `systemctl status [email protected]` and `journald -u [email protected]` ? It seems the workers aren't starting up properly

15GB is enough, if startup is timing out I wonder if it isn't able to hit the database. Can you try running `./tools/db_ping.rb` from the `/var/www/miq/vmdb` directory?

We currently only support External NAT, I've opened an enhancement to support this https://github.com/ManageIQ/manageiq-providers-google/issues/231

I wonder if the VixDiskLibServer case we could just let the child process write to STDOUT and let it get picked up by journald/k8s that way

I was thinking changing [this](https://github.com/ManageIQ/vmware_web_service/blob/master/lib/VMwareWebService/VixDiskLib/VixDiskLibServer.rb#L16) to `$vim_log = Logger.new(STDOUT)`

@Fryguy https://github.com/ManageIQ/vmware_web_service/pull/106 we can discuss specifics there, but I stole the "is it a logger::logdev" from this to conditionally log to the logfile or stdout. The parent process was already...