Absent Member.. Absent Member..
Absent Member..
355 views

SA - TIP: Software Repository (SWR) Error on Comm Test

There could be several errors showing up when satellite tries to communicate with core server but if specifically run a communication test against a satellite and receive a SWR error then the next steps should be followed in order to try to resolve that kind of error:

 

1. 404 error


- First check all other components are OK
- Then test word connection from the satellite server

 

telnet 127.0.0.1 3001
CONNECT theword:1003 HTTP/1.0
<enter>

 

Look for a 404 error in the connect. If seen - Check to ensure that nscd is not running or enabled on the satellite server.

 

ps auxwww | grep nscd

 

If nscd service is running, turn it off and disable it.

 

Then restart the satellite components via:

 

/etc/init.d/opsware-sas restart

 

2. Comm Test SWR fail "Server identification error”

 

- First check the Administration Guide there should be some steps to address this issue if doesn't work, here are some other steps to reach it.

- Check the /etc/localtime file the expected result should be:

rwxrwxrwx 1 root root 27 <DATE> /etc/localtime -> /usr/share/zoneinfo/UTC

If this not the result then the time zone to UTC should be restored and then a satellite restart will fix the issue.

Restore the link:

 

# ln -s /etc/localtime /usr/share/zoneinfo/UTC

 

Restart the Satellite. Full restart required since the change is made on OS Level.


3. Comm Test SWR fail "Gateway name resolution error"

 

- Check all servers are UTC & all symlinks are on place.
- Try to restart the server, if the error still present review the following logs from core and satellite.

 

opswgw.log

 

2014-11-28T04:53:33,584.945Z WARN 47282350115136 - ogthreads.cpp:4020 pac_thread: invalid CONNECT string from=127.0.0.1:48530, bailing
2014-11-28T04:56:48,051.302Z WARN 47282140318016 - ogthreads.cpp:2092 resolver_thread: address resolution failed for: theword:1003:

 

From wordbot.log

 

127.0.0.1 - - [27/Nov/2014 09:29:28] [47302785771840] "{Protocol error: crypto mismatch?}" 400 -

 

The problem is that the following two hosts were not properly configured in the /etc/hosts file:

 

<satellite ip> theword
<satellite ip> wordcache

 

To fix it comment out the original ip assignments of the hosts theword and wordcache in the /etc/hosts file.

 

And add the following in /etc/hosts:

 

<satellite ip> theword
<satellite ip> wordcache

 

Finally restart the satellite:

 

/etc/init.d/opsware-sas restart

 

I.e: Actual /etc/hosts:

 

# Begin Opsware Software Repository Cache Hostnames
10.10.10.10 <satellite host>
# End Opsware Software Repository Cache Hostnames
Do not remove the following line, or various programs
that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
10.10.10.10 <satellite host>
11.11.11.11 <core host>


Change it to:


# Begin Opsware Software Repository Cache Hostnames
10.10.10.10 word
10.10.10.10 wordcache
# End Opsware Software Repository Cache Hostnames
Do not remove the following line, or various programs
that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
10.10.10.10 <satellite host>
11.11.11.11 <core host>

 

Regards,

Manfred Monge Muñoz|SW Technical Support Consultant.
Server Automation
Mail | manfred.monge.munoz@hp.com
Hewlett-Packard (SSO Portal)


If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
Labels (1)
Tags (2)
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.