Not recognising PCS

Discussion in 'Installation, Update and Configuration' started by KonstantinosS, Jan 15, 2015.

  1. KonstantinosS

    KonstantinosS Mega Poster

    Messages:
    113
    I must have messed with the update of PVA, because the web interface doesn't recognise my installation of PCS, nor its license. It says that VZAgent can't communicate with the server, error 312 (PVA web management node runs ag the moment as a CT, inside PCS).

    Do you guys have a clue on how I should proceed?
     
  2. IP^__^

    IP^__^ Odin Team

    Messages:
    80
    1) What are versions of PVA Agent and MN? (if you updated only PVA MN, for example it is good idea to update PVA Agent)
    2) Is PVA Agent running (# pvaagent status)?
    3) Are you able to send packets to via vzlcon utility (http://kb.odin.com/en/111220)?
    4) Check if all necessary ports are open and you are able to establish connection (http://kb.odin.com/en/9516).
    5) Logs are the good way to troubleshoot the issue as well (http://kb.odin.com/en/6981).
     
  3. KonstantinosS

    KonstantinosS Mega Poster

    Messages:
    113
    Hi IP!

    Thank you for the reply!

    1. I've re-installed PVA using the KB article instructions, so I assume it's the latest one.
    2. PVA Agent is running on PCS, not on PVA (it says: command not found), PVAPP runs on PCS, not on PVA as well.
    3. On PVA the /opt/pva/agent/bin/vzlcon says: no such file or directory, on PCS it produces the following output:
    Code:
    <packet xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="0" priority="0" version="4.5.0">
    <origin>vzclient3285-0e06129b-a3ea-8648-976f-dc0623f06e6e</origin>
    <target>agent</target>
    <data>
    <ok/>
    <eid>0e06129b-a3ea-8648-976f-dc0623f06e6e</eid>
    </data>
    </packet>
    
    4. Ports should not be changed, as I've not messed up with the firewall, and before the update, everything was functioning properly...
     
    Last edited: Jan 16, 2015
  4. IP^__^

    IP^__^ Odin Team

    Messages:
    80
    Can you try to reregister the node in PVA MN (with force)?
    If it will not help than further investigation is needed with enabling debug log level and checking the issue directly.
     
  5. KonstantinosS

    KonstantinosS Mega Poster

    Messages:
    113
    How do I re-register the node with force?? Will it drop my existing containers? (it's a production machine, so I need to be a bit cautious)
     
  6. IP^__^

    IP^__^ Odin Team

    Messages:
    80
    Go to the PVA MN container and execute the command:
    # vzagroup removeSlave --force $IP

    After that in PVA Control Panel:
    New -> Hardware Node:
    Enter the credentials and tick the "Force registration even if Node is already registered in another Server Group".

    It will not drop any of exitsting containers.
     
  7. KonstantinosS

    KonstantinosS Mega Poster

    Messages:
    113
    That worked like a charm! Thanks a million IP!
     

Share This Page