# Migrating Sonarqube from RHEL7 to RHEL8 server **URL:** \ **Category:** SonarQube Server / Community Build\ **Created:** [June 10, 2024, 11:38pm UTC](https://community.sonarsource.com/t/migrating-sonarqube-from-rhel7-to-rhel8-server/117019 "2024-06-10T23:38:37Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![zeito29](https://avatars.discourse-cdn.com/v4/letter/z/d78d45/32.png) [@zeito29](https://community.sonarsource.com/u/zeito29)\ **Post date:** [June 10, 2024, 11:38pm UTC](https://community.sonarsource.com/t/migrating-sonarqube-from-rhel7-to-rhel8-server/117019/1 "2024-06-10T23:38:37Z")
Must-share information (formatted with [Markdown](https://commonmark.org/help/)): - which versions are you using: **Sonarqube Developer Edition, version 8.9.6 Stand-alone (yes, I know it’s “old” and I will upgrade it if I can ever get it off of RHEL7)** - how is SonarQube deployed: **Zip (I think)** - what are you trying to achieve: **Migrate to new server** - what have you tried so far to achieve this: I followed the suggested tips on the following three community forums (one was posted by me): > [@Migrating Sonarqube from RHEL7 to RHEL8](https://community.sonarsource.com/t/migrating-sonarqube-from-rhel7-to-rhel8/116258): > > Must-share information (formatted with [Markdown](https://commonmark.org/help/)): which versions are you using: Sonarqube Developer Edition, version 8.9.6 Stand-alone (not clustered) how is SonarQube deployed: ZIP what are you trying to achieve: Migrate current installation to new server what have you tried so far to achieve this: Searched thru existing posts on the subject Good day! I am preparing to migrate my existing Sonarqube installation from a RHEL7 server to RHEL8 server. I have found some good information on here i… > [@Migrating sonarqube instance from RHEL6 to RHEL8 server](https://community.sonarsource.com/t/migrating-sonarqube-instance-from-rhel6-to-rhel8-server/80965): > > We are hving sonarqube 8.9.6 community edition which is currently hosted in rhel6 server. We are planning to migrate this sonarqube instance form rhel6 to rhel8 server. Can anyone please help me with steps or important point that should be taken care bfore, during and after migration. Also i would want to know if 8,9,6 is supported by rhel8 server. Also please mention the docs links or articles which provides information on migration. Regards, Saad > [@Question about moving Sonarqube to New server](https://community.sonarsource.com/t/question-about-moving-sonarqube-to-new-server/58306): > > Must-share information (formatted with [Markdown](https://commonmark.org/help/)): which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension) 8.9.6 what are you trying to achieve: Trying to move SonarQube from one Linux server to another Linux server. what have you tried so far to achieve this: haven’t tried yet Hello Team, we have a requirement to move our SonarQube application from one Linux server to another server, there is no change in DB server. we will be migrating SonarQube from server1 t… All of which seemed to indicate that there was nothing to worry about and it will be as easy as flipping a switch - which apparently is not the case. I am unable to get Sonarqube up and running on my new server - the sonarqube service shows as being started but the service status does state “Waiting for Elasticsearch to be up and running” I am re-using the same external MS SQL database so no data migration should be needed (as far as I know of). The nginx log is filled with “connect() failed (111: Connection refused) while connecting to upstream” which would indicate something with the proxy setup but I copied over the exact sonar.properties and all nginx config files from my old server - so all configs are exactly the same. The sonar.log file just keeps repeating over and over again: ```auto 2024.06.10 19:28:33 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running 2024.06.10 19:28:34 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 1 2024.06.10 19:28:34 INFO app[][o.s.a.SchedulerImpl] Process[es] is stopped 2024.06.10 19:28:34 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped 2024.06.10 19:28:35 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /var/sonarqube/temp 2024.06.10 19:28:35 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:39131] 2024.06.10 19:28:35 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube-8.9.10.61524/elasticsearch]: /opt/sonarqube-8.9.10.61524/elasticsearch/bin/elasticsearch ``` There are no other log files in the (sonar\_home)/logs/ directory - only the sonar.log and nothing else. I have added ports 9000 and 9001 to the firewall and also tried with local firewall ON and also OFF. I have tried with SELinux in ‘permissive’ and also ‘enforcing’ mode. All with no luck. Please help! Nothing ever seems to be as “easy” as it indicates. Thanks! **Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!** ---
**Author:** ![zeito29](https://avatars.discourse-cdn.com/v4/letter/z/d78d45/32.png) [@zeito29](https://community.sonarsource.com/u/zeito29)\ **Post date:** [June 11, 2024, 9:53pm UTC](https://community.sonarsource.com/t/migrating-sonarqube-from-rhel7-to-rhel8-server/117019/2 "2024-06-11T21:53:39Z")
Does anyone have any suggestions at all? It’s definitely something with how Sonarqube is listening (or should I say NOT listening) on the specified port. Nginx and Sonarqube come up just fine, but whenever you try to hit it from a client the following is logged: 2024/06/11 17:48:57 [error] 1043508#0: \*1 connect() failed (111: Connection refused) while connecting to upstream, client: \, server: sonarqube., request: “GET / HTTP/1.1”, upstream: “[http://127.0.0.1:9000/](http://127.0.0.1:9000/)”, host: “\” Anyone ever see this? ---
**Author:** ![zeito29](https://avatars.discourse-cdn.com/v4/letter/z/d78d45/32.png) [@zeito29](https://community.sonarsource.com/u/zeito29)\ **Post date:** [June 11, 2024, 10:10pm UTC](https://community.sonarsource.com/t/migrating-sonarqube-from-rhel7-to-rhel8-server/117019/3 "2024-06-11T22:10:41Z")
My RHEL7 server shows that sonarqube is listening on port 9001. My RHEL8 server shows NOTHING listening on port 9001, and they have the same exact config and sonar.properties file. THE. SAME. EXACT. CONFIGURATIONS. ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [June 12, 2024, 11:47am UTC](https://community.sonarsource.com/t/migrating-sonarqube-from-rhel7-to-rhel8-server/117019/4 "2024-06-12T11:47:58Z")
Hi, I technically can’t help you with 8.9. And… there are more logs in that directory than just `sonar.log`. If you keep getting > [@zeito29](#): > > `Process exited with exit value [es]: 1` maybe you should check `es.log`? Elasticsearch wants a minimum number of files and threads that is higher than the default in some OSes…   HTH, Ann ---
**Author:** ![zeito29](https://avatars.discourse-cdn.com/v4/letter/z/d78d45/32.png) [@zeito29](https://community.sonarsource.com/u/zeito29)\ **Post date:** [June 12, 2024, 12:44pm UTC](https://community.sonarsource.com/t/migrating-sonarqube-from-rhel7-to-rhel8-server/117019/5 "2024-06-12T12:44:44Z")
Thanks for the suggestion - but as stated previously in the original post there are no other log files in that directory other than the sonar.log. Everyone can call off the dogs on this one - I figured it out. My RHEL8 server has FIPS enabled so that is the issue. See: > [@Installation on RHEL 8.3 in FIPS mode](https://community.sonarsource.com/t/installation-on-rhel-8-3-in-fips-mode/38792): > > I installed of Sonarqube 8.6.1.40680 on a RHEL 8.3 server in fips mode following the documentation. I configured postgresql 12 and verified that access to the database as the sonarqube user. We are using OpenJDK11 When I attempt to start the Sonarqube service I see the following error in the log file: java security nosuchalgorithmexception sha 512 secretkeyfactory not available If I disable fips mode and reboot the machine Sonarqube starts without issue. Are there additional steps needed to … So… C’mon Sonarqube - FIPS 140-2 has been out for 13 years now - you can’t be FIPS compliant in that timeframe??? ---
**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\ **Post date:** [June 12, 2024, 1:02pm UTC](https://community.sonarsource.com/t/migrating-sonarqube-from-rhel7-to-rhel8-server/117019/6 "2024-06-12T13:02:27Z")
[It’s not like we’re alone on this one.](https://jira.atlassian.com/browse/JRASERVER-71975) However, good news for you, SonarQube will be able to run in a FIPS environment in SonarQube _v10.6_ (coming this month)