Today I’ve found a little failure within our production environment.
We use icinga to monitor our production lan, its guests and services. For our Citrix XenApp servers we check the uptime to get notified if they are running to long without reboot.
After we upgrade several servers to vmx-10 everything works fine. Icinga reports all services and performance charts correctly. Now, two days later, the first uptime alerts came up. But the system boot time was only a few hours ago and not two days…
If we power off and power up the machine the uptime does reset.
The counter didn’t reset if the machine is only warm rebooted.
In my previous posts I wrote about the upgrade of vCSA (vCenter Server Appliance) from version 5.5 to 6.0.
In all my lab testing the upgrade runs without any errors. On our production site I was doing the upgrade and the migration went fine until the new appliance boots for the first time.
The services start all until the vPostgres database starts. Something in the upgrade script gives back an error. Installation abort and I must boot the old vCSA 5.5.
VMware closed my call, because of an unsupported way getting vCenter Server for Windows to the vCSA 5.5. Everything runs in the vCSA 5.5. The upgrade fails and with the migrated database there is no support.
In this articel I would like to do the initial configuration for a Windows Server 2008 Core installation.
After a pretty easy installation the “Welcome” screen appears.