asked on

StandAlone app Server profile - WAS 6.1

This is something intersting and wierd.

Well as a specific user I created a StandAlone app server profile on WAS 6.1 binaries. I Twas working fine till I applied a an upgrade package.

Well I had to apply a fixpack to the integrated solution console for the same profile. So I applied this fixpack and augmented this profile to this fixpack . All the fixpack process and augmenting was doen as a root user. Since Root was the only who could run the update installer, well I got what I wanted in the integrated solution console. But when I try to restart the server as the same user who created binaries and profile from the WASHOME/bin directory it gives me an error

"WCMD0002E: Command "startServer.sh" requires a profile. No default profile exists and a profile name was not specified. Ensure that a default profile exists or use the -profileName parameter to specify the name of an existing profile." Root was able to start the server from the same directory

I was able to start the server with the same user id from WASHOME/profiles/Appserver/bin/

So I want to know what got changed when I augmented the profile using root . Is ther any way I can let the user ID gain control of the profile . If you are wondering what the hell am I doing " I am working on IBM license metric tool and it needs some upgrades to the integrated solution console"

Thanks
Maddy

HonorGod

Apparently the "default" profile information got lost somehow.

To verify what profiles exist:

- "cd" to the AppServer bin directory
e.g., something like:
# cd /opt/IBM/WebSphere/AppServer/bin

- Use the manageprofiles command to list the available profiles:
e.g., something like:
# ./manageprofiles.sh -listProfiles

- Use the manageprofiles command to list the current default:
e.g., something like:
# ./manageprofiles.sh -getDefaultName

- if the default profile name is missing, or not what you want, change the default using something like:
# ./manageprofiles.sh -setDefaultName -profileName AppSrv01

maddy939

ASKER

Hi HonorGod ,

When I try to run the manageprofiles command as the user who originally created the profile, I get the following Errors

./manageprofiles.sh -listProfiles
Nov 26, 2010 9:13:16 AM com.ibm.wsspi.profile.WSProfileCLI getMaskableArgs
INFO: Maskable Action Arguments: { "winservicePassword" ,"adminPassword" ,"dmgrA dminPassword" ,"samplesPassword" ,"password" ,"adminPwd" }
Nov 26, 2010 9:13:16 AM com.ibm.wsspi.profile.WSProfileCLI invokeWSProfile
INFO: Incoming command line is: { "-listProfiles" }
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve templatePath from command line
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve profileName from command line
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve profileName from command line
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getModeInvoker
INFO: Identified WSProfile mode invoker to be: com.ibm.ws.profile.cli.WSProfileC LIListProfilesInvoker
Nov 26, 2010 9:13:16 AM com.ibm.wsspi.profile.WSProfileCLI isLogReInitialization Necessary
INFO: Log re-initialization is necessary: false
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve templatePath from command line
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve templatePath from command line
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve profileName from command line
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve profileName from command line
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve profileName from command line
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve profileName from command line
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve profileName from command line
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve profileName from command line
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getModeIn voker
INFO: Identified WSProfile mode invoker to be: com.ibm.ws.profile.cli.WSProfileC LIListProfilesInvoker
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker areComman dLineArgumentsValid
INFO: Validating command line arguments.
Nov 26, 2010 9:13:16 AM com.ibm.ws.install.configmanager.utils.SystemPropertiesU tils setValue
INFO: Set System property listProfiles with an empty value
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.utils.ValidationManagerUtils determin eCurrentMode
INFO: Mode was determined to be: null
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getArgume ntValue
WARNING: Could not resolve registry from command line
Nov 26, 2010 9:13:16 AM com.ibm.wsspi.profile.WSProfile getRegistryFile
INFO: Return profile registry location as: /opt/WAS/6.1/f/properties/profileRegistry.xml
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.cli.WSProfileCLIModeInvoker getProfil eRegistryPath
INFO: Profile registry being used is: /opt/WAS/6.1/f/properties/profileRegistry.xml
Nov 26, 2010 9:13:16 AM com.ibm.ws.install.configmanager.osutils.PlatformConstants getCurrentPlatform
INFO: Current platform was detected as AIX
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.utils.FileUtils getNormalizedPath
INFO: The path /opt/WAS/6.1/f/profiles/saILMT was sucessfully normalized to / opt/WAS/6.1/f/profiles/saILMT
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.utils.FileUtils getNormalizedPath
INFO: The path /opt/WAS/6.1/f/profileTemplates/default was sucessfully normalized to /opt/WAS/6.1/f/profileTemplates/default
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.utils.FileUtils getNormalizedPath
Nov 26, 2010 9:13:16 AM com.ibm.ws.profile.registry.FSProfileRegistry getScriptP athForThisProfile
INFO: The script path for this profile: saILMT:/opt//WAS/6.1/f/profiles/saILMT:truefalse, is: /opt/WAS/6.1/f/properties/fsdb/saILMT.sh
[]
Nov 26, 2010 9:13:16 AM com.ibm.wsspi.profile.WSProfileCLI invokeWSProfile
INFO: Returning with return code: INSTCONFSUCCESS

HonorGod

Yeah, apparently the update, as root, means that you have to either run the manageprofiles script as root,
or you have to do something like chown on the files to change the ownership.

If you use a recursive long list, you will probably find some number of files still owned by the non-root user (is it doen?).

ls -lAR | grep doen | wc -l

You might just be able to use something like this from the AppServer directory:

chown -R doen:doen *

BEFORE YOU DO THOUGH, BACKUP UP THE WHOLE DIRECTORY (e.g., use something like tar & gzip), just in case things go wrong.

maddy939

ASKER

ok i ran the command from the WAS home directory "ls -lAR | grep root | wc -l" It did show me there were 511 files .

Now how will I be able to display those files so that I Can change the permissions.

HonorGod

no, you should be able to use the recursive chown command, something like that shown above...

maddy939

ASKER

so is it like chown -R user:user opt/IBM/WebSphere/Apsperver home

ASKER CERTIFIED SOLUTION

HonorGod

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

HonorGod

Thanks for the grade & points

Good luck & have a great day