Question

Recently we moved from our old Sonar instance (2.x) to a recent 4.1 SonarQube version. During the migration we did a full port of the database with the migration of all data to latest 4.x format.

The migration was successful and all the data was available at our new server but, when trying to configure anything inside Sonar interface I detected that Sonar is not saving anything, it reloads the website with the old settings.

We are using the CAS plugin (the forked version that is compatible) and we are able to login into the system but unable to save any data. I have tried to have a look at log files but neither access nor sonar log give any information (some 404 but no exception to track). I have also tried to raise the log level but logback.xml is ignoring my settings...

I have run out of ideas (filesystem permissions... checked, database permissions... checked, logs... checked) and unable to find new information. Anyone knows how to increment log level on the new Sonar? Anyone has faced those problems?

Thanks

Was it helpful?

Solution

SonarQube CAS plugin is deprecated since SonarQube 3.3, as you can read on the documentation page.

So this plugin will probably not behave correctly with latest versions of SonarQube.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top