1. Community
  2. Game Support
  3. Rust
Seeing/changing Rust log file location?Solved
Posted 6 years ago
Last updated 6 years ago
#1

Iv noticed that with the May or June updated where they switch to a newer version of unity, that the rust server software is no longer outputting the log file (output_log.txt) to where it used to, even when trying to force it to with the -logfile option. Iv seen some people say that it no longer generates the log file, but this doesnt seem to be the case. The log file is just being created at
C:/users/<UserName>/appdata/locallow/facepunch studios ltd/rust/player.log

Is there any way to force it to generate the log file back to somewhere in the servers folder?

Posted 6 years ago
Last updated 6 years ago
#3
hello, as the title says how and where can i find the full NullReferenceException / NRE ?
I read -logfile in a .bat dont work any more, but it works for me before not on my OS dedicated Server. 
So how and where i can find the full NRE? At the moment its spams my server console and i can not see from which plugin it is! 
Or is it possible create a plugin that catch the full NRE error and will log it?
thanks
Posted 6 years ago
Last updated 6 years ago
#4
I dont think there is a similar plugin but you may ask someone to create an extension/plugin/whatever for it :)
Posted 6 years ago
Last updated 6 years ago
#5
Changing your -logfile to an absolute path should do the trick.
Posted 6 years ago
Last updated 6 years ago
#6
Yeah, but I remember someone was saying it doesnt work even with full (absolute) path now.
Posted 6 years ago
Last updated 6 years ago
#7
You made me curious, so I booted up my test server. At least for me (Win 10) it is still working with absolute path.
Posted 6 years ago
Last updated 6 years ago
#8
Thanks, will know this person was wrong :P
Posted 6 years ago
Last updated 6 years ago
#9
for example like this
-logfile "c:/example/path/output.txt"

we use WindowsServer2012R2 on our dedicated server. I will try it later. 
thanks
Posted 6 years ago
Last updated 6 years ago
#2
It wasn't generating it for a few updates I believe, which is what people were referring to. I believe it as reintroduced this update in that other location, but may be wrong. The -logifle option was from Unity, not Rust, so unless they handle that then it wouldn't be possible outside of a symlink on your system.
Posted 6 years ago
Last updated 6 years ago
#10
In response to dIMjIM ():
for example like this
-logfile "c:/example/path/output.txt"

we use WindowsServer2012...
My dev-env runs on a local Win7 machine, and this worked and still works for me all the time:
-logFile server/craggy/craggy_log.txt​
Posted 6 years ago
Last updated 6 years ago
#11
Thanks, I should have tried a full file path first, I just had it as -filepath "output.log" for the longest time and it worked without issue until the June update.
Posted 6 years ago
Last updated 6 years ago
#12
In response to dIMjIM ():
for example like this
-logfile "c:/example/path/output.txt"

we use WindowsServer2012...
They fixed it.
Posted 6 years ago
Last updated 6 years ago
#13
In response to Survey ():
They fixed it.
yes, i use like Fuji post a example, works for me now too.
Locked automatically