You should always do a yum update to make sure the OS is up to date before
a sipXecs install (if installing from RPM) or directly after install if
installing from ISO.
Also, fyi and just so folks remember, the ISO is not re-created with every
build of the code, only when there is a release that
As usual, I did the system update first:
Built another Centos 6 VM from scratch this afternoon:
Allocated 3 CPUs and 4GB of RAM to the VM
ran 'yum update' and restarted VM.
Completed 4.6 install per wiki.
Still trying to understand how a leap second issue might affect a system
installed,
On Tue, Jul 10, 2012 at 4:34 PM, Kurt Albershardt k...@nv.net wrote:
As usual, I did the system update first:
Built another Centos 6 VM from scratch this afternoon:
Allocated 3 CPUs and 4GB of RAM to the VM
ran 'yum update' and restarted VM.
Completed 4.6 install per wiki.
Still trying
Built another Centos 6 VM from scratch this afternoon:
Allocated 3 CPUs and 4GB of RAM to the VM
ran 'yum update' and restarted VM.
Competed 4.6 install per wiki.
ran sipxecs-setup, answered questions, got:
Configuring system, this may take a few minutes...
then
for the next ~50 minutes, memory
I did the same install over the weekend without these kind of issues.
Centos 6.2 minimal install.
Set network info
Yum install epel-release
Yum update
Reboot
Yum groupinstall sipxecs
I did use a vmware environment though. SINCE this is a Linux host, I think
maybe you need a leap second fix for
On Jul 9, 2012, at 18:52 , Tony Graziano wrote:
I did the same install over the weekend without these kind of issues.
Centos 6.2 minimal install.
Set network info
Yum install epel-release
Yum update
Reboot
Yum groupinstall sipxecs
I did use a vmware environment though. SINCE this
