Loading ...
home » spaces » UPS Management Devices & PowerChute Software » discussion » General » ESXi Host containing the Virtual Appliance doesn't shut down

ESXi Host containing the Virtual Appliance doesn't shut down

Discussion in UPS Management Devices & PowerChute Software started by Max , 5/16/2017 6:51 AM
Login  to follow, share, and participate in this space.
Not a member?Join now
  • Julkair
    Max
    Novice
    Novice
    Max 5/16/2017 6:51 AM

    Hello,

    In my configuration, there is a PCNS VA 4.2, two ESXi 6.5 Hosts and a vCenter 6.5

    So far the configuration works, after the correct definition of a shared local user.

    Except, the ESXi Host containing the PCNS VA is not shutting down.

    Log:

    05/15/2017    17:42:20    Shutting down physical machine that PowerChute is running on.
    05/15/2017    17:42:19    Shutting down vCenter Server VM Host 10.0.10.50.
    05/15/2017    17:42:19    Host 10.0.10.50 has successfully entered maintenance mode.
    05/15/2017    17:42:17    Starting Maintenance Mode Task on Host 10.0.10.50.
    05/15/2017    17:38:36    UPS critical event: On Battery resolved on Hosts 10.0.10.50, 10.0.10.51.
    05/15/2017    17:38:36    Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.
    05/15/2017    17:38:36    UPS is no longer running on battery power or output power has been turned on.
    05/15/2017    17:38:16    Maintenance Mode Task cancelled on Host 10.0.10.50 as VCSA VM is shutting down.
    05/15/2017    17:38:15    Shutting down vCenter Server VM VMware vCenter Server Appliance.
    05/15/2017    17:38:15    Exit maintenance mode on Host 10.0.10.50.
    05/15/2017    17:38:15    Exit maintenance mode on Host 10.0.10.51.
    05/15/2017    17:37:30    Shutting down VMs on Host 10.0.10.50.
    05/15/2017    17:37:30    Starting Maintenance Mode Task on Host 10.0.10.50.
    05/15/2017    17:37:30    Shutting down VMs on Host 10.0.10.51.
    05/15/2017    17:37:30    Starting Maintenance Mode Task on Host 10.0.10.51.
    05/15/2017    17:37:29    Shutdown sequence started on Hosts 10.0.10.50, 10.0.10.51 in response to UPS critical event: On Battery.
    05/15/2017    17:37:29    UPS critical event: On Battery.
    05/15/2017    17:35:29    UPS has switched to battery power.

    10.0.10.50 is the Host that contains the vcenter and is shut down.

    10.0.10.51 is the Host that contains the PCNS VA and is not shut down.

    It is shutting the VA down, but not the host containing it.

    I'm sure, that i defined the PCNS "running on VM", but i don't know how to verify it.

    Can you assist me with that?

    Thank you,

    Max

  • wpasquil
    Bill
    =S= Representative
    Bill 5/16/2017 3:33 PM (in response to Max)

    Hi,

    Seem that you have PCNS configured incorrectly.

    On 5/16/2017 2:51 AM, Max said:

    05/15/2017    17:42:20    Shutting down physical machine that PowerChute is running on.

    To verify that PCNS is recognizing the proper host go to Host Protection page in the PCNS web interface and verify the host that PCNS is running on is labeled with the PCNS icon. See page 18 of the User's Guide for an example. 

  • Julkair
    Max
    Novice
    Novice
    Max 5/18/2017 7:00 AM (in response to Bill)

    Hello,

    Thanks for your answer.

    In Host Protection I can see my two ESX Hosts, 1 labeled with the vcenter icon and the other one with the PCNS icon.

    If the vcenter is down, both Hosts are unlabeled.

    PCNS shuts the vcenter down before it shuts down itself.

    Maybe that's the Problem?

    Max

  • wpasquil
    Bill
    =S= Representative
    Bill 5/18/2017 4:52 PM (in response to Max)

    Hi,

    The shutdown process is

    1 - VMs/Vapps are powered down

    2 - vCenter server is powered down

    3 - Hosts are powered down starting with any hosts that do not have PCNS or vCenter Server running on them. Then the host that has vCenter Server is powered down and finally the host that PCNS is running on is powered down. 

    Please attach the error.log and VirtualizationFileStore.properties files that are in /opt/APC/PowerChute/group1 I would like to see if any errors where logged. 

  • Julkair
    Max
    Novice
    Novice
    Max 5/19/2017 6:35 AM (in response to Bill)

    Hi,

    The shutdown process works so far but the last host shutdown.

    Attached are the files you requested.

    I migrated the PCNS VA on the Host with the vCenter, but still the PCNS containing Host doesn't shut down.

    (10.0.10.50 is 10.240.0.150 and 10.0.10.51 is 10.240.0.59)

    PCNS VA has 10.240.0.53

    vCenter has 10.240.0.54

  • wpasquil
    Bill
    =S= Representative
    Bill 5/22/2017 12:26 PM (in response to Max)

    Hi,

    How is your network set up? I see in the FileStoreProperties file 

    10.240.7.150_VMs=Test4,Test5,Test3,Test6,vMA-6.5.0.0-4569350_OVF10
    10.240.7.59_VMs=Test2,Test1

    but you list 10.240.0.53 and 10.240.0.54 It looks like 10.240.7.150 might be 10.240.0.54 is that correct and that would that make 10.240.7.59 to equal 10.240.0.53?

    Also, did you look at the error log? There are many entries for connection refused and no route to host. Connection refused looks like a permissions issue and no route to host would be a networking issue.  

  • Julkair
    Max
    Novice
    Novice
    Max 5/22/2017 2:08 PM (in response to Bill)

    Hi,

    ESX1 10.240.0.59

    ESX2 10.240.0.150

    PCNS VA 10.240.0.53

    vCenter 10.240.0.54

    The PCNS VA can always reach the other host to shut down, but not its own. Doesn't matter on which host the VA is placed (ESX1 or 2).

    So I believe it's neither a network problem nor a rights problem.

  • wpasquil
    Bill
    =S= Representative
    Bill 5/23/2017 2:55 PM (in response to Max)

    Hi,

    Please stop the PCNS service (service PowerChute stop) and edit the log4j2.xml that is in /opt/APC/PowerChute/group1 and put PCNS into debug mode (see FAQ FA230514 for assistance). After putting PCNS into debug mode rename error.log to saverror.log and rename eventlog.txt to saveventlog.txt. Also open VirtualizationFileStore.properties and delete any entries that may be in there and save the file. Then restart PCNS and run a shutdown test. Once the test is completed after PCNS has restarted stop PCNS and take it out of debug mode, make copies of eventlog.txt, error.log, and VirtualizationFileStore.properties and attach them to you post. Then restart PCNS. 

    I will review the logs and file.

  • Julkair
    Max
    Novice
    Novice
    Max 20 days ago (in response to Bill)

    Hi,

    I had a lot of stuff going on the last days.

    Here are the logs, I needed to take away the second ESXi Host, so it is just 1 Host for testing, but still the single ESXi Host will not shut down at the end.

    Thanks for reviewing

  • wpasquil
    Bill
    =S= Representative
    Bill 20 days ago (in response to Max)

    max,

    Please attached the pcnsconfig.ini file that is in /opt/APC/PowerChute/group1. 

    Thanks,

  • Julkair
    Max
    Novice
    Novice
    Max 19 days ago (in response to Bill)

    Hi Bill,

    it is attached

    Max

    Attachments
  • wpasquil
    Bill
    =S= Representative
    Bill 18 days ago (in response to Max)

    Hi Max,

    The pcnsconfig.ini file is incomplete / truncated. There are 2/3 of the entries missing. I have attached a copy of a complete / full .ini file.

    This .ini file is from PCNS 4.2 appliance configured for vCenter Sever. If you look at the bottom of the file you will find the VMware entries.

    If the one in you system is incomplete you can edit the attached to match your needs and copy it to the appliance. Once edited stop the PCNS server on the appliance (command is service PowerChute stop), move the old .ini file to /opt/APC/PowerChute (command is mv pcnsconfig.ini /opt/APC/PowerChute), copy the edited file to /opt/APC/PowerChute/group1 (I use a FTP application to copy files between the appliance and my laptop) and then restart the service (command is service PowerChute start) 

    Attachments
  • Julkair
    Max
    Novice
    Novice
    Max 18 days ago (in response to Bill)

    Hi Bill,

    I found the answer in the .ini file:

    My first question:

    I'm sure, that i defined the PCNS "running on VM", but i don't know how to verify it.

    Can you assist me with that?

    Was the correct question.

    In the .ini file of me, the value was isPCNSonVM = false (but the image of the PCNS was next to the ESX Host in Host Protection)

    (The Rest of the file was missing, because I copy pasted it from putty and forgot the other lines, because WinSCP wouldn't work)

    Thanks for your assistance,

    Max

  • wpasquil
    Bill
    =S= Representative
    Bill 18 days ago (in response to Max)

    Max,

    The .ini file should read isPCNSonVM = true

  • Page 1 of 1 (14 items)
Choose your language:  English  
powered by Communifire
Version 5.0.5741.40378