Monthly Archives: November 2015

vCOPs: Error 500 The call failed on the server; see server log for details (StatusCode: 500)

Error 500 is rather annoying and quite generic “catch-all” error handler  for Web servers. VROPS is no different in this context.

In this blog , I aim to resolve one of the conditions with Analytics component of VROPS . Check if the symptoms and logs are relevant before you go ahead with the steps.


1- Login through ssh to the admin page of vrops


2- Check the status of all the services


In this case you observe that VCOPS Manager Service & Analytics Service stopped

3-This issue may also manifest as below , but you have not changed the ip address of either of the VMs(UI or Analytics)

The UI VM running at <IP address> but cannot to the Analytics VM at <IP address >, make sure it is running and reachable from <IP address> If the IP address of either VM has changes, then login to Administration interface that will guide you through the steps to restore connectivity between the two VMs.


4- Check logs $ALIVE_BASE/user/log/analytics.log

2015-11-12 16:38:41,225 ERROR [Thread-1] com.integrien.alive.dbaccess.AnalyticsFastLoaderCache.loadActiveAlarmsNative – Error while loading active alarms org.postgresql.util.PSQLException: PANIC: checksum mismatch: disk has 0x41ea3421, should be 0xda4b0281 filename pg_tblspc/16385/PG_9.0_201106101/16386/16435, BlockNum 171234, block specifier 16385/16386/16435/0/171234

2015-11-12 16:38:42,245 INFORMATION [Thread-1] – Analytics is stopping
2015-11-12 16:38:42,265 INFORMATION [Thread-1] – AnalyticsService has been stopped  

If these symptoms match, proceed to the next steps,

Root cause : For some reason the postgres db used by the analytics engineer encountered an error and needs you to correct it.


1- Login to Analytics VM

2- Connect to the DB

su postgres

3- Execute ” pg_ctl” stop -m smart -D /data/pgsql/data

** Force it using immediate switch if required/previous command errors out

4- Execute the following command and replace bolded text with the actual tablespace/database/relation/fork/blockNum recorded in analytics log

postgres –single -D $PGDATA -c fix_block_checksum= “16385/16386/16435/0/171234″

This should return with an message as ” ..* fixed”

5- pg_ctl start -D /data/pgsql/data

6- Go ahead and restart the vcops services

Happy Monitoring …


A Network Virtualization fairy tale . . .

I recently had the opportunity to co-present at vForum Singapore 2015 along with Al Da Silva from Juniper on the topic – “Smart Software is Indispensable, Smart Networking Hardware is Fundamental”

The flow of the presentation starts with the Value of SDDC and why it is the way forward.

We then provided a basic overview of what NSX is all about, while at it we also debunked some questions and myths around Network Virtualization such as , “Are we replacing Network hardware through NSX ?” or “Are the network engineers’ career doomed !!!”

Not really, to understand better draw a parallel of what was done in the Server Virtualization space. We consolidated x86 servers into more powerful hardware and enabled phenomenal features like vMotion, HA , DRS that transformed the way servers were managed.

By doing so we met the following objectives – Capex/Opex reduction, better resiliency, better operations management and automation capabilities and most importantly we delivered IT as a Service in the most optimal, efficient and rapid pace.

Very similarly from a networking standpoint, we want to be able to implement Network & Security Services such as load balancing, firewall, switching & routing from the software layer to accomplish the same objectives. We obviously are not getting rid of the physical networking gear, we actually need the IP backplane to be able to scale and optimize to meet the requirements of a Software Defined Networking.

We got into more details as we spoke about the convergence of Overlay and Underlay networks. We discussed tunneling as an example to demonstrate how different VxLAN replication modes require the physical network to be configured in a certain way to be able to build a robust L2 over L3. Juniper is able to provide “Single Switch management ” capabilities via Virtual Chassis Fabric. This is being positioned as the ideal fabric layout for the SDDC.

We then delved into how SDDC created newer challenges that were non-existent in conventional datacenter, for instance in a multi-tenant cloud how we cannot allow IP workloads run adjacently i.e. on the same ESX host without sufficient protection. This obviously requires security at the Virtual NIC level. With Micro-segmentation we are able to achieve just that, traffic is intercepted and governed even before it hits the “Virtual Wire”.

My favorite part of the session was the Management integration,VROPS NSX Management Pack together with Juniper Network Director provide amazing management and monitoring capabilities. For instance a drop down menu has a list of overlay identifiers(VNI), at the click of the VNI we can see all the VM’s running across various different hosts and their datapaths. Troubleshooting made easy isn’t it.

I’ve attached the presentation deck for your reading pleasure, it’s mostly self explanatory, but obviously not the same as being part of the live session.

If there is any ambiguity, drop me a note –


..a true fairy tale in the technology arena