To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/6e36157f-f7f3-4efa-9440-5e8c566c8669%40googlegroups.com.--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/07c7vA9Ye0g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.
To unsubscribe from this group and all its topics, send an email to sonarqube+...@googlegroups.com.
To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/59b1df6f-ca2f-4819-b919-3a605696a845%40googlegroups.com.
Cool!Can you please reply to the list with the maximum details (I'm not sure to understand what kind of lock you are talking about, is it a Windows specific feature?). It could help other people.Thanks
Julien Henry | SonarSource
Developer
https://sonarsource.com
2018-02-21 15:22 GMT+01:00 Syed Muhammad Ali Naqvi <smana...@gmail.com>:Hi Julien,Thanks for your time. My issue is fixed now. It was creating a deadlock on the folder. Just saw one issue on the internet and they advised to check the sonar logs.
And then I came to knew that it has the logs folder and checked the logs, and voilla. It worked. Just restarted the service and removed the lock file.Thanks again.On Wed, Feb 21, 2018 at 6:44 PM, Syed Muhammad Ali Naqvi <smana...@gmail.com> wrote:This report is generated in my project target "target\sonar\scanner-report" folder. Not on the server. But why it's not uploading the report, is still a mystery.On Wed, Feb 21, 2018 at 6:39 PM, Julien HENRY <julien...@sonarsource.com> wrote:Wait, how do you get this analysis.log? In the background task UI? If yes then it means the scanner report was correctly received by the server, so I'm even more puzzled.Regarding Wireshark, I'm targetting the loopback interface, and filtering to only keep packets for port 9000:
Julien Henry | SonarSource
Developer
https://sonarsource.com
2018-02-21 14:30 GMT+01:00 Syed Muhammad Ali Naqvi <smana...@gmail.com>:I am also attaching the file generated by Sonar. Perhaps you can find something in this file that can help me sort out the issue.On Wed, Feb 21, 2018 at 6:19 PM, Syed Muhammad Ali Naqvi <smana...@gmail.com> wrote:I have been trying to do it. How can I see my localhost traffic? Can you please mention the step? Thanks. I am using windows 10On Wed, Feb 21, 2018 at 6:08 PM, Julien HENRY <julien...@sonarsource.com> wrote:I'm a bit confused. In your previous logs the server URL was http://localhost:9000 but your capture seems to only contains connections to 192.168.0.xx with SSL. Can you clarify? Have you selected the correct interface (loopback) when doing the capture?
Julien Henry | SonarSource
Developer
https://sonarsource.com
2018-02-21 13:43 GMT+01:00 Syed Muhammad Ali Naqvi <smana...@gmail.com>:Hi Henry, Please find the attached scan.I truly appreciate the way you are helping.