WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

WAS Console links not displaying

charanjeet singh

charanjeet singhTue November 15, 2011 11:12 AM

so did the issue resolved .
charanjeet singh

charanjeet singhTue November 15, 2011 12:21 PM

Can you provide dmgr logs .

  • 1.  WAS Console links not displaying

    Posted Fri November 11, 2011 09:06 AM
    Hi All,

    I am facing problem. Four nodes in cluster, all services needs to run with one user id.

    In my environment, all nodeagents and servers is running with wasadmin user id, but dmgr service is runnig with root. I stopped dgmr service with root. Again i started dmgr with wasadmin, at this time i faced problem. Because properties and logs files wasadmin not having permission. I given  permission with ownership with wasadmin. After that i started dmgr, its started successfully.

    I logged in console, i am unble to see any tabs or links in console other than welcome.

    Again i stopped dgmr service, with wasadmin user id, i started with root, now this time i am able to all tabs,links in console.


    Please help me. Where its going wrong.

    Its urgent.

    Thanks,
    Chinna


  • 2.  WAS Console links not displaying

    Posted Fri November 11, 2011 09:32 AM
    1. Stop DMGR and all Java process.
    2. Change permission and ownership back to the user you want WAS to run as .
    3. go /wstemp and delete everything
    4. go /temp and delete everything
    5. Start DMGR and now check.This should resolve your issue


  • 3.  WAS Console links not displaying

    Posted Fri November 11, 2011 11:47 AM
    Hi Charnjeet,

    Thanks for your reply.

    i have changed permission and ownership. I started again, still also same problem, but i didn't deleted /wstem and /temp folder data.


    I will try...

    Thanks
    Chinna


  • 4.  WAS Console links not displaying

    Posted Fri November 11, 2011 02:46 PM
    yes you need to delete that as wstemp contain the session for dmgr console


  • 5.  WAS Console links not displaying

    Posted Sun November 13, 2011 01:10 AM
    Hi Charanjeet,

    I want know one thing, when i am starting with root id, i can see the links, with wasadmin user id its not displaying.

    please help me, where i can see the configuraion files for WAS console links in WAS directory structure.

    I will check these files having permission are not.


    Thanks,
    Chinna.


  • 6.  WAS Console links not displaying

    Posted Sun November 13, 2011 09:33 PM
    if you getting it displayed by root then some of files are under root , but most imp is deleting the all content of folder "wstemp" under dmgr home dir.did you deleted that , plz confirm then only I can look into something else


  • 7.  WAS Console links not displaying

    Posted Mon November 14, 2011 01:35 AM
    Hi Charanjeet,

    I tried, but no improvement. I deleted temp, wstemp folder data. Same problem.


    Please help me.


    Thanks,
    Chinna


  • 8.  WAS Console links not displaying

    Posted Mon November 14, 2011 08:15 AM
    Can you stop dmgr and start it using wasadmin user and delete all the logs of DMGR and then start dmgr using wasadmin and then try acessing console and send me logs. it will require logs to investigate.


  • 9.  WAS Console links not displaying

    Posted Mon November 14, 2011 08:25 AM
    Charanjeet - Lots of good information in this thread!

    Chinna -  What OS are you running WebSphere on?  I've seen similarly odd behavior when running on Windows vs. UNIX platforms.


  • 10.  WAS Console links not displaying

    Posted Mon November 14, 2011 02:38 PM
    Just another pointer...

    make sure all the directories under websphere_root of DMGR machine are owned by 'wasadmin' user


    1. As Charanjeet mentioned, you need to clear websphere_root/profiles/temp and wstemp directories. 

    2. Make sure, these two directories are owned by the new user who is running websphere process

     
    Repeat the above two step for logs directory as well 


  • 11.  WAS Console links not displaying

    Posted Mon November 14, 2011 02:45 PM
    yes thats a good point josepg , make sure these dir are also owned by wasadmin user.
    run below commands

    chown -R wasadminuser:group
    chown -R wasadminuser:group

    chmod -R 755 wasadminuser:group
    chmod -R 755 wasadminuser:group


  • 12.  WAS Console links not displaying

    Posted Mon November 14, 2011 03:27 PM
    As Joseph called out, I believe the appropriate way to address the issue is to assign the specific user running the WebSphere DMGR service full ownership to all of the files and directories from the WAS root directory.  As elluded to in my last post, I've seen strange behavior on some systems where the permission changes didn't take effect correctly and some additional steps were required to set the permissions to a service account if the WAS binaries were installed as root.  

    A blanket permission change of 755 to the files could introduce a security concern and should be discussed with your security group and server administration groups.  It's always advisable to try to minimize the changes to the file system and only set permissions for the user that you intend to run the WebSphere services as.


  • 13.  WAS Console links not displaying

    Posted Tue November 15, 2011 11:05 AM
    Hi All,

    Thanks for your help.

    OS : AIX

    I given permission what we require. wasadmin id having permission and ownership for logs also.


    Thanks,
    Chinna







  • 14.  WAS Console links not displaying

    Posted Tue November 15, 2011 11:12 AM
    Hi chinna,
    Perhaps I'm not following, but are you elluding to the issue being resolved now?  Or is the issue still persistant?

    If the issue is still there, are you logging into the DMGR using the wasadmin account under each scenario?  The first scenario being running the DMGR service as ROOT and the second scenario being running the DMGR service as the wasadmin service account?   


  • 15.  WAS Console links not displaying

    Posted Tue November 15, 2011 11:12 AM
    so did the issue resolved .


  • 16.  WAS Console links not displaying

    Posted Tue November 15, 2011 11:26 AM
    Hi All,

    Its not resolved.

    WAS installation and profiles having required permission.

    I can able to Dmgr with wasadmin user id, links are not dispalyed.

    Where the colsone properties/configuration  files  reside in WAS directory structure.



    Thanks,
    Chinna


  • 17.  WAS Console links not displaying

    Posted Tue November 15, 2011 12:21 PM
    Can you provide dmgr logs .


  • 18.  WAS Console links not displaying

    Posted Tue November 15, 2011 07:09 PM
    try 

    Assuming that all the files under dmgr profile are owned by the newuser

    1. Stop each and every websphere process belongs to that cell 
    2. Remove all the logs belongs to DMGR. 
    3. start DMGR as new user
    4. Sync each node manually
    5. Start all JVMs
    6. Try login to console 
    7. Attach the DMGR logs here.

    Also just for clarification, note down who owns the each websphere process on all nodes. [dmgr, nodeagents, jvms]


  • 19.  WAS Console links not displaying

    Posted Wed November 16, 2011 05:51 AM
    Hi All,


    Please find the below error in Dm logs.

    [11/16/11 14:54:14:986 GMT+05:30] 0000001f FileDocument E ADMR0104E: The system is unable to read document cells/12APPTR21VCell01/nodes/12APPTR23VNode01/node-metadata.properties: java.io.IOException: The file access permissions do not allow the specified action.



    at java.io.File.checkAndCreate(File.java:1380)



    at java.io.File.createTempFile(File.java:1468)



    at com.ibm.ws.management.repository.FileDocument.createTempFile(FileDocument.java:557)



    at com.ibm.ws.management.repository.FileDocument.read(FileDocument.java:493)



    at com.ibm.ws.management.repository.FileRepository.extractInternal(FileRepository.java:1034)


    In all four nodes "node-metadata.properties" having "-rw-rw-r--" (664) permission in all the nodes, with wasadmin  ownership.

    After that i changed permission to 775. After changing permission i was stopped Dmgr, again started with wasadmin user id.

    still also same error's in logs.

    Please confirm, i want to stop , start entire setup or only Dmgr enough. I stop, started only Dmgr.


    Thanks,
    Chinna.


  • 20.  WAS Console links not displaying

    Posted Wed November 16, 2011 08:22 AM
    try using vi command to actually see whether you are able to do so ..

    vi  /12APPTR21VCell01/nodes/12APPTR23VNode01/node-metadata.properties

    All the nodes need to be ownership of same user .


  • 21.  WAS Console links not displaying

    Posted Wed November 16, 2011 08:23 AM
    Morning chinna.

    The error you have posted is indicative of a permission issue (obviously.)  A quick google search has the following. which appears to be the same issue as you are currently experiencing.  Perhaps it can help you out:

    moturu.wordpress.com/admr0104e/
      

    Below is a DIRECT COPY FROM THE SOURCE SITE.  It's copied here for future archival purposes only.  I do not claim to be the author, just someone interested in making sure the information is around for future GWC users.

    ADMR0104E- Unable to read document





    While we were trying to deploy an application on WAS 6.0.2.19 .. we had the following errors:


    0000002e FileDocument  E   ADMR0104E: The system is unable to read document cells/server/nodes/nodename/perftuners.xml: java.io.IOException: The file access permissions do not allow the specified action.
    0000002e WorkSpaceMast E   Unable to create temp file for document: cells/server/nodes/nodename/perftuners.xml
    0000002e ServerRuleDri E  perfalert.Exception.errorjava.security.PrivilegedActionException: com.ibm.ws.sm.workspace.WorkSpaceException: WKSP0012E Exception when while extracting cells/server/nodes/nodename/perftuners.xml from Config Repository–com.ibm.websphere.management.exception.DocumentIOException: Unable to create temp file for document: cells/CU01-tx8aiuci00230/nodes/NU01-tx8aiuci00230/perftuners.xml [7/14/09 13:40:47:586 CDT]
    0000002e ServerRuleDri E   perfalert.Exception.error


    We figured out the error is mainly beacuse of the permissions issue. Some files are owned by root user which is preventing the was user to write the files to tmp directory which are created while deploying the application .


    Work Around:
    1. check who owns:  /appserver/config/temp
    2. check who owns: /appserver/logs/ffdc
    3. If possible try to chown everything under /Appserver and  /DMGR to wasuser. If any files are not owned by wasuser they will be displayed.


    Suporting Docs:www-01.ibm.com/support/docview.wss?uid=s...


    www-01.ibm.com/support/docview.wss?uid=s...






    Additional support information that may help can be found here, albeit from a slightly different version of WAS:  publib.boulder.ibm.com/infocenter/wasinf...

    Good luck and let us know if you give it a shot and the outcome.

    Erik


Related Content