View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008522||VALENTINA SERVER||Other||public||2019-05-05 12:06||2019-05-08 04:56|
|Reporter||Beatrix Willius||Assigned To|
|Target Version||Fixed in Version|
|Summary||0008522: If server can't be started don't try thousands of times again|
|Description||As reported in 8521 something isn't working on my computer. There are thousands of log files with|
Sun May 5 2019 14:03:20.062841 (TID 140736223429504): Database engine inited
Sun May 5 2019 14:03:20.064998 (TID 140736223429504): Port 15432. ERROR: Address already in use
Sun May 5 2019 14:03:20.065033 (TID 140736223429504): Shutting down server...
Sun May 5 2019 14:03:20.067267 (TID 140736223429504): Database kernel terminated
Sun May 5 2019 14:03:20.067299 (TID 140736223429504): Server terminated
Don't try to restart the server again and again when the server isn't working. And I just reinstalled VServer newest version.
|Tags||No tags attached.|
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
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.