Prev
Next
Forums S3 Systems Administration

Nodeagent will not start in Websphere

Sort:
You are not authorized to post a reply.
Author
Messages
ThomasT
Advanced Member
Posts: 27
Advanced Member
10/20/2010 4:45 PM
    AIX, Lawenv 9.0.0.6

    I am trying to recycle websphere 6.1
    Lawson environment is up and running OK. I have recycled the environment in the correct order.

    On command line, I start up the node agent successfully. It says "Server nodeagent open for e-business: process is 90704"

    However in the deployment manager console, the nodeagent has a big red X on the right, meaning it is still not started. I have tried repeatedly to refresh the console screen, log out, etc. and it still appears the node agent will not or has not started. I am getting conflicting messages that is has actually started. Command line says it has started, but console says it is not started. I have rechecked and reviewed all settings, I have not made any changes or configurations to websphere. This was working up until maybe a week ago. I don't know what if anything has changed.

    Help. How can I tell what is going on?
    I can't start the app server on websphere because the nodeagent still apparently has not started.

    Thank you in advance
    MattD
    Veteran Member
    Posts: 94
    Veteran Member
    10/20/2010 5:11 PM
      If you do pf -es is there multiple instances of the WAS processes maybe. I have seen a process not die properly causing the console to show something other than the command line.

      Cheers.
      ThomasT
      Advanced Member
      Posts: 27
      Advanced Member
      10/20/2010 5:33 PM
        Thank you, I did that previous with pf -es and stopped the appropriate WAS instance but I tried again on command line; it started up on command line, but still fails to show up as active on console
        MattD
        Veteran Member
        Posts: 94
        Veteran Member
        10/20/2010 5:47 PM
          This is a stretch but have you tried recycling the box. I know that is not an ideal solution but sometimes necessary.

          Cheers.
          ThomasT
          Advanced Member
          Posts: 27
          Advanced Member
          10/20/2010 6:24 PM
            More information: I tried to synch the nodes, with trace on, and found out the certificate had expired a few days ago. Not sure how or why that happened. ANyways I am going to renew the certificate and everything else. I will update within this post in case anyone is interested.
            You are not authorized to post a reply.