As the machine moved, IP was replaced. When you encounter some problems during restarting JIRA, record the key points and solutions.
Key points:
check the database configuration
/var/atlas/application data/JIRA/dbconfig. XML
since LDAP authentication is used, you also need to check the user group authentication configuration
find CWD in the database_ directory_ Attribute table, check the configuration with the attribute name ldap.url
Problems and solutions:
JIRA startup failed, JIRA has been locked.
******************************************
JIRA startup failed
unable to create and acquire lock file for jira.home directory ‘/ var/atlas/application data/JIRA… I don’t remember later
solution: delete the. Jira-home.lock (hidden file) under the corresponding directory prompted, enter the bin directory and restart the JIRA service
>>>>>
then an error is reported:
JIRA startup failed
unable to clean the cache directory:/var/atlas/application data/JIRA/plugins /. OSGi plugins/Felix
Check the startup log:
caused by: java.io.ioexception: unable to delete file:/var/atlas/application data/JIRA/plugins /. OSGi plugins/Felix/Felix cache/bundle163/bundle. State
solution: delete the. OSGi plugins folder (hidden folder) in the prompt directory and restart JIRA service
At this time, the original error page will become startup seccused and can be used normally
./startup.sh and./shutdown.sh are recommended for restarting the JIRA service
Read More:
- [Solved] Mycat Startup Error: ERROR Startup failed: Timed out waiting for a signal from the JVM
- NFS startup error: restart failed [How to Solve]
- [Solved] kafka Startup Error: Fatal error during KafkaServer startup
- Spark-shell startup error: Yarn application has already ended! It might have been killed or unable to launch application master
- New Spring boot startup error Failed to auto-configure a DataSource
- SpringBoot startup error Failed to determine a suitable driver class
- [Solved] ElasticSearch startup error: bootstrap checks failed
- Wildfly (JBoss) startup error: ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation (“add”) failed
- [Solved] Swagger Startup Error: Failed to start bean ‘documentationPluginsBootstrapper‘
- [Solved] Elasticsearch 7.10 Startup Error: bootstrap checks failed
- Tomcat startup error: Failed to start component [StandardServer[8005]] solution
- [Solved] Canal 1.1.5 Startup Error: caching_sha2_password Auth failed
- [Solved] mongodb Startup Error: ERROR: child process failed, exited with error number 14
- [Solved] Elasticsearch-7.2.1 startup error: ERROR: [1] bootstrap checks failed
- ES Startup error: ERROR: [2] bootstrap checks failed
- [Solved] zookeeper Startup Error: already running as process
- [Solved] Failed update hbase:meta table descriptor HBase Startup Error
- Hbase Shell startup error: [ERROR] Terminal initialization failed; falling back to unsupported
- [Solved] Windows Nginx Startup Error: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket
- [Solved] Springboot Startup Error: Consider defining a bean of type ‘XXX’ in your configuration.