Environment
Privileged Account Manager
Situation
Unable to connect to Update Channel in Package Manager
The following browser dialog error may appear: Failed to connect to server :443
Proxy Host field has been configured at least once previously
The old proxy host value is not being reset
Removing Proxy Host doesn't resolve the issue as a <NULL> or blank value is saved instead
Can't connect to Update Channel once proxy has been configured previously
The following appears in the unifid.log:
Error, Failed to connect to :443
Info, pkgman listAvailable client:localhost user:admin@<PAM-Manager-Server>(<IP-Address>) rc:0 status:500(Failed to connect to server: :443) (4ms)
The following browser dialog error may appear: Failed to connect to server :443
Proxy Host field has been configured at least once previously
The old proxy host value is not being reset
Removing Proxy Host doesn't resolve the issue as a <NULL> or blank value is saved instead
Can't connect to Update Channel once proxy has been configured previously
The following appears in the unifid.log:
Error, Failed to connect to :443
Info, pkgman listAvailable client:localhost user:admin@<PAM-Manager-Server>(<IP-Address>) rc:0 status:500(Failed to connect to server: :443) (4ms)
Resolution
A fix has been released in PAM 3.1.0.1 or later. Please refer to the Cause section below for an explanation. This particular issue would only occur if proxy was previously configured and then later removed by attempting to clear the configuration.
The following can be used as a workaround to reset corrupt Package Manager Settings:
The following can be used as a workaround to reset corrupt Package Manager Settings:
- On the Manager server, please navigate to /opt/netiq/npum/service/local/pkgman
- Enter the pkgman database:
sqlite3 pkgman.db - List the available tables:
.table
Note: Please verify PackageSource is available in this list to confirm you are in the correct database. - Remove the PackageSource table:
delete from PackageSource; - Exit the db:
.exit
Cause
Proxy Host field in the Package Manager Settings is not cleared in the DB properly even after removing the value.
Additional Information
If the above does not resolve this issue, please contact Customer Care.
The following appears in the unifid.log with DEBUG logging:
Debug, spf_peer connect :443
Error, Failed to connect to :443
Warning, Failed to receive package list from https://nu.novell.com/PUM/packages/Module/package.idx 500(Failed to connect to server: :443)
Debug, spf_peer connect :443
Warning, Failed to receive package list from https://nu.novell.com/PUM/packages/Engine/package.idx 500(Failed to connect to server: :443)
Debug, spf_peer connect :443
Warning, Failed to receive package list from https://nu.novell.com/PUM/packages/Console/package.idx 500(Failed to connect to server: :443)
Debug, spf_peer connect :443
Warning, Failed to receive package list from https://nu.novell.com/PUM/packages/Patch/package.idx 500(Failed to connect to server: :443)
Info, pkgman listAvailable client:localhost user:admin@<PAM-Manager-Server>(<IP-Address>) rc:0 status:500(Failed to connect to server: :443) (4ms)
The following appears in the unifid.log with DEBUG logging:
Debug, spf_peer connect :443
Error, Failed to connect to :443
Warning, Failed to receive package list from https://nu.novell.com/PUM/packages/Module/package.idx 500(Failed to connect to server: :443)
Debug, spf_peer connect :443
Warning, Failed to receive package list from https://nu.novell.com/PUM/packages/Engine/package.idx 500(Failed to connect to server: :443)
Debug, spf_peer connect :443
Warning, Failed to receive package list from https://nu.novell.com/PUM/packages/Console/package.idx 500(Failed to connect to server: :443)
Debug, spf_peer connect :443
Warning, Failed to receive package list from https://nu.novell.com/PUM/packages/Patch/package.idx 500(Failed to connect to server: :443)
Info, pkgman listAvailable client:localhost user:admin@<PAM-Manager-Server>(<IP-Address>) rc:0 status:500(Failed to connect to server: :443) (4ms)