Plugin Error: Flutter threw an uncaught NoClassDefFoundError. Disable Plugin

最新推荐文章于 2024-07-04 20:18:37 发布
原创 最新推荐文章于 2024-07-04 20:18:37 发布 · 833 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文解决了一个在安装Flutter过程中遇到的问题，即Flutter版本3.0与环境不兼容的情况。通过升级Android Studio到版本3.4，可以有效解决此问题，使Flutter开发环境正常运行。

安装Flutter过程中可能会有这个问题。显示Flutter中显示3.0已经可以，但是却不行。可以升级AndoridStudio到3.4就可以啦。。
更新步骤可参考
Flutter安装配置详解

4.5 Jmeter5.3监控Linux资源报错:Uncaught Exception java.lang.NoSuchMethodError: org.apache.jmeter.samplers.
fen_fen的专栏
09-08 3888
Jmeter5.3监控Linux资源报错:Uncaught Exception java.lang.NoSuchMethodError: org.apache.jmeter.samplers. 原因： setFormatter function exists in Jmeter 3.1 and not in Jmeter 3.2 。Work with Jmeter 3.1 until a fix will be done to PerfMon plugin Jmeter 3.1版本之后暂时没有s.
Unable to load extension: pydevd_plugins.extensions.types.pydevd_plugin_pandas_types 解决方案
热门推荐
weixin_43178406的博客
11-17 9万+
本文主要介绍了在运行jupyter notebook时报错Unable to load extension: pydevd_plugins.extensions.types.pydevd_plugin_pandas_types解决方案，希望能对新手有所帮助。 文章目录 1. 问题描述 2. 解决方案
PluginApplicationException: Failed to apply plugin class ‘FlutterPlugin‘.
qq_32852047的博客
05-01 2231
Caused by: org.gradle.api.internal.plugins.PluginApplicationException: Failed to apply plugin class 'FlutterPlugin'. Caused by: org.gradle.api.internal.tasks.DefaultTaskContainer$DuplicateTaskException: Cannot add task 'generateLockfiles' as a task with t
Flutter采坑系列之：Failed to apply plugin class ‘FlutterPlugin‘.
步行者
05-23 2324
最近由于又想重新研究下Flutter相关技能，由于android studio升级到了最新版，创建项目默认使用 id 'com.android.library' version '7.2.0' apply false module依赖参照官方文档进行: // Include the host app project. include ':app' // assumed existing content setBinding(new Bin
Android导入Flutter Module报错Failed to apply plugin class ‘FlutterPlugin’.
bi3220628的博客
12-01 3176
Android导入Flutter Module报错Failed to apply plugin class ‘FlutterPlugin’. 最近将Flutter版本升级到2.5.3后发现一个问题，在Android项目中import或new一个Flutter module会提示错误： Caused by: org.gradle.api.InvalidUserCodeException: Build was configured to prefer settings repositories over pro
flutter开发 android工程报错Failed to apply plugin class ‘FlutterPlugin‘
gw6601的博客
06-01 2341
settings.gradle里配置了FAIL_ON_PROJECT_REPOS,而Flutter插件又单独设置了repository，所以会构建报错，因此需要把FAIL_ON_PROJECT_REPOS改成PREFER_PROJECT。表示如果工程单独设置了仓库，就优先使用工程配置的，忽略settings里面的。表示如果工程单独设置了仓库，或工程的插件设置了仓库，构建就直接报错抛出异常。表述任何通过工程单独设置或插件设置的仓库，都会被忽略。最后sync now一下。
Flutter实战-flutter混合开发报错：Failed to apply plugin [class ‘FlutterPlugin‘]
分享+记录
09-26 6879
也忘了之前改过什么了，前几天有个朋友给我留言说flutterMix的工程github的链接打不开。我才想起来前些时间为了应付公司信息安全部门的要求，把我很多项目都给删掉了，如果想恢复只能重新创建上传。 本地flutter项目重新搭起来，报这个错误。百度谷歌了下，没有找到答案，好吧，只能靠自己了。 报错如下： Project evaluation failed including an er......
小白转flink技术栈心得之混编java和scala报错：error: java.lang.NoClassDefFoundError: javax/tools/ToolProvider
cankan6204的博客
07-10 3966
今天刚接手了一个flink项目，代码里有java也有scala写的部分，小白第一次遇到要java和scala都需编译的项目，于是乎先进行scala的编译： mvn clean scala:compile compile package -Pfat -DskipTests 结果报了一个错误: [ERROR] error: java.lang.NoClassDefFoundError: javax/tools/ToolProvider [ERROR] Failed to execute goal net.
报错解决：ERROR: While executing gem ... (Gem::CommandLineError)
个人博客
01-09 1万+
在使用GitHub Pages博客-- Jekyll后，GitHub发了一个警告给我： We found a vulnerable dependency in a repository you have security alert access to. @zhang0peter zhang0peter/zhang0peter.github.io Known moderate severity ...
[Error] [carb.gym.plugin] Gym cuda error: invalid resource handle/an illegal memory access was encou
shuia64649495的博客
07-04 1937
gym.simulate(sim)前，未将环境变量初始化，前加即可。
Android导入Flutter Module报错Failed to apply plugin class ‘FlutterPlugin’
Within的博客
10-19 1282
Android导入Flutter Module报错Failed to apply plugin class ‘FlutterPlugin’.到这里这个报错问题应该已经解决了，这个应该是flutter的一个bug，希望之后的版本可以解决掉这个问题。这个错误在我这里是必现的，所以在此记录一下解决方法，希望能够帮助遇到同样问题的同学。打开Android project的build.gradle增加如下设置。打开Android project的settings.gradle修改。
Android导入Flutter Module报错Failed to apply plugin class ‘FlutterPlugin
GGGL的专栏
05-29 1622
打开Android project的settings.gradle修改repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)为。到这里这个报错问题应该已经解决了，这个应该是flutter的一个bug，希望之后的版本可以解决掉这个问题。这个错误在我这里是必现的，所以在此记录一下解决方法，希望能够帮助遇到同样问题的同学。打开Android project的build.gradle增加如下设置。
‘disable_plugins‘ 不是内部或外部命令，也不是可运行的程序 或批处理文件。
二十一克阳光！的博客
03-07 744
【代码】‘disable_plugins‘ 不是内部或外部命令，也不是可运行的程序 或批处理文件。
Flutter 莫名其妙系列 -- 混合开发集成Flutter出现Failed to apply plugin class ‘FlutterPlugin‘
qq_34694261的博客
03-08 4157
Flutter 莫名其妙系列 -- 混合开发集成Flutter出现Failed to apply plugin class 'FlutterPlugin'
【android集成flutter报错：Failed to apply plugin class ‘FlutterPlugin‘】
Alpaca_exo的博客
12-13 1077
android集成flutter报错：Failed to apply plugin class 'FlutterPlugin'
Android Studio 把 kotlin 从插件disable禁用,启动不了恢复办法
j564712400的专栏
06-14 1459
E:\AndroidToolsSetup\.AndroidStudio3.5.4\config找到disabled_plugins.txt文件。
Flutter填坑：Plugin flutter is incompatible with this installation
100斤的博客
06-08 2796
Flutter是谷歌的移动UI框架，可以快速在iOS和Android上构建高质量的原生用户界面。 想尝尝鲜，却被环境卡了一下。 安装flutter插件时报错： Plugin flutter is incompatible with this installation 解决很简单。升级Android Studio. 以上。...
Flutter报错RenderBox was not laid out: RenderRepaintBoundary的解决方法
江上清风山间明月的博客
10-26 4583
因为当使用Column时，它会尝试处于屏幕高度，而当在内部使用Expanded时，该列会将剩余空间分配给扩展小部件的子级，现在，如果你使用SingleChildScrollView，它会尽可能长时间地扩展（按方向，一般时垂直方向），但当你使用Expanded时，它会试图占用剩余空间，所以它会无限大，从而引发错误，如果你在Column中使用Expanded，而这个Column具有父级SingleChildScrollView就报这个错误。
Android studio安装Database Navigator插件出现错误Plugin DBN failed to initialize and will be disabled
qq_45192089的博客
06-10 5634
Plugin 'DBN' failed to initialize and will be disabled. Please restart Android Studio. com.intellij.openapi.extensions.impl.PicoPluginExtensionInitializationException: Duplicate registration for EP: com.intellij.externalSystemManager: original plugin com
[root@yfw ~]# cd /etc/systemd/system [root@yfw system]# sudo nano /etc/systemd/system/wp-im-server.service [root@yfw system]# # 重载配置（必须） [root@yfw system]# systemctl daemon-reload [root@yfw system]# [root@yfw system]# # 停止旧进程 [root@yfw system]# systemctl stop wp-im-server [root@yfw system]# [root@yfw system]# # 清除失败状态 [root@yfw system]# systemctl reset-failed wp-im-server Failed to reset failed state of unit wp-im-server.service: Unit wp-im-server.service not loaded. [root@yfw system]# [root@yfw system]# # 启动新服务 [root@yfw system]# systemctl start wp-im-server [root@yfw system]# [root@yfw system]# # 查看实时日志 [root@yfw system]# journalctl -u wp-im-server -f -- Logs begin at Wed 2025-11-12 20:13:15 CST. -- Nov 13 17:33:12 yfw.szrengjing.com php[398340]: #0 {main} Nov 13 17:33:12 yfw.szrengjing.com php[398340]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:12 yfw.szrengjing.com php[398340]: Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:12 yfw.szrengjing.com php[398340]: Stack trace: Nov 13 17:33:12 yfw.szrengjing.com php[398340]: #0 {main} Nov 13 17:33:12 yfw.szrengjing.com php[398340]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:12 yfw.szrengjing.com systemd[1]: wp-im-server.service: Main process exited, code=exited, status=255/n/a Nov 13 17:33:12 yfw.szrengjing.com systemd[1]: wp-im-server.service: Failed with result 'exit-code'. Nov 13 17:33:12 yfw.szrengjing.com systemd[1]: Stopped WordPress IM Server (Workerman). Nov 13 17:33:12 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). Nov 13 17:33:12 yfw.szrengjing.com php[398370]: PHP Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:12 yfw.szrengjing.com php[398370]: Stack trace: Nov 13 17:33:12 yfw.szrengjing.com php[398370]: #0 {main} Nov 13 17:33:12 yfw.szrengjing.com php[398370]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:12 yfw.szrengjing.com php[398370]: Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:12 yfw.szrengjing.com php[398370]: Stack trace: Nov 13 17:33:12 yfw.szrengjing.com php[398370]: #0 {main} Nov 13 17:33:12 yfw.szrengjing.com php[398370]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:12 yfw.szrengjing.com systemd[1]: wp-im-server.service: Main process exited, code=exited, status=255/n/a Nov 13 17:33:12 yfw.szrengjing.com systemd[1]: wp-im-server.service: Failed with result 'exit-code'. Nov 13 17:33:16 yfw.szrengjing.com systemd[1]: wp-im-server.service: Service RestartSec=3s expired, scheduling restart. Nov 13 17:33:16 yfw.szrengjing.com systemd[1]: wp-im-server.service: Scheduled restart job, restart counter is at 1. Nov 13 17:33:16 yfw.szrengjing.com systemd[1]: Stopped WordPress IM Server (Workerman). Nov 13 17:33:16 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). Nov 13 17:33:16 yfw.szrengjing.com php[398375]: PHP Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:16 yfw.szrengjing.com php[398375]: Stack trace: Nov 13 17:33:16 yfw.szrengjing.com php[398375]: #0 {main} Nov 13 17:33:16 yfw.szrengjing.com php[398375]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:16 yfw.szrengjing.com php[398375]: Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:16 yfw.szrengjing.com php[398375]: Stack trace: Nov 13 17:33:16 yfw.szrengjing.com php[398375]: #0 {main} Nov 13 17:33:16 yfw.szrengjing.com php[398375]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:16 yfw.szrengjing.com systemd[1]: wp-im-server.service: Main process exited, code=exited, status=255/n/a Nov 13 17:33:16 yfw.szrengjing.com systemd[1]: wp-im-server.service: Failed with result 'exit-code'. Nov 13 17:33:19 yfw.szrengjing.com systemd[1]: wp-im-server.service: Service RestartSec=3s expired, scheduling restart. Nov 13 17:33:19 yfw.szrengjing.com systemd[1]: wp-im-server.service: Scheduled restart job, restart counter is at 2. Nov 13 17:33:19 yfw.szrengjing.com systemd[1]: Stopped WordPress IM Server (Workerman). Nov 13 17:33:19 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). Nov 13 17:33:19 yfw.szrengjing.com php[398395]: PHP Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:19 yfw.szrengjing.com php[398395]: Stack trace: Nov 13 17:33:19 yfw.szrengjing.com php[398395]: #0 {main} Nov 13 17:33:19 yfw.szrengjing.com php[398395]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:19 yfw.szrengjing.com php[398395]: Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:19 yfw.szrengjing.com php[398395]: Stack trace: Nov 13 17:33:19 yfw.szrengjing.com php[398395]: #0 {main} Nov 13 17:33:19 yfw.szrengjing.com php[398395]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:19 yfw.szrengjing.com systemd[1]: wp-im-server.service: Main process exited, code=exited, status=255/n/a Nov 13 17:33:19 yfw.szrengjing.com systemd[1]: wp-im-server.service: Failed with result 'exit-code'. Nov 13 17:33:22 yfw.szrengjing.com systemd[1]: wp-im-server.service: Service RestartSec=3s expired, scheduling restart. Nov 13 17:33:22 yfw.szrengjing.com systemd[1]: wp-im-server.service: Scheduled restart job, restart counter is at 3. Nov 13 17:33:22 yfw.szrengjing.com systemd[1]: Stopped WordPress IM Server (Workerman). Nov 13 17:33:22 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). Nov 13 17:33:22 yfw.szrengjing.com php[398399]: PHP Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:22 yfw.szrengjing.com php[398399]: Stack trace: Nov 13 17:33:22 yfw.szrengjing.com php[398399]: #0 {main} Nov 13 17:33:22 yfw.szrengjing.com php[398399]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:22 yfw.szrengjing.com php[398399]: Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:22 yfw.szrengjing.com php[398399]: Stack trace: Nov 13 17:33:22 yfw.szrengjing.com php[398399]: #0 {main} Nov 13 17:33:22 yfw.szrengjing.com php[398399]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:22 yfw.szrengjing.com systemd[1]: wp-im-server.service: Main process exited, code=exited, status=255/n/a Nov 13 17:33:22 yfw.szrengjing.com systemd[1]: wp-im-server.service: Failed with result 'exit-code'. Nov 13 17:33:25 yfw.szrengjing.com systemd[1]: wp-im-server.service: Service RestartSec=3s expired, scheduling restart. Nov 13 17:33:25 yfw.szrengjing.com systemd[1]: wp-im-server.service: Scheduled restart job, restart counter is at 4. Nov 13 17:33:25 yfw.szrengjing.com systemd[1]: Stopped WordPress IM Server (Workerman). Nov 13 17:33:25 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). Nov 13 17:33:25 yfw.szrengjing.com php[398403]: PHP Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:25 yfw.szrengjing.com php[398403]: Stack trace: Nov 13 17:33:25 yfw.szrengjing.com php[398403]: #0 {main} Nov 13 17:33:25 yfw.szrengjing.com php[398403]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:25 yfw.szrengjing.com php[398403]: Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:25 yfw.szrengjing.com php[398403]: Stack trace: Nov 13 17:33:25 yfw.szrengjing.com php[398403]: #0 {main} Nov 13 17:33:25 yfw.szrengjing.com php[398403]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:25 yfw.szrengjing.com systemd[1]: wp-im-server.service: Main process exited, code=exited, status=255/n/a Nov 13 17:33:25 yfw.szrengjing.com systemd[1]: wp-im-server.service: Failed with result 'exit-code'. Nov 13 17:33:29 yfw.szrengjing.com systemd[1]: wp-im-server.service: Service RestartSec=3s expired, scheduling restart. Nov 13 17:33:29 yfw.szrengjing.com systemd[1]: wp-im-server.service: Scheduled restart job, restart counter is at 5. Nov 13 17:33:29 yfw.szrengjing.com systemd[1]: Stopped WordPress IM Server (Workerman). Nov 13 17:33:29 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). Nov 13 17:33:29 yfw.szrengjing.com php[398405]: PHP Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:29 yfw.szrengjing.com php[398405]: Stack trace: Nov 13 17:33:29 yfw.szrengjing.com php[398405]: #0 {main} Nov 13 17:33:29 yfw.szrengjing.com php[398405]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:29 yfw.szrengjing.com php[398405]: Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:29 yfw.szrengjing.com php[398405]: Stack trace: Nov 13 17:33:29 yfw.szrengjing.com php[398405]: #0 {main} Nov 13 17:33:29 yfw.szrengjing.com php[398405]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:29 yfw.szrengjing.com systemd[1]: wp-im-server.service: Main process exited, code=exited, status=255/n/a Nov 13 17:33:29 yfw.szrengjing.com systemd[1]: wp-im-server.service: Failed with result 'exit-code'. Nov 13 17:33:32 yfw.szrengjing.com systemd[1]: wp-im-server.service: Service RestartSec=3s expired, scheduling restart. Nov 13 17:33:32 yfw.szrengjing.com systemd[1]: wp-im-server.service: Scheduled restart job, restart counter is at 6. Nov 13 17:33:32 yfw.szrengjing.com systemd[1]: Stopped WordPress IM Server (Workerman). Nov 13 17:33:32 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). Nov 13 17:33:32 yfw.szrengjing.com php[398409]: PHP Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:32 yfw.szrengjing.com php[398409]: Stack trace: Nov 13 17:33:32 yfw.szrengjing.com php[398409]: #0 {main} Nov 13 17:33:32 yfw.szrengjing.com php[398409]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:32 yfw.szrengjing.com php[398409]: Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:32 yfw.szrengjing.com php[398409]: Stack trace: Nov 13 17:33:32 yfw.szrengjing.com php[398409]: #0 {main} Nov 13 17:33:32 yfw.szrengjing.com php[398409]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:32 yfw.szrengjing.com systemd[1]: wp-im-server.service: Main process exited, code=exited, status=255/n/a Nov 13 17:33:32 yfw.szrengjing.com systemd[1]: wp-im-server.service: Failed with result 'exit-code'. Nov 13 17:33:35 yfw.szrengjing.com systemd[1]: wp-im-server.service: Service RestartSec=3s expired, scheduling restart. Nov 13 17:33:35 yfw.szrengjing.com systemd[1]: wp-im-server.service: Scheduled restart job, restart counter is at 7. Nov 13 17:33:35 yfw.szrengjing.com systemd[1]: Stopped WordPress IM Server (Workerman). Nov 13 17:33:35 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). Nov 13 17:33:35 yfw.szrengjing.com php[398411]: PHP Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:35 yfw.szrengjing.com php[398411]: Stack trace: Nov 13 17:33:35 yfw.szrengjing.com php[398411]: #0 {main} Nov 13 17:33:35 yfw.szrengjing.com php[398411]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:35 yfw.szrengjing.com php[398411]: Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:35 yfw.szrengjing.com php[398411]: Stack trace: Nov 13 17:33:35 yfw.szrengjing.com php[398411]: #0 {main} Nov 13 17:33:35 yfw.szrengjing.com php[398411]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:35 yfw.szrengjing.com systemd[1]: wp-im-server.service: Main process exited, code=exited, status=255/n/a Nov 13 17:33:35 yfw.szrengjing.com systemd[1]: wp-im-server.service: Failed with result 'exit-code'. Nov 13 17:33:38 yfw.szrengjing.com systemd[1]: wp-im-server.service: Service RestartSec=3s expired, scheduling restart. Nov 13 17:33:38 yfw.szrengjing.com systemd[1]: wp-im-server.service: Scheduled restart job, restart counter is at 8. Nov 13 17:33:38 yfw.szrengjing.com systemd[1]: Stopped WordPress IM Server (Workerman). Nov 13 17:33:38 yfw.szrengjing.com systemd[1]: Started WordPress IM Server (Workerman). Nov 13 17:33:38 yfw.szrengjing.com php[398415]: PHP Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:38 yfw.szrengjing.com php[398415]: Stack trace: Nov 13 17:33:38 yfw.szrengjing.com php[398415]: #0 {main} Nov 13 17:33:38 yfw.szrengjing.com php[398415]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:38 yfw.szrengjing.com php[398415]: Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php:9 Nov 13 17:33:38 yfw.szrengjing.com php[398415]: Stack trace: Nov 13 17:33:38 yfw.szrengjing.com php[398415]: #0 {main} Nov 13 17:33:38 yfw.szrengjing.com php[398415]: thrown in /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php on line 9 Nov 13 17:33:38 yfw.szrengjing.com systemd[1]: wp-im-server.service: Main process exited, code=exited, status=255/n/a Nov 13 17:33:38 yfw.szrengjing.com systemd[1]: wp-im-server.service: Failed with result 'exit-code'. Nov 13 17:33:42 yfw.szrengjing.com systemd[1]: wp-im-se
最新发布
11-14
你已经走到最后一步了，而且我们有明确的证据： ✅ 手动执行： ```bash /www/server/php/74/bin/php -c /www/server/php/74/etc/php-cli.ini -r "require 'vendor/autoload.php'; var_dump(class_exists('Workerman\\Worker'));" ``` 返回 `bool(true)` → **说明环境、依赖、路径都没问题！** ❌ 但 systemd 启动仍然报错： ``` PHP Fatal error: Uncaught Error: Class 'Workerman\Worker' not found in im-server.php on line 9 ``` --- ## 🔥 最终结论：**`nano` 没有保存 service 文件！** 你在运行 `sudo nano /etc/systemd/system/wp-im-server.service` 后，可能： - 修改了内容 ✅ - 但没有真正保存 ❌（忘记按 `Ctrl+O` 写入，或没确认文件名） 所以 `systemctl daemon-reload` 加载的还是旧的 `.service` 文件！ --- ## ✅ 紧急验证：检查当前 service 文件内容 运行以下命令查看实际文件内容： ```bash cat /etc/systemd/system/wp-im-server.service ``` 你应该看到类似输出。请确认是否包含这些关键行： ```ini WorkingDirectory=/www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin ExecStart=/www/server/php/74/bin/php -c /www/server/php/74/etc/php-cli.ini /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php ``` ### ❌ 如果没有 → 说明你之前用 `nano` 修改后未保存！ --- ## ✅ 正确操作：强制写入 service 文件 ### 方法一：使用 `tee` 直接覆盖（推荐） ```bash cat > /tmp/wp-im-server.service << 'EOF' [Unit] Description=WordPress IM Server (Workerman) After=network.target [Service] Type=simple User=www Group=www WorkingDirectory=/www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin ExecStart=/www/server/php/74/bin/php -c /www/server/php/74/etc/php-cli.ini /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php ExecStop=/www/server/php/74/bin/php -c /www/server/php/74/etc/php-cli.ini /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin/im-server.php stop Restart=always RestartSec=3 StandardOutput=journal StandardError=journal Environment=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin [Install] WantedBy=multi-user.target EOF # 复制到 systemd 目录并设置权限 sudo cp /tmp/wp-im-server.service /etc/systemd/system/wp-im-server.service sudo chmod 644 /etc/systemd/system/wp-im-server.service ``` --- ## ✅ 重新加载并启动服务 ```bash # 重载配置 sudo systemctl daemon-reload # 停止旧服务 sudo systemctl stop wp-im-server # 清除失败状态（现在应该可以） sudo systemctl reset-failed wp-im-server # 启动新服务 sudo systemctl start wp-im-server # 查看日志 sudo journalctl -u wp-im-server -f ``` --- ## ✅ 成功标志 你会看到： ``` Started WordPress IM Server (Workerman) Press Ctrl+C to stop. Workerman[start]: worker start success. ``` 并且不会再出现 `Class 'Workerman\Worker' not found` --- ## ✅ 额外保护：为 PHP 脚本添加自动调试日志 在 `im-server.php` 开头加入： ```php file_put_contents('/tmp/workerman_boot.log', "[" . date('Y-m-d H:i:s') . "] Booting...\n" . "CWD: " . getcwd() . "\n" . "__DIR__: " . __DIR__ . "\n" . "Autoload exists: " . (file_exists(__DIR__ . '/vendor/autoload.php') ? 'YES' : 'NO') . "\n", FILE_APPEND); require_once __DIR__ . '/vendor/autoload.php'; ``` 然后查看： ```bash cat /tmp/workerman_boot.log ``` 如果显示： ``` CWD: /www/wwwroot/yfw_szrengjing_com/wp-content/plugins/wp-im-plugin Autoload exists: YES ``` → 完全正确！ --- ## ✅ 总结：为什么之前失败？ | 原因 | 说明 | |------|------| | ❌ `nano` 修改未保存 | 这是最常见的“以为改了其实没改”错误 | | 🔄 `daemon-reload` 只重载磁盘文件 | 不会读取编辑器缓存，必须真实写入文件 | | 📂 路径依赖 `__DIR__` | 必须通过 `WorkingDirectory` 保证上下文一致 | ---
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值