tibhawkhma is not starting and a NullPointerException error "MachineStatusHandler.timeElapsed" appears in the Hawk log or console output. Also, inappropriate microagents may be in the Hawk log, like the Windows Registry microagent on a UNIX machine.

tibhawkhma is not starting and a NullPointerException error "MachineStatusHandler.timeElapsed" appears in the Hawk log or console output. Also, inappropriate microagents may be in the Hawk log, like the Windows Registry microagent on a UNIX machine.

book

Article ID: KB0092619

calendar_today

Updated On:

Products Versions
TIBCO Administrator -
Not Applicable -

Description

Resolution:

It is likely that a remote machine is connecting the RV daemon on your machine. The tibhawkhma binary on your machine will not start as long as there is one running on the remote machine that has connected to your RV daemon. You need to find the machine that is making the remote connection and stop it from doing so. You can prevent remote daemon connections to your machine by using the following option in your RV daemon: -listen 127.0.0.1


See the Rendezvous Administration manual for more details.

Issue/Introduction

tibhawkhma is not starting and a NullPointerException error "MachineStatusHandler.timeElapsed" appears in the Hawk log or console output. Also, inappropriate microagents may be in the Hawk log, like the Windows Registry microagent on a UNIX machine.