Resolving 'Root Partition Is Filling Up' Issue on Sophos UTM Firewall

本文提供了解决Sophos UTM防火墙根分区空间不足的方法,包括通过SSH登录并清理更新目录,以及调整固件下载设置,防止问题再次发生。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

from:

https://wandersick.blogspot.com/2016/06/resolving-root-partition-is-filling-up.html

 

This is a quick guide on how to resolve an occasional problem that could happen to neglected Sophos UTM firewall with default settings, where updates are automatically downloaded to device, filling up storage after some time.

An email alert similar to the below is sent to administrator when it happens:

From: Firewall Notification System [do-not-reply@fw-notify.net]
Sent: 18 June 2016 11:58 PM
To: Administrator [admin@wandersick.com]
Subject: [SOPHOS][INFO-150] Root partition is filling up - please check

Root partition is filling up - please check. Current usage: 86%
--
System Uptime      : 362 days 1 hour 2 minutes
System Load        : 0.05
System Version     : Sophos UTM 9.210-20

Please refer to the manual for detailed instructions.

To solve it, one way is to

  1. SSH into Sophos UTM firewall using root login
  2. Remove content under Sophos update directory (Main focus of this blog post)
  3. Configure firmware download interval for System Up2Date packages from Automatic to Manual

1. SSH into Sophos UTM firewall using root with public key authentication
In order for root login to be made possible, it is required to first generate a private key and set up public key authentication. You may refer to any guide found on the Internet such as this one.

After enabling root login, we can then authenticate using the private key file using SCP/SSH clients such as WinSCP, PuTTy by specifying private key file as shown below.

a. Specifying private key file in WinSCP SCP client:

image

b. Specifying private key file in PuTTy SSH client:

image

2. Remove content under Sophos update directory

Commands for determining storage utilization on directory /var

  • cd /var
  • du -shx  *

After root SSH login, executing the above directory size checking commands revealed the /var/up2date folder (containing downloaded firmware updates) took 2GB of space on the device.

image

Mitigate the situation by removing the update files under /var/up2date/sys. Below screenshot shows a way to do it using WinSCP. (Backing up the files is recommended prior to deletion.)

image

Command for listing space utilization statistics on each file system mounted on device

  • df -h

Before removing the files, the disk utilization was 86%:

image

After removing the files, the disk utilization lowered to 46%:

image

3. Configure download interval for System Up2Date packages as Manual

To prevent this problem from recurring, firmware download interval can be set to Manual on the firewall. After configuring the setting, firewall updates will not be automatically downloaded, hence device storage won’t be filled up as easily.

Tip: Be sure to do this quickly after moving/deleting the files. Otherwise, the device storage will be filled up again by the update download next time

clip_image002

Hope this post provides a quick way to resolve this problem for those who encounter it.

Update in April 2017: Fix it as early as we can! It was found that if we leave the problem unresolved until the firewall disk partition becomes 100% full, web administration console (httpd) will fail with the error below, and we must recover the firewall via console logon (or using Windows PE/Linux boot disc USB).

Internal Server Error

The server encounted an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at admin to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Reference

let's find where the problem is, from the command line as root:

cd /
du -shx *

And then go into the largest in the list and do du -shx * again.

It looks like you're now on 9.318, so I would set the Download interval to "Manual" and delete everything in /var/up2date/sys

转载于:https://www.cnblogs.com/k98091518/p/10488439.html

<think>好的,用户询问的是关于npm或Yarn在解决依赖包时显示“already up to date”的含义及应对措施。我需要先理解这个提示的具体情况。 首先,“Resolving packages”阶段是包管理器在确定需要安装或更新的依赖项。当显示“already up to date”时,通常意味着根据lock文件(如package-lock.json或yarn.lock),所有依赖的版本都已满足,无需更新。这可能是因为项目依赖已经安装过,且没有新的变更需要处理。 接下来,用户可能需要知道在这种情况下应该采取什么行动。例如,是否需要手动清除缓存、检查lock文件的一致性,或者强制重新安装依赖。此外,用户可能遇到即使有更新版本,但lock文件锁定了版本的情况,这时候是否需要更新lock文件。 还要考虑用户可能遇到的常见问题,比如缓存导致的问题,或者node_modules存在冲突需要清理。需要建议他们如何验证依赖状态,或者如何强制重新安装以确保正确性。 最后,根据提供的引用内容,用户之前提到过删除yarn.lock并使用npm install的情况,可能需要关联这些信息,说明lock文件在依赖解析中的重要性,以及不同包管理器的行为差异。</think>关于npm或Yarn显示"Resolving packages already up to date"的含义及应对措施,以下是详细说明: ### 1. 提示含义 当执行`npm install`或`yarn install`时出现该提示,表示: - 根据`package.json`和lock文件(`package-lock.json`/`yarn.lock`)的版本约束 - 所有依赖包已满足版本要求且本地`node_modules`目录完整 - 没有需要新增/更新的依赖包[^2] ### 2. 常见场景 | 场景 | 说明 | |-----|-----| | 首次安装后重复执行 | 依赖树未发生变化 | | lock文件未更新 | 未修改`package.json`且未升级依赖 | | 缓存命中 | 本地缓存与远程仓库版本一致 | ### 3. 建议操作 #### 基础验证 ```bash # 检查lock文件状态 git status package-lock.json # 或 yarn.lock # 清除缓存后重试 npm cache clean --force && npm install # 或 yarn cache clean ``` #### 强制更新 ```bash # 删除lock文件和node_modules后重装(谨慎操作) rm -rf node_modules package-lock.json npm install # 或使用覆盖安装 npm ci # 严格根据lock文件安装 ``` #### 版本升级 ```bash # 检查过时依赖 npm outdated # 交互式升级 npx npm-check -u ``` ### 4. 特殊情况处理 当依赖存在但运行异常时: 1. 检查`node_modules/.bin`目录是否存在二进制文件 2. 验证`NODE_PATH`环境变量配置 3. 尝试`npm rebuild`重新编译原生模块 ### 依赖管理对比 | 特性 | npm | Yarn | |-----|-----|-----| | Lock文件生成 | 自动生成package-lock.json | 需要yarn.lock[^3] | | 并行安装 | 支持(v5+) | 原生支持 | | 离线模式 | `npm ci --offline` | `yarn install --offline` |
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值