Avamar: No se puede iniciar MCS debido a un problema de configuración del nombre de host
Summary: En este artículo, se muestra cómo iniciar Management Console Server (MCS) abordando un problema de configuración de nombre de host existente en Avamar.
Symptoms
El intento de iniciar los servicios del servidor de consola de administración (MCS) genera el siguiente error:
admin@<incorrect-hostname>: mcserver.sh --start
Starting the database server.
Waiting for postmaster to start ..Started
Start MCDB: processing time = 2 s.
Check MCS: processing time = 8 s.
INFO: Starting messaging service.
INFO: Started messaging service.
Start Message Broker: processing time = 12 s.
=== BEGIN === check.mcs (prestart)
ERROR: check.mcs: [<incorrect-hostname>] checking if entry for <incorrect-hostname> is correctly defined in /etc/hosts CHECK FAILED: <incorrect-hostname> entry in /etc/hosts not found or incorrect
check.mcs failed
*** FAIL *** check.mcs FAILED OVERALL (prestart)
Starting Administrator Server at Fri May 26 04:54:25 JST 2023 ...
Upgrade MCS Preference: processing time = 286ms
Upgrade MCDB: processing time = 1634ms
Check node list: processing time = 1064ms
Prepare MC SSL Properties: processing time = 1ms
java.net.UnknownHostException: <incorrect-hostname>: <incorrect-hostname>: Name or service not known
at java.net.InetAddress.getLocalHost(Unknown Source)
at com.avamar.asn.Node.setPrefs(Node.java:345)
at com.avamar.asn.Node.init(Node.java:209)
at com.avamar.asn.Node.<init>(Node.java:89)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:110)
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:280)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1097)
at com.avamar.mc.util.MCSpringUtil.getBean(MCSpringUtil.java:96)
at com.avamar.mc.CLI.start(CLI.java:355)
at com.avamar.mc.CLI.process(CLI.java:133)
at com.avamar.mc.CLI.main(CLI.java:104)
Caused by: java.net.UnknownHostException: <incorrect-hostname>: Name or service not known
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(Unknown Source)
at java.net.InetAddress.getAddressesFromNameService(Unknown Source)
... 24 more
java.net.UnknownHostException: <incorrect-hostname>: <incorrect-hostname>: Temporary failure in name resolution
at java.net.InetAddress.getLocalHost(Unknown Source)
at com.avamar.asn.Node.setPrefs(Node.java:345)
at com.avamar.asn.Node.init(Node.java:209)
at com.avamar.asn.Node.<init>(Node.java:89)
at com.avamar.mc.CLI.start(CLI.java:357)
at com.avamar.mc.CLI.process(CLI.java:133)
at com.avamar.mc.CLI.main(CLI.java:104)
Caused by: java.net.UnknownHostException: <incorrect-hostname>: Temporary failure in name resolution
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(Unknown Source)
at java.net.InetAddress.getAddressesFromNameService(Unknown Source)
... 7 more
Administrator Server startup failed at Fri May 26 04:54:36 JST 2023: Closing all connections to database. Node initialization failed.
Starting REST API Service.....
REST API Service startup failed.
Start MC Rest: processing time = 11 s.
=== Start Avamar Certificate Service ===
Avamar Certificate Service started.Cause
Según el resultado anterior, la falla se produce en la resolución de nombres, lo que da lugar a una excepción de host desconocida:
java.net.UnknownHostException: <incorrect-hostname>: <incorrect-hostname>: Name or service not known
Cuando el código Java intenta obtener la información del nombre de host local, falla debido a un problema de configuración del nombre de host:
Ejemplo:
hostname
<incorrect-hostname>
hostname -f
hostname: Temporary failure in name resolution
hostname -i
hostname: Name or service not knownResolution
1. Ejecute el siguiente comando para actualizar el nombre de host:
hostname <correct-hostname>
Por ejemplo: Para configurar el nombre de host en avamar-prod-fs1:
hostname avamar-prod-fs1
2. Verifique los valores del nombre de host (con el mismo ejemplo)
hostname
avamar-prod-fs1
hostname -f
avamar-prod-fs1.company.com
hostname -i
10.1.2.3
3. Inicie MCS y reanude el programador de respaldo:
mcserver.sh --start
dpnctl start sched
Consulte el siguiente artículo para obtener más información sobre cómo iniciar MCS: Avamar: Cómo reiniciar el servidor de la consola de administración