Recommended Free Tools
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
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Stop changing restart settings first. Preserve the failure: capture the exact stdout and stderr lines, timestamps, exit status, restart count, memory use, deployment revision, Node.js version, environment, working directory, and service-manager or kernel messages from the same minute. Then classify the event as an application exception or rejection, an unhandled EventEmitter error, an operating-system/resource failure, a fatal Node.js runtime event, or an external termination. Each class needs a different fix.
A supervisor such as PM2 can restart a failed process, but it cannot repair the defect that caused the exit. Treat every restart as evidence to investigate, not as proof that the application is healthy.
Free tools Windows power users keep installed
One-click scans. No signup required.
What a Node.js crash on a VPS actually means
Node.js normally terminates when an exception reaches the event loop without a handler. Its process documentation describes uncaughtException as the event emitted when an uncaught JavaScript exception bubbles back to the event loop, and states that “The process will still crash if no ‘uncaughtException’ listener is installed.” The usual result is a stack trace on stderr and exit code 1.
That behavior is deliberate. An uncaught exception can leave application state inconsistent, so using an uncaughtException listener to continue serving requests is unsafe. Node.js documents the event as a last-resort opportunity for synchronous cleanup, with an external monitor responsible for restarting the process. The durable fix is to find and correct the operation that threw.
#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: 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.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Not every disappearance is a JavaScript exception. Node.js also reports system errors caused by operating-system constraints, assertion errors, and application-defined errors. An EventEmitter that emits error without an error listener can itself throw and bring down the process. The kernel, a service manager, a container limit, a deployment hook, or an administrator can terminate the process without leaving a useful Node stack trace.
Preserve the crash evidence before changing anything
Restarting repeatedly, increasing the heap, or adding a broad exception handler can destroy the clues needed to identify the cause. First record one complete failure and the state immediately before it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Record the application context
- UTC timestamp of the first failure and each subsequent restart.
- Full stdout and stderr, including the final line before exit.
- Exit code, signal if the supervisor reports one, uptime, and restart count.
- Resident memory, heap usage, CPU, open-file count, and disk space near the event.
- Deployment revision, dependency lockfile revision, Node.js version, and native-module build information.
- Working directory, Unix user, executable path, command-line arguments, and relevant environment variables. Redact secrets before sharing logs.
- Request, job, tenant, or message identifiers associated with the failing operation.
Keep the failing log with the deployment identifier. A timestamp without the corresponding revision and environment is rarely enough to reproduce a production-only crash.
Reproduce the production command in the foreground
When the service can be taken out of rotation safely, run the exact production start command as the same Unix user, from the same working directory, with the same environment and Node binary. Do not substitute an interactive shell’s defaults for the service’s environment.
cd /srv/myapp
/usr/bin/node server.js
> /tmp/myapp-stdout-2026-10-15T120000Z.log
2> /tmp/myapp-stderr-2026-10-15T120000Z.log
printf 'exit=%sn' "$?"Adapt the path and command to your deployment. The timestamped files let you compare the foreground result with what the supervisor saw. If it runs successfully in the foreground, the difference is evidence: environment variables, permissions, current directory, limits, startup ordering, traffic, or the supervisor’s command may not match.
Check PM2 before clearing or rotating logs
For a PM2-managed process, start with status and the recent log tail:
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
pm2 ls
pm2 status
pm2 logs myapp --lines 200
pm2 monitRecord the process name, uptime, restart count, exit time, and memory shown in the list or monitor. PM2 provides real-time logs and stores them by default under $HOME/.pm2/logs, with separate output and error files. Preserve the relevant files before deleting them. PM2 supports log rotation through pm2-logrotate; rotation prevents a full disk from becoming the next failure, but it must not erase the log segment containing the original crash.
Look outside Node.js
Correlate the exact exit time with the VPS service manager and kernel logs. Look for an out-of-memory kill, a cgroup or service limit, a signal termination, a permission error, a full filesystem, a failed mount, or a port conflict. On a systemd host, the service owner can inspect the unit and its journal with commands such as:
systemctl status myapp.service
journalctl -u myapp.service --since "2026-10-15 11:55:00" --until "2026-10-15 12:05:00"
journalctl -k --since "2026-10-15 11:55:00" --until "2026-10-15 12:05:00"Use the actual unit name and a narrow time window. A blank PM2 error file does not establish a clean exit: the kernel or supervisor may have killed the process before Node could write anything.
Classify the failure before choosing a fix
| Evidence pattern | Likely class | First action |
|---|---|---|
| JavaScript stack trace ending in an uncaught exception; exit code 1 | Application exception | Fix the throwing path and validate its inputs; do not resume an undefined process. |
Unhandled 'error' event naming an emitter |
Unhandled EventEmitter error | Attach an error listener at the operation boundary and decide whether to retry, fail the request, or terminate the worker. |
unhandledRejection or an async operation’s rejection reason |
Rejected promise without a boundary handler | Handle the rejection where the request, job, or startup operation is owned and log its context. |
| Heap out-of-memory text, kernel OOM message, or abrupt termination with memory at a limit | Node heap or system resource exhaustion | Identify the allocation or concurrency spike; inspect VPS memory, swap, and service limits. |
| No Node stack trace; service-manager or kernel records a signal, limit, permission, disk, or port error | External or operating-system failure | Resolve the reported limit or deployment/configuration problem before changing application code. |
| Repeated starts followed by connection failures to a database or API | Dependency outage or startup race | Use bounded retries and exponential backoff instead of an immediate infinite restart loop. |
Fix an uncaught exception or rejected promise
Uncaught synchronous exception
Use the stack trace to locate the first application frame, then inspect the value and invariant that the code assumed. Typical repairs include validating request data before dereferencing it, checking that a file or configuration key exists, handling a database result that can be empty, and making startup fail with a clear message when a required setting is absent.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsDo not wrap the entire process in a catch block that logs and carries on. If the exception occurred after shared state was mutated, continuing can produce corrupt responses or duplicate jobs. Let the process exit after minimal synchronous cleanup and let the supervisor start a fresh instance once the defect is fixed.
Rejected asynchronous work
Attach a rejection handler at the boundary that owns the operation. An HTTP request handler should turn an expected failure into an appropriate response; a background job should record the job identifier, retry only when the error is transient, and mark the job failed when it is not. Startup code should reject the boot sequence with a message that identifies the missing dependency or configuration.
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.
async function handleJob(job) {
try {
await processJob(job);
} catch (error) {
logger.error({ err: error, jobId: job.id }, 'job failed');
await markJobFailed(job.id);
}
}The example is a boundary handler, not a substitute for fixing the original failure. Preserve the rejection reason and request or job context so the next occurrence can be tied to a specific input.
Unhandled EventEmitter error
Find the emitter named in the message: a socket, stream, child process, database client, or custom emitter. Add an error listener as soon as the emitter is created, and define the intended policy. A recoverable connection may be closed and retried; a failed request may receive an error; a worker with invalid internal state may need to terminate.
const socket = createSocket(options);
socket.on('error', (error) => {
logger.error({ err: error }, 'socket error');
closeOrRetry(socket, error);
});Attaching a listener that only suppresses the error hides the symptom and can leak resources. Ensure the listener closes or disposes of the failed object and that retries have a limit.
Investigate heap and system out-of-memory failures
Distinguish V8 heap exhaustion from a VPS kill
A Node heap out-of-memory message indicates that V8 could not satisfy an allocation within its configured heap. A kernel or service-manager out-of-memory record indicates that the operating system killed a process after the VPS or its service limit ran short of memory. They can occur together, but the remedies differ.
- For a V8 failure, identify what is retaining objects: unbounded arrays or maps, cached responses, listeners, unresolved promises, or a queue growing faster than it drains.
- For a VPS failure, inspect total memory, swap, other processes, cgroup or unit limits, and concurrent workers. A healthy Node heap can still be killed when the host has no reclaimable memory.
- Correlate the failure with traffic, batch size, import volume, image or archive processing, and deployment changes.
Use a larger heap only as temporary containment
A higher heap limit can postpone a failure while increasing swap pressure and the amount of memory reclaimed during garbage collection. Measure normal memory use first, fix the allocation path or concurrency, and set a limit that fits the VPS rather than treating extra heap as a cure. If recycling is necessary to protect availability, keep the crash evidence and investigate the leak in parallel.
PM2 can recycle a process after it crosses a configured threshold:
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.
pm2 start app.js --name myapp --max-memory-restart 200MThe threshold is a containment setting, not proof that 200 MB is safe for your workload. Choose it from observed steady-state and peak memory, leave room for the operating system and other services, and alert when recycling begins.
Capture a diagnostic report when ordinary logs stop too early
Node.js diagnostic reports provide structured JSON describing the runtime and system when a hard failure is difficult to explain. Node supports reports for uncaught exceptions, fatal errors such as out-of-memory conditions, and selected signals. It also provides controls for the report directory, filename, and report-triggering signal.
NODE_OPTIONS="--report-uncaught-exception --report-on-fatalerror --report-on-signal --report-signal=SIGUSR2 --report-directory=/var/log/myapp" node server.js- Create the report directory with ownership and permissions that match the service user.
- Launch the application with the options in the real service environment, not only in an interactive shell.
- When policy permits, send the configured signal to request a report before reproducing the failure.
- Store the JSON report beside the application log and deployment revision.
- Restrict access: reports can contain environment values and detailed system information.
Do not trigger a signal report blindly on a production process. Confirm that the signal is allowed by your deployment policy and that the resulting file will not fill the disk or expose credentials.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallStop a dependency outage from becoming a crash loop
If every restart immediately attempts the same unavailable database, API, queue, or secret store, the supervisor can amplify the outage. At the operation boundary, classify errors as transient or permanent. Retry transient network failures a bounded number of times with exponential backoff and jitter; fail fast on invalid credentials, malformed configuration, or an incompatible schema.
Startup health checks should report a meaningful not-ready state while a dependency is unavailable when the deployment platform supports that distinction. A process that cannot safely serve any request may exit, but the restart policy must add delay. PM2 documents an exponential-backoff restart strategy that increases the delay between restarts and reduces pressure on an unavailable dependency.
Use PM2 for visibility and controlled recovery
PM2 describes PM2 Runtime as a production process manager for Node.js applications. It can keep an application alive, restart it after crashes and machine restarts, expose logs, and provide monitoring commands. The useful baseline is:
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.
pm2 start app.js --name myapp
pm2 ls
pm2 logs myapp --lines 200
pm2 monitConfigure restart behavior only after collecting evidence. Memory-based recycling can protect a VPS from a runaway process; exponential backoff can protect a failing dependency. Neither changes the exception, leak, permission problem, or external kill that caused the original exit.
Persist a known-good process definition
After the command, environment, user, working directory, and restart policy are verified, configure boot persistence with pm2 startup and save the process list with pm2 save where appropriate. Test a reboot or service restart in a maintenance window. Confirm that the boot-time environment matches the deployment environment; a process that works in your shell can fail at boot because PATH, secrets, current directory, or file permissions differ.
Protect logs and permissions
- Run the application with the least-privilege service account that can read its files and bind its required port.
- Ensure the PM2 log directory and report directory are writable by that account but not broadly readable.
- Configure rotation and monitor disk capacity. A full filesystem can prevent logs, temporary files, and even database writes.
- Alert on rising restart count, falling uptime, repeated backoff, and memory-threshold restarts.
Compare foreground/systemd and PM2 before switching supervisors
Choose the smallest supervisor setup that fits the VPS’s existing service-management model. Running both PM2 and systemd to supervise the same process can create competing restart loops and confusing ownership.
| Decision axis | Foreground or systemd | PM2 |
|---|---|---|
| Reproducing the exact command | Usually closest to the service’s executable, user, directory, and environment; foreground mode is easiest for one controlled reproduction. | Convenient when the PM2 process definition is the documented production command; verify its saved environment and working directory. |
| Logs | Foreground redirection or the service manager’s journal; retention depends on host configuration. | Real-time pm2 logs, status output, and files under $HOME/.pm2/logs by default. |
| Restart policy and backoff | Defined in the service manager or shell wrapper; inspect the unit rather than assuming defaults. | Crash restarts, memory-threshold recycling, and documented exponential-backoff options. |
| Memory handling | Use host or service limits and application-level controls. | --max-memory-restart can recycle after a measured threshold; it does not diagnose a leak. |
| Boot persistence | Native service-manager enablement and unit configuration. | pm2 startup plus pm2 save, with environment parity verified after reboot. |
| Multi-process behavior | Separate units or a service-manager-native model, depending on the host. | PM2 can manage multiple application processes; define how logs, ports, shared state, and graceful shutdown behave. |
| Alerting | Requires the host’s monitoring and alerting integration. | Provides status and monitoring views; connect restart and memory signals to your alerting system. |
A repeatable crash-loop runbook
- Freeze the evidence. Save stdout, stderr, PM2 status, restart count, timestamps, memory, deployment revision, Node version, environment differences, and service-manager or kernel records.
- Reproduce once safely. Use the production user, directory, command, environment, and Node binary in the foreground, redirecting both output streams.
- Classify the exit. Decide whether the evidence shows an exception, rejection, EventEmitter error, heap failure, OS resource failure, signal, or dependency outage.
- Apply the narrow fix. Correct the throwing path, add a boundary handler, attach an emitter error listener, resolve a limit or permission problem, or introduce bounded backoff.
- Contain without hiding. Use a measured memory threshold or supervisor restart policy only when it protects availability and preserves the original logs.
- Validate the deployment. Compare lockfile, native modules, Node version, configuration, working directory, service user, and startup command with the last successful revision.
- Test recovery. Confirm graceful shutdown, boot persistence, log rotation, health checks, dependency recovery, and behavior under the workload that triggered the crash.
- Alert on recurrence. Monitor restart count, uptime, memory, disk capacity, and repeated dependency failures instead of waiting for users to report an outage.
Common mistakes that prolong a Node.js crash loop
- Only increasing restart frequency: this creates more processes without supplying a cause.
- Installing a global
uncaughtExceptionhandler to keep serving: it can leave the process in an undefined state; use it only for last-resort synchronous cleanup before exit. - Trusting an empty application log: an external kill can occur before Node writes a stack trace.
- Raising the heap indefinitely: this can move the failure from V8 into swap exhaustion or a kernel kill.
- Retrying a dead dependency immediately: synchronized retries can overload the dependency and extend the outage.
- Testing as the wrong user: an interactive shell may have secrets, a different
PATH, permissions, or current directory. - Running two supervisors: competing restart policies make exit times and ownership difficult to interpret.
- Rotating evidence too aggressively: the decisive final lines may be gone before diagnosis begins.
What a successful fix looks like
The process stays up under the workload that previously triggered the exit, and its logs show an intentional handling path rather than repeated restarts. A dependency outage produces bounded, observable retries; an invalid request produces a controlled failure; an exhausted resource produces a measured limit and an alert; and a fatal condition produces a report or a clear supervisor record. After a reboot, the same user, command, directory, environment, logs, and health checks are restored without manual intervention.
Frequently Asked Questions
Why is the PM2 error log empty when the app keeps restarting?
The process may have been killed by the kernel, a cgroup or service limit, a deployment hook, or another supervisor before Node could write an error. Correlate the exit timestamp with service-manager and kernel logs.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Should I add an uncaughtException handler to stop the crashes?
No. Node.js treats it as a last-resort cleanup event, not a safe recovery mechanism. Fix the throwing code and let an external supervisor restart a process whose state may be inconsistent.
Will a larger Node.js heap permanently fix out-of-memory crashes?
No. It can postpone V8 exhaustion while increasing swap pressure. Identify the allocation path and concurrency, inspect VPS limits, and use a measured memory-restart threshold only as containment.
How do I know whether PM2 or systemd should manage the app?
Use the supervisor that matches the VPS’s existing service model and preserves the clearest command, environment, logs, restart policy, and boot behavior. Do not have both independently supervise the same process.
Quick Recap
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.
