and you can't remove any resource pools. I had this issue because I created an SRM lab, tried the exercises and then reverted to snapshots. While testing the lab I created resource pools which were pushed to the ESX hosts. When I reverted to the snapshots, my vCenter was resetted, but the ESX hosts still had the vcenter agent running and in effect they thought they were still connected to a vCenter. You'll also get the annoying issue that when you reconnect a host to "another" vCenter, it will complain about already being managed. When you then try to remove the resource pool, the ESXi host for some reason auto recreates the resource pool. Very annoying :) You could readadd it to a vCenter and then properly remove it. However you can also do the following
Enable the remote technical support.
Run /opt/vmware/uninstallers/VMware-vpxa-uninstall.sh
You should be able to remove the resource pool. I remembered this command from an issue I used to have when I did a migration. Here is a link to the kb article
2011/04/05
2011/04/03
Zimbra antispam and antivirus not working
If you notice that mails are getting stuck in deferred status you might have the same problem that i just had. Check the logs for a message like this (/var/log/zimbra.log)
First of all you should try to manually start the service
If you get this error you made a mistake like I did. I did gave the fqdn while setting up the server. You can fix this by executing
Then do an exit to get you back to the root shell and reboot
Apr 3 21:44:54 mail01 postfix/smtp[9304]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
First of all you should try to manually start the service
[root@mail01 conf]$ su zimbra -
[zimbra@mail01 conf]$ zmamavisdctl start
Starting amavisd... The value of variable $myhostname is "mail01", but should have been
a fully qualified domain name; perhaps uname(3) did not provide such.
You must explicitly assign a FQDN of this host to variable $myhostname
in amavisd.conf, or fix what uname(3) provides as a host's network name!
If you get this error you made a mistake like I did. I did gave the fqdn while setting up the server. You can fix this by executing
/opt/zimbra/libexec/zmsetservername -n mail01.demo
Then do an exit to get you back to the root shell and reboot
Install zimbra on Centos 5.5
Prereq part
Make sure you have at least 7 gb free (/opt/zimbra requires at least 5GB of space to install). If you scalled to small you can use this article (i did :D)
http://www.howtoforge.com/logical-volume-manager-how-can-i-extend-a-volume-group
Then you can extend the logical volume like this
lvextend /dev/VolGroup00/LogVol00 -l +100%FREE
resize2fs /dev/VolGroup00/LogVol00
You can check the size with
df -h
Remember, online resizing is a nono for production environment. I would recommend making a different partition for /opt/zimbra so you can resize this by bringing this partition offline
Fix your /etc/hosts so that it looks similar to
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
10.5.4.49 mail01 mail01.demo
::1 localhost6.localdomain6 localhost6
Install the necessary packages
yum install -y sudo libidn gmp libstdc++ perl sysstat sqlite bind-utils
And finally make sure your mx records are setup
dig demo mx
This should reply your name server
[root@mail01 ~]# dig demo mx
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> demo mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30023
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; QUESTION SECTION:
;demo. IN MX
;; ANSWER SECTION:
nato.demo. 3600 IN MX 10 mail01.demo.
;; ADDITIONAL SECTION:
mail01.demo. 3600 IN A 10.5.4.49
;; Query time: 0 msec
;; SERVER: 10.5.4.50#53(10.5.4.50)
;; WHEN: Sun Apr 3 21:16:02 2011
;; MSG SIZE rcvd: 66
Finally, make sure your firewall is configured correctly. I disabled it for the sake of simplicity in this demo setup. You can do this with the following tool (CentOS specific)
# system-config-securitylevel-tui
Actual install
First start by getting the package from http://www.zimbra.com/downloads/os-downloads.html. I usually use wget for this
mkdir -p /usr/src/zimbra
cd /usr/src/zimbra
wget http://files2.zimbra.com/downloads/7.0.1_GA/zcs-7.0.1_GA_3105.RHEL5_64.20110304210645.tgz
wget http://files2.zimbra.com/downloads/7.0.1_GA/zcs-7.0.1_GA_3105.RHEL5_64.20110304210645.tgz.md5
Check that your MD5sums match
md5sum zcs*.tgz
cat zcs*.tgz.md5
Untar your file and install it. Remember we will have to do a platform-override as centos is not supported :)
tar -xzvf zcs*tgz
cd zcs*
./install.sh --platform-override
While installing you will have to answer some questions and set the admin password. This should be quite straight forward if you have done all the previous prereqs. When the install starts, go sip some coffee or tea :)
When done, execute the following. I haven't figured out why this works but it makes the red crosses disappear on the service status page.
su - zimbra
zmsshkeygen
zmupdateauthkeys
zmloggerctl stop ; zmloggerctl start
exit
reboot
You can now do the admin tasks you like on
https://mail01.demo:7071/
(your login
And read mail from
http://mail01.demo/
Oneliner: Howto install VMware Tools on Centos
What the title say :). Ofcourse you must invoke "install vmware tools" on the vm itself first.
yum install -y perl;mkdir -p /mnt/cdrom;mount /dev/cdrom /mnt/cdrom/;tar -xzvf /mnt/cdrom/VMwareTools*.tar.gz -C /usr/src/;umount /dev/cdrom;cd /usr/src/vmware-tools-distrib/;./vmware-install.pl
Subscribe to:
Posts (Atom)