Installation stalls [message #122170] |
Fri, 19 June 2015 16:02  |
Bud Durland
Messages: 588 Registered: December 2013 Location: Plattsburgh, NY
|
|
|
|
I'm trying to deploy 8.5.0 multi-server in my VMWare 5.5 test environment. I get the link from the downloads page, start the 'deploy OVF template' process in VMWare. That part all goes pretty well. When I power up the virtual machine for the first time, I see messages go by on the console, include one about a script line missing, and another about the puppet config is missing.
The I see the configuration wizard screen, telling me about the various kinds of servers, and that's where is stops. No amount of pleading or button pressing will get it to go any farther.
I'm sure there's a simple step that I missed. I also have one other question -- The installation guide (http://kb.kerio.com/1775) gives advice about memory, CPU and Disk configs. Yet the template is a plain 1 CPU, 1GB ram, 10GB disk deployment. Changing the CPU and Ram is easy, but what about the disk? Do I just add an additional disk to the VM and it will auto-discover, or do I have to resize the original disk allocation> If the latter, what steps do I take to make the extra space visible to the VM?
|
|
|
|
Re: Installation stalls [message #122219 is a reply to message #122211] |
Mon, 22 June 2015 16:43   |
Bud Durland
Messages: 588 Registered: December 2013 Location: Plattsburgh, NY
|
|
|
|
Screen shot from VMWare client attached. At this point, the virtual machine console is unresponsive. I can shut the VM down by using the vCenter manager.
-
Attachment: Stalled.PNG
(Size: 84.48KB, Downloaded 901 times)
|
|
|
|
|
Re: Installation stalls [message #122274 is a reply to message #122268] |
Tue, 23 June 2015 17:10   |
Bud Durland
Messages: 588 Registered: December 2013 Location: Plattsburgh, NY
|
|
|
|
According to the setup guide (KB1775), the puppet master needs about 100GB of disk space. Adding a second hard drive to the Vm is easy enough, but where should it be mounted in the file system.
|
|
|
|
Re: Installation stalls [message #122276 is a reply to message #122275] |
Tue, 23 June 2015 17:27   |
Bud Durland
Messages: 588 Registered: December 2013 Location: Plattsburgh, NY
|
|
|
|
Brian -- it does, except that this is the 'puppet master' server, so I suspect it doesn't need a 'store' folder, so the question is which of the existing directory / mount points do I move to the new storage?
|
|
|
|
Re: Installation stalls [message #122294 is a reply to message #122286] |
Wed, 24 June 2015 00:42   |
nate.keegan
Messages: 46 Registered: June 2015
|
|
|
|
A couple of things I have run into so far, none of which are deal breakers but are handy to know the first time out maybe.
Underpowering the VMs as far as memory or CPU (but mostly memory) causes the installer to do some weird things. Example, I tried to run the Directory Server VMDK this morning with 384 Mb of virtual memory and it barfed when trying to start services during the installation.
With VMDK one needs an unintialized/unbooted copy of a VMDK before pointing a VM at the VMDK. Basically I run 'vmkfstools -i <source vmdk> kerio-<role>.vmdk' for each role in case I have to re-do a role installation.
Having said that, if an installation fails I stop the problem VM, remove it from vSphere/VMWare, create a new VMDK copy, clear the Puppet SSL certificate (on Puppet - 'puppet cert clean <fqhn of failed vm>') and remove the DHCP lease for the problem VM if I will be reusing the hostname.
The Multi-Server roles need/want FTP/HTTP/HTTPS access to ftp.debian.org, keyserver.ubuntu.com, and security.debian.org during the initial setup. I don't know that this is mandatory but to err on the side of caution I allowed this for our VMs in our firewall.
Depending on your setup this may or may not trip you up - when prompted during the Puppet installation the internet hostname is akin to the VIP name for a load balancer (i.e. the service name that hosts will use to hit Kerio MS) and the 'domain name' is the DNS domain for the hosts. In our environment the DNS domain is say 'foo.com' and our email is '<_at_>bar.com' so for 'domain name' we put in 'foo.com' and then I went ahead and added an A record for each role in our DNS.
For example, 192.168.1.1 is kerio-dhcp, 192.168.1.2 is kerio-puppet, 192.168.1.3 is kerio-directory, 192.168.1.4 is kerio-backend1, etc. This way the installation and Kerio Puppet are able to figure out that a given host is kerio-directory.foo.com.
|
|
|
Re: Installation stalls [message #122295 is a reply to message #122294] |
Wed, 24 June 2015 00:43   |
nate.keegan
Messages: 46 Registered: June 2015
|
|
|
|
I think your certificate error/message is due to your local DNS and Puppet not meshing so that Puppet can figure out the name of the new role.dnsDomain (i.e. kerio-directory.foo.com is 192.168.x.y or whatever it actually is).
|
|
|
Re: Installation stalls [message #122326 is a reply to message #122295] |
Wed, 24 June 2015 22:27   |
Bud Durland
Messages: 588 Registered: December 2013 Location: Plattsburgh, NY
|
|
|
|
I applied the "clean slate" protocol.
- I recreated all the VM's I need (KC-PuppetMaster, KC-Directory, KC-BackEnd, KC-FrontEnd)
- I created reservations in my DHCP server so they would obtain an IP address that's allowed out of my net work.
- I created DNS entries for the machines (*.MyDOmain.net). The dhcp server will also register *.myActiveDirectory.local.
I can install the puppet master without issue. The Directory server and the backend server both fail with an error as in the attached file. Basically, it gives a message that is is creating a new SSL key, then 'could not request certificate', and 'name or service not found'.
|
|
|
|
Re: Installation stalls [message #122352 is a reply to message #122332] |
Thu, 25 June 2015 13:27   |
Bud Durland
Messages: 588 Registered: December 2013 Location: Plattsburgh, NY
|
|
|
|
The PuppetMaster and the Directory server can resolve each other's names (all variants) and pings are successful. The 'puppet-install-*' file in /var/log/puppet on the Directory server contains the three lines shown in the screen shot.
|
|
|
|