Fresh Install 6.2.6 – monitor daemon will not start

[Stewart]

Getting the following error when starting the monitord.

[prod:prod:INFO/0:  STARTUP_TID:01/13/2020 16:22:11] Copyright (c) 2019 Infor. All rights reserved.
[prod:prod:INFO/0:  STARTUP_TID:01/13/2020 16:22:11] Infor Cloverleaf(R) Integration Services (monitord) 6.2.6.0P
[prod:prod:INFO/0:  STARTUP_TID:01/13/2020 16:22:11] Linked by root on host=(Linux usspvlclcentos6 2.6.32-696.20.1.el6.x86_64 #1 SMP Fri Jan 26 17:51:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux) at Thu Dec 19 19:41:53 2019 in /u01/cloverrel/cloverleaf/monitord (build 0)
[prod:prod:INFO/0:  STARTUP_TID:01/13/2020 16:22:11] Started at Mon Jan 13 16:22:11 2020
[prod:prod:INFO/0:  STARTUP_TID:01/13/2020 16:22:11] Monitord process is 122081 on host imngr1.arh.org
[prod:prod:INFO/0:_hcimonitord_:01/13/2020 16:22:11] Applying EO config: ”
[moni:moni:ERR /0:_hcimonitord_:01/13/2020 16:22:11] No protocol threads defined!
[moni:moni:ERR /0:_hcimonitord_:01/13/2020 16:22:11] You probably have an empty NetConfig…
[cmd :cmd :INFO/0:_hcimonitord_:01/13/2020 16:22:11] Shutting down command thread _hcimonitord_.
[prod:prod:INFO/0:_hcimonitord_:01/13/2020 16:22:11] Checking for leaked handles in the NCI interpreter…
<No active handles>

[prod:prod:INFO/0:_hcimonitord_:01/13/2020 16:22:11] Checking for leaked handles in the General interpreter…
<No active handles>

 

This is all that is in the NetConfig

 

$ cat NetConfig
prologue
who:        hci
date:       Sun Apr 14 21:40:15 CST 1996
type:       net
version:    3.10
end_prologue

Topic

[James Cobane]

Therein is the issue; you have no thread definitions in NetConfig for the site you are in.  Try starting the monitord in the ‘helloworld’ site (assuming that site was created with the fresh install), as there is a couple of threads pre-built in the helloworld site.

[Keith McLeod]

Do you have a site with threads/connections defined?  The site you are trying to start the monitor daemon on has no threads defined.

Type the command showroot and confirm you are where you want to be.

If not, then setsite <your_site>

and then check again.

[Stewart]

Found the problem.  If you have no threads/processes configured the monitord won’t start.

[Varun Sinha]

Hi,

I am unable to start Monitor Daemon of HelloWorld site.

Server Windows Server 2012 64 bit

 

Following error while killing Daemon

************************************

Command Issued: hcisitectl -k m
Command status: 0
[0:TEST] msiShmemAttach: Can’t create shmem file ‘C:\cloverleaf\cis6.2\integrator\helloworld/exec/monitorShmemFile’: No such file or directory
[0:TEST] msiGlobalInit: Couldn’t attach memory region
hcimonitord is NOT running

Unable to initialize MSI, err = 2

 

Following error while starting Daemon

************************************
Command Issued: hcisitectl -s m
Command status: 255

Starting DB dependency check…

Starting hcimonitord

Can’t connect to the named pipe \\.\pipe\Infor Cloverleaf(R) Integration Services 6.2

 

Need help on it.

 

I have put the license as well as per the Preferred Way (according to infor)
* Make backup of current license.dat file in hciroot/vers
* Put new license.dat file in hciroot/vers
* Bounce hostserver using hciss -k h followed by hciss -s h
* Use hcilicstatus to check information abouut your license.

Need help as what could have gone wrong.

Do let me know if any additional details required.

 

Thanks & Regards,

Varun

[Rob Abbott]

You’re on Windows … is the Cloverleaf service running?  Usually, this error is the result of the service being down:

Can’t connect to the named pipe \\.\pipe\Infor Cloverleaf(R) Integration Services 6.2

Rob Abbott
Cloverleaf Emeritus

[Varun Sinha]

Thanks Rob!

We figured out that Cloverleaf service was not running and as soon as it came up, we were able to start the Monitor Daemon.

 

Thanks Everyone for your valuable input.

Regards,

Varun

[Author]

Replies