My database connect has the permissions. But every time I go through the setup process once I connect the database it fails to move on. Yet it looks to me that it had no issue creating the tables. It successfully created 175 tables.
Once I restart jira I can connect it shows the loading/startup status but as soon as its finished it crashes again. Then I can't get any connection to the server. I'm using MySQL w/ MariaDB with the INNODB storage set.
I have set utf8 collation. Not sure what is going in I'm checking the logs but I don't really notice anything
Maybe someone can make sense of the logs below:
[MYIP] 1203x19x2 - [19/Jan/2019:20:03:42 +0000] "GET /s/d41d8cd98f00b204e9800998ecf8427e-CDN/i12px0/713000/1/7.9.9/_/download/batch/com.atlassian.auiplugin:internal-src-js-aui-jquery/com.atlassian.auiplugin:internal-src-js-aui-jquery.js HTTP/1.1" 200 304 16 "http://jira.taurozza.com:8080/secure/SetupMode!default.jspa" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.0.2 Safari/605.1.15" "1qvkbzx" [MYIP] 1203x21x3 - [19/Jan/2019:20:03:42 +0000] "GET /s/d41d8cd98f00b204e9800998ecf8427e-CDN/i12px0/713000/1/7.9.9/_/download/batch/com.atlassian.auiplug@@@
9936K(380224K), [Metaspace: 34312K->34312K(1081344K)], 0.0775749 secs] [Times: user=0.08 sys=0.00, real=0.07 secs] 2019-01-19T20:29:31.306+0000: 15.154: [GC (Allocation Failure) 2019-01-19T20:29:31.306+0000: 15.154: [DefNew: 105024K->2893K(118080K), 0.0078931 secs] 144960K->42829K(380224K), 0.0079642 secs] [Times: user=0.01 sys=0.00, real=0.01 secs] 2019-01-19T20:29:31.821+0000: 15.669: [GC (Allocation Failure) 2019-01-19T20:29:31.821+0000: 15.669: [DefNew: 107917K->5738K(118080K), 0.0120330 secs] 147853K->45674K(380224K), 0.0121014 secs] [Times: user=0.02 sys=0.00, real=0.01 secs] 2019-01-19T20:29:32.311+0000: 16.159: [GC (Allocation Failure) 2019-01-19T20:29:32.311+0000: 16.159: [DefNew: 110762K->6948K(118080K), 0.0120385 secs] 150698K->46884K(380224K), 0.0121184 secs] [Times: user=0.01 sys=0.00, real=0.01 secs] 2019-01-19T20:29:32.761+0000: 16.608: [GC (Allocation Failure) 2019-01-19T20:29:32.761+0000: 16.608: [DefNew: 111972K->6665K(118080K), 0.0178732 secs] 151908K->47623K(380224K), 0.0179537 secs] [Times: user=0.03 sys=0.00, real=0.02 secs] 2019-01-19T20:29:33.321+0000: 17.169: [GC (Allocation Failure) 2019-01-19T20:29:33.321+0000: 17.169: [DefNew: 111689K->7794K(118080K), 0.0162822 secs] 152647K->51201K(380224K), 0.0163517 secs] [Times: user=0.02 sys=0.01, real=0.02 secs] 2019-01-19T20:29:33.965+0000: 17.812: [Full GC (Metadata GC Threshold) 2019-01-19T20:29:33.965+0000: 17.813: [Tenured: 43406K->50746K(262144K), 0.1373622 secs] 106601K->50746K(380224K), [Metaspace: 57408K->57408K(1099776K)], 0.1374508 secs] [Times: user=0.27 sys=0.00, real=0.14 secs] 2019-01-19T20:29:34.469+0000: 18.317: [GC (Allocation Failure) 2019-01-19T20:29:34.469+0000: 18.317: [DefNew: 105024K->2201K(118080K), 0.0074403 secs] 155770K->52948K(380224K), 0.0075030 secs] [Times: user=0.00 sys=0.00, real=0.01 secs] 2019-01-19T20:29:34.880+0000: 18.728: [GC (Allocation Failure) 2019-01-19T20:29:34.880+0000: 18.728: [DefNew: 107225K->6774K(118080K), 0.0188661 secs] 157972K->57521K(380224K), 0.0189583 secs] [Times: user=0.04 sys=0.00, real=0.02 secs] 2019-01-19T20:29:35.246+0000: 19.093: [GC (Allocation Failure) 2019-01-19T20:29:35.246+0000: 19.093: [DefNew: 111798K->3078K(118080K), 0.0133931 secs] 162545K->55013K(380224K), 0.0134692 secs] [Times: user=0.03 sys=0.00, real=0.01 secs] 2019-01-19T20:29:35.830+0000: 19.678: [GC (Allocation Failure) 2019-01-19T20:29:35.830+0000: 19.678: [DefNew: 108102K->6774K(118080K), 0.0135611 secs] 160037K->58710K(380224K), 0.0136328 secs] [Times: user=0.01 sys=0.00, real=0.01 secs] 2019-01-19T20:29:36.824+0000: 20.672: [GC (Allocation Failure) 2019-01-19T20:29:36.824+0000: 20.672: [DefNew: 111798K->10667K(118080K), 0.0196978 secs] 163734K->63439K(380224K), 0.0197779 secs] [Times: user=0.02 sys=0.00, real=0.02 secs]
GC Allocation errors point towards the memory being the problem - sometimes it's not enough allowed for the application, sometimes it's poor settings.
But I would not look there first. You've said you are using MariaDB, which is not (yet) supported. Change to using a supported database first, then see if you still get the problem. See https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html (use the button at the top right to select your version)
Thank for the reply... Is there a way to set jira to go back to setting up the database again?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Delete (well, more safely, move) the <jira home>/dbconfig.xml file. That will make your install re-run the setup process.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- Yup, that was it. The server just didn't have any "balls" haha :)...
Upgraded the instance with more RAM. Now we cookin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.