LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  LAE Won't Start, server.Server PIDs?

    Employee
    Posted 07-10-2017 11:16

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Brad Brezinski

    Hello, My LAE server is not starting. I do get a PID on the server.Server, but nothing else (please see status below). Also, I'm getting different PIDs when I grep on "server.Server" (6864) and "lavastorm.brain.server.Server" (6887). I was curious about that because serverShutDown script does this kill, "pkill -f com.lavastorm.brain.server.Server" .... Does that mean anything, not sure what to try next. Thanks, Brad

    Update - Question:
    I'm assuming I would do a kill on the PID I find with ps -ef | grep server.Server (6864), not the other PID (6887). Is that correct?
    Update:
    I also seem to be getting no such process when I try to kill the PID listed on this greps? Thanks, Brad


    $ netstat -tnlp | egrep "(7721|8080|8089|9092)"
    (Not all processes could be identified, non-owned process info
    will not be shown, you would have to be root to see it all.)
    $ ps -ef | grep server.Server
    t1lae1c1 6584 127478 0 14:04 pts/0 00:00:00 grep server.Server
    $ cat startServer_6.1.4

    . ../.profile.lavastorm

    ./startDatabase &
    ./startLavastormJettyServer &
    ./laeServer > ../log/laeServer.log 2>&1 &
    $ nohup shutDownServer.sh
    nohup: failed to open `nohup.out': Read-only file system
    nohup: failed to open `/opt/app/t1lae1c1/nohup.out': Read-only file system
    $ ps -ef | grep server.Server
    t1lae1c1 6792 127478 0 14:05 pts/0 00:00:00 grep server.Server
    $ cat shutDownServer.sh
    . "/opt/app/t1lae1c1/Lavastorm/LAE6.1.4/.profile.lavastorm"

    pkill -f com.lavastorm.brain.server.Server
    $ ps -ef | grep server.Server
    t1lae1c1 6864 127478 0 14:07 pts/0 00:00:00 grep server.Server
    $ ps -ef | grep lavastorm.brain.server.Server
    t1lae1c1 6887 127478 0 14:08 pts/0 00:00:00 grep lavastorm.brain.server.Server


  • 2.  RE: LAE Won't Start, server.Server PIDs?

    Employee
    Posted 07-10-2017 14:09

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: prasmussen

    Hi Brad - When you do a 'ps -ef | grep Server' , you should see "com.lavastorm.brain.server.Server". The easiest fix is to shut down all of the existing processes, and then force a shutdown on any remaining processes with a kill -9. Once that is done, please delete the logs and restart. This should give you an idea of what is happening. Are you seeing any messages in the log(s) about the failure to start? Please make sure to look in "/$LAE_HOME/log/lae/server/server.7721.log".

    Prior to doing this, can you do a 'df -k' just to validate the /opt file system is not full.