I hear you on the cores but that host runs a lot of VMs and I prefer to
avoid the scheduling overhead. However, I'll keep close watch.
I added the VM to the normal DNS Bind VM by adding a new master zone for
the SOGo test domain (which is different from the domain I use
normally). I then added an A record for the test VM and all of the
unresolved errors disappeared.
First Q: There are a list of DNS entries that I am supposed to add that
refer to my routable IP address assigned by my ISP (I have a 29 subnet)
and I'm not sure what to do with these since I don't intend to publish
this on the Internet. Can I just ignore them?
The script seems to run much better until the below pops up during Samba
installation.
Wait to start Samba4 LDAP .. OK
ldap_result: Can't contact LDAP server (-1)
[!] User 'Administrator' not found
ldap_result: Can't contact LDAP server (-1)
ldap_result: Can't contact LDAP server (-1)
ERROR: Failed to set expiry for user 'administrator': Unable to find
user "(&(objectClass=user)(sAMAccountName=administrator))"
ERROR(ldb): Failed to create group "SOGOTEST Users" - objectclass:
Cannot add CN=SOGOTEST Users,CN=Users,DC=sogotest,DC=com, parent does
not exist!
Operations are OK [Yn]?
Any ideas? Do you need more info? Should I answer Y or n?
Thanx,
Garth
On 07/10/2013 06:28 AM, Szládovics Péter wrote:
Hi Garth,
2013-07-10 12:45 keltezéssel, Garth Keesler írta:
I'll revert the VM to just after the install and try it again and let
you know what happens.
Ok, thanks.
Normally, I only give one core to a VM since my host is an i7 and I'm
not really after performance at this stage.
The i7 as 4 phisical core and HT extension, so, if your VM got not a
phisical core, just a HT thread, then VM can be stuck when the host is
working harder - eg. massive IO.
So, I very recommend you to add 2 cores for every VM what you use -
the host will share them between VM-s as well, don't worry.
I'll do a bit more diagnosing this time if/when it gets to Dovecot.
Lastly, just before the Dovecot install stage, I tried installing
open ssh-server so I could conveniently remote in to the VM but it
failed with several conflicts. I may do that initially and see what
happens.
OpenSSH server installs on the 0. step ;)
So, if you accept the step with Yes answer on 'All operations are ok'
question, and then ctrl+c at the first screen of the 1. step, you can
continue the install through ssh too ;)
--
[email protected]
https://inverse.ca/sogo/lists
