Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jira don't want to use my created database #117

Closed
Floryder opened this issue Feb 10, 2016 · 1 comment
Closed

Jira don't want to use my created database #117

Floryder opened this issue Feb 10, 2016 · 1 comment

Comments

@Floryder
Copy link

Hey there,

i become desperate with die jira-module.
How will jira write in the created Database "jira". In my case the used parameteres are only used for the dbconfig.xml. If I watch the MySQL DB, it is empty. And then I tried the config.sh from the bin-directory. There I saw that Jira is still using the default Database. If I change the DB-settings in this config jira will work. But this should work as default in my opinion.

It would be nice if someone could support me with my puppet-manifest which looks like this:

class { 'jira':
         version     => '6.3.13',
         installdir  => '/opt/atlassian-jira',
         homedir     => '/var/atlassian-jira/jira-home',
         user        => 'jira',
         group       => 'root',
         db => 'mysql',
         dbtype => 'mysql',
         dbuser => 'jira',
         dbname => 'jira',
         dbpassword  => 'test',
         dbserver    => 'localhost',
         javahome    => '/opt/java/jdk1.7.0_21/',
         mysql_connector_URL => 'https://dev.mysql.com/downloads/file/?id=460362',
         proxy          => {
            scheme       => 'https',
            proxyName    => 'localhost',
            proxyPort    => '8443',
         }
    }

Greetings,
Florian

@Floryder Floryder changed the title Can't access jira on webinterface Jira don't want to use my created database Feb 26, 2016
@oranenj
Copy link
Contributor

oranenj commented Apr 14, 2021

This issue is old enough that I'm just going to close it. Chances are, this will work better with current master.

@oranenj oranenj closed this as completed Apr 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants