Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: Brad BrezinskiHello, 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