View Issue Details

IDProjectCategoryView StatusLast Update
0009332VALENTINA SERVEROtherpublic2024-03-11 10:52
ReporterChris Zakrewsky Assigned To 
PriorityhighSeveritycrashReproducibilitysometimes
Status newResolutionopen 
PlatformINTELOSWindowsOS Version10
Summary0009332: vServer 13.9 - crash
DescriptionGot Exception 0xC0000374 which is STATUS_HEAP_CORRUPTION error.

There were 2 open vConnections at the time (of 5 allowed).
Cache was 100MB.
Two vDatabases (Valentina) registered, only one open by both vConnections.
Nothing in vlog.

OS: Windows Server 2019 Standard.

What is needed by you to diagnose the reason for the crash?
This is nothing which can be easily reproduced, but some monitoring may help. Please advice.
I Increased vlog VerboseLevel to 3 now. Something else?
TagsNo tags attached.

Activities

Chris Zakrewsky

Chris Zakrewsky

2024-03-10 19:30

reporter  

Screenshot at 2024-03-07 22-03-50.png (84,558 bytes)
Ivan Smahin

Ivan Smahin

2024-03-11 09:43

manager   ~0012326

Well,

1. Send me please that vServer log (after crash);
2. Check your INI file -
CRASH_REPORTER_SEND = 1
CRASH_REPORTER_OWNER_NAME = <your email>
So, on next start vServer will send us prev. crash report
3. Please try to reproduce the crash
Chris Zakrewsky

Chris Zakrewsky

2024-03-11 10:17

reporter   ~0012327

Absolutely, a top priority here.
Tomorrow and on Thursday we will try to reproduce it in original environment (needs 3 guys).

BTW, is there any way for vServer to notify for example me on its own crash, preferably in real time?
Chris Zakrewsky

Chris Zakrewsky

2024-03-11 10:31

reporter   ~0012328

> CRASH_REPORTER_OWNER_NAME = <your email>

You probably meant: CRASH_REPORTER_OWNER_EMAIL = <your email>
Or both should be verbatim = <your email> ?
Ivan Smahin

Ivan Smahin

2024-03-11 10:34

manager   ~0012329

>> BTW, is there any way for vServer to notify for example me on its own crash, preferably in real time?

Crashed process - of course not,
- but you may write some script (never mind the language), which periodically checks - is vServer.exe process still alive (probably more process params to check);
- Or you may monitor the vServer using SNMP protocol;
Ivan Smahin

Ivan Smahin

2024-03-11 10:52

manager   ~0012330

Yes, sorry

CRASH_REPORTER_OWNER_NAME=<name>
CRASH_REPORTER_OWNER_EMAIL=<email>

Issue History

Date Modified Username Field Change
2024-03-10 19:30 Chris Zakrewsky New Issue
2024-03-10 19:30 Chris Zakrewsky File Added: Screenshot at 2024-03-07 22-03-50.png
2024-03-11 09:43 Ivan Smahin Note Added: 0012326
2024-03-11 10:17 Chris Zakrewsky Note Added: 0012327
2024-03-11 10:31 Chris Zakrewsky Note Added: 0012328
2024-03-11 10:34 Ivan Smahin Note Added: 0012329
2024-03-11 10:52 Ivan Smahin Note Added: 0012330