Starting the dedicated server warns NO LOG FILE! on every line. If I knew the name of the file it was expecting I could create it.
Linked issues
is duplicated by 2
relates to 1
Attachments
Comments 19
For now Im just working around it with this quick startup script. This has been working well, but if you have a really busy server you probably want to rotate the log at some point.
(this is supposed to be all one line, it may wrap in this post)
cd /home/bedrock && screen -d -m -S Bedrock /bin/bash -c "LD_LIBRARY_PATH=. /home/bedrock/bedrock_server | tee -a /home/bedrock/mylog.log"
@nougator The .log file under the worlds folder is for the worlds database. That is different that the server.log file that would be the target of the messages in console output.
Hey, I'm still having this issue, I'm guessing it has to do with log files on the PC that is stored in the BDS CONTENT LOG LOCATION: `C:\Users\Administrator\AppData\Roaming\logs`.
This issue only occurs when multiple BDS instances are running causing what I'm guessing is a permissions issue for the second bds server.
Please fix this issue, or allow us to change the log file path please!
It is unwise to run any service as administrator. Not a solution to your problem but you might try running instances as normal users who will store logs in different locations. A thought anyway.
Yeah, I'd really like to be able to have a log file, but I don't see how to set that up to get rid of this message.