-
Bug
-
Resolution: Tracked Elsewhere
-
Low
-
3.8.1
-
None
-
None
-
Severity 3 - Minor
-
1
-
Summary
When performing either a Hercules Log Scan or Scheduled Log Scan in FishEye while behind a reverse proxy the scan does not seem to complete.
Environment
- FishEye installed behind a reverse proxy
- Experienced both behind nginx & apache
Steps to Reproduce
- Log Scanner
- With FishEye integrated with the reverse proxy navigate to Administration > System Settings > Atlassian Support Tools
- Select the Log Scanner tab
- Select the log file you wish to scan and select Scan
- Scheduled Scanner
- With FishEye integrated with the reverse proxy navigate to Administration > System Settings > Atlassian Support Tools
- Select the Scheduled Log Scan tab
- Schedule a scan
Expected Results
In both cases the scan completes successfully and this is reflected in the logs;
2015-08-12 17:55:40,593 INFO [hercules ] com.atlassian.support.tools.hercules.LogScanReportTask LogScanReportTask-call - Scanning log file '/opt/fecru-3.8.0/var/log/atlassian-fisheye-2015-08-12.log'... 2015-08-12 17:55:43,140 INFO [hercules ] com.atlassian.support.tools.hercules.LogScanReportTask LogScanReportTask-call - Finished scanning /opt/fecru-3.8.0/var/log/atlassian-fisheye-2015-08-12.log using Hercules. Total size: 52063 bytes. Time taken: 2545 ms. Patterns matched: 0 2015-08-12 17:55:43,140 INFO [hercules ] com.atlassian.support.tools.hercules.LogScanReportTask LogScanReportTask-call - No issues found in log file '/opt/fecru-3.8.0/var/log/atlassian-fisheye-2015-08-12.log'. Not sending the report by email.
Above is without a proxy in place and for the Scheduled Log Scan.
Actual Results
The below details are shown in the fisheye.out file (for Scheduled Log Scan):
2015-08-13 15:04:58,225 INFO [hercules ] com.atlassian.support.tools.hercules.LogScanReportTask LogScanReportTask-call - Scanning log file '/var/AtlasData/fecru-37/var/log/atlassian-fisheye-2015-08-13.log'... 2015-08-13 15:04:58,226 INFO [hercules ] com.atlassian.support.tools.hercules.LogScanReportTask LogScanReportTask-call - Finished scanning /var/AtlasData/fecru-37/var/log/atlassian-fisheye-2015-08-13.log using Hercules. Total size: 3424133 bytes. Time taken: 0 ms. Patterns matched: 0 2015-08-13 15:04:58,226 INFO [hercules ] com.atlassian.support.tools.hercules.LogScanReportTask LogScanReportTask-call - No issues found in log file '/var/AtlasData/fecru-37/var/log/atlassian-fisheye-2015-08-13.log'. Not sending the report by email.
As can be seen the scan takes 0ms to complete - in comparison to the test without a proxy this is not true.
Workaround
Bypassing the proxy allows the scan to be completed successfully..
Notes
Removing the proxy-port proxy-scheme proxy-host parameters from FishEye results in the scan completing successfully;
2015-08-19 16:59:19,127 INFO [hercules ] com.atlassian.support.tools.hercules.LogScanReportTask LogScanReportTask-call - Scanning log file '/var/AtlasData/fecru-37/var/log/atlassian-fisheye-2015-08-19.log'... 2015-08-19 16:59:21,861 INFO [hercules ] com.atlassian.support.tools.hercules.LogScanReportTask LogScanReportTask-call - Finished scanning /var/AtlasData/fecru-37/var/log/atlassian-fisheye-2015-08-19.log using Hercules. Total size: 55267 bytes. Time taken: 2733 ms. Patterns matched: 0 2015-08-19 16:59:21,861 INFO [hercules ] com.atlassian.support.tools.hercules.LogScanReportTask LogScanReportTask-call - No issues found in log file '/var/AtlasData/fecru-37/var/log/atlassian-fisheye-2015-08-19.log'. Not sending the report by email.
Note
Removing these parameters can break other features such as Application links