Alexis Robert Community Champion

Hi @Mike Allen, in web.xml did you try changing <url-pattern>/</url-pattern> with <url-pattern>/*</url-pattern> Just thinking it might be because you're not matching the proper URL pattern to redirect. Let me know if this helps, --Alexis

Hi @Harish Tuccapuram, the quickest way, if both instances are on the same version, would be to simply dump the production database and import it into your test database instance. You can also simply use the native Jira export and import feature to copy your production content to the Dev one. Let me know if this helps,…

Hello @Marko Schröder, for Bitbucket you can use mybitbucket.company.com/status to check for a "Status: Running" return. --Alexis

Hello @Damien Frutiger, it seems like you might have not set properly the Base URL in your Jira instance, can you check this how-to to make sure everythiing is set up properly ? Also, I'm not an Nginx expert but it seems that your ProxyPass should be pointing to your Jira instance and not localhost. Let me know if this…

You can run Confluence on MySQL 5.7, but make sure all your other websites/applications run fine on this version first. What you can try to force InnoDB is to modify your MySQL startup script to include the storage engine in the daemon command line: <span>mysqld </span><span>--default-storage-engine=InnoDB</span> I am not…

Hello @Development GGN, could you provide more details on the server where you're trying to install Bamboo ? RAM, CPU, virtual machine, OS and version, cloud provider ... ? --Alexis

Can you try uninstalling and reinstalling completely MySQL ? Also, try to keep only one configuration file int /etc/mysql/ if possible and not in /root/ .

Can you make sure that you don't have a my.cnf file in /etc/mysql/ and /root/ as these files will be read too on startup. What's weird is that InnoDB is the default storage engine on MySQL 5.6 so you shoud not have to do anything, but somehow on your server it seems that is the default. Is that a server that was upgraded…

OK so this is why Confluence can't continue the installation properly, InnoDB is not set as default storage engine on your instance. The MySQL configuration file located in /etc/my.cnf, make sure that this one has the correct setting for default-storage-engine. You should also have a look at the MySQL log files, in…

Can you do a "show engines;" in MySQL ? This should give more information on the default engine.

Hi @Anthony, can you connect to your database isntance, select your Confluence database and execute this query: <span>SHOW</span> <span>TABLE</span> <span>STATUS</span><span>;</span> Just to make sure that your instance is indeed using INNODB. Thanks, --Alexis

Hello @Anthony, after you made the change to your configuration file, did you properly reload/restart the MySQL service ? Also, can you specify what version of MySQL you're using ? --Alexis

Hi @Jason Pawloski, since you're installing on a VPS, have you checked your security scheme to make sure that port 8090 is authorized to be reached from the internet ? On most providers, only port 80 will be allowed by default, you need to specify what ports can be opened to the outside world. Let me know if this helps,…

From my experience on AWS with small VPS, you'll have significant slowdowns with 2GB RAM and need a big swap file as well, otherwise your instance will crash with OutOfMemory errors. I wouldn't even try to run both on the same 4GB server, unless it's a dedicated machine.

Hello, what AWS server are your using ? how much RAM do you have ? You should remember that both Confluence and Jira need a minimum of 4GB RAM each, so your server should not have less than 8GB at the very minimum. Also, you shoud try and look at the "<JIRA_HOME>/log/atlassian-jira.log" file and look for line starting with…

Hi @jitendramohan, looking at the log file, it's confirmed that the problem is with your confluence-init.properties: 2018-08-01 08:10:50,310 ERROR [localhost-startStop-1] [atlassian.config.bootstrap.DefaultAtlassianBootstrapManager] init Home is not configured properly:com.atlassian.config.ConfigurationException: Failed to…

Hi @thiagoteixeira, you can see the current supported versions of MySQL here. As you can see the latest version supported is 5.7, however several tickets like this one have been opened to ask Atlassian to provide support for version 8, but no updates so far. Regards, Alexis

Can you maybe show us with a screenshot for what element you would like to change the color ?

Hello @Eduard Diez you can change the bar color and other elements by going to "Color Scheme" in the General Configuration menu, as described here. Let me know if it helps, --Alexis

Hi @jitendramohan, first, the log you provided for "atlassian-confluence.log" does not show an error but only a warning, could you please try to find a line starting with "ERROR" ? that would help a lot. Did you change anything recently on your server ? an upgrade a few weeks ago maybe ? This error is probably caused by a…

Hello @Pieter-Jan Vanhoutte, if you're not familiair with server administration you should look into Atlassian Cloud: https://www.atlassian.com/software/jira/pricing You won't need to handle any of the installation or configuration of the server as they provide an instance that's ready to use. Have a look at the…

Hi, I can actually see an error in the logs, though very generic (null pointer exception). Could you try starting Jira, on another server maybe, with the standard server.xml file ? It would help narrowing down the error cause. Alexis

Hi, these are garbage collection logs and not very useful for your issue. I'm looking for the application logs that should be named "atlassian-jira.log", if you can find those (they should be in the JIRA_HOME/log/ directory) and attach team it'd be great. Alexis

Hi @DST team, can you attach the log file atlassian-jira.log located in your JIRA_HOME directory ? Thanks, Alexis

Can you check a few things: * on your AWS server, that the JIRA process is running: "ps -ef | grep java" * from your computer, that you can reach the AWS server on port 8081: "telnet ec2-x-x-x-x.ap-south-1.compute.amazonaws.com 8081" * can you check the JIRA logs for any errors, they will be located in the <JIRA_HOME>/log…

Hello @Baptiste Billy, as soon as your licence expires, you're not able to upgrade your JIRA and Confluence instance, whether it's to the latest version or one released 2 years ago. Let me know if this helps, --Alexis

Hello @DST team, since you're using AWS, can you make sure that your security scheme allows for port 8080 (used by Jira) to be accessed from outside ? You should then be able to access Jira using a URL like this: ec2-x-x-x-x.ap-south-1.compute.amazonaws.com:8080 Let me know if this helps, --Alexis

Hi @vatsal_dhar, there isn't a setting to make the portal available from a different URL than the Jira where it is installed. If you want to have only internal access, you will need to play with your firewall/proxy rules to restrict the URLs used by the Service Desk portal but without any guarantee that it will not break…

Hi @Ravichandra_Itagi, you cannot have both applications using the same port if they're running on the same server. You should assign a different port to one of them, or have another server to run each application on it own server. Hope this helps, --Alexis

Hi @vishal03kadam, you might not have the "Bulk Change" permission on your instance. Are you the project or instance administrator ? You can check this documentation to manage global permissions.