一、报错情况

报错一:

1、重点内容:

ERROR  | wrapper  | 2021/11/30 13:44:40 | Startup failed: Timed out waiting for a signal from the JVM.
ERROR  | wrapper  | 2021/11/30 13:44:40 | JVM did not exit on request, terminated
INFO   | wrapper  | 2021/11/30 13:44:40 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper  | 2021/11/30 13:44:40 | JVM exited in response to signal SIGKILL (9).

2、完整报错内容:

STATUS | wrapper  | 2021/11/30 13:44:11 | --> Wrapper Started as Daemon
STATUS | wrapper  | 2021/11/30 13:44:11 | Launching a JVM...
ERROR  | wrapper  | 2021/11/30 13:44:40 | Startup failed: Timed out waiting for a signal from the JVM.
ERROR  | wrapper  | 2021/11/30 13:44:40 | JVM did not exit on request, terminated
INFO   | wrapper  | 2021/11/30 13:44:40 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper  | 2021/11/30 13:44:40 | JVM exited in response to signal SIGKILL (9).
STATUS | wrapper  | 2021/11/30 13:44:44 | Launching a JVM...
STATUS | wrapper  | 2021/11/30 13:45:04 | TERM trapped.  Shutting down.
ERROR  | wrapper  | 2021/11/30 13:45:38 | Shutdown failed: Timed out waiting for signal from JVM.
ERROR  | wrapper  | 2021/11/30 13:45:38 | JVM did not exit on request, terminated
INFO   | wrapper  | 2021/11/30 13:45:38 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper  | 2021/11/30 13:45:38 | JVM exited in response to signal SIGKILL (9).
STATUS | wrapper  | 2021/11/30 13:45:38 | <-- Wrapper Stopped
STATUS | wrapper  | 2021/11/30 13:46:24 | --> Wrapper Started as Daemon
STATUS | wrapper  | 2021/11/30 13:46:25 | Launching a JVM...
ERROR  | wrapper  | 2021/11/30 13:46:54 | Startup failed: Timed out waiting for a signal from the JVM.
ERROR  | wrapper  | 2021/11/30 13:46:54 | JVM did not exit on request, terminated
INFO   | wrapper  | 2021/11/30 13:46:54 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper  | 2021/11/30 13:46:54 | JVM exited in response to signal SIGKILL (9).
STATUS | wrapper  | 2021/11/30 13:46:58 | Launching a JVM...
ERROR  | wrapper  | 2021/11/30 13:47:27 | Startup failed: Timed out waiting for a signal from the JVM.
ERROR  | wrapper  | 2021/11/30 13:47:27 | JVM did not exit on request, terminated
INFO   | wrapper  | 2021/11/30 13:47:27 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper  | 2021/11/30 13:47:27 | JVM exited in response to signal SIGKILL (9).
STATUS | wrapper  | 2021/11/30 13:47:32 | Launching a JVM...
ERROR  | wrapper  | 2021/11/30 13:48:01 | Startup failed: Timed out waiting for a signal from the JVM.
ERROR  | wrapper  | 2021/11/30 13:48:01 | JVM did not exit on request, terminated
INFO   | wrapper  | 2021/11/30 13:48:01 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper  | 2021/11/30 13:48:01 | JVM exited in response to signal SIGKILL (9).
STATUS | wrapper  | 2021/11/30 13:48:05 | Launching a JVM...
ERROR  | wrapper  | 2021/11/30 13:48:34 | Startup failed: Timed out waiting for a signal from the JVM.
ERROR  | wrapper  | 2021/11/30 13:48:34 | JVM did not exit on request, terminated
INFO   | wrapper  | 2021/11/30 13:48:34 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper  | 2021/11/30 13:48:34 | JVM exited in response to signal SIGKILL (9).
STATUS | wrapper  | 2021/11/30 13:48:38 | Launching a JVM...
ERROR  | wrapper  | 2021/11/30 13:49:08 | Startup failed: Timed out waiting for a signal from the JVM.
ERROR  | wrapper  | 2021/11/30 13:49:08 | JVM did not exit on request, terminated
INFO   | wrapper  | 2021/11/30 13:49:08 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper  | 2021/11/30 13:49:08 | JVM exited in response to signal SIGKILL (9).
FATAL  | wrapper  | 2021/11/30 13:49:08 | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
FATAL  | wrapper  | 2021/11/30 13:49:08 |   There may be a configuration problem: please check the logs.
STATUS | wrapper  | 2021/11/30 13:49:08 | <-- Wrapper Stopped

报错二:

1、重点内容:

INFO   | jvm 1    | 2021/11/30 13:59:37 |  WARN | Failed startup of context o.e.j.w.WebAppContext@e7892a8{/admin,file:///data/apache-activemq-5.15.15/webapps/admin/,STOPPED}
INFO   | jvm 1    | 2021/11/30 13:59:37 | java.lang.IllegalStateException: Parent for temp dir not configured correctly: writeable=false

2、完整报错内容:

STATUS | wrapper  | 2021/11/30 13:50:42 | --> Wrapper Started as Daemon
STATUS | wrapper  | 2021/11/30 13:50:43 | Launching a JVM...
INFO   | jvm 1    | 2021/11/30 13:51:39 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2021/11/30 13:51:39 |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
INFO   | jvm 1    | 2021/11/30 13:51:39 | 
INFO   | jvm 1    | 2021/11/30 13:51:39 | Java Runtime: Oracle Corporation 1.8.0_191 /data/jdk8/jre
INFO   | jvm 1    | 2021/11/30 13:51:39 |   Heap sizes: current=1005056k  free=963112k  max=3728384k
INFO   | jvm 1    | 2021/11/30 13:51:39 |     JVM args: -Dactivemq.home=../.. -Dactivemq.base=../.. -Djavax.net.ssl.keyStorePassword=password -Djavax.net.ssl.trustStorePassword=password -Djavax.net.ssl.keyStore=../../conf/broker.ks -Djavax.net.ssl.trustStore=../../conf/broker.ts -Dcom.sun.management.jmxremote -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties -Dactivemq.conf=../../conf -Dactivemq.data=../../data -Djava.security.auth.login.config=../../conf/login.config -Xms1024m -Xmx4096m -Djava.library.path=../../bin/linux-x86-64/ -Dwrapper.key=Ig7SAerLj21TEukK -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=11220 -Dwrapper.version=3.2.3 -Dwrapper.native_library=wrapper -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1
INFO   | jvm 1    | 2021/11/30 13:51:39 | Extensions classpath:
INFO   | jvm 1    | 2021/11/30 13:51:39 |   [../../lib,../../lib/camel,../../lib/optional,../../lib/web,../../lib/extra]
INFO   | jvm 1    | 2021/11/30 13:51:39 | ACTIVEMQ_HOME: ../..
INFO   | jvm 1    | 2021/11/30 13:51:39 | ACTIVEMQ_BASE: ../..
INFO   | jvm 1    | 2021/11/30 13:51:39 | ACTIVEMQ_CONF: ../../conf
INFO   | jvm 1    | 2021/11/30 13:51:39 | ACTIVEMQ_DATA: ../../data
INFO   | jvm 1    | 2021/11/30 13:51:39 | Loading message broker from: xbean:activemq.xml
INFO   | jvm 1    | 2021/11/30 13:51:39 |  INFO | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@7ab00cbf: startup date [Tue Nov 30 13:51:39 CST 2021]; root of context hierarchy
INFO   | jvm 1    | 2021/11/30 13:53:32 |  INFO | Using Persistence Adapter: KahaDBPersistenceAdapter[/data/apache-activemq-5.15.15/bin/linux-x86-64/../../data/kahadb]
INFO   | jvm 1    | 2021/11/30 13:53:32 |  INFO | PListStore:[/data/apache-activemq-5.15.15/bin/linux-x86-64/../../data/static-broker1/tmp_storage] started
INFO   | jvm 1    | 2021/11/30 13:54:28 |  INFO | Apache ActiveMQ 5.15.15 (static-broker1, ID:rabbitmq-0001.novalocal-25301-1638251668680-0:1) is starting
INFO   | jvm 1    | 2021/11/30 13:55:24 |  INFO | Listening for connections at: tcp://rabbitmq-0001.novalocal:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600
INFO   | jvm 1    | 2021/11/30 13:55:24 |  INFO | Connector openwire started
INFO   | jvm 1    | 2021/11/30 13:56:21 |  INFO | Listening for connections at: amqp://rabbitmq-0001.novalocal:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600
INFO   | jvm 1    | 2021/11/30 13:56:21 |  INFO | Connector amqp started
INFO   | jvm 1    | 2021/11/30 13:57:17 |  INFO | Listening for connections at: stomp://rabbitmq-0001.novalocal:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600
INFO   | jvm 1    | 2021/11/30 13:57:17 |  INFO | Connector stomp started
INFO   | jvm 1    | 2021/11/30 13:58:13 |  INFO | Listening for connections at: mqtt://rabbitmq-0001.novalocal:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600
INFO   | jvm 1    | 2021/11/30 13:58:13 |  INFO | Connector mqtt started
INFO   | jvm 1    | 2021/11/30 13:58:13 |  INFO | Starting Jetty server
INFO   | jvm 1    | 2021/11/30 13:58:41 |  INFO | Creating Jetty connector
INFO   | jvm 1    | 2021/11/30 13:59:37 |  WARN | ServletContext@o.e.j.s.ServletContextHandler@f461c24{/,null,STARTING} has uncovered http methods for path: /
INFO   | jvm 1    | 2021/11/30 13:59:37 |  INFO | Listening for connections at ws://rabbitmq-0001.novalocal:61614?maximumConnections=1000&wireFormat.maxFrameSize=104857600
INFO   | jvm 1    | 2021/11/30 13:59:37 |  INFO | Connector ws started
INFO   | jvm 1    | 2021/11/30 13:59:37 |  INFO | Apache ActiveMQ 5.15.15 (static-broker1, ID:rabbitmq-0001.novalocal-25301-1638251668680-0:1) started
INFO   | jvm 1    | 2021/11/30 13:59:37 |  INFO | For help or more information please see: http://activemq.apache.org
INFO   | jvm 1    | 2021/11/30 13:59:37 |  WARN | Failed startup of context o.e.j.w.WebAppContext@e7892a8{/admin,file:///data/apache-activemq-5.15.15/webapps/admin/,STOPPED}
INFO   | jvm 1    | 2021/11/30 13:59:37 | java.lang.IllegalStateException: Parent for temp dir not configured correctly: writeable=false
INFO   | jvm 1    | 2021/11/30 13:59:37 | 	at org.eclipse.jetty.webapp.WebInfConfiguration.makeTempDirectory(WebInfConfiguration.java:499)[jetty-all-9.4.39.v20210325-uber.jar:9.4.39.v20210325]
INFO   | jvm 1    | 2021/11/30 13:59:37 | 	at org.eclipse.jetty.webapp.WebInfConfiguration.resolveTempDirectory(WebInfConfiguration.java:468)[jetty-all-9.4.39.v20210325-uber.jar:9.4.39.v20210325]
INFO   | jvm 1    | 2021/11/30 13:59:37 | 	at org.eclipse.jetty.webapp.WebInfConfiguration.preConfigure(WebInfConfiguration.java:140)[jetty-all-9.4.39.v20210325-uber.jar:9.4.39.v20210325]
INFO   | jvm 1    | 2021/11/30 13:59:37 | 	at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:488)[jetty-all-9.4.39.v20210325-uber.jar:9.4.39.v20210325]

二、处理步骤

2.1 问题一解决方法:

找到activemqwrapper.conf配置文件
位置参加:/data/apache-activemq-5.15.15/bin/linux-x86-64/wrapper.conf
在末尾添加如下内容:

wrapper.startup.timeout=300

2.2 问题二解决方法:

查看 tmp目录是否有其他用户的写权限,如下图所示,我这边其他用户没有写的权限
在这里插入图片描述
可以使用chmod进行权限赋予

chmod +x /tmp

无法赋予的话可以使用lsblk查看是否有挂载

[root@cheng0307 linux-x86-64]# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda      8:0    0   60G  0 disk
├─sda1   8:1    0  500M  0 part /boot
├─sda2   8:2    0   20G  0 part /home
├─sda3   8:3    0    4G  0 part [SWAP]
├─sda4   8:4    0    1K  0 part
└─sda5   8:5    0 35.5G  0 part /
sr0     11:0    1  4.2G  0 rom  /mnt
sr0     11:0    1  4.2G  0 rom  /tmp

有挂载需要进行解挂载,无法接触使用强制命令

umount /tmp						##解除挂载
umount -1f /tmp					##强制解除挂载

三、经验总结

1)不要使用tmp作为本地yum镜像的挂载路径,因为有很多服务需要在tmp目录下写入文件,比如mysql.sock文件;
2)解除挂载目录的时候一定要确保已经成功解除挂载。

Logo

为开发者提供学习成长、分享交流、生态实践、资源工具等服务,帮助开发者快速成长。

更多推荐