Bukkit

What steps will reproduce the problem?
1.Install all dependencies
2.Executed the install
3.configured configs
4. launched ./abm.sh

What is the expected output? What do you see instead?
Proper screen comes up (3-way split)...
Appears as if the server is running in the top
Logs section shows the server shut down
Try to view the server from client, shows offline
Try to launch server from option 1 and it says it is launched
Try to stop the server via option 2 and it says it is shutting down but hangs and never stops shutting down

What version of the product are you using?

Do you have an error log of what happened?

Please provide any additional information below.

I have dug a little deeper.  If I bypass ./abm.sh and go into the scripts folder and run menu and status in seperate windows WITHOUT logs running, everything works great.  As soon as logs is turned on, it looses its mind.  

With the Menu & Status running and server off:  Status shows proper info... "not running"
With Menu, Status, and Log running with the server off:  Status suddenly populates with old info as if the server is up and running

With Menu & Status running and server on:  Status appears correct.
With Menu, Status, and Log : it thinks the server is already running yet it isnt.  Turn logs off, and the server starts right up.  It apparently gets some info from the logfile (on startup of log.sh and thinks the server is running.

Yes, ABM requires the log file to be generated to read a great deal of the information.  However, the log files are rotated on every startup and shutdown, as well as compressed.  There should be little reason to remove them.

Not sure I follow you. I am reporting that when the log.sh is on, the abm.sh THINKS the server is running and will not allow me to start the server.

Are you running other java applications? I wonder if it's having a hard time finding the right PID for the bukkit server.

Can you do a
# ps -ef |grep -i java

I've seen it where apps like crashplan running will cause issues.

@user777: Go

So I think your problems are actually fixed in the next version. I will try to push this out shortly.