It turns out that PermSize is an invalid argument in Java 9, so it can’t even start even if done manually. But since you’re typing it in manually, I’m guessing you’re also …using a startup script instead of invoking Java itself?
Because otherwise, there isn’t a good reason PermSize should be coming up at all.
So we’re dealing with separate issues:
- EULA for some reason is never being detected as being accepted.
- FTB (or presumably just the startup script) uses arguments that Java9 does not like
- Can’t get vanilla to run.
For number #1, the EULA shouldn’t actually prevent anything from starting–it (at its worst) should just be wrongly nagging. EULAs didn’t even exist prior to 1.7 (or some version, I can’t remember), and those versions still can be used. I’ll have to look into this more, but I’d start with updating the webui (or actually more importantly, restarting the webui process).
Can you verify that when you ran all these commands manually you didn’t do it as root? If, for example, the eula.txt is owned by root, it only makes sense that as mc (or other non-root user) tries to change it to true, that the modification fails (and thus the popup returns over and over).
For #2, confirm you’re running a startup script rather than invoking it directly through Java’s binary. You’d have to manually remove the PermSize (or maybe some related argument) from the startup script since Java9 doesn’t accept it (or use the IgnoreUnrecognizedVMOptions, which I’d say is less preferable).
For #3. Clear out the value in server.properties for the ip-address. For the most part, this basically is always best off when empty, so it can attach to ‘all interfaces’ (0.0.0.0) on it’s own. But while you’re at it, restart your host machine, to make sure there aren’t any errant java processes in the background that are keeping 25566 (or 25565) active–perhaps from previous attempts at running the server that are still running (even if not actively hosting)