I found this error last week during a deployment in a customer. The vCenter Infrastructure Navigator appliance does not maintain its configured hostname after a reboot, it gets reset to the default localhost.localdom value.
Setting it again in the administration web interface doesn’t solve problem, it will be lost again after the next reboot.
The problem is in the vami_set_hostname script, it has a HOSTNAME variable set to localhost.localdom and if it fails to make the reverse lookup of the hostname from the IP address using the host command it will be set to the default value.
To fix this edit that file, it can be found on /opt/vmware/share/vami, and set the value of the variable to your hostname. After that reboot the appliance to check that everything works as expected.
I thought it would be worthy to write a quick post to show the script I’ve been using to create CBM databases in customers installations. The original script wasn’t mine, honestly I don’t know who wrote it, and I’ve modified it to suit my needs.
Just remember to adjust the path of the files, its size, the usernames and password to your environment standards. Hope you find it helpful.
use [master] GO CREATE DATABASE [CBDB] ON PRIMARY (NAME = N'CBDB', FILENAME = N'E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\CBDB.mdf' , SIZE = 200000KB , FILEGROWTH = 10% ) LOG ON (NAME = N'CBDB_log', FILENAME = N'E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\CBDB.ldf' , SIZE = 20000KB , FILEGROWTH = 10%) COLLATE SQL_Latin1_General_CP1_CI_AS GO use [CBDB] GO ALTER DATABASE [CBDB] SET SINGLE_USER WITH ROLLBACK IMMEDIATE; ALTER DATABASE [CBDB] SET ALLOW_SNAPSHOT_ISOLATION ON; ALTER DATABASE [CBDB] SET READ_COMMITTED_SNAPSHOT ON WITH NO_WAIT; ALTER DATABASE [CBDB] SET MULTI_USER; GO use [CBDB] CREATE LOGIN [cbdbAdmin] WITH PASSWORD = 'VMwarerocks!', DEFAULT_DATABASE = [CBDB], DEFAULT_LANGUAGE =[us_english] GO ALTER LOGIN [cbdbAdmin] WITH CHECK_POLICY = OFF GO CREATE USER [cbdbAdmin] for LOGIN [cbdbAdmin] GO ALTER USER [cbdbAdmin] WITH DEFAULT_SCHEMA =[DBO] GO sp_addrolemember [db_owner], [cbdbAdmin] GO if not exists (SELECT name FROM sysusers WHERE issqlrole=1 AND name = 'cbAdminRole') CREATE ROLE [cbAdminRole]; GRANT ALTER ON SCHEMA :: [DBO] to [cbAdminRole]; GRANT REFERENCES ON SCHEMA :: [DBO] to [cbAdminRole]; GRANT INSERT ON SCHEMA :: [DBO] to [cbAdminRole]; GRANT CREATE TABLE to [cbAdminRole]; GRANT CREATE VIEW to [cbAdminRole]; GRANT CREATE Procedure to [cbAdminRole]; GRANT ALTER ON SCHEMA :: [DBO] TO [cbAdminRole] GRANT REFERENCES ON SCHEMA :: [DBO] TO [cbAdminRole] GRANT INSERT ON SCHEMA :: [DBO] TO [cbAdminRole] GRANT SELECT ON SCHEMA :: [DBO] TO [cbAdminRole] GRANT DELETE ON SCHEMA :: [DBO] TO [cbAdminRole] GRANT UPDATE ON SCHEMA :: [DBO] TO [cbAdminRole] GRANT EXECUTE ON SCHEMA :: [DBO] TO [cbAdminRole] GRANT ALTER ANY DATASPACE TO [cbAdminRole] GRANT CREATE TABLE to [cbAdminRole] GRANT CREATE VIEW to [cbAdminRole] GRANT CREATE PROCEDURE to [cbAdminRole] GRANT CREATE FUNCTION TO [cbAdminRole] GO sp_addrolemember [cbAdminRole] , [cbdbAdmin] GO
After the previous article about SSL certificate generation in Chargeback I decided that it was worth to write a couple more tips in a second blog post. This is not a “how to install…” or “how to configure…” post. There are other bloggers in the community that have written about it before so I believe there is no point on repeating the same.
At one point the CBM installer will ask for the database details, apparently nothing to worry about. Except for the following:
- Port: It says is optional but if you don’t enter the port the connection will fail. The default port is 1433 but of course fill it with the value from your installation.
Adding a vCenter Server
The first task you want to perform after Chargeback installation is to add a vCenter Server, in theory pretty easy until you get to the database screen. It is very important to remember that in the Database URL field you only need to put the database server IP address as shown in the screen capture.
This year edition of VMworld Europe 2013 is gone. For second time it was held in Barcelona, one of most beautiful cities of Spain, and for the second time I was there to enjoy a great week… and what a week.
If you weren’t under a rock during last week you are probably aware of the announcements in the cloud management space, with new upcoming releases for vC Ops, ITBM and vCAC just to name some. Or the announcement of VMware NSX going GA and the tech preview of vSAN.
Regarding the announced vCAC 6.0 the attendees had a glimpse of its awesomeness in the Hands-on Labs since the HOL-SDC-1321 lab was based on 6.0 Beta bits. vCAC 6.0 was also featured in a very well executed keynote by Kit Colbert and our EMEA CTO Joe Baguley on Wednesday morning, showing from all the new features in the portal to the integration with VMware vCHS and other public cloud providers.
I am genuinely excited about this new vCloud Automation Center release and will come back with more articles about my experience with it in the future. In the meantime my friend and colleague Omer has done a nice article in his blog Elastic Skies about what’s new.
But that’s only one side of the coin, for me the most important aspect of VMworld is the Community. This is the only time of the year I have the opportunity to hang face to face with many of the people I already consider my friends, this is I’m not sales, marketing or social media, I am a consultant as you all know and that means that I’m always in the field doing engagements for customers and having lots of fun of course but that leave me no time or even the chance to attend tech conferences… besides VMworld :-)
And this year has been AWESOME!
I had again the opportunity of attending several parties. Parties are always sponsored by several companies, like Cisco, EMC or Simplivity, but in some of them the sense of community is omnipresent.
Take the vRockstar Party for example, held on Sunday evening at the Hard Rock Cafe. That really was a community event, the perfect moment to share a few beers (more than a few actually ;D) a good conversations and strength your friendship with the other members of the community. Or the GeekFest on Tuesday night, again at the Hard Rock and sponsored by EMC, Cisco and VMware. Oh man that party was really great with amazing food and beer and many many friends from all around the world there.
But for me the best example this year was the #BeerTweetup organized by Hans De Leenheer (@HansDeLeenheer) and sponsored by Simplivity. IMHO that was a true community event, no marketing, no vendor swag, just good Belgium beer, great talking and good company.
But hey it wasn’t all about the parties, at least no during the night you know, seriously parties are amazing but it was the only part of the fun. During all day, for three days, some of the most active and prominent members of the VMware community were spreading the word in the Community Lounge. I’m taking about the guys of #vBrownbag or James Bowling (@vsential) and his Operation: Through my eyes series of videos or Craig Waters (@cswaters1) who interviewed many other vExperts for his blog.
Also for me this VMworld has been very special since I had the opportunity to contribute to the community besides of this blog, and of my awesome drinking skills of course ;D My friend Amy Lewis (@CommsNinja) finally manage to got me into her video podcast Engineers Unplugged, Amy and his team really know how to bring social media and community to a different level. As my “opponent” I had Matthew Yeager himself (@mpyeager) from EMC and we had tons of fun recording it and talking about cloud management, APIs and the Software Defined Datacenter. As soon as Amy gets the video up in the show YouTube channel I will feature it here.
My final though is if next year you have the opportunity of going to VMworld, either US or Europe, take it and show up in the community lounge to have some good conversations with the great people there, show your support to that people, get into the parties and enjoy the conference. You won’t regret it, surely I didn’t :-)
vCenter Chargeback Manager gives you the possibility during the installation process to generate an SSL certificate. But this certificate is generated with an expiration period of 60 days.
No problem with that, you can always regenerate it again. Actually Chargeback provides the mechanism to do it. The process can be launched from the vCenter Chargeback Manager Tools folder as it can be seen in the screenshot below.
However this new certificate will come with the same limitation of 60 days of valid period. To easily avoid that we only need to edit the .bat file that generates the certificate and modify the correspondent value.
The script is called Generate_Ssl_Certificate.bat and can be found C:\Program Files(x86)\VMware\VMware vCenter Chargeback\Apache2.2\bin.
Edit the file using your favorite text editor, in my case I’m using Notepad++, and go to line number 72 as in the capture.
Change the –days flag from 60 to your desired value, in the example the value is 365 this is the certificate will expire in one year.
:generatePublicKeyAndCopy echo "Generating a Self-Signed Certificate"... openssl.exe x509 -req -days 365 -in default.csr -signkey default.key -out default.cert if not %ERRORLEVEL%==0 goto :error
After we can launch the generation process. The batch file will open a cmd window, stop the CBM Load Balancer service and asks for the passphrase of default.key. You’ll have to enter it three times and after that the process will ask for information about the State, City, common name (usually the server FQDN), company name, email, etc.
After that it will generate the new certificate and will start Load Balancer services.
Well it’s been a while since my last post, near nine months. Too much time for any author that really wants to maintain its site more or less alive. I’m sure that many of my loyal readers thought that I decided to abandon the blog, specially those that also follow my steps on Twitter where I have not been very active either.
What can I say? Working for VMware is without any doubt one of the most awesome and mind-blowing experiences I’ve ever had! During these months I’ve been involved in some really big vCloud engagements, had the opportunity to work with vCAC, vCloud, Chargeback, vC Ops and vCO in an everyday basis and have learn tons of new cool things. I’ve finally started a personal and professional transition from an infrastructure role to an automation and development focused one.
And I’ve been awarded as VMware vExpert for third year! :D
Honestly being a consultant at PSO is amazing but it’s also a very exhausting and time consuming job, there are always lots of new interesting things to do but not enough time available to try and test every crazy stuff you find, write on the blog, do your job and attend your family. As you can imagine not spending time with my family is completely out of the question and I have to admit that closing the blog has crossed my mind a couple of times. Instead I’ve decided to organize better the rest of my life and try to find time every week to write a couple of posts.
I really enjoy write about my experiences at work, time will tell if I am able to keep my promise, I really hope so :)
I got aware of this issue last week after installing a Fedora 18 virtual machine on Fusion 5. The installation of the Tools went as expected but when the install process launched the vmware-tools-config,pl script I got the typical error of not being able to find the Linux Kernel headers.
Searching for a valid kernel header path... The path "" is not a valid path to the 3.7.2-204.fc18.x86_64 kernel headers. Would you like to change it? [yes]
I installed the kernel headers and devel packages with yum.
[root@fed18 ~]# yum install kernel-headers kernel-devel
Fired up again the configuration script and got the same error. The problem is that snce kernel 3.7 all the kernel header files have been relocated to a new path and because of that the script is not able to find them. To solve it just create a symlink of the version.h file from the new location to the old one.
[root@fed18 src]# ln -s /usr/src/kernels/3.7.2-204.fc18.x86_64/include/generated/uapi/linux/version.h /lib/modules/3.7.2-204.fc18.x86_64/build/include/linux/
With the problem fixed I launched the config script again and the tools finally got configured without problems.
[root@fed18 ~]# vmware-config-tools.pl Initializing... Making sure services for VMware Tools are stopped. Stopping Thinprint services in the virtual machine: Stopping Virtual Printing daemon: done Stopping vmware-tools (via systemctl): [ OK ] The VMware FileSystem Sync Driver (vmsync) allows external third-party backup software that is integrated with vSphere to create backups of the virtual machine. Do you wish to enable this feature? [no] Before you can compile modules, you need to have the following installed... make gcc kernel headers of the running kernel Searching for GCC... Detected GCC binary at "/bin/gcc". The path "/bin/gcc" appears to be a valid path to the gcc binary. Would you like to change it? [no] Searching for a valid kernel header path... Detected the kernel headers at "/lib/modules/3.7.2-204.fc18.x86_64/build/include". The path "/lib/modules/3.7.2-204.fc18.x86_64/build/include" appears to be a valid path to the 3.7.2-204.fc18.x86_64 kernel headers. Would you like to change it? [no]