-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not start server with error: reading config: read config: is a directory #387
Comments
Just to confirm: this is not using the docker container but just 'native' Linux? I think the correct CLI flag should be |
This one caught me out too. The suggested commandline |
I have the exact same issue, both with changing the CWD or using absolute path. In both case I specify both the It seems to be able to find Here is the folders structure I used:
First by changing the CWD then calling the script:
Then by calling the script using absolute path:
I checked if it was a permission error but I do have ownership on all files:
I tried using the |
apparently this can happen when your config.json is malformed, for me it was a trailing comma at the end of the "false" statement regarding the "secure" setting. part of the program's response to this was to clobber my config.json, so make sure you keep a backup because FSM is merciless and will just nuke the file and replace it with something new. I've also noticed while investigating this issue for myself, that the program parses but does not pass the factorio bind IP or bind port arguments/settings from FSM to the server executable itself, all the bits needed are in place, it's just missing some glue logic apparently. :/ maybe I'll make a PR for a slight improvement to "server.go" which is where the issue lies. also, setting "autostart" in the settings file doesn't work. same issue, glue logic missing apparently. I ended up absolute pathing EVERYTHING in the config json file due to some other issues with how this program deals with paths, I've also backed up in case it nukes itself, again. It would mostly be a matter of setting the server object variables to the appropriate config values on server object instantiation, but go programming isn't exactly my wheelhouse, at the moment defaults of 34197 and 0.0.0.0 still seem to get passed when a config file is used and the program is called without any other arguments.
in theory if this config.json (with the censored values replaced with sane values) is used with FSM without any arguments, it should automatically spin up a server. what it does is ignore factorio_port, factorio_ip and autostart. unless autostart is passed as a program argument to FSM in which case it will autostart, but it still ignores the IP and port configuration or the equivalent program arguments. there's just some general issues with config file parsing and argument passing. it needs some love. I got this far, it works, I pulled the repo down today and got it working, it just doesn't listen to bind ip/bind port settings for the factorio server itself! sorry if this is OT/unwanted. |
The text was updated successfully, but these errors were encountered: