解决在centos x64 上安装openfire出现的错误

最新推荐文章于 2024-12-27 14:13:54 发布
原创 最新推荐文章于 2024-12-27 14:13:54 发布 · 9.5k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#centos #command #java #服务器 #file

在centos x64 上安装openfire，运行  /etc/init.d/openfire start后发现服务器没法开启，查看log日志：


nohup: failed to run command `/opt/openfire/jre/bin/java': No such file or directory


很奇怪，我是在centos上安装了java，openfire自带的jre就没法使用了，在论坛上搜索到下面的解决办法：


http://community.igniterealtime.org/thread/43673


cd /opt/openfire/jre/bin

cp java java.bak

rm java

ln -s /usr/bin/java java

service openfire start


问题解决^-^



[文章作者]曾健生

[作者邮箱]zengjiansheng1@126.com

[作者QQ]190678908

[博客]  http://blog.csdn.net/newjueqi

http://blog.sina.com.cn/h6k65




CentOS 7 64位操作系统，自建加密聊天环境Openfire XMPP服务
简简单单,平平凡凡.
08-10 2328
0、参考资料： https://xmpp.org/software/clients.html http://aqq.eu/ http://www.igniterealtime.org/projects/openfire/ 1、首先准备自己的服务器，安装好CentOS7操作系统，如果是自己公司的服务器，需要自己安装操作系统。     CentOS 7 启动图形界面问题，之前有在
centos6.8下升级ssh
weixin_44767040的博客
06-17 1268
centos6.8下升级ssh
openfire 重新安装
sskicgah的专栏
10-30 3769
之前安装的openfire用于做简单的推送，自己开发了一个小模块，在一个应用中嵌入，后来估计有上千的用户吧。 昨天发现不能推送了，就去看了一下，卡着动不了，停止服务也停不了，kill -9了。 重启，启动后一直没得进登录页面，要重新配置，配置后继续配置。 因为之前用的是自带的hsqldbc，似乎是数据库不能用。改配置成mysql，也不行。 想想只能卸载重新安装了，数据没了。 rpm -e
openfire 重启进入配置界面
mayi18的博客
05-01 596
Openfire Restart 关闭openfire，/etc/init.d/openfire stop。 杀死openfire进程。ps aux查看openfire进程，kill -9 xx杀死openfire进程。 设置配置文件权限，确保conf文件夹下所有文件可读写权限，chmod -Rf 777 conf。 重新启动openfire，/etc/init.d/openfire start...
nohup: failed to run command java: No such file or directory解决
wwwwww33的博客
06-11 2万+
程序里远程执行shell命令（nohup java -jar ...）的执行，后台日志报错如下： nohup: failed to run command `java': No such file or directory 原因：一般来说这个报错说明服务器执行不了"java"这个命令 解决：创作中心 1、检查执行该shell的服务器有没有装jdk 2、检查执行该shell的服务器的环境变量有没有将JAVA_HOME/bin加入（目的是可以在linux任意位置执行java命令） ---------
nohup: failed to run command 'java': No such file or directory
我的博客
03-03 9540
文章目录问题现象：解决办法： 问题现象： 在Ambari平台启动某个服务时， 会在ambari-server节点执行类型nohup java -jar XX.jar这样的指令 如果把这个指令单独拿出来，放在Linux上执行是没有任何问题的 通过平台调用就出现如下错误 nohup: failed to run command 'java': No such file or directory 解决...
failed to run command ‘java‘: No such file or directory
weixin_43135696的博客
02-22 8851
一、报错场景 nohup java -jar xxx.jar 2>&1 & 运行上述命令后报错“failed to run command ‘java’: No such file or directory”，且执行 java -version、javac 正常，查看/etc/profile中配置正常。 二、解决方法 vim ~/.bashrc #最后面添加 export JAVA_HOME=/home/soft/jdk1.8.0_261 export JRE_HOME=${.
[root@yfw openfire]# ls -l /opt/openfire/bin/start.sh -rwxr-xr-x 1 openfire openfire 2630 Nov 15 15:15 /opt/openfire/bin/start.sh [root@yfw openfire]#
最新发布
11-16
| `Environment="OPENFIRE_HOME=/opt/openfire"` | ✅ 强制告诉 OpenFire 它的“家”在哪，解决 `Could not locate home` 错误 | | `JAVA_HOME` | 避免因默认 Java 版本不对导致启动失败 | > 这两个环境变量 **...
[root@yfw ~]# cd /etc/systemd/system [root@yfw system]# ls -l /opt/openfire/lib/startup.jar -rwxr-xr-x 1 openfire openfire 51542 Feb 1 1980 /opt/openfire/lib/startup.jar [root@yfw system]# sudo -u openfire cat /opt/openfire/lib/startup.jar | head -c 4 PK[root@yfw system]# sudo sed -i '/^su -s \/bin\/sh -c/c\ > su -s /bin/sh -c "\ > echo \"DEBUG: Current user: $(whoami)\";\ > echo \"DEBUG: Current dir: $(pwd)\";\ > echo \"DEBUG: Checking startup.jar...\";\ > ls -l lib/startup.jar;\ > file lib/startup.jar;\ > java -cp lib/startup.jar org.jivesoftware.openfire.starter.ServerStarter --help 2>&1 || echo \\\"Failed to run ServerStarter\\\";\ > echo \"Starting OpenFire正式启动...\";\ > exec '\"$JAVA\"' \ > -server \ > -Xms64m \ > -Xmx512m \ > -DopenfireHome=\"'$OPENFIRE_HOME'\" \ > -Dopenfire.lib.dir=\"'$OPENFIRE_HOME'/lib\" \ > -Dlog4j.configurationFile=\"file://'$OPENFIRE_HOME'/lib/log4j2.xml\" \ > -classpath '\"$CP\"' \ > org.jivesoftware.openfire.starter.ServerStarter" openfire >> "$LOG_FILE" 2>&1 &\' /opt/openfire/bin/start.sh [root@yfw system]# /opt/openfire/bin/start.sh Using Java: /usr/lib/jvm/java-17-openjdk/bin/java Java Version: openjdk version "17.0.1" 2021-10-19 LTS OpenJDK Runtime Environment 21.9 (build 17.0.1+12-LTS) OpenJDK 64-Bit Server VM 21.9 (build 17.0.1+12-LTS, mixed mode, sharing) Classpath: /opt/openfire/lib/activation-1.1.jar:/opt/openfire/lib/apache-el-9.0.107.jar:/opt/openfire/lib/apache-jsp-9.0.107.jar:/opt/openfire/lib/asm-9.8.jar:/opt/openfire/lib/asm-commons-9.8.jar:/opt/openfire/lib/asm-tree-9.8.jar:/opt/openfire/lib/bcpg-jdk18on-1.78.1.jar:/opt/openfire/lib/bcpkix-jdk18on-1.78.1.jar:/opt/openfire/lib/bcprov-jdk18on-1.78.1.jar:/opt/openfire/lib/bcutil-jdk18on-1.78.1.jar:/opt/openfire/lib/caffeine-3.2.0.jar:/opt/openfire/lib/checker-qual-3.33.0.jar:/opt/openfire/lib/common-image-3.9.4.jar:/opt/openfire/lib/common-io-3.9.4.jar:/opt/openfire/lib/common-lang-3.9.4.jar:/opt/openfire/lib/commons-codec-1.15.jar:/opt/openfire/lib/commons-dbcp2-2.9.0.jar:/opt/openfire/lib/commons-ip-math-1.32.jar:/opt/openfire/lib/commons-lang3-3.18.0.jar:/opt/openfire/lib/commons-logging-1.2.jar:/opt/openfire/lib/commons-pool2-2.9.0.jar:/opt/openfire/lib/commons-text-1.10.0.jar:/opt/openfire/lib/dom4j-2.1.4.jar:/opt/openfire/lib/dwr-3.0.2-RELEASE.jar:/opt/openfire/lib/ecj-3.33.0.jar:/opt/openfire/lib/error_prone_annotations-2.18.0.jar:/opt/openfire/lib/failureaccess-1.0.1.jar:/opt/openfire/lib/guava-32.0.1-jre.jar:/opt/openfire/lib/hsqldb-2.7.1.jar:/opt/openfire/lib/httpclient-4.5.13.jar:/opt/openfire/lib/httpcore-4.4.13.jar:/opt/openfire/lib/i18n-5.0.2.jar:/opt/openfire/lib/imageio-bmp-3.9.4.jar:/opt/openfire/lib/imageio-core-3.9.4.jar:/opt/openfire/lib/istack-commons-runtime-3.0.11.jar:/opt/openfire/lib/j2objc-annotations-2.8.jar:/opt/openfire/lib/jakarta.activation-1.2.2.jar:/opt/openfire/lib/jakarta.annotation-api-1.3.5.jar:/opt/openfire/lib/jakarta.transaction-api-1.3.3.jar:/opt/openfire/lib/jakarta.xml.bind-api-2.3.3.jar:/opt/openfire/lib/jansi-1.18.jar:/opt/openfire/lib/javax.activation-api-1.2.0.jar:/opt/openfire/lib/javax.mail-1.6.2.jar:/opt/openfire/lib/jaxb-api-2.3.1.jar:/opt/openfire/lib/jaxb-runtime-2.3.3.jar:/opt/openfire/lib/jaxen-1.2.0.jar:/opt/openfire/lib/jcip-annotations-1.0.jar:/opt/openfire/lib/jcl-over-slf4j-2.0.9.jar:/opt/openfire/lib/jetty-ee-12.0.24.jar:/opt/openfire/lib/jetty-ee8-annotations-12.0.24.jar:/opt/openfire/lib/jetty-ee8-apache-jsp-12.0.24.jar:/opt/openfire/lib/jetty-ee8-nested-12.0.24.jar:/opt/openfire/lib/jetty-ee8-plus-12.0.24.jar:/opt/openfire/lib/jetty-ee8-security-12.0.24.jar:/opt/openfire/lib/jetty-ee8-servlet-12.0.24.jar:/opt/openfire/lib/jetty-ee8-webapp-12.0.24.jar:/opt/openfire/lib/jetty-ee8-websocket-jetty-api-12.0.24.jar:/opt/openfire/lib/jetty-ee8-websocket-jetty-common-12.0.24.jar:/opt/openfire/lib/jetty-ee8-websocket-jetty-server-12.0.24.jar:/opt/openfire/lib/jetty-ee8-websocket-servlet-12.0.24.jar:/opt/openfire/lib/jetty-http-12.0.24.jar:/opt/openfire/lib/jetty-io-12.0.24.jar:/opt/openfire/lib/jetty-jmx-12.0.24.jar:/opt/openfire/lib/jetty-jndi-12.0.24.jar:/opt/openfire/lib/jetty-plus-12.0.24.jar:/opt/openfire/lib/jetty-security-12.0.24.jar:/opt/openfire/lib/jetty-server-12.0.24.jar:/opt/openfire/lib/jetty-servlet-api-4.0.6.jar:/opt/openfire/lib/jetty-session-12.0.24.jar:/opt/openfire/lib/jetty-util-12.0.24.jar:/opt/openfire/lib/jetty-websocket-core-common-12.0.24.jar:/opt/openfire/lib/jetty-websocket-core-server-12.0.24.jar:/opt/openfire/lib/jetty-xml-12.0.24.jar:/opt/openfire/lib/jmdns-1.0.jar:/opt/openfire/lib/jsmpp-2.3.10.jar:/opt/openfire/lib/json-20231013.jar:/opt/openfire/lib/jspecify-1.0.0.jar:/opt/openfire/lib/jsr305-3.0.2.jar:/opt/openfire/lib/jtds-1.3.1.jar:/opt/openfire/lib/jzlib-1.1.3.jar:/opt/openfire/lib/libidn-1.35.jar:/opt/openfire/lib/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar:/opt/openfire/lib/log4j-api-2.20.0.jar:/opt/openfire/lib/log4j-core-2.20.0.jar:/opt/openfire/lib/log4j-slf4j2-impl-2.20.0.jar:/opt/openfire/lib/mssql-jdbc-9.4.1.jre11.jar:/opt/openfire/lib/mysql-connector-j-8.2.0.jar:/opt/openfire/lib/netty-all-4.1.118.Final.jar:/opt/openfire/lib/netty-buffer-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-dns-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-haproxy-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-http2-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-http-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-memcache-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-mqtt-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-redis-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-smtp-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-socks-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-stomp-4.1.118.Final.jar:/opt/openfire/lib/netty-codec-xml-4.1.118.Final.jar:/opt/openfire/lib/netty-common-4.1.118.Final.jar:/opt/openfire/lib/netty-handler-4.1.118.Final.jar:/opt/openfire/lib/netty-handler-proxy-4.1.118.Final.jar:/opt/openfire/lib/netty-handler-ssl-ocsp-4.1.118.Final.jar:/opt/openfire/lib/netty-resolver-4.1.118.Final.jar:/opt/openfire/lib/netty-resolver-dns-4.1.118.Final.jar:/opt/openfire/lib/netty-resolver-dns-classes-macos-4.1.118.Final.jar:/opt/openfire/lib/netty-resolver-dns-native-macos-4.1.118.Final-osx-aarch_64.jar:/opt/openfire/lib/netty-resolver-dns-native-macos-4.1.118.Final-osx-x86_64.jar:/opt/openfire/lib/netty-transport-4.1.118.Final.jar:/opt/openfire/lib/netty-transport-classes-epoll-4.1.118.Final.jar:/opt/openfire/lib/netty-transport-classes-kqueue-4.1.118.Final.jar:/opt/openfire/lib/netty-transport-native-epoll-4.1.118.Final-linux-aarch_64.jar:/opt/openfire/lib/netty-transport-native-epoll-4.1.118.Final-linux-riscv64.jar:/opt/openfire/lib/netty-transport-native-epoll-4.1.118.Final-linux-x86_64.jar:/opt/openfire/lib/netty-transport-native-kqueue-4.1.118.Final-osx-aarch_64.jar:/opt/openfire/lib/netty-transport-native-kqueue-4.1.118.Final-osx-x86_64.jar:/opt/openfire/lib/netty-transport-native-unix-common-4.1.118.Final.jar:/opt/openfire/lib/netty-transport-rxtx-4.1.118.Final.jar:/opt/openfire/lib/netty-transport-sctp-4.1.118.Final.jar:/opt/openfire/lib/netty-transport-udt-4.1.118.Final.jar:/opt/openfire/lib/ojdbc11-23.7.0.25.01.jar:/opt/openfire/lib/ons-23.7.0.25.01.jar:/opt/openfire/lib/oraclepki-23.7.0.25.01.jar:/opt/openfire/lib/orai18n-23.7.0.25.01.jar:/opt/openfire/lib/postgresql-42.7.7.jar:/opt/openfire/lib/rsi-23.7.0.25.01.jar:/opt/openfire/lib/shaj-0.5.jar:/opt/openfire/lib/simplefan-23.7.0.25.01.jar:/opt/openfire/lib/sitemesh-2.5.0.jar:/opt/openfire/lib/slf4j-api-2.0.9.jar:/opt/openfire/lib/startup.jar:/opt/openfire/lib/taglibs-standard-impl-1.2.5.jar:/opt/openfire/lib/taglibs-standard-spec-1.2.5.jar:/opt/openfire/lib/tinder-2.1.0.jar:/opt/openfire/lib/txw2-2.3.3.jar:/opt/openfire/lib/ucp-23.7.0.25.01.jar:/opt/openfire/lib/xdb-23.7.0.25.01.jar:/opt/openfire/lib/xmppserver-5.0.2.jar:/opt/openfire/lib/xpp3-1.1.4c.0.jar Starting OpenFire... /opt/openfire/bin/start.sh: line 48: cd: $OPENFIRE_HOME: No such file or directory /opt/openfire/bin/start.sh: line 49: exec: $JAVA: not found [root@yfw system]# tail -f /opt/openfire/logs/nohup.out DEBUG: Current user: root DEBUG: Current dir: /opt/openfire DEBUG: Checking startup.jar... -rwxr-xr-x 1 openfire openfire 51542 Feb 1 1980 lib/startup.jar lib/startup.jar: Zip archive data, at least v1.0 to extract Error: LinkageError occurred while loading main class org.jivesoftware.openfire.starter.ServerStarter java.lang.UnsupportedClassVersionError: org/jivesoftware/openfire/starter/ServerStarter has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0 "Failed to run ServerStarter" Starting OpenFire正式启动... sh: line 0: exec: -s: invalid option exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]
11-16
sudo chmod +x /opt/openfire/bin/start.sh sudo chown -R openfire:openfire /opt/openfire /opt/openfire/bin/start.sh ``` --- ### ✅ 查看日志确认 Java 版本 ```bash tail -f /opt/openfire/logs/nohup.out ...
[root@yfw ~]# cd /opt/openfire [root@yfw openfire]# # 在 Linux 上执行： [root@yfw openfire]# openssl rand -base64 32 uEufYKuoXRnq3lrHq8BB/BG8qPzK5M0/FsYyNFf+zDo= [root@yfw openfire]# curl -X GET \ > -H "Authorization: Bearer uEufYKuoXRnq3lrHq8BB/BG8qPzK5M0/FsYyNFf+zDo=" \ > -H "Accept: application/json" \ > http://localhost:9090/plugins/restapi/v1/system/liveness [root@yfw openfire]# curl -X GET \ > -H "Authorization: Bearer uEufYKuoXRnq3lrHq8BB/BG8qPzK5M0/FsYyNFf+zDo=" \ > -H "Accept: application/json" \ > http://124.71.230.244:9090/plugins/restapi/v1/system/liveness [root@yfw openfire]#
10-03
你在 Openfire 后台设置了： ``` 允许的IP地址：127.0.0.1,124.71.230.244 ``` ⚠️ 注意： - 当你从服务器内部用 `curl http://124.71.230.244:9090/...` 请求时，来源 IP 是 `124.71.230.244` 自身 - Linux 的...
nohup: failed to run command ‘java’: No such file or directory
qq_31674229的博客
02-21 2697
nohup: failed to run command ‘java’: No such file or directory
nohup: failed to run command `python3‘: No such file or directory
weixin_41987117的博客
01-12 6522
nohup: failed to run command `python3’: No such file or directory 我的 python 是用别名设置的，可以直接使用，但是加上 nohup 就会报错，这个时候使用绝对路径引用 python 就好了。
nohup: failed to run command ‘java’: No such file or directory报错解决
weixin_53389944的博客
12-27 1957
如果Java的可执行文件目录没有在PATH中，您可以编辑系统的环境变量配置文件（例如.bashrc，.bash_profile等）并添加Java的安装路径到PATH变量中。您可以通过在终端中运行"java -version"命令来检查Java的安装情况。如果系统中没有安装Java，请安装Java运行时环境（JRE）或Java开发工具包（JDK）。的命令或可执行文件。这可能是因为Java环境变量没有正确设置或Java并没有安装在系统中。环境变量复制在我的Shell脚本中去，再去执行，问题就解决了。
nohup: failed to run command `java': No such file or directory解决
热门推荐
小末的博客
12-29 7万+
  程序里远程执行shell命令（nohup java -jar ...）的执行，后台日志报错如下： nohup: failed to run command `java': No such file or directory 原因：一般来说这个报错说明服务器执行不了"java"这个命令 解决： 1、检查执行该shell的服务器有没有装jdk 2、检查执行该shell的服务器的环境变...
failed to run command ‘java’: No such file or directory
Yann
10-31 4615
今天启动项目的时候遇到一个问题，使用shell脚本启动Java的jar项目，一直提示“‘java’: No such file or directory”，遇到这个提示，第一个想到的是jdk环境配置问题，可以jdk环境一直没有动。3.直接使用java -jar启动项目，可以正常启动，但是写入shell脚本中，一样报错，无法找到java命令。1.使用“java -version”查看jdk版本信息时，输出正确的版本号；2.使用java命令的根目录替代shell文件中的java命令，成功启动项目。
linux 启动 jar 提示 nohup: failed to run command ‘java‘: No such file or directory
liman1002的专栏
11-10 4230
在linux 启动jar包出现该提示 场景： 服务器主机由A栋楼 转移到B栋楼，IP发生改变，服务器内容无任何变化 启动服务提示nohup: failed to run command 'java': No such file or directory 解决方案： 1、查看jdk版本 java -version 2、echo $JAVA_HOME 查看安装目录 3、执行启动jar nohup 上一步结果/bin/java -jar XX.jar ...
Linux上启动项目报错:nohup: failed to run command `java‘: No such file or directory
weixin_43401380的博客
12-01 7093
    一直使用nohup java -jar XXX.jar &启动项目,但是今天控制台报错:nohup: failed to run command `java’: No such file or directory.在此记录一下.     出现此问题的原因一般是:jdk安装问题,主要看一下环境变量配置;具体到我这边的情况来看,配置文件没有改动过,不会是配置问题; 解决方案:    &n
nohup: failed to run command ‘java‘: No such file or directory
bug程序猿的博客
12-15 2308
Linux jar包后台启动是时候报nohup: failed to run command 'java': No such file or directory， 解决办法： 1、检查执行该shell的服务器有没有装jdk 2、检查执行该shell的服务器的环境变量有没有将JAVA_HOME/bin加入（目的是可以在linux任意位置执行java命令） 3、先执行：source /etc/profile然后执行：nohup java -jar ... 4、我的执行命令是：sudo nohup j.
评论 4
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

newjueqi

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值