We’re using sonarqube 8.8 developer edition (docker)
We noticed that since the upgrade from 8.4.1 to 8.8 (yesterday)
The New Bugs screen is blank, even though the count is not zero.
is this a filtering bug?
Click on the link and you get this
Thanks
Hi,
Thanks for reporting this. I don’t suppose there are any JS errors in your browser console?
What happens if you click “Show More”? Also, could you try dropping your ES indices?
Thx,
Ann
Hi Ann,
Thanks for the follow up
Thanks for reporting this. I don’t suppose there are any JS errors in your browser console?
No, just this
What happens if you click “Show More”?
Nothing happens
Also, could you try dropping your ES indices?
Just to be clear,
You’re asking me to stop Sonarqube
Delete from sonarqube_data volume the following folderses7/*
Rebuild sonarqube container and run.
If this is correct, what are the implications of doing so? would we lose any data?
Thanks
Hi,
Mostly, yes. There’s no actually need to “rebuild”, just restart. You won’t loose any data. Elasticsearch will automatically rebuild its indices from the database.
Ann
Hi Ann,
Sorry to report that clearing the indices did not make a difference.
I believe the Creation Date filter which applies NEW CODE is not working.
If I select All of course I see the all my tickets, when I switch to New Code which the individual run link to (apply) we see no tickets even though the counts is shown.
Clicking on the blue bar from the Creation Date Filter, it applies a date range
And that too is not working
Thanks
And this happens on all browsers.
Hi,
We’ve tried everything I know off-hand & I’ve referred this internally for the experts. And Europe is off for Easter Monday so it may be a few days.
Ann
Thanks Anne,
Appreciate your efforts, I look forward to a resolution as this is limiting the product usability / functionality.
Hi Ann,
Any update on this? This is quite limiting.
Thanks
Hey there.
Thanks Colin for the follow up.
Does this happen for all projects, just one?
Yes
Does it persist if you reanalyze the project?
Yes
Anything interesting in your logs directory? Specifically your web.log and es.log files (in the former, you should also be able to confirm your indices are being rebuilt)
web.log does not have much data, would web.log report indices being rebuilt or es.log?
Here’s a list of all log files showing timestamps and sizes.
-rwx------ 1 sonarqub sonarqub 88 Feb 25 2020 README.txt
-rw-r--r-- 1 sonarqub sonarqub 372112 Apr 7 23:59 access.2021-04-07.log
-rw-r--r-- 1 sonarqub sonarqub 339303 Apr 8 23:59 access.2021-04-08.log
-rw-r--r-- 1 sonarqub sonarqub 378993 Apr 9 23:59 access.2021-04-09.log
-rw-r--r-- 1 sonarqub sonarqub 266645 Apr 10 23:59 access.2021-04-10.log
-rw-r--r-- 1 sonarqub sonarqub 246240 Apr 11 23:59 access.2021-04-11.log
-rw-r--r-- 1 sonarqub sonarqub 339458 Apr 12 23:59 access.2021-04-12.log
-rw-r--r-- 1 sonarqub sonarqub 332091 Apr 13 23:59 access.2021-04-13.log
-rw-r--r-- 1 sonarqub sonarqub 133954 Apr 14 12:03 access.log
-rw-r--r-- 1 sonarqub sonarqub 84097 Apr 7 22:43 ce.2021-04-07.log
-rw-r--r-- 1 sonarqub sonarqub 67242 Apr 8 21:07 ce.2021-04-08.log
-rw-r--r-- 1 sonarqub sonarqub 109184 Apr 9 23:16 ce.2021-04-09.log
-rw-r--r-- 1 sonarqub sonarqub 25222 Apr 10 02:00 ce.2021-04-10.log
-rw-r--r-- 1 sonarqub sonarqub 83969 Apr 12 21:44 ce.2021-04-12.log
-rw-r--r-- 1 sonarqub sonarqub 75639 Apr 13 19:26 ce.2021-04-13.log
-rw-r--r-- 1 sonarqub sonarqub 8374 Apr 14 02:13 ce.log
-rwx------ 1 sonarqub sonarqub 8933 Jan 26 17:18 es.2021-01-26.log
-rwx------ 1 sonarqub sonarqub 4624 Feb 18 20:27 es.2021-02-18.log
-rwx------ 1 sonarqub sonarqub 186989 Mar 26 22:19 es.2021-03-26.log
-rwx------ 1 sonarqub sonarqub 24995 Mar 29 20:47 es.2021-03-29.log
-rwx------ 1 sonarqub sonarqub 32164 Mar 31 16:25 es.2021-03-31.log
-rwx------ 1 sonarqub sonarqub 8436 Apr 5 12:52 es.2021-04-05.log
-rw-r--r-- 1 sonarqub sonarqub 162 Apr 11 08:02 es.log
-rwx------ 1 sonarqub sonarqub 4249 Apr 29 2020 sonar.2020-04-29.log
-rwx------ 1 sonarqub sonarqub 2641 Jun 11 2020 sonar.2020-06-11.log
-rwx------ 1 sonarqub sonarqub 41689 Aug 25 2020 sonar.2020-08-25.log
-rwx------ 1 sonarqub sonarqub 2770 Oct 6 2020 sonar.2020-10-06.log
-rwx------ 1 sonarqub sonarqub 32512 Mar 29 17:42 sonar.2021-03-29.log
-rwx------ 1 sonarqub sonarqub 13200 Mar 31 16:25 sonar.2021-03-31.log
-rwx------ 1 sonarqub sonarqub 2614 Apr 5 12:52 sonar.log
-rwx------ 1 sonarqub sonarqub 18977 Apr 29 2020 web.2020-04-29.log
-rwx------ 1 sonarqub sonarqub 18397 Jun 11 2020 web.2020-06-11.log
-rw-r--r-- 1 sonarqub sonarqub 244 Apr 6 12:51 web.2021-04-06.log
-rw-r--r-- 1 sonarqub sonarqub 244 Apr 7 12:51 web.2021-04-07.log
-rw-r--r-- 1 sonarqub sonarqub 244 Apr 8 12:51 web.2021-04-08.log
-rw-r--r-- 1 sonarqub sonarqub 244 Apr 9 12:51 web.2021-04-09.log
-rw-r--r-- 1 sonarqub sonarqub 244 Apr 10 12:51 web.2021-04-10.log
-rw-r--r-- 1 sonarqub sonarqub 244 Apr 11 12:51 web.2021-04-11.log
-rw-r--r-- 1 sonarqub sonarqub 244 Apr 12 12:51 web.2021-04-12.log
-rw-r--r-- 1 sonarqub sonarqub 244 Apr 13 12:51 web.log
Notice how web.log is always 244 bytes in 2021.
The content is always (with different timestamps)
2021.04.13 12:51:51 INFO web[][o.s.s.a.p.ExpiredSessionsCleaner] Purge of expired session tokens has removed 0 elements
2021.04.13 12:51:51 INFO web[][o.s.s.a.p.ExpiredSessionsCleaner] Purge of expired SAML message ids has removed 0 elements
And here are some of the es logs
bash-5.0# cat es.log
2021.04.11 08:02:51 WARN es[][o.e.m.f.FsHealthService] health check of [/opt/sonarqube/data/es7/nodes/0] took [6204ms] which is above the warn threshold of [5s]
bash-5.0# cat es.2021-04-05.log
2021.04.05 12:48:44 INFO es[][o.e.n.Node] stopping ...
2021.04.05 12:48:44 INFO es[][o.e.n.Node] stopped
2021.04.05 12:48:44 INFO es[][o.e.n.Node] closing ...
2021.04.05 12:48:44 INFO es[][o.e.n.Node] closed
2021.04.05 12:51:18 INFO es[][o.e.n.Node] version[7.11.2], pid[37], build[default/tar/3e5a16cfec50876d20ea77b075070932c6464c7d/2021-03-06T05:54:38.141101Z], OS[Linux/5.4.0-1043-azure/amd64], JVM[AdoptOpenJDK/OpenJDK 64-Bit Server VM/11.0.10/11.0.10+9]
2021.04.05 12:51:18 INFO es[][o.e.n.Node] JVM home [/opt/java/openjdk]
2021.04.05 12:51:18 INFO es[][o.e.n.Node] JVM arguments [-XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -Djava.io.tmpdir=/opt/sonarqube/temp, -XX:ErrorFile=../logs/es_hs_err_pid%p.log, -Des.networkaddress.cache.ttl=60, -Des.networkaddress.cache.negative.ttl=10, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dio.netty.allocator.numDirectArenas=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.locale.providers=COMPAT, -Des.enforce.bootstrap.checks=true, -Xmx512m, -Xms512m, -XX:MaxDirectMemorySize=256m, -XX:+HeapDumpOnOutOfMemoryError, -Des.path.home=/opt/sonarqube/elasticsearch, -Des.path.conf=/opt/sonarqube/temp/conf/es, -Des.distribution.flavor=default, -Des.distribution.type=tar, -Des.bundled_jdk=false]
2021.04.05 12:51:19 INFO es[][o.e.p.PluginsService] loaded module [analysis-common]
2021.04.05 12:51:19 INFO es[][o.e.p.PluginsService] loaded module [lang-painless]
2021.04.05 12:51:19 INFO es[][o.e.p.PluginsService] loaded module [parent-join]
2021.04.05 12:51:19 INFO es[][o.e.p.PluginsService] loaded module [percolator]
2021.04.05 12:51:19 INFO es[][o.e.p.PluginsService] loaded module [transport-netty4]
2021.04.05 12:51:19 INFO es[][o.e.p.PluginsService] no plugins loaded
2021.04.05 12:51:19 INFO es[][o.e.e.NodeEnvironment] using [1] data paths, mounts [[/opt/sonarqube/data (/dev/sda1)]], net usable_space [11.5gb], net total_space [28.9gb], types [ext4]
2021.04.05 12:51:19 INFO es[][o.e.e.NodeEnvironment] heap size [495.3mb], compressed ordinary object pointers [true]
2021.04.05 12:51:19 INFO es[][o.e.n.Node] node name [sonarqube], node ID [S32nxqJMSm2phsMLYrNS6Q], cluster name [sonarqube], roles [master, remote_cluster_client, data, ingest]
2021.04.05 12:51:21 INFO es[][o.e.t.NettyAllocator] creating NettyAllocator with the following configs: [name=unpooled, suggested_max_allocation_size=1mb, factors={es.unsafe.use_unpooled_allocator=null, g1gc_enabled=false, g1gc_region_size=0b, heap_size=495.3mb}]
2021.04.05 12:51:21 INFO es[][o.e.d.DiscoveryModule] using discovery type [zen] and seed hosts providers [settings]
2021.04.05 12:51:21 INFO es[][o.e.g.DanglingIndicesState] gateway.auto_import_dangling_indices is disabled, dangling indices will not be automatically detected or imported and must be managed manually
2021.04.05 12:51:22 INFO es[][o.e.n.Node] initialized
2021.04.05 12:51:22 INFO es[][o.e.n.Node] starting ...
2021.04.05 12:51:22 INFO es[][o.e.t.TransportService] publish_address {127.0.0.1:36199}, bound_addresses {127.0.0.1:36199}
2021.04.05 12:51:22 INFO es[][o.e.b.BootstrapChecks] explicitly enforcing bootstrap checks
2021.04.05 12:51:22 INFO es[][o.e.c.c.Coordinator] setting initial configuration to VotingConfiguration{S32nxqJMSm2phsMLYrNS6Q}
2021.04.05 12:51:22 INFO es[][o.e.c.s.MasterService] elected-as-master ([1] nodes joined)[{sonarqube}{S32nxqJMSm2phsMLYrNS6Q}{ImwcjgLqR1OsuRdbCdLRXA}{127.0.0.1}{127.0.0.1:36199}{dimr}{rack_id=sonarqube} elect leader, _BECOME_MASTER_TASK_, _FINISH_ELECTION_], term: 1, version: 1, delta: master node changed {previous [], current [{sonarqube}{S32nxqJMSm2phsMLYrNS6Q}{ImwcjgLqR1OsuRdbCdLRXA}{127.0.0.1}{127.0.0.1:36199}{dimr}{rack_id=sonarqube}]}
2021.04.05 12:51:22 INFO es[][o.e.c.c.CoordinationState] cluster UUID set to [u83sTSYZTz6JDFo_iCLvpQ]
2021.04.05 12:51:22 INFO es[][o.e.c.s.ClusterApplierService] master node changed {previous [], current [{sonarqube}{S32nxqJMSm2phsMLYrNS6Q}{ImwcjgLqR1OsuRdbCdLRXA}{127.0.0.1}{127.0.0.1:36199}{dimr}{rack_id=sonarqube}]}, term: 1, version: 1, reason: Publication{term=1, version=1}
2021.04.05 12:51:23 INFO es[][o.e.g.GatewayService] recovered [0] indices into cluster_state
2021.04.05 12:51:23 INFO es[][o.e.h.AbstractHttpServerTransport] publish_address {127.0.0.1:9001}, bound_addresses {127.0.0.1:9001}
2021.04.05 12:51:23 INFO es[][o.e.n.Node] started
2021.04.05 12:51:37 INFO es[][o.e.c.m.MetadataCreateIndexService] [metadatas] creating index, cause [api], templates [], shards [1]/[0]
2021.04.05 12:51:38 INFO es[][o.e.c.r.a.AllocationService] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[metadatas][0]]]).
2021.04.05 12:51:38 INFO es[][o.e.c.m.MetadataMappingService] [metadatas/vEv9gCh_QduuB6AMlmI1QQ] create_mapping [metadata]
2021.04.05 12:51:39 INFO es[][o.e.c.m.MetadataCreateIndexService] [components] creating index, cause [api], templates [], shards [5]/[0]
2021.04.05 12:51:39 INFO es[][o.e.c.r.a.AllocationService] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[components][4]]]).
2021.04.05 12:51:39 INFO es[][o.e.c.m.MetadataMappingService] [components/3Lg3Zz0LTvucbOTaGa_p2w] create_mapping [auth]
2021.04.05 12:51:39 INFO es[][o.e.c.m.MetadataCreateIndexService] [projectmeasures] creating index, cause [api], templates [], shards [5]/[0]
2021.04.05 12:51:39 INFO es[][o.e.c.r.a.AllocationService] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[projectmeasures][4]]]).
2021.04.05 12:51:39 INFO es[][o.e.c.m.MetadataMappingService] [projectmeasures/NnM_WPt0T1-Mkjn14MzKpA] create_mapping [auth]
2021.04.05 12:51:40 INFO es[][o.e.c.m.MetadataCreateIndexService] [rules] creating index, cause [api], templates [], shards [2]/[0]
2021.04.05 12:51:40 INFO es[][o.e.c.r.a.AllocationService] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[rules][0]]]).
2021.04.05 12:51:40 INFO es[][o.e.c.m.MetadataMappingService] [rules/oKtJWuZCRy-tcJavRlfuRQ] create_mapping [rule]
2021.04.05 12:51:40 INFO es[][o.e.c.m.MetadataCreateIndexService] [issues] creating index, cause [api], templates [], shards [5]/[0]
2021.04.05 12:51:49 INFO es[][o.e.c.r.a.AllocationService] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[issues][4]]]).
2021.04.05 12:51:49 INFO es[][o.e.c.m.MetadataMappingService] [issues/j_A5XnFdSLao3R9CTB6HvA] create_mapping [auth]
2021.04.05 12:51:49 INFO es[][o.e.c.m.MetadataCreateIndexService] [users] creating index, cause [api], templates [], shards [1]/[0]
2021.04.05 12:51:49 INFO es[][o.e.c.r.a.AllocationService] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[users][0]]]).
2021.04.05 12:51:49 INFO es[][o.e.c.m.MetadataMappingService] [users/tvkCVCbjTAyxTj4HjcejzQ] create_mapping [user]
2021.04.05 12:51:49 INFO es[][o.e.c.m.MetadataCreateIndexService] [views] creating index, cause [api], templates [], shards [5]/[0]
2021.04.05 12:51:49 INFO es[][o.e.c.r.a.AllocationService] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[views][4]]]).
2021.04.05 12:51:49 INFO es[][o.e.c.m.MetadataMappingService] [views/12ycPAQhRJaKML2e-heuGg] create_mapping [view]
2021.04.05 12:52:10 INFO es[][o.e.c.s.IndexScopedSettings] updating [index.refresh_interval] from [30s] to [-1]
2021.04.05 12:52:10 INFO es[][o.e.c.s.IndexScopedSettings] updating [index.refresh_interval] from [30s] to [-1]
2021.04.05 12:52:10 INFO es[][o.e.c.s.IndexScopedSettings] updating [index.refresh_interval] from [-1] to [30s]
2021.04.05 12:52:10 INFO es[][o.e.c.s.IndexScopedSettings] updating [index.refresh_interval] from [-1] to [30s]
2021.04.05 12:52:11 INFO es[][o.e.c.s.IndexScopedSettings] updating [index.refresh_interval] from [30s] to [-1]
2021.04.05 12:52:11 INFO es[][o.e.c.s.IndexScopedSettings] updating [index.refresh_interval] from [30s] to [-1]
2021.04.05 12:52:11 INFO es[][o.e.c.s.IndexScopedSettings] updating [index.refresh_interval] from [-1] to [30s]
2021.04.05 12:52:11 INFO es[][o.e.c.s.IndexScopedSettings] updating [index.refresh_interval] from [-1] to [30s]
Hope this helps
Thanks
Hi Colin,
Any update?
Thanks
Hello @123dev ,
Could you inspect and share what request your browser is sending to SonarQube instance when the page is loaded?
I would especially be interested in api/issues/search calls - request and responses.
Cheers,
Jacek
Thanks Jacek for the follow up,
This is the call that is being made:
curl "https://sonar.local/api/issues/search?componentKeys=API&s=FILE_LINE&resolved=false&sinceLeakPeriod=true&types=BUG&ps=100&facets=owaspTop10^%^2CsansTop25^%^2Cseverities^%^2CsonarsourceSecurity^%^2Ctypes&additionalFields=_all&timeZone=America^%^2FToronto" ^
-H "authority: sonar.local" ^
-H "pragma: no-cache" ^
-H "cache-control: no-cache" ^
-H "sec-ch-ua: ^\^"Google Chrome^\^";v=^\^"89^\^", ^\^"Chromium^\^";v=^\^"89^\^", ^\^";Not A Brand^\^";v=^\^"99^\^"" ^
-H "accept: application/json" ^
-H "dnt: 1" ^
-H "x-xsrf-token: REDACTED" ^
-H "sec-ch-ua-mobile: ?0" ^
-H "user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36" ^
-H "sec-fetch-site: same-origin" ^
-H "sec-fetch-mode: cors" ^
-H "sec-fetch-dest: empty" ^
-H "referer: https://sonar.local/project/issues?id=API&resolved=false&sinceLeakPeriod=true&types=BUG" ^
-H "accept-language: en-US,en;q=0.9" ^
-H "cookie: XSRF-TOKEN=REDACTED; JWT-SESSION=REDACTED" ^
-H "sec-gpc: 1" ^
--compressed
Thanks a lot for the request, but could you attach a response of that call as well?
Also were you able to see those 2 bugs in the overall code, without new code filter?
I see that, there is a warning in your analysis in the screenshot you have attached previously, what is it about?
Hi Jacek,
Here’s the response
{
"total": 2,
"p": 1,
"ps": 100,
"paging": {
"pageIndex": 1,
"pageSize": 100,
"total": 2
},
"effortTotal": 7,
"issues": [],
"components": [],
"rules": [],
"users": [{
"login": "admin",
"name": "Administrator",
"active": true
}
],
"languages": [{
"key": "css",
"name": "CSS"
}, {
"key": "plsql",
"name": "PL/SQL"
}, {
"key": "scala",
"name": "Scala"
}, {
"key": "cs",
"name": "C#"
}, {
"key": "java",
"name": "Java"
}, {
"key": "web",
"name": "HTML"
}, {
"key": "jsp",
"name": "JSP"
}, {
"key": "xml",
"name": "XML"
}, {
"key": "flex",
"name": "Flex"
}, {
"key": "vbnet",
"name": "VB.NET"
}, {
"key": "swift",
"name": "Swift"
}, {
"key": "c",
"name": "C"
}, {
"key": "cpp",
"name": "C++"
}, {
"key": "objc",
"name": "Objective-C"
}, {
"key": "py",
"name": "Python"
}, {
"key": "kotlin",
"name": "Kotlin"
}, {
"key": "go",
"name": "Go"
}, {
"key": "tsql",
"name": "T-SQL"
}, {
"key": "js",
"name": "JavaScript"
}, {
"key": "ts",
"name": "TypeScript"
}, {
"key": "ruby",
"name": "Ruby"
}, {
"key": "php",
"name": "PHP"
}, {
"key": "abap",
"name": "ABAP"
}
],
"facets": [{
"property": "severities",
"values": [{
"val": "MINOR",
"count": 2
}, {
"val": "INFO",
"count": 0
}, {
"val": "MAJOR",
"count": 0
}, {
"val": "CRITICAL",
"count": 0
}, {
"val": "BLOCKER",
"count": 0
}
]
}, {
"property": "types",
"values": [{
"val": "CODE_SMELL",
"count": 43
}, {
"val": "BUG",
"count": 2
}, {
"val": "VULNERABILITY",
"count": 0
}
]
}, {
"property": "owaspTop10",
"values": []
}, {
"property": "sansTop25",
"values": []
}, {
"property": "sonarsourceSecurity",
"values": []
}
]
}
As for the warning, not sure which one you’re referring to, I see this.
Thanks
Thanks that’s helpful, could you also answer second question:
Also were you able to see those 2 bugs in the overall code, without new code filter?
If yes what are the dates you are seeing on them?
No, I’m not able to
If I choose a start date of Apr 22, I’m supposed to see 30 issues
I see none
If I set the start date to April 21
I see some tickets
but they don’t add up to 83 issues (only 45)
At the bottom is says 45 of 83
but show more does not show me more
