Adding a windows service node

Discussion in 'Plesk Automation Suggestions and Feedback' started by VaggelisG, Aug 16, 2013.

  1. VaggelisG

    VaggelisG Bit Poster

    Messages:
    3
    Good Morning,
    We are evaluating ppa for our hosting infrastructure here and I am fasing the following error when adding a windows IIS node.
    The Poa agent install OK the error appears on task Install additional packages on node <node> according role PPA_IIS
    The error is:
    ERR [1:8525:f5565b90:260 1:8500:f57cbb90 lib]: [txn:185 task:468 FILEOPS] ExSystem: module_id:'HCL', ex_type_id:'1101',Message:'Destination host 'webcpw-test01' (#16), IP '172.31.120.247' : createTextFile /admin/conf/agent_certificate.pem: No such file or directory (errno 2).', deprecated_codes = (0, 0), properties = { errno: '2',reason: 'No such file or directory',operation: 'createTextFile',op_target: '/admin/conf/agent_certificate.pem', }

    Taken from /var/poa.log

    The details Are:
    PPA Version: 11.1 Update #13
    Windows 2008R2 (activated)
    IIS Role is installed
     
  2. IgorG

    IgorG Guru

    Messages:
    19,081
    Have you tried to check this Service Node with help of command:

    # /usr/local/ppa/bin/check_service_node --ip IP_OF_SERVICE_NODE
     
  3. VaggelisG

    VaggelisG Bit Poster

    Messages:
    3
    Good morning Igor,
    the out put of the tool is:

    [19 Aug 2013 09:39:02 EEST][INFO] The service node is registered in PPA with hostId = 16
    [19 Aug 2013 09:39:02 EEST][INFO] Start checking the service node (OS: 'Windows', IP address: 'x.y.z.y', username: 'Administrator')

    [19 Aug 2013 09:39:03 EEST][INFO] Checking the operating system version running on the service node...
    [19 Aug 2013 09:39:04 EEST][INFO] [OK]

    [19 Aug 2013 09:39:04 EEST][INFO] Checking whether the system time is synchronized between the service node and the management node...
    [19 Aug 2013 09:39:11 EEST][INFO] [OK]

    [19 Aug 2013 09:39:11 EEST][INFO] Checking whether DNS is configured on the service node...
    [19 Aug 2013 09:39:14 EEST][INFO] [OK]

    [19 Aug 2013 09:39:14 EEST][INFO] Checking whether there is enough disk space on the service node...
    [19 Aug 2013 09:39:16 EEST][INFO] [OK]

    [19 Aug 2013 09:39:16 EEST][INFO] Checking whether WinRM is installed...
    [19 Aug 2013 09:39:17 EEST][INFO] [OK]

    [19 Aug 2013 09:39:17 EEST][INFO] Checking whether the IIS and IIS components are installed...
    [19 Aug 2013 09:39:18 EEST][INFO] [OK]

    [19 Aug 2013 09:39:18 EEST][INFO] Checking whether a valid SSL certificate is installed...
    [19 Aug 2013 09:39:18 EEST][INFO] --retrieving the SSL certificate...
    [19 Aug 2013 09:39:23 EEST][ERROR] Unable to find an SSL certificate by connecting to the port 8443. Please determine the service that is listening on the port 8443 and resolve the issue

    [19 Aug 2013 09:39:23 EEST][INFO] Checking connection from the service node to the management node...
    [19 Aug 2013 09:39:25 EEST][INFO] Checking whether the service node uses its communication IP address for connections to the management node. Trying to establish connection from the IP address:'172.31.120.247', port:'51618' (service node) to the IP address:'x.y.z.y', port:'51618' (management node).
    [19 Aug 2013 09:39:28 EEST][INFO] Checking connection from the service node to the IP address '172.31.120.244', port '80'
    [19 Aug 2013 09:39:30 EEST][INFO] Skipping ports ('8352, 8354, 8356, 8360, 8362, 8364, 8412, 8490, 8532') checking as the service node is already registered in PPA and the 'pem' service is up and running
    [19 Aug 2013 09:39:30 EEST][INFO] [OK]

    [19 Aug 2013 09:39:30 EEST][INFO] Checking connection from the management node to the service node...
    [19 Aug 2013 09:39:32 EEST][INFO] Checking whether the management node uses its communication IP address for connections to the service node. Trying to establish connection from the IP address:'172.31.120.244', port:'51619' (management node) to the IP address:'x.y.z.a', port:'51619' (service node).
    [19 Aug 2013 09:39:35 EEST][INFO] Skipping ports ('8352') checking as the service node is already registered in PPA and the 'pem' service is up and running
    [19 Aug 2013 09:39:35 EEST][INFO] Skipping ports ('8354') checking as the service node is already registered in PPA and the 'pem' service is up and running
    [19 Aug 2013 09:39:35 EEST][INFO] Checking connection from the management node to the IP address x.y.z.y', port '8443'
    [19 Aug 2013 09:39:37 EEST][INFO] [OK]

    [19 Aug 2013 09:39:37 EEST][INFO] Checking whether Windows Firewall is running on the service node...
    [19 Aug 2013 09:39:38 EEST][INFO] [OK]

    [19 Aug 2013 09:39:38 EEST][INFO] Checking whether communication between the registered service node and management node is possible through the 8352 and 8354 ports...
    [19 Aug 2013 09:39:45 EEST][INFO] [OK]

    [19 Aug 2013 09:39:45 EEST][CRITICAL] This node FAILED to meet some of the PPA requirements. Please correct all the errors and run the tool again
    [19 Aug 2013 09:39:45 EEST][ERROR] The following errors were detected:
    [19 Aug 2013 09:39:45 EEST][ERROR] - Unable to find an SSL certificate by connecting to the port 8443. Please determine the service that is listening on the port 8443 and resolve the issue



    As you can see it reports something related to an ssl certificate.

    How can it find the plesk daemon if it has not yet been installed?
    From my understanding it requests access to a port (8443) designated for pleskd access but initial installation installs only the POA agent.
     
    Last edited: Aug 18, 2013
  4. VaggelisG

    VaggelisG Bit Poster

    Messages:
    3
    Is there no answer?
     
  5. IgorG

    IgorG Guru

    Messages:
    19,081
    Let me explain a little bit.
    On port 8443 should be installed second agent, in addition to pleskd. During installation SSL certificate should be generated and assigned to this port. Your initial error is really related to problem with installation of this second agent.
    Logs should be deeply investigated directly on servers. Therefore I strongly recommend you contact Support Team.
     

Share This Page