IIS85 installation Issues with xmeta pass

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
vemisr
Participant
Posts: 72
Joined: Thu Sep 11, 2008 1:31 pm

IIS85 installation Issues with xmeta pass

Post by vemisr »

HI experts,

i am installing IIS8.5 (fresh new installation) on Redhat Linux.

while ruuning the installation program i stuck with xmeta passwd.

it's not accepting the passwd, saying invalid passwd.

let me know how can i trouble shoot this one
mobashshar
Participant
Posts: 91
Joined: Wed Apr 20, 2005 7:59 pm
Location: U.S.

Post by mobashshar »

Check to see if you can log into xmeta schema with the password you are using to install..
vemisr
Participant
Posts: 72
Joined: Thu Sep 11, 2008 1:31 pm

Post by vemisr »

how will i know it's created database or not ?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Did you create the xmeta user before performing the installation?

If not, the installer restricts the password to alphanumeric and underscore characters (for example it would not accept P@ssw0rd because of the "@" character).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
vemisr
Participant
Posts: 72
Joined: Thu Sep 11, 2008 1:31 pm

Post by vemisr »

here is the log file , still i don't understand what is problem with this ID.

Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.PermissionSetterUnix
INFO: CDIIN3053I: Change 755 permission on directory: /opt/IBM/InformationServer
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: CDIIN2753I:Command Array: chmod 755 /opt/IBM/InformationServer, env = null, workingDir =null
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: Exit Code: 0
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.PermissionSetterUnix
INFO: CDIIN3053I: Change 755 permission on directory: /opt/IBM
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: CDIIN2753I:Command Array: chmod 755 /opt/IBM, env = null, workingDir =null
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: Exit Code: 0
Jun 13, 2011 1:05:58 AM com.ibm.is.install.check.PathCanBeMadeWritableChecker
INFO: tmpFile = /opt/IBM/InformationServer/__ibm__test.txt...
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: CDIIN2753I:Command Array: /bin/sh -c ls -l /opt/IBM/InformationServer/__ibm__test.txt | awk {'print ($3)'}, env = null, workingDir =null
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: Exit Code: 0, Info: root
Jun 13, 2011 1:05:58 AM com.ibm.is.install.check.PathCanBeMadeWritableChecker
INFO: output = root
Jun 13, 2011 1:05:58 AM com.ibm.is.install.check.CheckResultList
INFO: PASSED: CDIPR2121I: Ensure that the directory /opt/IBM/InformationServer/Repos/xmeta is writable with root ownership.
Jun 13, 2011 1:05:58 AM com.ibm.is.install.check.CheckResultList
INFO: PASSED: CDIPR2004I: Ensure that the directory /opt/IBM/InformationServer/Repos/xmeta either exists and is writable or does not exist but can be created.
Jun 13, 2011 1:05:58 AM com.ibm.is.install.atlasinstaller.ui.control.InstallResourceManager
INFO: Added resource /opt/IBM/InformationServer/Repos/xmeta
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.PermissionSetterUnix
INFO: CDIIN3053I: Change 755 permission on directory: /opt/IBM/InformationServer
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: CDIIN2753I:Command Array: chmod 755 /opt/IBM/InformationServer, env = null, workingDir =null
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: Exit Code: 0
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.PermissionSetterUnix
INFO: CDIIN3053I: Change 755 permission on directory: /opt/IBM
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: CDIIN2753I:Command Array: chmod 755 /opt/IBM, env = null, workingDir =null
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: Exit Code: 0
Jun 13, 2011 1:05:58 AM com.ibm.is.install.check.PathCanBeMadeWritableChecker
INFO: tmpFile = /opt/IBM/InformationServer/__ibm__test.txt...
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: CDIIN2753I:Command Array: /bin/sh -c ls -l /opt/IBM/InformationServer/__ibm__test.txt | awk {'print ($3)'}, env = null, workingDir =null
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: Exit Code: 0, Info: root
Jun 13, 2011 1:05:58 AM com.ibm.is.install.check.PathCanBeMadeWritableChecker
INFO: output = root
Jun 13, 2011 1:05:58 AM com.ibm.is.install.check.CheckResultList
INFO: PASSED: CDIPR2121I: Ensure that the directory /opt/IBM/InformationServer/Repos/xmeta is writable with root ownership.
Jun 13, 2011 1:05:58 AM com.ibm.is.install.check.CheckResultList
INFO: PASSED: CDIPR2004I: Ensure that the directory /opt/IBM/InformationServer/Repos/xmeta either exists and is writable or does not exist but can be created.
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: CDIIN2753I:Command Array: /usr/sbin/groupadd xmeta, env = null, workingDir =null
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.SuiteLogger logWarning
WARNING: com.ibm.is.install.core.CommonProcess Exit Code: 9, groupadd: group xmeta exists
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.SuiteLogger logError
SEVERE: com.ibm.is.install.core.util.User CDIIN3183E: groupadd command failed with return code: 9
Jun 13, 2011 1:05:58 AM com.ibm.is.install.core.CommonProcess
INFO: CDIIN2753I:Command Array: /usr/sbin/useradd -g xmeta -d /home/xmeta -m -s /bin/ksh xmeta, env = null, workingDir =null
Jun 13, 2011 1:06:03 AM com.ibm.is.install.core.SuiteLogger logWarning
WARNING: com.ibm.is.install.core.CommonProcess Exit Code: 9, useradd: user xmeta exists
Jun 13, 2011 1:06:03 AM com.ibm.is.install.core.SuiteLogger logError
SEVERE: com.ibm.is.install.core.util.User CDIIN3176E: useradd command failed with return code: 9
vemisr
Participant
Posts: 72
Joined: Thu Sep 11, 2008 1:31 pm

Yes, i created the xmeta user with passwd no special charact

Post by vemisr »

ray.wurlod wrote:Did you create the xmeta user before performing the installation?

If not, the installer restricts the password to alphanumeric and underscore characters (for example it would not accept P@ssw0rd be ...

Yes, i created the xmeta user with passwd no special characters
asorrell
Posts: 1707
Joined: Fri Apr 04, 2003 2:00 pm
Location: Colleyville, Texas

Post by asorrell »

I'm not certain what caused it, but the error message is very straightforward.

It is trying to add a group called xmeta and a user-id called xmeta at the UNIX level and is failing because you've pre-created it.

If it isn't a problem - just remove the id / group and let it re-create them.
Andy Sorrell
Certified DataStage Consultant
IBM Analytics Champion 2009 - 2020
vemisr
Participant
Posts: 72
Joined: Thu Sep 11, 2008 1:31 pm

Post by vemisr »

HI,

i deleted the user from the server. ran the Installer program. but it's created new user and passwd. still getting the 'password is invalid' message.
still i can able to login to the server using xmeta user and passwd.
but installer giving invalid user.

see this log.

Jun 13, 2011 7:15:48 PM com.ibm.is.install.check.CheckResultList
INFO: PASSED: CDIPR2004I: Ensure that the directory /opt/IBM/InformationServer/Repos/xmeta either exists and is writable or does not exist but can be created.
Jun 13, 2011 7:15:48 PM com.ibm.is.install.core.CommonProcess
INFO: CDIIN2753I:Command Array: /tmp/is-suite/tools/ValidateUser -validate xmeta ******, env = null, workingDir =null
Jun 13, 2011 7:15:48 PM com.ibm.is.install.core.CommonProcess
INFO: Exit Code: 4, Info: Password is invalid.
[rc 7] PAM error description = Authentication failure


could you let me know what to do ?

thanks a Lot.
vemi
jwiles
Premium Member
Premium Member
Posts: 1274
Joined: Sun Nov 14, 2004 8:50 pm
Contact:

Post by jwiles »

Code: Select all

INFO: Exit Code: 4, Info: Password is invalid.
[rc 7] PAM error description = Authentication failure
I recently performed an 8.5 installation for a client in which we experienced a similar issue. The cause was the LDAP authentication software.

Try stopping the software service/daemon and also removing references to it from /etc/pam.d/system-auth (at least temporarily). This was the only way we could stop any of the LDAP software's modules from being loaded. After installation was complete and IS was operational, LDAP was re-enabled.

Regards,
- james wiles


All generalizations are false, including this one - Mark Twain.
Post Reply