View Issue Details

IDProjectCategoryView StatusLast Update
0008522VALENTINA SERVEROtherpublic2019-11-06 11:43
ReporterBeatrix Willius Assigned To 
Status newResolutionopen 
Target VersionTODO_FEATURES 
Summary0008522: If server can't be started don't try thousands of times again
DescriptionAs 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.
TagsNo tags attached.


Chris Zakrewsky

Chris Zakrewsky

2019-05-05 19:04

reporter   ~0010773

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.
Ivan Smahin

Ivan Smahin

2019-05-06 06:37

manager   ~0010774

If you want that vServer starts manually you should set


2019-05-07 18:11

reporter   ~0010785

Which operating system is this about, if I may ask?

Thank you in advance.
Beatrix Willius

Beatrix Willius

2019-05-08 04:56

reporter   ~0010787

@Tomas Stehlik: macOS High Sierra.

@Ivan Smahin: the problem was caused by mixing up LaunchDaemons and LaunchAgents.

Issue History

Date Modified Username Field Change
2019-05-05 12:06 Beatrix Willius New Issue
2019-05-05 19:04 Chris Zakrewsky Note Added: 0010773
2019-05-06 06:37 Ivan Smahin Note Added: 0010774
2019-05-07 18:11 stehlo Note Added: 0010785
2019-05-08 04:56 Beatrix Willius Note Added: 0010787
2019-11-06 11:43 Ruslan Zasukhin Target Version => TODO_FEATURES