Scheduled Log Scanner not working
Asked by R Donato:

Hello,

Prior to upgrading to 5.5.2 from 4.3.1 to 5.0.3 to 5.5.2, I received scanner logs daily per the schedule I had set. After the upgrade which included lots of dev testing and reading release notes, I have to manually generate the log scan despite the schedule set. Is there any way to fix this?

We're also experiencing long latency issues. During testing pages loaded quickly and easily. Now they are very sluggish. Is there anything I should check to see what could be causing this?

Any help is greatly appreciated.

Thanks,

rd


Answers:
author: R Donato
body: Hi Paul,

I checked the email error queue. And luckily, there are no errors in it. But I didn't see settings in that section for Authenticated Users.

Did you add a new SMTP or POP mail server to receive the logs? That may be my problem. But I'm not sure which one to use. Also, I came across some instructions on Changing the Destination of the Log Files on <https://confluence.atlassian.com/x/sYN1Bg>. If this information can solve my problem, I'll have to pass this on to our IT department since it requires stopping Confluence.

Thanks for your suggestions! I'll update this post when I have more information.

Regards,

r

comments: author: Paul Biagio
body: The authenticated users setting was changed on our actual email server and not in Confluence. A very easy way to debug is to schedule the log scan for a specific time and at that point tail the error log and see what happens.


author: R Donato
body: Great suggestion. I'll try that and review the results. Thanks again!


author: Paul Biagio
body: Check the email error queue. I had the same issue and then realized that our email server settings were changed to not allow Authenticated Users to send as 'any sender'. Mail comes from [noreply@atlassian.com](mailto:noreply@atlassian.com) and fails authentication.


author: R Donato
body: Hello Guilherme,

Yes, I used the built-in Hercules Atlassian Support Bot. Below is how I scheduled the regular scans:

Under **Confluence Admin** \> **Atlassian Support Tools** , I selected the **Scheduled Log Scan** tab.

I entered the following information:

* **Enabled** to run the report.
* **Start Time:** 6:30.
* **Frequency:** daily
* **Recipients:** my work email.

I saved the changes. This is exactly what I had set up when we were on 4.3.1. During that time, I received daily reports from the log scan.

I'll ask the engineer here to check memory and increase it. When I look at **System Information** , the **Heap Memory** is 80% free with **Maximum Heap Size** at 3640 MB. And the **Permanent Generation Memory** is 76% free with T**otal Free Memory** at 2913 MB. Are there any other stats I should review to figure out the performance issue?

Thanks for your help! :)

comments: author: Madhu Vasudevan
body: We are also facing the same issue with Hercules log scan Scheduler. Any solution for this issue ?


author: R Donato
body: No resolution for us yet. If I want a log file, I run it manually. What version are you using? We're still on 5.4.2.


author: Madhu Vasudevan
body: Hi, We are using JIRA v6.2.7


author: Guilherme Nedel [Atlassian]
body: Hello Rd,

Could you describe the method for scheduling and scanning Confluence logs, that used to work with 4.3.1 that is no longer functional? Confluence does have [built in tool](https://confluence.atlassian.com/display/DOC/Troubleshooting+Problems+and+Requesting+Technical+Support#TroubleshootingProblemsandRequestingTechnicalSupport-scanner) for scanning logs, was this the case?

Regarding the second point, there is a chance that the application is demanding more resources from the system, em thus having the performance decreased, you may like to check the available memory status, and consider an increase adjustment as per [this documentation](https://confluence.atlassian.com/display/CONFKB/How+to+Fix+Out+of+Memory+Errors+by+Increasing+Available+Memory#HowtoFixOutofMemoryErrorsbyIncreasingAvailableMemory-Determineavailablesystemmemory).