Initial Steps

• I have updated to the latest build from Jenkins before reporting a bug
• I have checked, if the bug was not already reported by using the search.
• Attached is my ForgeEssentials/modlist.txt, my latest.log, and my debug.log
  -> modlist.txt not available
• Also, attached are the client logs (if applicable)

Describe the bug
When i start the server with the latest Version of FE it crashes at some point. I can't figue out why the server is crashing. The log does not seem to give me an answer.

Desktop (please complete the following information):

• OS: Debian 10

Additional context
Add any other context about the problem here.

debug.log
latest.log
crash-2019-11-22_15.43.36-server.txt

Sure, thanks for the fast answer.
I changed the file extension to txt due to github limitations. In the FE folder they have the cfg extension.

The h2-database file mentioned in the playerlogger.cfg wasn't created... could this be the problem?

PlayerLogger.txt
main.txt

Hi, can you post main.cfg and PlayerLogger.cfg from ForgeEssentials folder?

If you run your minecraft server on debian, it's possible that the server doesn't have write/read perms on the ForgeEssentials folder.
Can you check it with ls -la in the FE folder?

I have already checked the read/write permissions of the FE folder. FE created serveral files before the crash without any problem. So i don't think this could be the case, will check it again anyways when i'm back home.

As i already predicted above the rights are all set correctly. :/

Check to see if your 'lib' folder in ./ForgeEssentials/lib exists and that it has 19 jar files in it. Based on your log, player logger is unable to find a library that it needs.

Check to see if your 'lib' folder in ./ForgeEssentials/lib exists and that it has 19 jar files in it. Based on your log, player logger is unable to find a library that it needs.

yep, 19 libs are in the folder, all accessible by the user running the server.

Hey,

Today i tried if the error is present anymore. Sadly i encountered the same error i mentioned above.
I enabled the debug mode in the main.cfg and reuploaded a debug.log for you. If i disable the module PlayerLogger in the main.cfg the server seems to start. I will now do some testing but at this point the only issue seems to be the PlayerLogger module causing this error

At this point i don't know if this has to do with another mod running on the server due to the huge amount on mods we are using. Perhabs this modlist helps you.

With best regards
H4mm3r

Did you try to create a second empty server with only FE?
Do you have a crash-report file with during the last crash?

Is this still an issue @H4mm3rb0y