Alexis Robert Community Champion

Hi @RichardP , the license key is not restricted to a particular server - the Server ID is only used to generate the key but will work on any other Server ID. You just need to copy the key on your new server and it will work fine.

there's clearly an issue with available memory on this server as the error is very clear : the java process can't allocate memory to get Jira running. You should definitely investigate more on this front.

Well MariaDB is not officially supported, and the logs you're showing do not point to a DB issue but you should still try to deploy Jira with the recommended versions if possible.

Hi @Christoph Garbe , I'm not sure why this information is displayed here, but Synchrony does not have a dedicated database, it's using the same db as the one configured in Confluence. I think this is displayed for legacy reasons, when collaborative editing was first introduced. You can disregard it anyway.

are you using the JRE binary bundled with your linux distribution or the one bundled with the Jira installer ? Atlassian only supports AdoptOpenJDK or Oracle JRE as mentioned here : https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html

Hi @gf , can you try changing the JVM memory parameters for Jira ? Stop Jira and follow these insctructions : * To increase heap space memory in Linux installations: In your <JIRA application installation directory>/bin open the setenv.sh file. * Find the sections JVM_MINIMUM_MEMORY= and JVM_MAXIMUM_MEMORY= * Change both…

Hi @Tyler Simecek , what version are you on right now, and what's your target version ? You can upgrade without testing first of course, but I'd suggest at least doing a full database backup and XML backup. You should also copy your JIRA_HOME directory in case anything goes wrong.

Hi @Fluccs Australia , if you already have Apache running as a reverse proxy, then it's very easy to install your SSL certificate, just follow this documentation: https://confluence.atlassian.com/doc/using-apache-with-mod_proxy-173669.html Let me know if you have any questions, --Alexis

Hi @gf , the issue is pretty clear: you don't have enough memory on your server, leading to these errors (GC Allocation Failure means the system can't allocate memory to Jira). You need to increase the server memory from 2GB to 4GB and try again the installation.

Hi @gf , these log lines start with "INFO" as you can see, we need the ones starting with "ERROR" to get a more detailed view of what is going wrong.

Hi @gf , if you open the log files, can you search for lines starting with ERROR ? You can then copy these lines here.

Hi @gf , it might be a permissions issue on the database, can you have a look at the logs in JIRA_INSTALL_DIR/log/catalina.out and see if you have any errors related to the database ? 

Hi @Jennifer Dozar , I personnaly prefer using the .tar package to install/upgrade Jira, but this is purely a personnal preference :) For the target versions, it's much easier to upgrade to 7.13.5 as it's the same major version (Jira 7) whereas version 8.3. is a new major version (Jira 8). If you want to upgrade using the…

Hi @Mydesq Support , the message you're seeing : We could not connect to Confluence, possibly because that instance is behind a misconfigured proxy means that there is a problem with the network between both instances. You should have a look at the documentation to debug this…

what about the processes running on your server ? are you sure that enough memory is available ? can you post the output of "free" ?

Hi @Ganesh , this message is a warning if I'm not mistaken, and it's normal to have the import stuck at 90% - this is when Confluence is doing a reindexing and other internal stuff. You should leave it running, I believe it will complete after a while.

Hello @Ganesh , yes it's possible to import any XML export from version 5.x to a Confluence 6.x instance. Let me know if this helps, --Alexis

ok, from your screenshot you're gettin Out Of Memory error right at the beginning. You should try to check if your server has enough memory available (is Bitbucket the only tool running on it ? ) and adjust Bitbucket memory (in config file _start-webapp.sh ) settings to 2048m for example. 

Hi @[deleted] , from the error message, looks like your PostgreSQL instance is not properly configured. Can you connect to the database with the command line on your server to test it ? You can follow this documentation to login from the command line. Let me know if this helps, --Alexis

Hi @M_ Ludwig , if you keep seeing the errors on your production servers, but the setup works fine on your test server, then the issue is definitely with your production server. I would check again if there is not a SELinux or iptables policy preventing the connection to synchrony.

Hi @James Price , there's a documentation very well done by Atlassian that you can use to setup SSL with Jira : https://confluence.atlassian.com/adminjiraserver073/integrating-jira-with-apache-using-ssl-861253896.html Let me know if you have any questions, --Alexis

Hi @M_ Ludwig , I have pretty much the same configuration (my Apache proxy runs on another VM but very similar otherwise). Here's my Apache config (I left out the SSL stuff) : <Proxy *> Require all granted </Proxy> ProxyPass /synchrony http://my.ip:8091/synchrony <Location /synchrony> Require all granted RewriteEngine on…

Hi @laknath , can you add server.scheme=https to your bitbucket.properties file and restart Bitbucket ? Thanks, --Alexis

Hi @laknath , can you share what is in your bitbucket.properties configuration file ? Also, make sure that you don't already have a zombie instance of Bitbucket still running (you may reboot your server for example if you're not sure). Let me know if this helps, --Alexis

They provide a solution for environments in the Cloud or On premise, maybe that's where you read this !

Hi @PhilB , I'm afraid that OpeGenie is only a cloud service at the moment. --Alexis

Hi @[deleted] , does the workaround "add jira.lf.date.relativize = false" to jira-application.properties not work for you on Jira 8.2.4 ? I am not sure if you're saying that you managed to fix your initial problem or not. Thanks, --Alexis

Hi @slsdeveloper , you can find on this page exactly what versions are affected by the vulnerability and which one to install. You should install version 8.2.3 or 8.2.4 for example. Since this vulnerability is based on the Contact Administrators form as a way to breach the system, it may the reason why you're getting these…

Hi @Asif AlWaqfi , looks like you're using MySQL 8, which is not compatible with Jira. You should install MySQL 5.7 instead. Let me know if this helps, --Alexis

Hi @RBDev , did you update your bitbucket.properties file with the proper SSL configuration : * server.secure=true * server.scheme=https * server.proxy-port=443 * server.proxy-name=mydomain.com