1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

BUG?: starting PEM on node requires communication via external IP address to CP

Discussion in 'Plesk Automation' started by GregorL, Nov 9, 2011.

Thread Status:
Not open for further replies.
  1. GregorL

    GregorL Basic Pleskian

    16
    60%
    Joined:
    Oct 24, 2011
    Messages:
    61
    Likes Received:
    0
    Software: MSP new build (1.0.1?)

    Added a node1 using IP External as shared and IP Internal as Exclusive.

    When starting PEM on node1 it hangs for several minutes and then says [FAILED] even though PEM is running.
    under /usr/local/pem/etc I noticed in pleskd.props

    kernel_resolver_ior=corbaloc:iiop:[EXTERNAL MSP CP IP]:8354/ObjectResolver

    plesk seems to want to communicate via external IP with the MSP server.
    When I open the firewall on the MSP CP server the pem service on node one starts immediately.

    I think since I defined the INTERNAL IP for cluster communications during node setup, the node should talk via INTERNAL IP to the INTERNAL IP of the CP Server?
     
  2. Andrew Andriatis

    Andrew Andriatis Regular Pleskian Plesk Team

    23
    57%
    Joined:
    Apr 16, 2009
    Messages:
    431
    Likes Received:
    1
    Hi, GregorL,

    What happens here is that the management node normally installs on an internal IP, and the service nodes point at this IP, which you call EXTERNAL MSP CP IP. In reality it is not external. We configure external https access to this IP for simplicity, just to be operational right out of the box. Full POA installation even keeps this IP open on http access, assuming it is always on the internal network. The external access is configured via branding sites, which have different IPs and URLs, and internally redirect to the management node IP. Later in the project when well introduce branded access, you will see this configuration in MSP as well.
     
Thread Status:
Not open for further replies.
Loading...