Windows Agent Fork failure....?

Trainee · Post by **Trainee** » 07 Jul 2009 2:38

Why would you get this on a windows box running a control-m 6.3.01.300

If any one can assist please

?

GNappo · Post by **GNappo** » 07 Jul 2009 2:44

Hi Trainee,

I've not understood or I don't see the windows

Best Regards

Giuseppe Nappo

Trainee · Post by **Trainee** » 07 Jul 2009 2:47

On a host thats installed with a control-m agent I am running .bat files as jobs but its failing with an error " due to fork failure" in the logs.

My question is , what will cause this to happen..?

GNappo · Post by **GNappo** » 07 Jul 2009 2:50

ok! only some information:

- Control-M Agent Version and Fix-Pack installed
- OS on which you have installed the Control-M Agent

by the way... this error message was displied by Control-M Agent 6.1, solved in Fix Pack 6

This problem was indicative of Microsoft Windows not being able to create a new desktop heap for the program being executed. Any service that creates processes (like the CONTROL-M/Agent) cannot run more than eight processes at the same time. Additionally, it has been noted that when the exit return code is longer than eight digits, this issue will occur.

Best Regards

Giuseppe Nappo

Trainee · Post by **Trainee** » 08 Jul 2009 9:19

running on Windows Server 2003, Fixpack 2 and the agent is a 6.3.01.300

So what will your suggestion be to debug this issue...?

GNappo · Post by **GNappo** » 08 Jul 2009 9:54

Hi Trainee,

I don't know what your .bat do!

I can suggest you

- to make a test configuring JOB TASK TYPE in "Detached" mode

- upgrade Control-M Agent Fix-Pack to 400

- Modify the following Registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\SubSystems\Windows\SharedSection

The value should be 1024,3072,512

Save this entry and Reboot the machine.

Disclaimer: Modifying the registry can cause serious problems that may require you to reinstall your operating system. I cannot guarantee that problems resulting from modifications to the registry can be solved. Use the information provided at your own risk.

Some additional information:

- Can you please copy and paste Job's log?
- The Control-M Agent is a New Installed Agent?

Best Regards

Giuseppe Nappo

Trainee · Post by **Trainee** » 08 Jul 2009 10:11

The registry key that you created what sort of entry is it :

REG_ZS or ...?

GNappo · Post by **GNappo** » 08 Jul 2009 10:27

Hi Trainee,

the registry key name is WINDOWS and it is REG_EXPAND_SZ but it already exist in system, it should not be created.

Inside this key there are some value, one of this value is "SharedSection".

Following the value of my registry key (only as an illustration of):

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\SubSystems\Windows\

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

Best Regards

Giuseppe Nappo[/b]

GNappo · Post by **GNappo** » 08 Jul 2009 10:48

Hi Trainee,

before you modify Registry Key make sure that the option "Logon as user" is unchecked on the agent side!

Best Regards

Giuseppe Nappo

kylo_h · Post by **kylo_h** » 08 Jul 2009 11:13

GNappo wrote:Hi Trainee,

the registry key name is WINDOWS and it is REG_EXPAND_SZ but it already exist in system, it should not be created.

Inside this key there are some value, one of this value is "SharedSection".

Following the value of my registry key (only as an illustration of):

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\SubSystems\Windows\

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

Best Regards

Giuseppe Nappo[/b]

Hi,

The SharedSection value = 1024,3072,512
The extra ",512" on the end is missing.

Please could you explain what this value actually means.

Thanks.

kylo_h · Post by **kylo_h** » 08 Jul 2009 11:27

Some more info on the issue.

I have a batch schedule consisting of roughly 150 jobs.
They are running on Windows Server 2003, Service Pack2
Agent version: 6.3.01, Fixpack 3 (this is a newly installed agent)

149 of the 150 jobs run without any issues.
This one job in particular fails with the following error in the ctm log:
FAILED TO EXECUTE DUE TO FORK FAILURE
OSCOMPSTAT= -1

GNappo · Post by **GNappo** » 08 Jul 2009 11:38

Hi Kylo_h,

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session
Manager\SubSystems\Windows

SharedSection=1024,3072,512,512 - Default value - allows 28 services MAX
SharedSection=1024,3072,256,256 - Allows me to run 58 Services MAX
SharedSection=1024,3072,128,256 - Allows me to run 120 Services (we
could probably go more than 120, but I stopped here).

This values depending on OS.
After the MAX services running is reached, NO other services (any services - does not have to be a ..NET service) will run under USER context. Services still can be run under the LocalSystem account though. so MAKE SURE THAT THE OPTION "Logon as user" IS UNCHECKED ON THE AGENT SIDE!

For more information see:
http://blogs.msdn.com/ntdebugging/archi ... rview.aspx
http://blogs.msdn.com/ntdebugging/archi ... art-2.aspx

Best Regards

Giuseppe Nappo

kylo_h · Post by **kylo_h** » 08 Jul 2009 1:46

I changed the SharedSection to a higher value as specified above and rebooted the server, still no joy... the jobs still don't execute due to fork failure.

GNappo · Post by **GNappo** » 08 Jul 2009 1:52

Hi kylo_h,

have you verified that the "Logon as user" option is unchecked in the agent configuration?

You can find this option on "WIN CM" tag in "Agent Configuration Management"

Best Regards

Giuseppe Nappo

kylo_h · Post by **kylo_h** » 08 Jul 2009 1:53

Yes, the "Logon as user" option is unchecked.