Page MenuHomeFeedback Tracker

-netlog no longer works.
Closed, ResolvedPublic

Description

-netlog is no longer working on our windows Servers. I know that in 1.52 you "moved it's location to %AppData%" (https://paronity.com/i/0L9Yj88k.png), but after checking there, I can confirm that it is not being written there. To take it further, I took procmon and watched the PID to confirm that it is not writing the netlog ANYWHERE on the machine. No netlog is being created at all any more. I use this file to map playerIDs to GUIDs through a custom tool, so this file is critical for the automation of our admin systems.

Procmon showing no Disk IOs for the netlog (which would be happening like CRAZY): https://paronity.com/i/0Q7pw81q.png
Empty AppData folder: https://paronity.com/i/8l9aM86j.png

It seems to be causing issues with Linux servers that have it enabled as well: http://feedback.arma3.com/view.php?id=25974

Details

Legacy ID
3989383301
Severity
None
Resolution
Open
Reproducibility
Always
Category
Dedicated Server
Steps To Reproduce

add -netlog to your startup parameters.

Event Timeline

Paronity edited Steps To Reproduce. (Show Details)Oct 11 2015, 4:37 AM
Paronity set Category to Dedicated Server.
Paronity set Reproducibility to Always.
Paronity set Severity to None.
Paronity set Resolution to Open.
Paronity set Legacy ID to 3989383301.May 8 2016, 12:56 PM
Adam added a comment.Oct 13 2015, 9:34 AM

-netlog works fine for me on Stable branch. Could you please provide more info? Maybe it has something to do with configs / mods. Thanks!

Thanks for the reply.

After you replied, I confirmed that as well. I then started eliminating parameters and I was finally able to get it to work. Turns out that the server executable behaves differently when started by FireDaemon. If I start the server with FireDaemon, the netlog doesn't get created or written to, but if I start it with a batch file or straight from cmd, it works just fine.

After that, I figured it had to be a permissions issue since FireDaemon starts services as LocalSystem by default. Once I added it to run it as the Administrator account, it logged the netlog just fine.

Are there any plans of allowing that to be moved in the future? I would much rather have it in the server folder somewhere. Especially since boxes with multiple servers are going to be hard to determine which is which..... Especially for ARMACon, that I'm working on. It's going to be impossible to determine which file to use since the files are distinguished by PID, which can't be determined by FTP or even HDD access for those running locally.....

Maybe you can do what the RPT file does and use the profile that is being used as to where it should put those files.

Either way, thanks for your help on this one.

dedmen closed this task as Resolved.May 18 2020, 11:09 AM