Highlighted
RaphAlv Respected Contributor.
Respected Contributor.
273 views

Unable To Startync Satellite Side

Unable To Startync Satellite Side
today lot of servers could not finish comm tests accordingly
after /etc/init.d/opsware-sas health
wordbot and tsunami got failure status, like:
---
Verify local word is listening on port 1003: FAILURE (Connection refused)
Verify local word is listening on port 1006: FAILURE (Connection refused)
---
Verify tsunami process groups are running: FAILURE (process not running)
Verify tsunami web server is listening on port 8061: (Waiting approx. 10 seconds)
Operation timed out - FAILURE (Connection refused)

gave the satellite a restart, then /var/log/opsware/startup logs are:
>>> Stopping tsunami ...
Stopping tsunami web server... Couldn't determine running PID of tsunami web server.. aborting!
Stopping tsunami application server... Couldn't determine running PID of tsunami application server.. aborting!
>>> Starting mm_wordbot ...
Starting mm_wordbot synchronously
CheckBotUp: Fri Jul 5 17:44:05 2019: Failed to connect to server on :1003
opsware-sas: "mm_wordbot" failed to startsync
Failed to perform "restart" operation on Opsware SAS components.

could even boot the server just in case to a fresh start by /etc/init.d/opsware-sas restart
no luck either, the same output as above...

any suggestions?
BR
Raphael

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.