Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
Highlighted

com.install4j.runtime.beans.actions.text.ModifyTextFileAction failed error while installing Atlassia

error while installing Atlassian in ubuntu

com.install4j.runtime.beans.actions.text.ModifyTextFileAction failed

 

3 comments

Pavel Junek Community Leader Jul 21, 2019

Hi Vinod,

Please be more specific about this error. I need to see the greater part of the error log.

It is a new, clean Jira installation? At what installation step did you encounter this problem?

Thanks, Pavel

Hi Pavel,

while I am trying to install Atlassian on Ubuntu 18.04.2 LTS version. am facing this error.

Steps I have followed: 

wget https://product-downloads.atlassian.com/software/jira/downloads/atlassian-jira-software-8.2.4-x64.bin
chmod a+x atlassian-jira-software-8.2.4-x64.bin
sudo ./atlassian-jira-software-8.2.4-x64.bin

root@ip-172-31-80-122:/home/ubuntu# ./atlassian-jira-software-8.2.4-x64.bin Unpacking JRE ...
Starting Installer ...

This will install JIRA Software 8.2.4 on your computer.
OK [o, Enter], Cancel [c]
o
Click Next to continue, or Cancel to exit Setup.

Choose the appropriate installation or upgrade option.
Please choose one of the following:
Express Install (use default settings) [1], Custom Install (recommended for adva nced users) [2], Upgrade an existing JIRA installation [3, Enter]
2

Select the folder where you would like JIRA Software to be installed.
Where should JIRA Software be installed?
[/home/ubuntu]


Default location for JIRA Software data
[/var/atlassian/application-data/jira]


Configure which ports JIRA Software will use.
JIRA requires two TCP ports that are not being used by any other
applications on this machine. The HTTP port is where you will access JIRA
through your browser. The Control port is used to startup and shutdown JIRA.
Use default ports (HTTP: 8080, Control: 8005) - Recommended [1, Enter], Set cust om value for HTTP and Control ports [2]
1

JIRA can be run in the background.
You may choose to run JIRA as a service, which means it will start
automatically whenever the computer restarts.
Install JIRA as Service?
Yes [y, Enter], No [n]
y

Details on where JIRA Software will be installed and the settings that will be u sed.
Installation Directory: /home/ubuntu
Home Directory: /var/atlassian/application-data/jira
HTTP Port: 8080
RMI Port: 8005
Install as service: Yes
Install [i, Enter], Exit [e]
i

Extracting files ...

com.install4j.runtime.beans.actions.text.ModifyTextFileAction failed

Ignore [i, Enter], Quit [q]
q
Rolling back changes ...
root@ip-172-31-80-122:/home/ubuntu#

Please find the error logs and installation procedure

Regards,

Vinod 

Pavel Junek Community Leader Jul 21, 2019

Hi Vinod,
Thank you for providing this information. This bug looks strange. Do you have enough space in /home/ubuntu?

I recommend change Jira install folder from /home/ubuntu to default locations (/opt/atlassian/jira).

You can try install Jira manually - see https://confluence.atlassian.com/adminjiraserver/installing-jira-applications-on-linux-from-archive-file-938846844.html or you can contact Atlassian support (https://support.atlassian.com)

Pavel

Hello Pavel,

as you see the previous logs, /home/ubuntu is the default location.

Select the folder where you would like JIRA Software to be installed.
Where should JIRA Software be installed?
[/home/ubuntu]
Pavel Junek Community Leader Jul 22, 2019

Ahhh, I see.

OK, well. You can try install Jira manually according to the instructions Installing Jira applications on Linux from Archive File

Let me know if this method has helped.

Thanks

Pavel

Hello Pavel, 

after installation i have opened http://<ipaddress>:8080/

and done database settings, after clicking on the Next button, total server getting hanged up, and after rebooting I was unable to access the URL.

please suggest how to access the URL and to get back the application page

and once confirm what was the basic hardware requirement to configure Jira in Linux server.

Regards,

Vinod

Pavel Junek Community Leader Jul 22, 2019

Hi Vinod,

Good news! We have progressed :-)

It is quite possible that Jira has not started because it is not installed Jira as a service. The installer does this function by itself, for manual installation you need to do it manually - see Starting JIRA Automatically on Linux or see Start and Stop Jira applications. Remember that the owner of Jira Home and Jira Install must not be root, but the user under which Jira app is running eg. jira.

Pavel

hi 

can I get an example of the last two lines , regarding ownership

Hi,

yes, there are is:

root@localhost jira]# chmod jira:jira -R /home/ubuntu/jira/
root@localhost jira]# ll
drwxr-x---. 2 jira jira 4096  2. čec 19.18
analytics-logs
drwxr-x---. 4 jira jira   44 23. led 12.53 caches
drwxr-x---. 4 jira jira   40  8. úno 14.11 data
-rw-r-----. 1 jira jira 1042 23. led 12.53 dbconfig.xml
drwxr-x---. 3 jira jira 4096 12. úno 13.06 export
drwxr-x---. 4 jira jira   87 12. úno 13.07 import
-rw-r--r--  1 jira jira   57  9. dub 08.59 jira-config.properties
drwxr-x---  3 jira jira   56 11. bře 13.15 kepler
drwxr-x---. 2 jira jira 4096 28. bře 12.50 log
drwxr-x---. 2 jira jira    6 23. led 13.35 logos
drwxr-x---. 2 jira jira   76 23. led 12.54 monitor
drwxr-x---. 6 jira jira  100 29. led 10.24 plugins
drwxr-x---  4 jira jira   32  8. úno 10.42 scriptrunner
drwxr-x---  2 jira jira    6  8. úno 10.32 scripts
drwxr-x---  2 jira jira    6 11. bře 13.15 silprograms
drwxr-x---. 3 jira jira   26 23. led 12.43 tmp

Hi Pavel,

As soon as I execute the below command total server getting hang, and again I have to reboot the server.

Last login: Mon Jul 22 18:13:15 2019 from <ip address>
ubuntu@ip-<ip address>:~$ sudo /etc/init.d/jira start

To run JIRA in the foreground, start the server with start-jira.sh -fg
executing using dedicated user: jira

`sMMMMMMMMMMMMMM+
MMMMMMMMMMMMMM
:sdMMMMMMMMMMM
MMMMMM
`sMMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sMMMMMMMMMMM MMMMM
MMMMMM `UOJ
`sMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sdMMMMMMMMMM MMMMM
MMMMMM `UOJ
MMMMMM
+MMMMM
MMMMM
`UOJ

Atlassian Jira
Version : 8.2.4


If you encounter issues starting or stopping JIRA, please see the Troubleshooting guide at https://docs.atlassian.com/jira/jadm-docs-082/Troubleshooting+installation


Server startup logs are located in /opt/atlassian/jira/logs/catalina.out
Using CATALINA_BASE: /opt/atlassian/jira
Using CATALINA_HOME: /opt/atlassian/jira
Using CATALINA_TMPDIR: /opt/atlassian/jira/temp
Using JRE_HOME: /opt/atlassian/jira/jre/
Using CLASSPATH: /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira /bin/tomcat-juli.jar
Using CATALINA_PID: /opt/atlassian/jira/work/catalina.pid
Existing PID file found during start.
Removing/clearing stale PID file.
Tomcat started.
Starting Jira

 and unable to open an application in the browser. 

 

Regards,

Vinod

Pavel Junek Community Leader Jul 23, 2019

Hi Vinod,

Can you try this command?

ps aux | grep jira

This command show lists of processes that Jira has running. According to your log, it seems that Jira has started, but it may not be true and Jira will crash immediately after the start. 

Please look into Jira Install directory log for more information:

less /opt/atlassian/jira/logs/catalina.out 

 or Jira Home directory log

less /home/ubuntu/atlassian/jira/log/atlassian-jira.log 

 Pavel

Hello Pavel, 

by running the cmd I got the result as 

ubuntu@ip-172-31-23-197:~$ ps aux | grep jira
ubuntu 1476 0.0 0.0 14856 1000 pts/0 S+ 06:16 0:00 grep --color=auto jira
ubuntu@ip-172-31-23-197:~$ sudo less /opt/atlassian/jira/logs/catalina.out
22-Jul-2019 12:43:48.546 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.40
22-Jul-2019 12:43:48.549 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Apr 10 2019 14:31:19 UTC
22-Jul-2019 12:43:48.549 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.40.0
22-Jul-2019 12:43:48.549 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Linux
22-Jul-2019 12:43:48.549 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 4.15.0-1043-aws
22-Jul-2019 12:43:48.549 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
22-Jul-2019 12:43:48.550 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /opt/atlassian/jira/jre
22-Jul-2019 12:43:48.550 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_181-b13
22-Jul-2019 12:43:48.550 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
22-Jul-2019 12:43:48.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /opt/atlassian/jira
22-Jul-2019 12:43:48.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /opt/atlassian/jira
22-Jul-2019 12:43:48.558 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties
22-Jul-2019 12:43:48.558 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
22-Jul-2019 12:43:48.559 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms384m
22-Jul-2019 12:43:48.559 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx2048m
22-Jul-2019 12:43:48.559 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:InitialCodeCacheSize=32m
22-Jul-2019 12:43:48.560 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:ReservedCodeCacheSize=512m
22-Jul-2019 12:43:48.560 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
22-Jul-2019 12:43:48.560 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
22-Jul-2019 12:43:48.560 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
22-Jul-2019 12:43:48.561 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
22-Jul-2019 12:43:48.561 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
22-Jul-2019 12:43:48.562 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
22-Jul-2019 12:43:48.562 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.locale.providers=COMPAT
22-Jul-2019 12:43:48.562 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.plugins.startup.options=
22-Jul-2019 12:43:48.562 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
22-Jul-2019 12:43:48.562 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
22-Jul-2019 12:43:48.563 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.catalina.security.SecurityListener.UMASK=0027
22-Jul-2019 12:43:48.563 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:/opt/atlassian/jira/logs/atlassian-jira-gc-%t.log
22-Jul-2019 12:43:48.564 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
22-Jul-2019 12:43:48.564 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
22-Jul-2019 12:43:48.570 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=20M
22-Jul-2019 12:43:48.572 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDetails
22-Jul-2019 12:43:48.572 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
22-Jul-2019 12:43:48.572 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCTimeStamps
22-Jul-2019 12:43:48.576 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCCause
22-Jul-2019 12:43:48.576 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=
22-Jul-2019 12:43:48.577 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/opt/atlassian/jira
22-Jul-2019 12:43:48.577 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/opt/atlassian/jira
22-Jul-2019 12:43:48.578 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/opt/atlassian/jira/temp
22-Jul-2019 12:43:48.578 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [/home/ubuntu/opt/atlassian/jira/atlassian-jira-software-8.2.4-x64.bin.22674.dir/user::/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]
22-Jul-2019 12:43:48.918 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
22-Jul-2019 12:43:48.967 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1328 ms
22-Jul-2019 12:43:48.993 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
22-Jul-2019 12:43:48.996 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.40
22-Jul-2019 12:43:49.028 SEVERE [Catalina-startStop-1] org.apache.catalina.startup.HostConfig.beforeStart Unable to create directory for deployment: [/opt/atlassian/jira/conf/Catalina/localhost]
2019-07-22 12:43:56,517 localhost-startStop-1 INFO [c.a.jira.startup.JiraHomeStartupCheck] The jira.home directory '/var/atlassian/application-data/jira' is validated and locked for exclusive use by this instance.
2019-07-22 12:43:56,830 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

:

 Please find the logs,

 

regards,

Vinod

Pavel Junek Community Leader Jul 23, 2019

Hi Vinod,

Based on output:

ubuntu@ip-172-31-23-197:~$ ps aux | grep jira
ubuntu 1476 0.0 0.0 14856 1000 pts/0 S+ 06:16 0:00 grep --color=auto jira

It is obvious that the Jira process is not running. The Catalina.out log is also fine, there is no error.

What is your problem exactly? Jira can't run?

Look at the end of the file 

less /var/log/messages

Pavel 

Hello pavel, 

but i am giving the cmd 

sudo /etc/init.d/jira start

 and it shows Jira starting, please go through previous comments.

yes unable to open jira.

"less /var/log/messages" not found.

please go through jira logs

root@ip-172-31-23-197:/var/atlassian/application-data/jira/log# vi atlassian-jira.log
Memory Pool: Eden Space : Eden Space: init = 107479040(104960K) used = 28808424(28133K) committed = 107544576(105024K) max = 572653568(559232K)
Memory Pool: Survivor Space : Survivor Space: init = 13369344(13056K) used = 0(0K) committed = 13369344(13056K) max = 71565312(69888K)
Memory Pool: Tenured Gen : Tenured Gen: init = 268435456(262144K) used = 18446896(18014K) committed = 268435456(262144K) max = 1431699456(1398144K)
JVM Input Arguments : -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms384m -Xmx2048m -XX:InitialCodeCacheSize=32m -XX:ReservedCodeCacheSize=512m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:-OmitStackTraceInFastThrow -Djava.locale.providers=COMPAT -Datlassian.plugins.startup.options= -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Xloggc:/opt/atlassian/jira/logs/atlassian-jira-gc-%t.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCCause -Dignore.endorsed.dirs= -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home=/opt/atlassian/jira -Djava.io.tmpdir=/opt/atlassian/jira/temp

"less /var/log/messages" not found.

Sorry, in Ubuntu is /var/log/syslog

 

vi atlassian-jira.log

You cannot edit the Jira log file.  Use: 

less atlassian-jira.log

and then on keyboard Shift + g to jump to End of log file.

Hello Pavel,

please find the logs, after giving the cmd, Jira starts and after some time total server not works even ssh also not works, again I need to restart the server and Jira also. jira error.png

root@ip-172-31-23-197:/# sudo /etc/init.d/jira start

To run JIRA in the foreground, start the server with start-jira.sh -fg
executing using dedicated user: jira

`sMMMMMMMMMMMMMM+
MMMMMMMMMMMMMM
:sdMMMMMMMMMMM
MMMMMM
`sMMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sMMMMMMMMMMM MMMMM
MMMMMM `UOJ
`sMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sdMMMMMMMMMM MMMMM
MMMMMM `UOJ
MMMMMM
+MMMMM
MMMMM
`UOJ

Atlassian Jira
Version : 8.2.4


If you encounter issues starting or stopping JIRA, please see the Troubleshootin g guide at https://docs.atlassian.com/jira/jadm-docs-082/Troubleshooting+install ation


Server startup logs are located in /opt/atlassian/jira/logs/catalina.out
Using CATALINA_BASE: /opt/atlassian/jira
Using CATALINA_HOME: /opt/atlassian/jira
Using CATALINA_TMPDIR: /opt/atlassian/jira/temp
Using JRE_HOME: /opt/atlassian/jira/jre/
Using CLASSPATH: /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira /bin/tomcat-juli.jar
Using CATALINA_PID: /opt/atlassian/jira/work/catalina.pid
Existing PID file found during start.
Removing/clearing stale PID file.
Tomcat started.
Starting jira
root@ip-172-31-23-197:/# less /var/log/syslog
Jul 24 06:25:01 ip-172-31-23-197 rsyslogd: [origin software="rsyslogd" swVersion="8.32.0" x-pid="915" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: 2019-07-24 06:28:52 INFO Backing off health check to every 600 seconds for 1800 seconds.
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: 2019-07-24 06:28:52 ERROR Health ping failed with error - EC2RoleRequestError: no EC2 instance role found
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: caused by: EC2MetadataError: failed to make EC2Metadata request
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: caused by: <?xml version="1.0" encoding="iso-8859-1"?>
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: <head>
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: <title>404 - Not Found</title>
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: </head>
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: <body>
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: <h1>404 - Not Found</h1>
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: </body>
Jul 24 06:28:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: </html>
Jul 24 06:35:01 ip-172-31-23-197 CRON[1445]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 24 06:38:40 ip-172-31-23-197 systemd[1]: Starting Cleanup of Temporary Directories...
Jul 24 06:38:40 ip-172-31-23-197 systemd[1]: Created slice User Slice of ubuntu.
Jul 24 06:38:40 ip-172-31-23-197 systemd[1]: Starting User Manager for UID 1000...
Jul 24 06:38:40 ip-172-31-23-197 systemd[1]: Started Session 4 of user ubuntu.
Jul 24 06:38:40 ip-172-31-23-197 systemd[1]: Started Cleanup of Temporary Directories.
Jul 24 06:38:40 ip-172-31-23-197 systemd[1465]: Reached target Paths.
Jul 24 06:38:40 ip-172-31-23-197 systemd[1465]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jul 24 06:38:40 ip-172-31-23-197 systemd[1465]: Listening on GnuPG cryptographic agent and passphrase cache.
Jul 24 06:38:40 ip-172-31-23-197 systemd[1465]: Listening on GnuPG network certificate management daemon.
Jul 24 06:38:40 ip-172-31-23-197 systemd[1465]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jul 24 06:38:40 ip-172-31-23-197 systemd[1465]: Reached target Timers.
Jul 24 06:38:40 ip-172-31-23-197 systemd[1465]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 24 06:38:40 ip-172-31-23-197 systemd[1465]: Reached target Sockets.
Jul 24 06:38:40 ip-172-31-23-197 systemd[1465]: Reached target Basic System.
Jul 24 06:38:40 ip-172-31-23-197 systemd[1]: Started User Manager for UID 1000.
Jul 24 06:38:40 ip-172-31-23-197 systemd[1465]: Reached target Default.
Jul 24 06:38:40 ip-172-31-23-197 systemd[1465]: Startup finished in 84ms.
Jul 24 06:45:01 ip-172-31-23-197 CRON[1655]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 24 06:46:46 ip-172-31-23-197 dbus-daemon[930]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.14' (uid=0 pid=1662 comm="timedatectl set-timezone IST " label="unconfined")
Jul 24 06:46:46 ip-172-31-23-197 systemd[1]: Starting Time & Date Service...
Jul 24 06:46:46 ip-172-31-23-197 dbus-daemon[930]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jul 24 06:46:46 ip-172-31-23-197 systemd[1]: Started Time & Date Service.
Jul 24 06:47:09 ip-172-31-23-197 systemd-timedated[1663]: Changed time zone to 'Asia/Kolkata'.
Jul 24 06:53:46 ip-172-31-23-197 systemd-timesyncd[587]: Network configuration changed, trying to establish connection.
Jul 24 06:53:46 ip-172-31-23-197 systemd-timesyncd[587]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com).
Jul 24 06:55:01 ip-172-31-23-197 CRON[1740]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jul 24 06:58:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: 2019-07-24 06:58:52 INFO Backing off health check to every 1200 seconds for 3600 seconds.
Jul 24 06:58:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: 2019-07-24 06:58:52 ERROR Health ping failed with error - EC2RoleRequestError: no EC2 instance role found
Jul 24 06:58:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: caused by: EC2MetadataError: failed to make EC2Metadata request
Jul 24 06:58:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: caused by: <?xml version="1.0" encoding="iso-8859-1"?>
Jul 24 06:58:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
Jul 24 06:58:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Jul 24 06:58:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
Jul 24 06:58:52 ip-172-31-23-197 amazon-ssm-agent.amazon-ssm-agent[896]: <head>

please find the Syslog attached.

 

Regards,

Pavel Junek Community Leader Jul 24, 2019

Hi Vinod,

Thank you for your input. Everything look OK.

At the moment Jira is starting, a potential problem will be seen in atlassian-jira.log. In Jira, the default is 300 seconds to wait for plugins to start, so sometimes Jira takes a long time to start. You can monitor the current log in the terminal:

tail -f /var/atlassian/application-data/jira/log/atlassian-jira.log

As for the freezing of the server, ssh and Jira, so it is strange and I'm not sure if it is rather a problem with the Ubuntu server itself.

Pavel

when i run "ps aux | grep jira"

root@ip-172-31-23-197:/# ps aux | grep jira
jira 1838 83.8 49.7 4504600 501220 ? Sl 16:07 0:41 /opt/atlassian jira/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms384m -Xmx2048m -XX:InitialCodeCacheSize=32m -XX:ReservedCodeCacheSize=512m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:-OmitStackTraceInFastThrow -Djava.locale.providers=COMPAT -Datlassian.plugins.startup.options= -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Xloggc:/opt/atlassian/jira/logs/atlassian-jira-gc-%t.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCCause -Dignore.endorsed.dirs= -classpath /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home=/opt/atlassian/jira -Djava.io.tmpdir=/opt/atlassian/jira/temp org.apache.catalina.startup.Bootstrap start
postgres 1925 12.0 1.8 324208 18376 ? Ss 16:08 0:03 postgres: 10/main: jirau jira 127.0.0.1(50202) idle
root 1996 0.0 0.0 14856 976 pts/0 S+ 16:08 0:00 grep --color=auto jira
Pavel Junek Community Leader Jul 24, 2019

Yeah, great. This is OK. Jira is UP.

wait wait wait,

Jira is up but only for jus couple of minutes only.

As I shared a screenshot earlier, that is the problem,...

when I run tail until 15 seconds remaining of 300 seconds everything goes fine but last 14 seconds something goes wrong. please verify the error logs below. 

tail -f /var/atlassian/application-data/jira/log/atlassian-jira.log
2019-07-24 17:15:45,557 Spring DM Context Creation Timer WARN [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Timeout occurred before finding service dependencies for [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.gadgets.directory, config=osgibundle:/META-INF/spring/*.xml)]
2019-07-24 17:15:46,289 JIRA-Bootstrap INFO [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (11): [com.atlassian.jira.gadgets, com.atlassian.jira.jira-projects-issue-navigator, com.atlassian.jira.plugin.ext.bamboo, com.atlassian.jira.plugins.jira-bitbucket-connector-plugin, com.atlassian.gadgets.directory, com.atlassian.jira.rest, com.atlassian.jira.plugins.jira-development-integration-plugin, com.pyxis.greenhopper.jira, com.atlassian.jira.jira-core-reports-plugin, com.atlassian.jira.jira-issue-nav-plugin, com.atlassian.troubleshooting.plugin-jira], 14 seconds remaining
2019-07-24 17:15:46,289 Spring DM Context Creation Timer ERROR [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.gadgets.directory' never resolved service '&subscribedGadgetFeedStore' with filter '(&(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore)(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore))'
2019-07-24 17:15:47,293 Spring DM Context Creation Timer ERROR [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.gadgets.directory'
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.gadgets.directory' has timed out waiting for (&(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore)(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore))
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
2019-07-24 17:15:48,316 JIRA-Bootstrap INFO [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (11): [com.atlassian.jira.gadgets, com.atlassian.jira.jira-projects-issue-navigator, com.atlassian.jira.plugin.ext.bamboo, com.atlassian.jira.plugins.jira-bitbucket-connector-plugin, com.atlassian.gadgets.directory, com.atlassian.jira.rest, com.atlassian.jira.plugins.jira-development-integration-plugin, com.pyxis.greenhopper.jira, com.atlassian.jira.jira-core-reports-plugin, com.atlassian.jira.jira-issue-nav-plugin, com.atlassian.troubleshooting.plugin-jira], 12 seconds remaining
2019-07-24 17:16:30,530 Gemini Blueprint context shutdown thread 1 WARN [o.s.b.factory.support.DisposableBeanAdapter] Invocation of destroy method failed on bean with name 'dashboardItemModulesList': java.lang.NullPointerException
2019-07-24 17:16:30,734 Gemini Blueprint context shutdown thread 1 WARN [o.s.b.factory.support.DisposableBeanAdapter] Invocation of destroy method failed on bean with name 'localGadgetSpecProviders': java.lang.NullPointerException
2019-07-24 17:16:30,777 Gemini Blueprint context shutdown thread 1 WARN [o.s.b.factory.support.DisposableBeanAdapter] Invocation of destroy method failed on bean with name 'gadgetSpecProviders': java.lang.NullPointerException
2019-07-24 17:16:30,980 Spring DM Context Creation Timer ERROR [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.gadgets.directory, config=osgibundle:/META-INF/spring/*.xml))
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.gadgets.directory' has timed out waiting for (&(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore)(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore))
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
2019-07-24 17:16:31,784 Spring DM Context Creation Timer ERROR [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.gadgets.directory], unsatisfied dependencies: Dependency on [(&(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore)(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore))] (from bean [&subscribedGadgetFeedStore])
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.gadgets.directory' has timed out waiting for (&(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore)(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore))
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
2019-07-24 17:16:32,110 Spring DM Context Creation Timer WARN [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Timeout occurred before finding service dependencies for [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.plugins.jira-development-integration-plugin, config=osgibundle:/META-INF/spring/*.xml)]
2019-07-24 17:16:32,112 Spring DM Context Creation Timer ERROR [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.jira.plugins.jira-development-integration-plugin' never resolved service '&dvcsChangesetService' with filter '(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService))'
2019-07-24 17:16:32,112 Spring DM Context Creation Timer ERROR [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.jira.plugins.jira-development-integration-plugin' never resolved service '&dvcsPullRequestService' with filter '(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService))'
2019-07-24 17:16:32,112 Spring DM Context Creation Timer ERROR [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.jira.plugins.jira-development-integration-plugin' never resolved service '&bambooRestService' with filter '(&(objectClass=com.atlassian.jira.plugin.ext.bamboo.service.BambooRestService)(objectClass=com.atlassian.jira.plugin.ext.bamboo.service.BambooRestService))'
2019-07-24 17:16:32,113 Spring DM Context Creation Timer ERROR [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.jira.plugins.jira-development-integration-plugin' never resolved service '&dvcsBranchService' with filter '(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService))'
2019-07-24 17:16:32,113 Spring DM Context Creation Timer ERROR [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.jira.plugins.jira-development-integration-plugin' never resolved service '&dvcsRepositoryService' with filter '(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService))'
2019-07-24 17:16:32,113 Spring DM Context Creation Timer ERROR [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.jira.plugins.jira-development-integration-plugin' never resolved service '&dvcsLinkService' with filter '(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService))'
2019-07-24 17:16:32,113 Spring DM Context Creation Timer ERROR [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.jira.plugins.jira-development-integration-plugin'
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.jira.plugins.jira-development-integration-plugin' has timed out waiting for (|(&(objectClass=com.atlassian.jira.plugin.ext.bamboo.service.BambooRestService)(objectClass=com.atlassian.jira.plugin.ext.bamboo.service.BambooRestService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService)))
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
2019-07-24 17:16:34,507 Spring DM Context Creation Timer ERROR [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.plugins.jira-development-integration-plugin, config=osgibundle:/META-INF/spring/*.xml))
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.jira.plugins.jira-development-integration-plugin' has timed out waiting for (|(&(objectClass=com.atlassian.jira.plugin.ext.bamboo.service.BambooRestService)(objectClass=com.atlassian.jira.plugin.ext.bamboo.service.BambooRestService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService)))
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
2019-07-24 17:16:34,508 Spring DM Context Creation Timer ERROR [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.jira.plugins.jira-development-integration-plugin], unsatisfied dependencies: Dependency on [(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService))] (from bean [&dvcsPullRequestService]), Dependency on [(&(objectClass=com.atlassian.jira.plugin.ext.bamboo.service.BambooRestService)(objectClass=com.atlassian.jira.plugin.ext.bamboo.service.BambooRestService))] (from bean [&bambooRestService]), Dependency on [(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService))] (from bean [&dvcsBranchService]), Dependency on [(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService))] (from bean [&dvcsRepositoryService]), Dependency on [(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService))] (from bean [&dvcsChangesetService]), Dependency on [(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService))] (from bean [&dvcsLinkService])
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.jira.plugins.jira-development-integration-plugin' has timed out waiting for (|(&(objectClass=com.atlassian.jira.plugin.ext.bamboo.service.BambooRestService)(objectClass=com.atlassian.jira.plugin.ext.bamboo.service.BambooRestService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsBranchService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsChangesetService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsLinkService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsPullRequestService))(&(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService)(objectClass=com.atlassian.jira.plugins.dvcs.service.api.DvcsRepositoryService)))
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
tail -f /var/atlassian/application-data/jira/log/atlassian-jira.log

wait wait wait, jira error.png

Pavel,

as soon as I give tail cmd shows below log, Jira is up to some time Jira starts as shown in the screenshot, and immediately the server stops, again I need to restart the server and as well as service also.

 

2019-07-24 19:15:19,783 JIRA-Bootstrap INFO [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (12): [com.atlassian.jira.jira-issue-nav-components, com.atlassian.jira.jira-projects-issue-navigator, com.atlassian.jira.plugins.jira-bitbucket-connector-plugin, com.atlassian.jira.gadgets, com.atlassian.jira.plugin.ext.bamboo, com.pyxis.greenhopper.jira, com.atlassian.jirafisheyeplugin, com.atlassian.jira.plugins.webhooks.jira-webhooks-plugin, com.atlassian.gadgets.directory, com.atlassian.jira.plugins.jira-development-integration-plugin, com.atlassian.jira.rest, com.atlassian.jira.jira-issue-nav-plugin], 228 seconds remaining
2019-07-24 19:17:00,634 JIRA-Bootstrap INFO [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (12): [com.atlassian.jira.jira-issue-nav-components, com.atlassian.jira.jira-projects-issue-navigator, com.atlassian.jira.plugins.jira-bitbucket-connector-plugin, com.atlassian.jira.gadgets, com.atlassian.jira.plugin.ext.bamboo, com.pyxis.greenhopper.jira, com.atlassian.jirafisheyeplugin, com.atlassian.jira.plugins.webhooks.jira-webhooks-plugin, com.atlassian.gadgets.directory, com.atlassian.jira.plugins.jira-development-integration-plugin, com.atlassian.jira.rest, com.atlassian.jira.jira-issue-nav-plugin], 124 seconds remaining
2019-07-24 19:18:45,548 JIRA-Bootstrap INFO [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (12): [com.atlassian.jira.jira-issue-nav-components, com.atlassian.jira.jira-projects-issue-navigator, com.atlassian.jira.plugins.jira-bitbucket-connector-plugin, com.atlassian.jira.gadgets, com.atlassian.jira.plugin.ext.bamboo, com.pyxis.greenhopper.jira, com.atlassian.jirafisheyeplugin, com.atlassian.jira.plugins.webhooks.jira-webhooks-plugin, com.atlassian.gadgets.directory, com.atlassian.jira.plugins.jira-development-integration-plugin, com.atlassian.jira.rest, com.atlassian.jira.jira-issue-nav-plugin], 23 seconds remaining
2019-07-24 19:20:29,122 JIRA-Bootstrap INFO [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (12): [com.atlassian.jira.jira-issue-nav-components, com.atlassian.jira.jira-projects-issue-navigator, com.atlassian.jira.plugins.jira-bitbucket-connector-plugin, com.atlassian.jira.gadgets, com.atlassian.jira.plugin.ext.bamboo, com.pyxis.greenhopper.jira, com.atlassian.jirafisheyeplugin, com.atlassian.jira.plugins.webhooks.jira-webhooks-plugin, com.atlassian.gadgets.directory, com.atlassian.jira.plugins.jira-development-integration-plugin, com.atlassian.jira.rest, com.atlassian.jira.jira-issue-nav-plugin], -21 seconds remaining
2019-07-24 19:26:18,867 Spring DM Context Creation Timer WARN [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Timeout occurred before finding service dependencies for [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.gadgets.directory, config=osgibundle:/META-INF/spring/*.xml)]
Pavel Junek Community Leader Jul 24, 2019

Jira logs does not conetent any problems, the log show the normal application start. It looks like there is a problem with the Ubuntu server itself.

How much RAM is allocated to the server and how much disk space is available?

Hi,

it's RAM: 1GB
and memory: 50GB

Pavel Junek Community Leader Jul 24, 2019

Hi,

Voila, here is the problem 🙂. 1GB RAM is too much small. Please look to https://confluence.atlassian.com/adminjiraserver/jira-applications-installation-requirements-938846826.html and https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html

Recommended minimum RAM is 4GB (Jira + OS)

Oh no !! 

please say one good news!

if I use ubuntu CLI mode (no graphical). with 2gb RAM.

and I will be having <8users

                                <3projects

                                <and issues are also very less.

these all can be run on 2GB ram ?? 

 

Regards,

Vinod

Pavel Junek Community Leader Jul 24, 2019

Probably yes, 2GB RAM may be enough. However, the following needs to be modified:

 vim /opt/atlassian/jira/bin/setenv.sh


# The following 2 settings control the minimum and maximum given to the JIRA Java virtual machine.  In larger JIRA instances, the maximum amount will need to be increased.
#

JVM_MINIMUM_MEMORY="512m"
JVM_MAXIMUM_MEMORY="1024m"

This is a reduction in the JVM's Heap JVM settings. Minimum memory for Jira is 512 MB and maximum is 1024MB, that will probably be enough.

Pavel 

Hi @Pavel Junek 

I tried in another Ubuntu server with 2gb ram, everything goes fine.

Thanks for the quick response.

 

Regards,

Vinod

Like Pavel Junek likes this

Hi @Pavel Junek 

 

can I install the below 64bit version on ubuntu 32bit operating system

https://product-downloads.atlassian.com/software/jira/downloads/atlassian-jira-software-8.3.1-x64.bin

 

Regards,

Vinod

Pavel Junek Community Leader Aug 05, 2019

Hi @Vinod Bathi,

Probably not, Atlassian has stopped supporting 32-bit versions.

If I helped you in any way, please mark this thread as Accepted answer so that other Atlassian community users might know that this thread has a solution :-)

Thank you!

Pavel

Comment

Log in or Sign up to comment
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you