adding any mods to 41.72 on debian server will fail to start

[Shifty51]

As soon as a new fresh server installed via steamcmd on linux begins to reference non-existant folders in the Zomboid root folder. this can be replicated by starting a new server. stopping it when it starts gracefully, add any valid workshop name and id where applicable and start server via start script. Sample error below:
 

ERROR: General     , 1663177466436> 4,080,024> ExceptionLogger.logException> Exception thrown java.nio.file.NoSuchFileException: /home/debian/Zomboid/mods at UnixException.translateToIOException.
ERROR: General     , 1663177466438> 4,080,026> DebugLogStream.printException> Stack trace:
java.nio.file.NoSuchFileException: /home/debian/Zomboid/mods
        at java.base/sun.nio.fs.UnixException.translateToIOException(Unknown Source)
        at java.base/sun.nio.fs.UnixException.asIOException(Unknown Source)
        at java.base/sun.nio.fs.LinuxWatchService$Poller.implRegister(Unknown Source)
        at java.base/sun.nio.fs.AbstractPoller.processRequests(Unknown Source)
        at java.base/sun.nio.fs.LinuxWatchService$Poller.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)

 

[Shifty51]

Further amendment, this is specific to a mod, and I don't think this bug report has any value. I'll close it now, but hoping if someone has this issue in the future try disabling all but on known good mod to test.

[Shakesbeere]

I'll add: to circumvent this issue you can also simply mkdir Zomboid/mods

That should also solve the issue, the folder goes unused anyway.

[Pandorea]

12 hours ago, Shakesbeere said:

I'll add: to circumvent this issue you can also simply mkdir Zomboid/mods

That should also solve the issue, the folder goes unused anyway.

 

Thanks for posting a possible solution! Might help someone else down the line!