You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Di Li (JIRA)" <ji...@apache.org> on 2017/08/23 19:54:00 UTC
[jira] [Updated] (AMBARI-21798) Oozie server crashes post migration
after regen kerberos keytabs and restart all services
[ https://issues.apache.org/jira/browse/AMBARI-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Di Li updated AMBARI-21798:
---------------------------
Description:
This is specifically for the IOP *4.2.0 *to HDP migration
Start with an IOP 4.2.0 cluster with both Oozie and Knox installed, enable Kerberos then run thru the migration. Once EU is finalized, regen Kerberos keytabs via Ambari web UI and check the checkbox to make Ambari restart all services as part of the regen process.
Notice Oozie crashes after a successful restart with following error in the oozie.log file
_2017-08-23 12:39:48,480 FATAL Services:514 - SERVER[umiak2.fyre.ibm.com] E0550: Could not normalize host name [${host}], Could not resolve host [${host}], ${host}: Name or service not known
org.apache.oozie.service.ServiceException: E0550: Could not normalize host name [${host}], Could not resolve host [${host}], ${host}: Name or service not known
_
This is because Knox kerberos.json in IOP 4.2.0 has oozie proxy setting as
"oozie.service.ProxyUserService.proxyuser.knox.hosts": "${hosts}",
In HDP 2.6.2, the same property is now
""oozie.service.ProxyUserService.proxyuser.${knox-env/knox_user}.hosts": "${clusterHostInfo/knox_gateway_hosts}", where the ${hosts} placeholder is changed and Knox params.py no longer has the logic to calculate it .
*A manual fix* is to change Kerboers config for Knox - update "oozie.service.ProxyUserService.proxyuser.knox.hosts" to have value "${clusterHostInfo/knox_gateway_hosts}" ( done via UI, this will kick off regen keytabs and restart services)
was:
This is specifically for the IOP *4.2.0 *to HDP migration
Start with an IOP 4.2.0 cluster with both Oozie and Knox installed, enable Kerberos then run thru the migration. Once EU is finalized, regen Kerberos keytabs via Ambari web UI and check the checkbox to make Ambari restart all services as part of the regen process.
Notice Oozie crashes after a successful restart with following error in the oozie.log file
_2017-08-23 12:39:48,480 FATAL Services:514 - SERVER[umiak2.fyre.ibm.com] E0550: Cou
ld not normalize host name [${host}], Could not resolve host [${host}], ${host}: Name or service not known
org.apache.oozie.service.ServiceException: E0550: Could not normalize host name [${
host}], Could not resolve host [${host}], ${host}: Name or service not known
_
This is because Knox kerberos.json in IOP 4.2.0 has oozie proxy setting as
"oozie.service.ProxyUserService.proxyuser.knox.hosts": "${hosts}",
In HDP 2.6.2, the same property is now
""oozie.service.ProxyUserService.proxyuser.${knox-env/knox_user}.hosts": "${clusterHostInfo/knox_gateway_hosts}", where the ${hosts} placeholder is changed and Knox params.py no longer has the logic to calculate it .
*A manual fix* is to change Kerboers config for Knox - update "oozie.service.ProxyUserService.proxyuser.knox.hosts" to have value "${clusterHostInfo/knox_gateway_hosts}" ( done via UI, this will kick off regen keytabs and restart services)
> Oozie server crashes post migration after regen kerberos keytabs and restart all services
> -----------------------------------------------------------------------------------------
>
> Key: AMBARI-21798
> URL: https://issues.apache.org/jira/browse/AMBARI-21798
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.5.2
> Reporter: Di Li
> Fix For: 2.5.2
>
>
> This is specifically for the IOP *4.2.0 *to HDP migration
> Start with an IOP 4.2.0 cluster with both Oozie and Knox installed, enable Kerberos then run thru the migration. Once EU is finalized, regen Kerberos keytabs via Ambari web UI and check the checkbox to make Ambari restart all services as part of the regen process.
> Notice Oozie crashes after a successful restart with following error in the oozie.log file
> _2017-08-23 12:39:48,480 FATAL Services:514 - SERVER[umiak2.fyre.ibm.com] E0550: Could not normalize host name [${host}], Could not resolve host [${host}], ${host}: Name or service not known
> org.apache.oozie.service.ServiceException: E0550: Could not normalize host name [${host}], Could not resolve host [${host}], ${host}: Name or service not known
> _
> This is because Knox kerberos.json in IOP 4.2.0 has oozie proxy setting as
> "oozie.service.ProxyUserService.proxyuser.knox.hosts": "${hosts}",
> In HDP 2.6.2, the same property is now
> ""oozie.service.ProxyUserService.proxyuser.${knox-env/knox_user}.hosts": "${clusterHostInfo/knox_gateway_hosts}", where the ${hosts} placeholder is changed and Knox params.py no longer has the logic to calculate it .
> *A manual fix* is to change Kerboers config for Knox - update "oozie.service.ProxyUserService.proxyuser.knox.hosts" to have value "${clusterHostInfo/knox_gateway_hosts}" ( done via UI, this will kick off regen keytabs and restart services)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)