Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira could not connect to database error

veerakumar Bose September 18, 2019

Hi ,

We have installed and setup the Jira software successfully and it was working fine , today i tried to configure SMTP mail server and added Jira importer plugin. suddenly it starts giving Database error , Please find attached log from server.Error.PNG

1 answer

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 18, 2019

It is very likely to be one of the things listed in the red box, can you check through those?

veerakumar Bose September 18, 2019

We have tried listed options. But still not working, 

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 18, 2019

What does the log file complain that the error is?

veerakumar Bose September 18, 2019

One of the log file shows following error

OpenJDK 64-Bit Server VM (25.202-b08) for windows-amd64 JRE (1.8.0_202-b08), built on Jan 17 2019 17:10:34 by "jenkins" with MS VC++ 10.0 (VS2010)
Memory: 4k page, physical 8388148k(3135052k free), swap 9698868k(3853312k free)
CommandLine flags: -XX:GCLogFileSize=20971520 -XX:InitialCodeCacheSize=33554432 -XX:InitialHeapSize=402653184 -XX:MaxHeapSize=2147483648 -XX:NumberOfGCLogFiles=5 -XX:-OmitStackTraceInFastThrow -XX:+PrintGC -XX:+PrintGCCause -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:ReservedCodeCacheSize=536870912 -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseGCLogFileRotation -XX:-UseLargePagesIndividualAllocation -XX:+UseParallelGC
2019-09-18T11:48:43.972-0500: 6.810: [GC (Allocation Failure) [PSYoungGen: 98304K->11642K(114688K)] 98304K->11650K(376832K), 0.0452111 secs] [Times: user=0.05 sys=0.00, real=0.05 secs]
2019-09-18T11:48:46.641-0500: 9.479: [GC (Allocation Failure) [PSYoungGen: 109946K->11488K(114688K)] 109954K->11504K(376832K), 0.1286434 secs] [Times: user=0.13 sys=0.00, real=0.13 secs]
2019-09-18T11:48:49.628-0500: 12.466: [GC (Allocation Failure) [PSYoungGen: 109792K->11812K(114688K)] 109808K->11828K(376832K), 0.0191731 secs] [Times: user=0.05 sys=0.00, real=0.02 secs]
2019-09-18T11:48:53.007-0500: 15.844: [GC (Allocation Failure) [PSYoungGen: 110116K->12672K(212992K)] 110132K->12768K(475136K), 0.0382131 secs] [Times: user=0.09 sys=0.00, real=0.04 secs]
2019-09-18T11:48:59.466-0500: 22.303: [GC (Allocation Failure) [PSYoungGen: 209280K->15063K(212992K)] 209376K->15167K(475136K), 0.0950127 secs] [Times: user=0.13 sys=0.00, real=0.10 secs]
2019-09-18T11:49:14.301-0500: 37.137: [GC (Allocation Failure) [PSYoungGen: 211671K->14817K(406016K)] 211775K->16931K(668160K), 0.0344350 secs] [Times: user=0.06 sys=0.00, real=0.03 secs]
2019-09-18T11:49:24.593-0500: 47.442: [GC (Allocation Failure) [PSYoungGen: 405985K->16447K(408064K)] 408099K->27306K(670208K), 0.1213211 secs] [Times: user=0.11 sys=0.00, real=0.13 secs]
2019-09-18T11:49:28.359-0500: 51.203: [GC (Metadata GC Threshold) [PSYoungGen: 162854K->8871K(679936K)] 173714K->20026K(942080K), 0.0205404 secs] [Times: user=0.03 sys=0.00, real=0.02 secs]
2019-09-18T11:49:28.375-0500: 51.224: [Full GC (Metadata GC Threshold) [PSYoungGen: 8871K->0K(679936K)] [ParOldGen: 11155K->17667K(262144K)] 20026K->17667K(942080K), [Metaspace: 20629K->20629K(1069056K)], 0.3145585 secs] [Times: user=0.31 sys=0.00, real=0.33 secs]
Heap
PSYoungGen total 679936K, used 243195K [0x00000000d5580000, 0x0000000100000000, 0x0000000100000000)
eden space 662016K, 36% used [0x00000000d5580000,0x00000000e42fec88,0x00000000fdc00000)
from space 17920K, 0% used [0x00000000fee80000,0x00000000fee80000,0x0000000100000000)
to space 18432K, 0% used [0x00000000fdc00000,0x00000000fdc00000,0x00000000fee00000)
ParOldGen total 262144K, used 17667K [0x0000000080000000, 0x0000000090000000, 0x00000000d5580000)
object space 262144K, 6% used [0x0000000080000000,0x0000000081140e20,0x0000000090000000)
Metaspace used 25850K, capacity 26408K, committed 26496K, reserved 1073152K
class space used 2986K, capacity 3196K, committed 3200K, reserved 1048576K

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 18, 2019

Ok, that's not the database failing, it's the java virtual machine memory failing.  These can be really hard to diagnose and fix, but start at https://confluence.atlassian.com/jirakb/jira-running-out-of-memory-due-to-gc-allocation-race-condition-957122851.html

veerakumar Bose September 18, 2019

one quick question Jira bitbucket also installed in the same server, we are not having any issues with jira bit bucket server and its running normally. why jira software alone has the issue.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 18, 2019

I don't know, I have not run through your entire logs and settings.

veerakumar Bose September 18, 2019

I have following files in log folder, please let me know which file specify the error?. how to attach the file here

Thanks 

Veera

Log.PNG

Suggest an answer

Log in or Sign up to answer