So I'll be happy to provide logs and everything, but I thought I'd take a stab at a post first, as I may just be hitting up against a setting I can change that I don't know about.
Am using the network edition, and I run a small network of modded Minecraft servers, some of them running very "heavy" modpacks that take a while to start up. Everything is working fine on all of them, except one running the "AllTheMods" (henceforth ATM) modpack. In fact, the ATM server was working great until we accumulated enough data that the server started taking quite a while to boot up.
What is happening is that it seems that if the server doesn't start within a certain amount of time, AMP simply gives up, kills the process (or whatever it does) and tries again. It's not a server issue, as I installed Mark2 (an open source Python panel) on the same server, and can boot and run the server without issue (and is what I'm currently using).
Since ATM isn't on the list of servers, I'm simply running it as a forge server using the current version they are using.
Is there a time limit or anything that you can think of that would be causing this? If so, is there something I can change to make it more lenient?
NOTE: I want to point out, as I did before, that AMP was working fine on this server until the server started taking longer to boot up.