For those of you deploying Log Insight on vCloud Director (VCD) I wanted to point out a couple gotchas to be aware of. Read on to learn more.
I was recently asked to assist in configuring a wildcard SSL certificate on a pair of vCloud Director (vCD) cells. While the certificate had been installed on the cells, some browsers were displaying SSL errors such as the following:
|While other browsers appeared to work:||Until you drilled down a little further:|
In addition, while uploading/downloading VMs SSL errors like the following were displayed:
So what was going on and how can it be fixed?
vCloud Director (vCD) is a great application for its first iteration and I expect great things from it in the future. Like any application, it has its fair share of issues and if only for my own edification, I figured I would document some issues I have experienced and the resolutions or workaround I have found. As I find more, I will update this post.
For those of you with an active dpeloyment of VMware’s vCloud Director (vCD) or those looking into deploying it, I would like to point out an important thing to check on your Red Hat vCD cells. From: http://www.vmware.com/support/vcd/doc/rel_notes_vcloud_director_101.html
“Too many open files” errors
vCloud Director can require high open file limits. Make sure that every cell in your vCloud Director environment allows processes to open more than 1024 files. To see what the current limit is for a cell, log in to the cell, and type ulimit -n. If it says 1024 or less, then take the following steps to increase the open files limit:
- Type su -.
- Edit /etc/security/limits.conf and make sure it includes the following lines:
* soft nofile 65535
* hard nofile 65535
- Edit /etc/pam.d/login to include the following line:
session required pam_limits.so
- Type the following command to restart the cell:
service vmware-vcd restart
- Log out of the cell and log back in.
- Type ulimit -n to verify your changes.