当前位置: 首页 > news >正文

连接一个新的服务器时,打开PyCharm时报错:报错内容是服务器磁盘或配额满了

连接一个新的服务器时,打开PyCharm时报错:报错内容是服务器磁盘或配额满了

2025-11-11 22:05:52,703 INFO uname -sm stdout: Linux x86_64 2025-11-11 22:05:52,828 INFO echo $SHELL stdout: /bin/bash 2025-11-11 22:05:52,955 INFO uname -sm stdout: Linux x86_64 2025-11-11 22:05:53,070 INFO echo $SHELL stdout: /bin/bash 2025-11-11 22:05:53,190 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ echo\ \$HOME stdout: REMOTE_EXEC_OUTPUT_MARKER_ /root 2025-11-11 22:05:53,307 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ echo\ \$XDG_CACHE_HOME stdout: REMOTE_EXEC_OUTPUT_MARKER_ 2025-11-11 22:05:53,417 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ test\ -f\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64 stdout: REMOTE_EXEC_OUTPUT_MARKER_ 2025-11-11 22:05:53,528 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ test\ -x\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64 stdout: REMOTE_EXEC_OUTPUT_MARKER_ 2025-11-11 22:05:53,653 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ get-path\ --path=cache stdout: REMOTE_EXEC_OUTPUT_MARKER_ /root/.cache/JetBrains 2025-11-11 22:05:53,775 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ get-path\ --path=config stdout: REMOTE_EXEC_OUTPUT_MARKER_ /root/.config/JetBrains 2025-11-11 22:05:53,883 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ exists\ --path=/root/.cache/JetBrains stdout: REMOTE_EXEC_OUTPUT_MARKER_ true 2025-11-11 22:05:53,992 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ exists\ --path=/root/.config/JetBrains stdout: REMOTE_EXEC_OUTPUT_MARKER_ true 2025-11-11 22:05:54,101 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ lock-support stdout: REMOTE_EXEC_OUTPUT_MARKER_ 2025-11-11 22:05:54,214 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ available-memory stdout: REMOTE_EXEC_OUTPUT_MARKER_ 263686132 2025-11-11 22:05:54,336 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ cpu-count stdout: REMOTE_EXEC_OUTPUT_MARKER_ 128 2025-11-11 22:05:54,448 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ port-forwarding-test stdout: REMOTE_EXEC_OUTPUT_MARKER_ 36145 2025-11-11 22:05:54,621 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ readlink\ --path=/workspace/lcc/DeepSeek-OCR-main stdout: REMOTE_EXEC_OUTPUT_MARKER_ /workspace/lcc/DeepSeek-OCR-main 2025-11-11 22:05:54,739 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ get-path\ --path=cache stdout: REMOTE_EXEC_OUTPUT_MARKER_ /root/.cache/JetBrains 2025-11-11 22:05:54,849 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ get-path\ --path=config stdout: REMOTE_EXEC_OUTPUT_MARKER_ /root/.config/JetBrains 2025-11-11 22:05:54,958 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ exists\ --path=/root/.cache/JetBrains stdout: REMOTE_EXEC_OUTPUT_MARKER_ true 2025-11-11 22:05:55,066 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ exists\ --path=/root/.config/JetBrains stdout: REMOTE_EXEC_OUTPUT_MARKER_ true 2025-11-11 22:05:55,175 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ get-path\ --path=cache stdout: REMOTE_EXEC_OUTPUT_MARKER_ /root/.cache/JetBrains 2025-11-11 22:05:55,283 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ get-path\ --path=config stdout: REMOTE_EXEC_OUTPUT_MARKER_ /root/.config/JetBrains 2025-11-11 22:05:55,395 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ available-space\ --path=/root/.cache/JetBrains stdout: REMOTE_EXEC_OUTPUT_MARKER_ 0 2025-11-11 22:05:55,503 INFO /bin/bash -lc echo\ REMOTE_EXEC_OUTPUT_MARKER_\ \&\&\ /root/.cache/JetBrains/RemoteDev/remote-dev-worker/remote-dev-worker_83eb3f8153ed29f38ae607b0a82d4ed8470bcd5f8f346034c4e370bb06d9dd64\ available-space\ --path=/root/.config/JetBrains stdout: REMOTE_EXEC_OUTPUT_MARKER_ 0 ==== FAILURES ==== The following exception failed the deployment com.jetbrains.gateway.ssh.deploy.DeployException: 0.5GB of free space is necessary to run the IDE. Make sure that there's enough space in following paths:<ul><li><code>/root/.cache/JetBrains</code></li><li><code>/root/.config/JetBrains</code></li></ul> at com.jetbrains.gateway.ssh.DeployFlowUtil$fullDeployCycleImpl$2.invokeSuspend(DeployFlowUtil.kt:303) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at com.intellij.openapi.rd.util.CoroutineProgressContext$Companion$create$task$1$3.invokeSuspend(BackgroundProgressCoroutineUtil.kt:174) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:280) at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:85) at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59) at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source) at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38) at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source) at com.intellij.openapi.rd.util.CoroutineProgressContext$Companion$create$task$1.invoke(BackgroundProgressCoroutineUtil.kt:170) at com.intellij.openapi.rd.util.CoroutineProgressContext$Companion$create$task$1.invoke(BackgroundProgressCoroutineUtil.kt:160) at com.intellij.openapi.rd.util.CoroutineProgressContext$Companion$createModal$1$1.run(BackgroundProgressCoroutineUtil.kt:205) at com.intellij.openapi.progress.impl.CoreProgressManager.startTask(CoreProgressManager.java:428) at com.intellij.openapi.progress.impl.ProgressManagerImpl.startTask(ProgressManagerImpl.java:115) at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressSynchronously$9(CoreProgressManager.java:512) at com.intellij.openapi.progress.impl.ProgressRunner.lambda$new$0(ProgressRunner.java:87) at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:251) at com.intellij.openapi.progress.ProgressManager.lambda$runProcess$0(ProgressManager.java:71) at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:186) at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$13(CoreProgressManager.java:604) at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:679) at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:635) at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:603) at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:61) at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:173) at com.intellij.openapi.progress.ProgressManager.runProcess(ProgressManager.java:71) at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$5(ProgressRunner.java:251) at com.intellij.openapi.progress.impl.ProgressRunner.lambda$launchTask$18(ProgressRunner.java:465) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702) at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699) at java.base/java.security.AccessController.doPrivileged(AccessController.java:399) at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699) at java.base/java.lang.Thread.run(Thread.java:840) Caused by: com.jetbrains.gateway.ssh.deploy.DeployException: 0.5GB of free space is necessary to run the IDE. Make sure that there's enough space in following paths:<ul><li><code>/root/.cache/JetBrains</code></li><li><code>/root/.config/JetBrains</code></li></ul> at com.jetbrains.gateway.ssh.SshDeployFlowUtil.checkAvailableSpace(SshDeployFlowUtil.kt:156) at com.jetbrains.gateway.ssh.SshDeployFlowUtil$checkAvailableSpace$1.invokeSuspend(SshDeployFlowUtil.kt) ... 37 more

🧭 问题本质

JetBrains Gateway 在连接远程服务器时,会自动在远程机器的 /root/.cache/JetBrains/root/.config/JetBrains 下安装一个远程 worker,用于运行 IntelliJ 的后台逻辑。
但现在磁盘或配额满了,所以部署失败。

查看磁盘使用情况

df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay         1.8T  1.7T     0 100% /
tmpfs            64M     0   64M   0% /dev
tmpfs           126G     0  126G   0% /sys/fs/cgroup
shm             6.3G     0  6.3G   0% /dev/shm
/dev/sdb1        15T  3.6T   11T  26% /workspace
/dev/sda2       1.8T  1.7T     0 100% /etc/hosts
tmpfs           126G   12K  126G   1% /proc/driver/nvidia
tmpfs            26G  4.4M   26G   1% /run/nvidia-persistenced/socket
tmpfs           126G     0  126G   0% /proc/acpi
tmpfs           126G     0  126G   0% /proc/scsi
tmpfs           126G     0  126G   0% /sys/firmware
tmpfs           126G     0  126G   0% /sys/devices/virtual/powercap

关键是这一行:

overlay 1.8T 1.8T 0 100% /

👉 根目录 / 已经被完全占满(Avail=0),这就是 JetBrains 报错的根源。

而且:

/dev/sdb1 15T 3.6T 11T 26% /workspace

👉 /workspace 挂载在另一个磁盘上,有 11T 可用空间。这很好,我们可以把 JetBrains 的缓存、配置目录迁移到这里。

我们让 JetBrains 的缓存目录放在 /workspace 下,而不是 /root
执行以下命令一步步来 👇

1️⃣ 创建新的缓存和配置路径
mkdir -p /workspace/jetbrains_cache /workspace/jetbrains_config /workspace/jetbrains_remote_ide
chmod -R 777 /workspace/jetbrains_cache /workspace/jetbrains_config /workspace/jetbrains_remote_ide
2️⃣ 设置环境变量
# 2. 创建全局环境变量配置文件(JetBrains Gateway 会读取)
cat << 'EOF' > /etc/profile.d/jetbrains_env.sh
export XDG_CACHE_HOME=/workspace/jetbrains_cache
export XDG_CONFIG_HOME=/workspace/jetbrains_config
export JETBRAINS_REMOTE_DEV_DIR=/workspace/jetbrains_remote_ide
EOF

然后让配置立即生效:

# 3. 让环境变量立即生效
source /etc/profile.d/jetbrains_env.sh
3️⃣ 验证是否设置成功

执行:

# 4. 检查确认
echo $XDG_CACHE_HOME
echo $JETBRAINS_REMOTE_DEV_DIR

应输出:

/workspace/jetbrains_cache
/workspace/jetbrains_remote_ide

4️⃣ 清理 /root 缓存(可选但建议执行)

释放一些空间,防止别的程序出错:

rm -rf /root/.cache/* rm -rf /root/.config/* rm -rf /tmp/*

5️⃣ 重新打开 JetBrains Gateway 连接

这时 Gateway 会检测到新的缓存路径(在 /workspace 下),
磁盘空间足够,它会成功启动远程 IDE。

http://www.dtcms.com/a/601467.html

相关文章:

  • 传媒有限公司免费网站武安市精品网站开发
  • 如何从多源业务表对商家进行综合评估?
  • DELMIA Role: RFE - Operations Experience Manager
  • 灭屏使用对讲,概率性出现无声
  • 问答系统网站模板天津建设工程交易信息网
  • GitHub 热榜项目 - 日榜(2025-11-12)
  • 继续访问这个网站字体安装wordpress
  • Java 进阶:反射机制深度解析
  • 如何开发高性能直播美颜sdk?人脸检测、美型算法与渲染优化详解
  • StreamAPI,取出list中的name属性,返回一个新list
  • SSM基于web的佳茗天香茶品销售平台的设计与实现z2m56(程序+源码+数据库+调试部署+开发环境)带论文文档1万字以上,文末可获取,系统界面在最后面。
  • 请别人做网站需要注意什么问题公司做网站怎么做账
  • 茂名网站制作策划如何查看用wordpress建的站点
  • 【湿地数据集4】基于 TOPMODEL模型的1980–2020年全球湿地动态数据集 GWDD
  • C++重点知识梳理(下)
  • 苍穹外卖(第七天)
  • 新乡网站建设制作报价方案网站如何布局
  • 安全狗 网站打不开成都网络营销搜索推广
  • 预测汽车燃油效率——线性回归
  • 【自然语言处理】基于深度学习基的句子边界检测算法
  • 链接脚本(Linker Scripts)
  • 素材网站整站下载WordPress做图床
  • 企业网站相关案例网站建设域名怎么用
  • 太原专业做网站wordpress主体开发
  • 零基础新手小白快速了解掌握服务集群与自动化运维(十八)Ansible自动化模块--安装与入门
  • 【C++11】Lambda表达式+新的类功能
  • C语言编译工具 | 探讨常用C语言编译工具的选择与使用
  • SCT2A26——5.5V-100V Vin,4A峰值电流限制,高效率非同步降压DCDC转换器,兼容替代LM5012
  • 手机网站搜索框代码网上做网站怎么防止被骗
  • 滑动窗口(同向双指针)