Article ID: 117615, created on Sep 30, 2013, last review on Dec 20, 2015

  • Applies to:
  • Plesk Automation 11.1
  • Plesk Automation 11.5

Symptoms

  1. It is not possible to add a Service Node. The task fails with the following error:

    Destination host 'node.example.com' (#12), IP '10.10.0.3' : Unable to establish connection with the node #12
    
  2. It is not possible to update the DNS zone records. The task Update named ns1.example.com fails:

    Destination host 'ns1.example.tld' (#11), IP '10.10.0.4' : Unable to establish connection with the node #11
    
  3. A Parallels Plesk Automation update fails with the following error:

    ERROR [pingHost] ExSystem: module_id:'HostManager', ex_type_id:'515',Message:'Destination host 'ppa-service.node.tld' (#3), IP '1.2.3.4' : Unable to establish connection with the node #3.', deprecated_codes = (0, 0), properties = { host_id: '3', }
    

    Or:

    [LOGTEE]: Failed to ping host ppa-service.node.tld (3): ['/usr/local/pem/bin/pleskd_ctl', '-f', '/usr/local/pem/etc/pleskd.props', 'ping', '3'] exited with non-zero status 1
    
  4. /usr/local/ppa/bin/ppa_update --install-updates returns errors like:

    [ERROR]: Failed to connect to the agent on the host server1.ppa.com (29): ['/usr/local/pem/bin/pleskd_ctl', '-f', '/usr/local/pem/etc/pleskd.props', 'ping', '29'] Please check that PPA agent (the "pem" service) is running and that the node is accessible.
        [ERROR]:
        Unable to check the availability of registered hosts in PPA.
        Check the following hosts:
                * The host server1.pa.com is not available: make sure it is up and POA agent (the "pem" service) is running there.
    

Cause

  1. The error is caused by network issues between the Management and Service Nodes.

  2. Pem Agent is not running on a Service Node.

Resolution

  1. Run the check_service_node script from the Management Node to find and fix potential issues:

    # /usr/local/ppa/bin/check_service_node --ip 10.10.0.4
    
  2. When all issues reported by the check_service_node script are fixed, re-run the failed tasks.

  3. Make sure that Pem Agent is running on the Service Node. If the service has stopped, start it with:

    # /etc/init.d/pem status
    pleskd is running
    

Search Words

Update failed + node is inaccessible

The host is not available: make sure it is up and POA agent (the "pem" service) is running there.

DNS host not functioning

upgrade failed, need assistance

Install MU#2

Update installation fails

Contact Node

Unable to establish connection

DNS changes not propagating to slave nameservers

Installation of PPA 11.5.5

nameserver communication issue

Reason: '[Errno 111] Connection refused'

nable to establish the communication. It is possible that the 'pem' service is not running or that the required ports are closed

Install Update#3

Unexpected error: 'PPAUpdater' object has no attribute '_checkDmsScript'

PA Update 20 problem

e0aff7830fa22f92062ee4db78133079 c1ecc6010feff26cb42d1d14a7881dd6 33a70544d00d562bbc5b17762c4ed2b3 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF