About jluzon

jluzon · ‎01-26-2017

Hi, sure, it was a recomendation for future developments 🙂 Thanks a lot, finally we'll change the OS.

jluzon · ‎01-25-2017

Hi, Not in this case, versions are right. The problem, in my opinion, is under the validation script of cdm_install, marked in the attach, where script is not well detecting "Version" in zypper info output Really versions are right. This is my CM Version: *Proveedor de VM de Java*: Oracle Corporation *Versión de Java*: 1.8.0_121 *Hora del servidor*: 25-ene-2017 18:06:37, Hora de Europa Central (CET) Copyright © 2011-2017 Cloudera, Inc. Todos los derechos reservados. Hadoop y el logotipo del elefante de Hadoop son marcas comerciales de Apache Software Foundation. Thanks for the reply

jluzon · ‎01-25-2017

When installing with Cloudera Manager over SLES 12 SP2 platform, installation process is stopped after "cloudera-manager-agent" package check. This is the server log: END (0) BEGIN zypper info cloudera-manager-agent | grep -E 'Version:[[:space:]]5.9.1-.*\.8' END (1) cloudera-manager-agent must have Version=5.9.1 and Build=8, exiting closing logging file descriptor And the problem seems to be in the zypper info output. In scm_prepare_nodexxxx.sh scripts, the pattern "Version:[[:space:]]5.9.1-.*\.8" is not correct, because in SLES 12 SP2, zypper info returns a tab, not a space, after "Version" word. Then ,validation is null, and install process is stopped. The output in SLES 12 is in attached output.png file

Online	Offline
Last Visited	‎08-25-2017 03:35 AM

Member Since	‎01-25-2017 06:38 AM
Last Visited	‎08-25-2017 03:35 AM
Posts	4

Cloudera Community

Re: Check Script problem with SLES 12 Installation

Re: Check Script problem with SLES 12 Installation

Check Script problem with SLES 12 Installation