Framework error: code: E_COULDNT_CONNECT (7) reason: Failed to connect to localhost port 1008 after 0 ms: Connection refused (Doc ID 2886130.1)

Last updated on FEBRUARY 19, 2024

Applies to:

Symptoms

Any pkg subcommand in a non-global zone that tries to retrieve data from the repositories returns "Connection refused" error, e.g.

# pkg list -af entire

pkg: 0/6 catalogs successfully updated:
1/1 repositories for publisher '{PUBLISHER}' could not be refreshed.
Unable to contact valid package repository: http://{IP_ADDRESS}:{PORT}/IPS/
Encountered the following error(s):
Framework error: code: E_COULDNT_CONNECT (7) reason: Failed to connect to
localhost port 1008 after 0 ms: Connection refused
URL: 'http://{IP_ADDRESS}:{PORT}/IPS/' (happened 4 times)

# pkg update java-8-incorporation

Errors were encountered while attempting to retrieve package or file data for
the requested operation.
Details follow:

pkg://solaris/consolidation/java-8/java-8-incorporation@1.8.0.341.10,5.11-0:20220707T174426Z
Framework error: code: E_COULDNT_CONNECT (7) reason: Failed to connect to localhost port 1008 after 0 ms: Connection refused
URL: 'http://{IP_ADDRESS}/manifest/0/consolidation%2Fjava-8%2Fjava-8-incorporation@1.8.0.341.10%2C5.11-0%3A20220707T174426Z' (happened 4 times)

# pkg install jdk-8

Errors were encountered while attempting to retrieve package or file data for
the requested operation.
Details follow:

pkg://solaris/runtime/java/jre-8@1.8.0.333.2,5.11:20220428T210149Z
Framework error: code: E_COULDNT_CONNECT (7) reason: Failed to connect to localhost port 1008 after 0 ms: Connection refused
URL: 'http://pkg.oracle.com/solaris/support/manifest/0/runtime%2Fjava%2Fjre-8@1.8.0.333.2%2C5.11%3A20220428T210149Z' (happened 4 times)

The truss output shows the connect system call returning EADDRNOTAVAIL error:

# truss -vall -tconnect pkg list -af entire
..
18505: 4.707274 0.000054 0.000024 connect(8, 0xFFFFFD4797E7EF00,32, SOV_XPG4_2) Err#126 EADDRNOTAVAIL
18505: AF_INET6 name = ::1 port = 1008
18505: scope id = 0 source id = 0xd
18505: flow class = 0x00 flow label = 0x00000
..

Another indirect symptom or side effect of this issue is that if you update the publisher in the global zone the publisher in the non-global zones doesn't change so the publisher in the non-global zones and global zones won't be longer in sync.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.