No Log.txt

Silent262

My server is either not generating a log.txt OR it is being generated out of my reach. The admin panel is not showing me the log in my root directory. I am in a non-default location, and being hosted by JestServers. I have already sent a ticket asking him, and I figured I would ask around here for ideas. I will get back to you when he responds, or if there are updates.

UPDATE:
Jest has responded and said that the logviewer is reporting all the txt files in the accessible section of the server. I do not have access, and, therefore, the log is either still being generated in appdata OR not at all. Any other thoughts, guys?

CoTTon

C:\Users\Administrator\AppData\Roaming\Natural Selection 2

Silent262

<!--quoteo(post=2015130:date=Nov 8 2012, 02:27 AM:name=CoTTon)--><div class='quotetop'>QUOTE (CoTTon @ Nov 8 2012, 02:27 AM) <a href="index.php?act=findpost&pid=2015130"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->C:\Users\Administrator\AppData\Roaming\Natural Selection 2<!--QuoteEnd--></div><!--QuoteEEnd-->

I am on a server. I do not have access to the AppData, and it is likely there is more than one NS2 server located on my box. I have NO access to AppData, and I cannot reasonably expect access to that location.

Let me be more blunt: I need a way to get a log without having access to AppData. I had a crash and would obviously like to report it. This will not happen, because I have no log. I need a commandline switch to move said log OR the log needs to be generated in the same directory as the Server.exe. If this is the case, then I am having a problem, and that deserves reporting, too.

kraze

Hi,

I am not sure how your company has your server setup but I would image they are using the -file option in your command line, wherever the location leads is where the log.txt should be created.

They are most likely not specifying the log.txt file itself. If that is the case they would need to edit your command line to this;

-file "C:yourserver\log.txt"

Vitdom

My dedicated server puts the log files in C:\, when the server is in C:\NS2-server\. It's quite irritating. :P

kraze

Probably specifying this on your command line will fix that;

-file "C:yourserver\log.txt"

Silent262

Alright, I am trying that. I will get back to you when my provider gets back to me.

eLbot

I'm not sure if I've missed a change, but -file is the pointer to the file that holds your command line options (typically server.txt). So to see people suggest you add that flag with the idea that this will instruct the server instance to create a log file there makes me a little worried that you're about to strip every command line option away from your server boot and breaking your server in the process.

Silent262

That is kind of what I thought eLbot, after reading the dedicated usage I did not suggest that to my provider, who probably would not have done it anyway. So, back to trying other solutions. Are there other solutions?

kraze

I didn't actually test that, just a best guess :/

I did just test it though and it does not break the server, server just ignores it since it doesn't see it as valid.

Whosat

The log will be created in %APPDATA%\Natural Selection 2.

I don't think there is any way to change the log directory - I agree that this issue does need to be reported.