iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
Plenty of RAM in free -h does not prove that the failing process can allocate memory. A cgroup or service limit, systemd-oomd, swap policy, disk or inode exhaustion, storage latency, CPU throttling, network limits, filesystem damage, a kernel panic, or a provider-side reset can all take a VPS down while host-wide memory appears comfortable.
Start by classifying what actually happened—one process died, the guest froze, it rebooted, or the provider reset it—then use previous-boot logs and correlated metrics to identify the failure domain. Resize the VPS only after that evidence shows a guest-wide capacity shortage.
“The VPS crashed” can describe four different failures
The recovery path depends on the event. A service killed by the kernel is not the same incident as a frozen virtual machine or a host reset.
| Observed symptom | What it may mean | First evidence to collect |
|---|---|---|
| One application exits and other services remain up | Kernel OOM selection, a cgroup limit, a service limit, or an application crash | Unit logs, kernel messages, cgroup memory files, and the process exit status |
| SSH stops responding but the VPS later answers without a reboot | CPU starvation, I/O hang, network failure, or a saturated queue | Provider graphs, console access, load and I/O metrics, and timestamps from monitoring |
| The guest reboots | Kernel panic, watchdog action, host fault, or an intentional/provider reset | Previous-boot journal, uptime, boot list, and provider event history |
| The guest is unreachable and has no new guest logs | Power or host event, a hard hang, or a panic before logs were flushed | Provider serial console, event timeline, and boot-disk diagnostics |
Record the exact UTC time, affected services, last successful health check, and whether uptime reset. Those timestamps let you align guest evidence with provider events instead of guessing from a later symptom.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
Why global free memory can coexist with a local out-of-memory failure
Cgroups and service limits
Linux accounts memory at several scopes: the whole guest, a cgroup, a systemd unit, a container, and sometimes a NUMA or cpuset policy. A workload can hit its local ceiling while unrelated memory remains free elsewhere. In cgroup v2, inspect the directory for the affected service or container:
memory.maxis the hard memory ceiling; a value ofmaxmeans no explicit ceiling.memory.currentshows current usage in that cgroup.memory.eventsrecords events such ashigh,max,oom, andoom_kill.memory.swap.maxcan limit swap independently of RAM. A low or zero value can make a cgroup fail even when host swap is available.
Find the unit’s cgroup with systemctl status your-service and inspect its control-group path under /sys/fs/cgroup. Also review unit settings such as MemoryMax=, MemoryHigh=, and container runtime limits. Correct the applicable limit or reduce the workload; adding VPS RAM does not raise a lower service or container cap.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Memory policy and allocation context
The kernel documentation notes that a memory policy or cgroup can constrain an allocation even when another node or the system appears to have free memory. The relevant question is therefore: free to whom? Report whether the pressure is at the host, VM, cgroup, service, or container level rather than citing only aggregate totals.
systemd-oomd can act before kernel OOM
On systems using cgroups v2, Ubuntu’s systemd-oomd uses pressure-stall information (PSI) and policy to terminate units before a kernel-space OOM occurs. Its action can look like an unexplained service crash while free -h still shows available memory. Check whether it is enabled and inspect its decisions:
systemctl status systemd-oomd
journalctl -u systemd-oomd --since "-2 hours"
cat /proc/pressure/memoryIdentify the unit or cgroup named in the message, then examine its PSI history and memory policy. Do not disable the daemon blindly: remove the runaway workload or revise an intentionally tight policy after confirming the workload’s requirements.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
What swap does—and what it cannot do
Swap is a pressure valve, not a promise that allocations will succeed. The kernel can still invoke the OOM killer when reclaimable memory and permitted swap are insufficient. Kernel documentation summarizes the emergency behavior: “If this is set to 0, the kernel will kill some rogue process, called oom_killer.” That statement describes termination, not a guarantee that the largest process or the offending service will be selected.
Recommended Free Tools
Swap may also be unavailable to the failing scope. A cgroup can have its own memory.swap.max, and a swap device can be present globally but excluded by policy. Capture both views:
free -h
swapon --show
cat /proc/swaps
vmstat 1 5- High swap-in and swap-out with sustained run-queue pressure: the guest may be genuinely short of memory or suffering from a runaway process.
- Swap present but cgroup
memory.swap.maxis restrictive: the workload can fail locally despite global swap. - Swap nearly full: reclaim headroom is reduced, but this does not explain a disk, inode, network, or provider-limit failure.
Never treat “create more swap” as a universal crash fix. Swap cannot restore write capability on a full filesystem, reduce a storage device’s latency, undo CPU throttling, repair filesystem corruption, or bypass a provider’s network or burst limit.
Read the previous boot before changing capacity
A reboot often erases the only useful clues unless the journal is persistent. First list boots and inspect the one that ended unexpectedly:
journalctl --list-boots
journalctl -k -b -1
journalctl -b -1 -p warning..alertIf you know the affected unit, filter it directly:
journalctl -b -1 -u your-service
journalctl -b -1 -u systemd-oomdSearch the output for signatures such as oom-kill, Out of memory, panic_on_oom, systemd-oomd, hung_task, BUG:, Oops:, I/O error, EXT4-fs error, XFS, No space left on device, and watchdog messages.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Interpret common signatures
| Signature | Likely direction | Next check |
|---|---|---|
oom-kill or Killed process |
Kernel OOM selection, often within a constrained scope | Victim, cgroup path, memory.events, swap limits, and concurrent jobs |
systemd-oomd |
Userspace pressure-based termination before kernel OOM | PSI, unit policy, and the named cgroup |
Kernel panic - not syncing |
Fatal kernel condition, not necessarily memory exhaustion | Exact panic reason, serial-console output, and previous-boot messages |
No space left on device or journal write failures |
Filesystem blocks or inodes exhausted | df -h, df -i, and safe cleanup or expansion |
I/O error, EXT4-fs error, or XFS corruption messages |
Storage failure or damage after an unclean shutdown | Provider disk metrics, filesystem checks, and a recovery plan |
Google’s boot guidance distinguishes panic categories such as memory-exhaustion panic, crashed init, filesystem damage, machine checks, and corrupt kernel images by the panic text. Capture that exact text; “panic” alone is not enough to choose a remedy.
Measure every independent limit during the next incident
Take a snapshot while the VPS is healthy and repeat it during pressure so you can compare values:
free -h
swapon --show
vmstat 1 5
df -h
df -i
ulimit -a
systemctl status systemd-oomdFor the affected cgroup, save memory.max, memory.current, memory.events, and memory.swap.max. Record the process tree and service configuration as well. A one-time reading after recovery can hide a short spike, so use monitoring with timestamps when possible.
Check disk, inode, CPU, and network bottlenecks
Disk space and inodes
Blocks and inodes are separate resources. A filesystem can report free gigabytes while having no inodes for new files, or it can have free inodes but no writable blocks. Run both checks and inspect the mount that holds logs, databases, queues, or temporary files:
df -h
df -iFull storage can prevent services from writing state, rotate logs, create sockets, or complete a boot. Kernel documentation and cloud troubleshooting guidance both identify full disks and I/O errors as causes of filesystem damage after an unclean shutdown. Free space carefully, then expand or repair the filesystem using a tested recovery procedure; deleting active database files is not a safe emergency shortcut.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
I/O latency and queueing
High load with low CPU utilization commonly indicates tasks waiting on I/O. Rising latency with unsaturated CPU points toward storage or network rather than a need for more vCPUs. Collect:
iostat -xz 1
pidstat -d 1
vmstat 1Look for high await times, growing queue depth, and a process generating sustained reads or writes. Compare those observations with the provider’s IOPS, throughput, burst, and latency graphs. A virtual disk can be throttled even when the guest sees free RAM and idle CPU.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →CPU throttling and burst limits
Use per-CPU statistics and provider metrics together:
mpstat -P ALL 1CPU that repeatedly rises and falls at a fixed ceiling can indicate a burst or credit limit. A workload may appear slow, trigger health-check timeouts, and be mistaken for a memory crash. Provider dashboards may expose throttled time or credit balance that is invisible inside the guest; preserve those graphs with the incident timestamp.
Network and host-side events
Latency without CPU or disk saturation can be a network path or provider issue. If the guest is unreachable and its journal stops abruptly, use the provider’s serial console and event history. A host fault, provider reset, or panic before log flush cannot be diagnosed from SSH logs alone.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Make logs survive the reboot
By default, some distributions keep only volatile journal data. Create /var/log/journal, then configure bounded persistence in /etc/systemd/journald.conf. Set values appropriate to the disk, including:
Storage=persistentso boots are retained on disk.SystemMaxUse=andRuntimeMaxUse=to cap journal growth.SystemKeepFree=andRuntimeKeepFree=to reserve space for the operating system.
After changing the file, restart journald and verify that a new boot appears in journalctl --list-boots. Retention limits must leave enough room for logs from the incident you are trying to diagnose; an overly small cap can erase the evidence before the next reboot.
Choose a remedy by failure domain
| Evidence | Targeted remedy | Why a RAM upgrade alone may fail |
|---|---|---|
| Guest-wide memory pressure, no lower cgroup or service cap | Reduce peak usage, tune concurrency, or add RAM and appropriate swap | This is the case where additional capacity addresses the measured constraint |
memory.max, MemoryMax=, or swap cap reached |
Correct the limit or redesign workload placement | Unused memory outside the scope remains inaccessible |
OOM or systemd-oomd names a runaway unit |
Fix the leak, queue size, batch concurrency, or policy | More memory can postpone recurrence without removing the trigger |
| Full blocks or inodes | Free space safely, rotate or relocate data, and expand the filesystem | Memory does not create filesystem entries or writable blocks |
| High I/O wait, queue depth, or provider IOPS throttling | Reduce write amplification, move data, or change storage tier/provider | Extra RAM cannot lower device latency |
| Kernel panic, filesystem corruption, or host reset | Use console evidence, repair or roll back the implicated component, and involve the provider | The failure is below ordinary application memory accounting |
Evaluate each change by the failure domain it addresses, quality and persistence of evidence, recovery time, data-loss risk, reversibility, and whether the provider exposes the relevant CPU, I/O, burst, and event metrics.
Common “fixes” that obscure the real cause
Adding swap without checking scope
More swap helps only when reclaimable memory is the constraint and the failing scope may use it. Check cgroup swap limits and actual swap activity first.
Dropping caches
echo 3 > /proc/sys/vm/drop_caches is a diagnostic experiment, not a production cure. Kernel documentation warns that it can add I/O and CPU cost. It does not repair a limit, a full filesystem, or a failing disk.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsReading one metric in isolation
Load, CPU percentage, free memory, and swap usage each describe only part of the system. Microsoft’s troubleshooting guidance recommends observing behavior and relationships: high load with low CPU suggests I/O wait; unsaturated CPU with rising latency suggests disk or network; fluctuating CPU can indicate throttling or burst limits.
Resizing before preserving evidence
A resize can clear a symptom while destroying the chance to identify a provider event, cgroup cap, or kernel regression. Save logs, cgroup files, provider graphs, and timestamps before changing the instance whenever the system is still accessible.
Quick Recap
A repeatable incident checklist
- Write down the failure time, uptime before and after, affected services, and whether the provider recorded a reset.
- Classify the event as process kill, guest freeze, guest reboot, or provider-side interruption.
- Read
journalctl -k -b -1, the warning-to-alert range, and the affected unit’s previous-boot log. - Search for OOM,
systemd-oomd, panic, hung-task, filesystem, I/O, watchdog, and no-space signatures. - Capture
free -h,swapon --show,vmstat,df -h,df -i,ulimit -a, and service limits. - Inspect cgroup memory and swap files for the exact workload.
- Correlate
iostat,pidstat,mpstat, network latency, and provider CPU/I/O/burst graphs. - Preserve journals persistently with bounded retention, then apply the smallest reversible fix that matches the evidence.
- Reproduce or monitor the workload after the change and verify that the original signature disappears rather than merely moving.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
