Subject INET/inet_error: fork/CreateProcess errno = 5
Author Vacek, Miroslav

Hi all,

 

I have recently run into INET/inet_error: fork/CreateProcess errno = 5 error in one of my Firebird boxes and I was wondering if anyone could help me with understanding what it actually means.

 

I have several identical Windows Server machines running Firebird 2.1.3 64-bit in Classic Server mode. Recently application using Firebird on one of these servers died.

 

When investigating the issue I came across following records in Firebird.log that coincided with the application crash.

NB-ES-0180 Wed Nov 06 12:12:16 2019

     INET/inet_error: fork/CreateProcess errno = 5

 

 

NB-ES-0180 Wed Nov 06 12:32:16 2019

     INET/inet_error: fork/CreateProcess errno = 5

 

 

NB-ES-0180 Wed Nov 06 13:52:16 2019

     INET/inet_error: fork/CreateProcess errno = 5

 

 

NB-ES-0180 Wed Nov 06 15:32:16 2019

     INET/inet_error: fork/CreateProcess errno = 5

 

 

NB-ES-0180 Wed Nov 06 15:52:16 2019

     INET/inet_error: fork/CreateProcess errno = 5

 

I have also discovered that database file on that machine was corrupted.

gfix -v -full -no_update -user sysdba -pass <redacted> localhost/3050:<redacted>
Summary of validation errors

        Number of index page errors     : 4

        Number of database page errors  : 4424

 

I am not sure whether this is actually symptom or the cause of the errors reported in Firebird.log. Database files on other boxes are corruption free. But there were no problems with other Firebirds.

 

I have looked into resource consumption at the time of the crash and found nothing out of the ordinary. The memory was sitting comfortably at 50% utilization which it always does. CPU was also under-utilized (25%).

 

I was able to fix the database corruption and run the application again. The system is running without an incident since then.

 

I am just wondering what could possibly cause the “INET/inet_error: fork/CreateProcess errno = 5” so I can prevent it in future.
Did anyone else encounter this error?
Any thoughts whether or not this could be related to the database corruption?

 

Thanks!

Miroslav Vacek