Alexis Robert Community Champion

Hi @Bem Mehret, it's a bit tricky to do a server migration and upgrade at the same time. I would suggest first to upgrade the existing instance: you can follow this guide to do so. Then, you can migrate to the new server following this guide. Let me know if this helps, --Alexis

Hi @Kale Ganann, you can probably use the same JRE for both, as long as it's at least version 1.8 If you really want to use different JREs, you can just set your "JAVA_HOME" in bin/setenv.sh Let me know if it helps, --Alexis

Hi @Rilwan Ahmed, have you tried forcing a reindex in your Confluence instance ? this page describes how to do it. Let me know if this helps, --Alexis

Hello @Muhammad Fahad, you should probably provision between 10GB and 20GB for an instance like this. For reference, my ServiceDesk database is 2GB with ~20k issues. Alexis

Hi @Sushma Nagaraj, can you give us a bit more details on the server where Jira is running, like CPU, RAM, VPS or dedicated, ... How many users/projects/issues do you have on this jnstance ? Thanks, Alexis

Hello @Thayle Byington, can you try configuring the DB with a DNS or IP ? It's possible that "HOU-JIRASRV" is not know to the server where you're installing Jira. Can you give more detail on the server you're using for Jira ? Is it Linux or Windows, dedicated or VPS, ... ? Thanks, Alexis

Good to hear @Tom Wealthy ! Please take a moment to mark our posts as "Accepted" so that other users can find this when they run into a similar issue. Thanks, --Alexis

Hello @Amit Dhaka, there is a good explanation provided here to automate Lets Encrypt certificate renewal for Tomcat. However, this is quite complicated and if it's possible I would rather suggest that you use a Proxy server like Apache to achieve this. With certbot it will be very easy, you'll only need to create a vhost…

Happy we could help you @Maksim Kunin ! Please take a moment to mark our posts as "Accepted" so that other users can find this when they run into a similar issue. Thanks, --Alexis

You're welcome @Martin Greksa ! Please take a moment to mark the post as "Accepted" so that other users can find this when they run into a similar issue. Thanks, --Alexis

Hello @Martin Greksa, it looks like a known bug as there is a ticket opened with Atlassian support about this issue. No solutions as of yet, I'd recommend you add yourself as a Watcher to this issue to know when it will be fixed. Let me know if this helps, --Alexis

Hello @Alexander Poryvkin, from the supported platform page it seems that Jira can only work with the following versions: * PostgreSQL 9.6 * PostgreSQL 9.5 * PostgreSQL 9.4 * PostgreSQL 9.3 You might have not seen the warning before but it looks like your version is not officially supported, even though it might work fine.…

Glad we could help @Hans-Georg Emberger Please take a moment to mark our posts as "Accepted" so that other users can find this when they run into a similar issue. Thanks, --Alexis

Hi @Christian Palacios, you will be able to achieve this by using a Proxy, such as Apache, to act as a intermediate between your users and your Atlassian products so that the users only need to access jira.mycompany.com or confluence.mycompany.com. You can follow this documentation to get started. Let me know if you have…

From this kb, it looks like it's a problem directly with your DB. Try restarting that instance, it might still have connection opened from your previous installation attempts.

So that was really the error ? That's weird because the JRE is supposed to be bundled in the installer ... Good for you anyway, remember to mark the post as resolved so that others can find it if the have the same issue ! Thanks, --Alexis

Hello @Hans-Georg Emberger, you will need to perform a XML backup as described here, and then import it during the new server Confluence. You might want to save following from the old server: * conf/server.xml file if you manually changed it * bin/setenv.sh file if you manually changed it * your attachment directory You…

These settings are the standard ones so no problem here, we're going to need more details to help you out: * what version of Jira are you installing * what version of Java is installed * check both atlassian-jira-xxx/logs/catalina.out and <JIRA_HOME>/log/atlassian-jira.log for any lines starting with "ERROR" * check with…

Hi @Tom Wealthy, this is probably something to do with the JVM settings, basically Jira tries to allocate memory but something goes wrong and it fails. Can you check the settings in your setenv.bat for JVM_MAXIMUM_MEMORY and JVM_MINIMUM_MEMORY ? Also, can you confirm what other software is running on this server ?…

Can you try following these instructions to delete the Application Links in the database ? It might help as it describes how to do so specifically for Bitbucket. --Alexis

Hi @Jordan Villalobos, I have found 2 Atlassian KB that reference this error: here and here. You will likely need to remove the ApplicationLinks in the database, remember to take a backup before you commit any changes that might break the application. Let me know if this helps, --Alexis

Hello @veerup, this sounds like a network error, maybe ask your network administrators if any change was made to your network, proxy or firewall. Let me know if this helps, --Alexis

Hi @Maksim Kunin, can you try disabling CompressedOops ? just remove the "-XX:-UseCompressedOops" part of the set-jmx-opts.sh. Also, your jvm heap size settings seem weird for a server with 4GB RAM. Can you try setting both to 1024m in case the CompressedOops removal is not enough ? Let me know if this helps, --Alexis

Hello @Ahmad Behzadi, based on this thread with the same error encountered, it might have to do with user permissions. Are you sure your SQL user has enough permissions ? It needs the following: * Give this user full create, read and write permissions for the database tables. Confluence must be able to create its own…

No problem ! Please remember to accept the solution so that others can find it if they run into the same issue :) --Alexis

Hi, indeed, it does confirm that you need to install Jira Software instead of Jira Core to get all those features back. You will need to start again the upgrade on your testing instance from scratch, just to be sure nothing is lost during the process. --Alexis

Hi @Ahmed Ben Abid from the screenshot in your first post, I noticed you have "Agile Scrum" as a project type, so you definitely have the Agile plugin in Jira 6.4 :) You should check the add-ons page and select "All add-ons" instead of "User-installed", I'm pretty sure you will find it. --Alexis

Hi @Ahmed Ben Abid, from Jira version 7, the Agile add-on has disappeared and is replaced by Jira Software (it's basically Jira Core + Agile add-on bundled together). I'm guessing you had the Agile plugin before, so in order to get back all your features you need to deploy Jira Software and not Jira Core. This document…

Good to hear @Anthony ! Please mark my answer as accepted so that other people can find this and fix similar issues :) --Alexis

After an xml import on your Dev instance, you just need to make sure that the base URL is correctly set, and you can disable email notifications too so that your tests don't sen emails to users.