Honestly, they\u2019re like CPGuard\u2019s own running journal. Every scan, every bit of malware it catches, every move it makes\u2014it logs everything. Got a question about what happened, or why something broke? The answer\u2019s probably in there.<\/p>\n\n\n\n
Here\u2019s where you\u2019ll find the main log files:<\/strong><\/p>\n\n\n\n \/usr\/local\/cpguard\/logs\/<\/p>\n\n\n\n Inside that folder, you\u2019ll see a bunch of files, each tracking something different:<\/p>\n\n\n\n Once you know where to look, you\u2019ll stop dreading the logs. They\u2019re the best way to see what CPGuard\u2019s been up to.<\/p>\n\n\n\n You don\u2019t have to stick with the GUI. The CLI <\/a>commands are perfect when you\u2019re on SSH or managing a headless server. Here are some handy ones:<\/p>\n\n\n\n cpguard –status<\/p>\n\n\n\n Shows you if CPGuard is running smoothly.<\/p>\n\n\n\n cpguard –scan \/path\/to\/directory<\/p>\n\n\n\n Runs a manual scan on whatever directory you point it at. Results show up right in your terminal.<\/p>\n\n\n\n cpguard –report <\/p>\n\n\n\n Gives you a summary report of recent detections.<\/p>\n\n\n\n cpguard –update<\/p>\n\n\n\n Manually updates malware signatures or rules.<\/p>\n\n\n\n Every time you run one of these, CPGuard leaves a record in the logs. So you\u2019re never in the dark about what\u2019s been done.<\/p>\n\n\n\n Open a log, and you\u2019ll see lines packed with timestamps, file paths, and messages. For example:<\/p>\n\n\n\n [2025-10-28 03:12:17] [SCAN] File \/home\/user\/public_html\/index.php infected with PHP.Shell<\/p>\n\n\n\n [2025-10-28 03:12:17] [ACTION] Quarantined file to \/usr\/local\/cpguard\/quarantine\/<\/p>\n\n\n\n Here\u2019s what\u2019s what:<\/p>\n\n\n\n Timestamp: When it happened.<\/strong><\/p>\n\n\n\n Type: What kind of event\u2014scan, action, update, info.<\/p>\n\n\n\n Details: Which file or process it involved, and what was done.<\/p>\n\n\n\n If you\u2019re troubleshooting, search for keywords like ERROR, FAILED, or INFECTED. They jump right out and point you to the problem.<\/p>\n\n\n\n Logs are great for detail, but sometimes you just want a summary. That\u2019s what reports are for. Generate one with:<\/p>\n\n\n\n cpguard –report<\/p>\n\n\n\n A typical report shows:<\/p>\n\n\n\n Signature version<\/strong><\/p>\n\n\n\n It\u2019s a quick way to check if everything\u2019s working and nothing slipped through. If you\u2019ve set up automated reporting, CPGuard can even email these to you on a schedule. Makes life easier for admins who don\u2019t want to dig through logs every day.<\/p>\n\n\n\n When something\u2019s off, the logs are your best friend. For example:<\/p>\n\n\n\n Update not working? Check update.log for network or permission errors.<\/p>\n\n\n\n License problems? License.log will show if the server can\u2019t reach CPGuard\u2019s API.<\/p>\n\n\n\n Missing malware <\/a>detections? Scan.log might reveal a skipped directory or file.<\/p>\n\n\n\n You can speed things up with grep. For example:<\/p>\n\n\n\n grep “INFECTED” \/usr\/local\/cpguard\/logs\/malware.log<\/p>\n\n\n\n That\u2019ll pull up every infected file detection, instantly.<\/p>\n\n\n\n You don\u2019t have to remember every single log file or command. What really matters is knowing where to look when something comes up. Maybe you\u2019re chasing down a scan problem, checking if cleanup worked, or just making sure your server\u2019s behaving\u2014CPGuard\u2019s logs and reports lay it all out. Above all SupportPRO <\/a>can help you out with any requirements, which will make things better for you, so that none of the technical hurdles are cleared through us. <\/p>\n\n\n\n So if things feel weird, dive to SupportPRO<\/a>. Odds are, you\u2019ll get your answer way faster than you expect.<\/p>\n\n\n\n Facing issues? <\/p>\n\n\n\n Our technical support\n
Running CPGuard from the Command Line<\/strong><\/h2>\n\n\n\n
How to Read the Logs<\/strong><\/h2>\n\n\n\n
Reports: The Big Picture<\/strong><\/h2>\n\n\n\n
\n
Troubleshooting with Logs<\/strong><\/h2>\n\n\n\n
Wrapping Up<\/strong><\/h2>\n\n\n\n
engineers can solve it. <\/p>\n\n\n\n![\"Contact](\"https:\/\/no-cache.hubspot.com\/cta\/default\/2725694\/3350a795-db50-482f-9911-301930d1b1be.png\")
<\/a><\/span>