Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does the diagnostic daemon “diagmond” fail to start after I install diagnostics on an NFS diskless cluster?

April 26, 2017cluster daemon diagmond diagnostic Diagnostics diskless fail install NFS

0

Posted

Why does the diagnostic daemon “diagmond” fail to start after I install diagnostics on an NFS diskless cluster?

1 Answer

0

Posted

If you use sam(1M) or swcluster(1M) to install the IPR 9902 or IPR 9904 version of diagnostics on an NFS Diskless Cluster on HP-UX 10.20, some of the required files are not installed in the /var directory of the clients. (If this is the case, a message stating that /var/stm/data/id_mod_xref could not be accessed will be found in the local map log visible using command File -> Administration -> Local UUT Logs -> Map Log .) To fix this problem, log onto the cluster server, and issue the following command for each client. (Replace the string with the name of the client in the directory /export/private_roots/ .