Autoreaction doesn't work from client 000 but works from other clients

Question

Autoreaction doesn't work from client 000.
More details coming.   Having trouble getting the thread to post.

Answer 1

We set up a new local auto-reaction.   This is not a central auto-reaction.  The auto-reaction writes a
message to the UNIX system log /var/adm/messages when a "Security"
alert i.e. - Logon, RFCLogon, TransactionStart, etc.  occurs.
The RZ20 alerts are being properly generated and can be seen in both
the CEN system and the local system. On the local system if I view
all alerts for the MTE using transaction RZ20 and select one of the
alerts and choose Edit -> Nodes ( MTE ) -> Start methods -> Start auto-
reaction method. The auto-reaction writes the message to the UNIX
system log. If I execute the same procedure in client 000 nothing is
written to the UNIX system log.
I've also tried triggering a new alert and running SAPMSSY8 from SE38
while the alert is still in status ACTION_REQUIRED. If I do this from
client 010, an entry is written to the unix system log. If I do this
from client 000, nothing is written to the unix system log. In both
cases, the status of the alert changes from ACTION_REQUIRED to ACTIVE.
Since the System Cyclic program ( SAPMSSY6 ) that triggers SAPMSSY8
always runs in client 000, the auto-reaction never writes the messages
to the UNIX system log.
I have been working on this issue for days.  There are several posts and notes relevant to a similar situation with e-mail alerts that are not working from client 000 because SAPCONNECT is not set up in client 000.   However, this auto-reaction does not send an e-mail, so SAPCONNECT set-up should not be necessary.   I've searched Service Marketplace and could not find any notes that resolved the problem either.  
I've also checked CCMS Self-Monitoring and cannot find any alerts or errors relevant to this problem.
Does anyone know why the auto-reaction only works from a client other than client 000?
Best regards,
Dave