Hi
I'm running a dedicated bedrock server from a home server and cannot seem to find what ever is the problem with my server not creating content log files. I have enabled the settling in my server.properties file and have done some minor tweaks to game play but yet cannot find the problem. Every time I restart my server logs from the previous launch do not n carry over the reason I'm trying to log my server activity is because I let a few close friends join and play on the server and would like to monitor who exactly joins there.
Attachments
Comments 9
migrated
Hi Jason,
The Content Log only logs issues with content (for examples issues with a behaviour pack or similar, it does not log console output. Console output is logged to the \internalStorage\Dedicated_Server.txt
However that file is only written on successful server stop and is overwritten when the server launches so at a very basic level you would need to set up a script that copies and renames that file after each successful stop or before each start.
For more logging options you would need to put in a suggestion at https://feedback.minecraft.net
All the best.
Ionic
Hi Jason,
The Content Log only logs issues with content (for examples issues with a behaviour pack or similar, it does not log console output. Console output is logged to the \internalStorage\Dedicated_Server.txt
However that file is only written on successful server stop and is overwritten when the server launches so at a very basic level you would need to set up a script that copies and renames that file after each successful stop or before each start.
For more logging options you would need to put in a suggestion at https://feedback.minecraft.net
All the best.
Ionic
This folder is always empty yet it says its being written to this .txt file
If crash errors are not logged to this file where might I find some information on why my server crashes when using "/stop" command I have not once stopped my server without it crashing and someone losing inventory or chests bugging out ingame.
This folder is always empty yet it says its being written to this .txt file
If crash errors are not logged to this file where might I find some information on why my server crashes when using "/stop" command I have not once stopped my server without it crashing and someone losing inventory or chests bugging out ingame.
To see the output of the crash just launch the server from a command prompt or Powershell window rather than double clicking the executable. The command prompt will remain open with the crash details when the service fails.
Its not likely to do you much good though, nothing helpful is shown on the output from experience on here. Its all logged to Mojang automatically as well so unless we're able to work out exact steps to reproduce they aren't tracked here because its impossible to track whether a non-descript, occasional crash has been fixed.
If you want to log direct to a log file you would have to hook into stdout. There are existing scripts that do that for linux but I haven't seen any for Windows.
Ionic
To see the output of the crash just launch the server from a command prompt or Powershell window rather than double clicking the executable. The command prompt will remain open with the crash details when the service fails.
Its not likely to do you much good though, nothing helpful is shown on the output from experience on here. Its all logged to Mojang automatically as well so unless we're able to work out exact steps to reproduce they aren't tracked here because its impossible to track whether a non-descript, occasional crash has been fixed.
If you want to log direct to a log file you would have to hook into stdout. There are existing scripts that do that for linux but I haven't seen any for Windows.
Ionic
Note that the console log DOES NOT log anything if you just close out the .exe, you need to run the command "STOP" in order for the Dedicated_Server.txt to update.