Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Installation and Upgrades / Re: DNS Updates stopped working after Upgrade from 4.2 to 5.0
« on: June 15, 2017, 05:32:38 am »
Update, indeed, I was able to use the Microsoft Tools to get further, however, there is no DNS related groups at all in the active directory group membership. I added to Domain Admins, set that as the primary group, and remove Domain Users as the secodry membership for that dns-pdc user.
2
Installation and Upgrades / Re: DNS Updates stopped working after Upgrade from 4.2 to 5.0
« on: June 15, 2017, 05:22:21 am »
Im having similiar issues since the upgrade to 5.
Essentially, now, I can't even 'add a dns' record via DNS module in the web min without throwing an error.
It appears that I'm getting the 'password expired' error others are getting, but I see no way to correct it (im not an experienced LDAP/AD admin, especially from nix point of view)
it looks to me that the previous post solves the issue, but his fix mentions go here do that from 'Active Directory users and Groups'. But I have no Windows machine running active directory users and groups from which to make these changes.
Any help would be appreciated on how I can correctly replicate the steps to restore functionality to the dnc-pdc user, or fix the dns issue.
Cheers
Will these tools help I wonder? about to try it anyway
https://www.microsoft.com/en-ca/download/details.aspx?id=45520
Essentially, now, I can't even 'add a dns' record via DNS module in the web min without throwing an error.
It appears that I'm getting the 'password expired' error others are getting, but I see no way to correct it (im not an experienced LDAP/AD admin, especially from nix point of view)
it looks to me that the previous post solves the issue, but his fix mentions go here do that from 'Active Directory users and Groups'. But I have no Windows machine running active directory users and groups from which to make these changes.
Any help would be appreciated on how I can correctly replicate the steps to restore functionality to the dnc-pdc user, or fix the dns issue.
Cheers
Quote
2017/06/14 19:25:32 INFO> GlobalImpl.pm:625 EBox::GlobalImpl::saveAllModules - Saving config and restarting services: firewall dns dhcp
2017/06/14 19:25:32 INFO> Base.pm:231 EBox::Module::Base::save - Restarting service for module: firewall
2017/06/14 19:25:33 INFO> Base.pm:231 EBox::Module::Base::save - Restarting service for module: dns
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host pdc.somedomain.com with IP 10.5.0.2 is not going to be added $
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host jira.somedomain.com with IP 10.5.0.41 is not going to be adde$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host jenkins.somedomain.com with IP 10.5.0.44 is not going to be a$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host fileserver.somedomain.com with IP 10.5.0.45 is not going to b$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host git.somedomain.com with IP 10.5.0.40 is not going to be added$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host unitycache.somedomain.com with IP 10.5.0.39 is not going to b$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 176.68.184 is already mapped to domain dev.somedomain.com. The host vpn.somedomain.com with IP 184.68.176.202 is not going to$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host maas.somedomain.com with IP 10.5.0.144 is not going to be add$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host igg-srv-001.somedomain.com with IP 10.5.0.220 is not going to$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host igg-srv-005.somedomain.com with IP 10.5.0.242 is not going to$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host igg-srv-007.somedomain.com with IP 10.5.0.232 is not going to$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host potato.somedomain.com with IP 10.5.0.62 is not going to be ad$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host kube-master.somedomain.com with IP 10.5.0.34 is not going to $
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host bigdata-database.somedomain.com with IP 10.5.0.35 is not goin$
2017/06/14 19:25:35 WARN> DNS.pm:838 EBox::DNS::_reverseData - Inconsistent DNS configuration detected. IP group 0.5.10 is already mapped to domain dev.somedomain.com. The host docker-node-a.somedomain.com with IP 10.5.0.37 is not going t$
2017/06/14 19:25:36 INFO> DNS.pm:91 EBox::DNS::appArmorProfiles - Setting DNS apparmor profile
2017/06/14 19:25:37 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command kinit -k -t /var/lib/samba/private/dns.keytab dns-pdc failed.
Error output: Password has expired
dns-pdc@somedomain.COM's Password:
Command output: .
Exit value: 1 at root command kinit -k -t /var/lib/samba/private/dns.keytab dns-pdc failed.
Error output: Password has expired
dns-pdc@somedomain.COM's Password:
Will these tools help I wonder? about to try it anyway
https://www.microsoft.com/en-ca/download/details.aspx?id=45520
3
Installation and Upgrades / Re: zentyal 5.0 delveopment install failing
« on: June 15, 2017, 05:11:42 am »
usually, its a bad idea to play around with any of the configuration files from the terminal, if at all possible, use the web interface to make changes. this is because zentyal will often overwrite configuration changes you made.
I assume its 'seeing' you're interfaces in the web panel, but you need to choose the 'method' and configure them first.
I assume its 'seeing' you're interfaces in the web panel, but you need to choose the 'method' and configure them first.
Pages: [1]