some ports depend on apache 1.3 and die with error :
Error from bsd.apache.mk. apache20 is installed (or APACHE_PORT is defined) and port requires 1.3.
solution :
make install WITH_MODPERL2=yes
I’ve encountered this error when trying to connect to web dav enabled folder.
I saw some web posts to add :
RewriteEngine Off
However that did not work for me, I finally traced it back to SElinux, I was using a custom folder and needed to change the permissions :
[user@server]>sudo stat -Z -c %C /var/webdav
user_u:object_r:user_home_dir_t
Compared to /var/www
[user@server]>sudo stat -Z -c %C /var/www
system_u:object_r:httpd_sys_content_t
A change of SElinux permissions and all was well :
[user@server]> chcon -R -u system_u -r object_r -t httpd_sys_content_t /var/webdav
This message appears if the Service Console does not have network redundancy configured properly and can be safely ignored.
To prevent this message from appearing and to comply with proper network redundancy, VMware recommends that you add a second service console on a different vSwitch and subnet. Alternatively, you can add a second vmnic to the service console vSwitch.
To suppress this message on ESX hosts in the VMware High Availability (HA) cluster or if the warning appears for a host already configured in a cluster, set the VMware HA advanced option das.ignoreRedundantNetWarning to true and reconfigure VMware HA on that host. This advanced option is available in VMware Virtual Center 2.5 Update 3 and later.
Note: If the warning continues to appear, disable and re-enable VMware High Availability in the cluster.
To set das.ignoreRedundantNetWarning to true:
1. From VMware Infrastructure Client, right-click on the cluster and click Edit Settings.
2. Select VMware HA and click Advanced Options.
3. In the Options column, enter das.ignoreRedundantNetWarning.
4. In the Value column, enter true.
Note: Steps 3 and 4 create a new option.
5. Click OK.
6. Reconfigure HA.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004700
on install : press TAB and add “nocheckCPUIDLimit” after “vmkernel.gz”
mboot.c32 vmkernel.gz nocheckCPUIDLimit
on first boot : press shift + O at the ESX load screen and type
nocheckCPUIDLimit
Once installed using vSphere client disable CPUID check by unchecking the option:
Configuration -> Advanced Settings -> VMkernel -> Boot -> VMKernel.Boot.checkCPUIDLimit