 |
I have seen this condition several times. It is very difficult to reproduce at will, but sooner or later it happens - VServer gets itself into a thread deadlock and ends responding to either clients or OS (operating system) or both. It will hang forever onto its port and effectively block all subsequent restarts. Only a total reboot fixes this. At my setup this sometimes happens when i "stop the time" - in my configuration I run VServer in a virtual machine and VClient in another. When I pause both machines at the end of the day (time stops as far as machines are concerned) and un-pause the day after, this is when it happens, but not every time. When I have no VClient loaded it can not be reproduced on VServer alone. |
 |
If you want that vServer starts manually you should set <key>KeepAlive</key> <false/> <key>RunAtLoad</key> <false/> |
 |
Which operating system is this about, if I may ask? Thank you in advance. |
 |
@Tomas Stehlik: macOS High Sierra. @Ivan Smahin: the problem was caused by mixing up LaunchDaemons and LaunchAgents. |
- Anonymous
