ARK Server Admin Log: How to Read & Use It

This guide explains how to read and use the ARK: Survival Evolved server admin log, which records key events like player joins, deaths, structure demolitions, and admin commands. You’ll learn where to find the log, how to filter it, and how to use it to monitor your server or troubleshoot issues.

What You’ll Need

• Access to your ARK server’s file system (via FTP, a hosting control panel, or local files if you run a dedicated server).
• Basic familiarity with your server’s folder structure.
• A text editor that can handle large files (e.g., Notepad++, VS Code, or even a simple text editor).

Step-by-Step

1. Locate the log file. The admin log is typically stored in your server’s ShooterGame/Saved/Logs folder. Look for files named ArkServer.log or similar (e.g., ArkServer_YYYY.MM.DD.log if you have log rotation enabled). If you use a hosting provider, check their file manager or FTP access for this folder.
2. Open the log file. Download or open the log file with a text editor. If the file is very large (hundreds of MB), consider using a tool like tail (on Linux) or a text editor that can handle large files efficiently.
3. Understand the log format. Each log entry typically starts with a timestamp in brackets, followed by a log level (e.g., [Info], [Warning], [Error]), and then the message. For example: [2025.01.15-14.32.05:123][ 65]LogNet: Join succeeded: PlayerName. The number in brackets after the timestamp is the frame number, which is usually not important for admin purposes.
4. Identify key events. Search for specific keywords to find relevant events:
   • Player joins/leaves: Search for Join succeeded or Player joined to see who connected. Search for Disconnect or Logout to see who left.
   • Deaths: Search for was killed or died to find player or dino death messages.
   • Structure changes: Search for Demolished, Destroyed, or Placed to see when structures were built or removed.
   • Admin commands: Search for AdminCommand or Cheat to see which admin commands were executed and by whom.
   • Server errors: Search for Error or Warning to spot potential issues.
5. Filter the log. Use your text editor’s search or filter function to narrow down to specific players, tribes, or time periods. For example, you can search for a player’s Steam ID to see all their actions.
6. Use the log for troubleshooting. If players report issues (e.g., items disappearing, structures missing), check the log around the reported time to see if there were any relevant events like a server restart, a rollback, or a structure decay.
7. Check for admin command usage. If you suspect an admin is abusing commands, search for AdminCommand to see a history of commands run. Note that some commands may be logged differently depending on your server configuration.
8. Enable or adjust logging. If the log seems incomplete, you can adjust your server’s logging settings. In your GameUserSettings.ini, under [ServerSettings], you can set ServerLog to true or false, and ServerLogOutputFormat to control the detail level. Restart the server after changes.

Common Mistakes

• Looking in the wrong folder. The admin log is not in the same place as the game’s client logs. Make sure you’re looking in the server’s ShooterGame/Saved/Logs folder.
• Ignoring log rotation. If your server rotates logs (e.g., daily), you may need to check multiple files to get a complete picture. Don’t assume the current log contains everything.
• Misinterpreting timestamps. Log timestamps are usually in server local time, not your local time. If you’re comparing with player reports, convert time zones appropriately.
• Not enabling verbose logging. By default, the log may not contain all events. If you need more detail, enable verbose logging in the INI file.

Tips

• Use a log viewer tool. Tools like tail -f (Linux) or a GUI log viewer can help you monitor the log in real time.
• Create a filter preset. In your text editor, save a search for common keywords so you can quickly re-run it.
• Keep a backup. If you’re investigating a serious issue, make a copy of the log before making changes.
• Check the server console too. Some events may appear in the server console but not in the file log, or vice versa. Use both if possible.

Troubleshooting

• Log file is empty or missing. Ensure the server is running with logging enabled. Check the GameUserSettings.ini for ServerLog=True. Also, verify the folder path exists and is writable by the server process.
• Log is too large to open. Use a command-line tool like grep (Linux) or findstr (Windows) to search the file without opening it fully. For example: grep "Join succeeded" ArkServer.log.
• Log doesn’t show player chat. By default, player chat is not logged to the file. You need to enable chat logging via a mod or a separate plugin, or check the server console output.
• Timestamps are in UTC or offset. Some server configurations may log in UTC. Adjust your reading accordingly.
• Can’t find a specific event. If you know the approximate time, search with a broader keyword. Also, check if the event was perhaps not logged due to a server restart or a logging glitch.

Frequently Asked Questions

Where exactly is the admin log file located?

On a dedicated server, it’s usually in ShooterGame/Saved/Logs/ within the server installation folder. On a hosted server, use your provider’s file manager or FTP to navigate to that folder.

Can I see who used admin commands?

Yes, admin commands are typically logged with the player’s Steam ID and the command used. Search for AdminCommand or Cheat in the log.

Does the log include chat messages?

By default, no. Chat is not written to the file log. You need a mod or plugin to log chat, or you can view it in the server console if it’s running.

How do I enable more detailed logging?

In GameUserSettings.ini, under [ServerSettings], set ServerLog=True and ServerLogOutputFormat=Verbose (or similar). Restart the server for changes to take effect.

Why is the log file so huge?

ARK logs can grow quickly, especially with many players and events. Enable log rotation in your server settings or use an external log rotation tool to keep files manageable.

Can I delete old log files?

Yes, you can delete old logs to free up space. However, if you need them for troubleshooting, back them up first.

Related

• How Web Browsers Work: A Developer’s Guide
• AI Module Workload: Can It Scale If Boundaries Hold?
• Witcher 3 Main Quests: Full List by Act and Location