install vps

SSH Logout ke baad OpenClaw Run Karein (PM2)

Aapna laptop close karne ya VPS se disconnect hone ke baad background mein apne OpenClaw Gateway ko 24/7 chalate rahne ke liye PM2 ka use kaise karein.

Read in English

Difficulty

beginner

Duration

10 minutes

Tested On

Ubuntu 24.04 LTS with Node.js v20+

Access Mode

SSH

Pre-flight status

Pre-Flight Approved

Risk low

Gateway Private

On this page

Safe guide Standard background process management. Apne non-root user ke roop mein run karna safe hai.

Short answer

Agar aap npx openclaw start ka use karke OpenClaw start karte hain aur fir apna terminal close kar dete hain, toh process mar jata hai. Isko permanently chalate rahne ke liye, PM2 naam ka ek process manager install karein.

Logout ke baad processes band kyun hote hain

Jab aap SSH ke zariye apne VPS se connect hote hain, toh Linux ek naya “session” start karta hai. Koi bhi program jo aap terminal mein start karte hain (jaise npx openclaw start) woh us session se attach ho jata hai. Jab aap disconnect karte hain ya apna laptop close karte hain, toh Linux us session ko end kar deta hai aur sabhi attached programs ko kill kar deta hai.

Isko rokne ke liye, aapko ek process manager ki zaroorat hoti hai. Yeh background mein (ek “daemon” ke roop mein) chalta hai, aapke programs ko SSH session se detach kar deta hai, aur agar woh crash hote hain toh unhe automatically restart karta hai.

OpenClaw jaisi Node.js applications ke liye, PM2 industry standard hai. (Systemd bhi ek option hai, lekin beginners ke liye PM2 bahut aasan hai aur Node logs gracefully handle karta hai).

Step 1: PM2 Install Karein

Pahle, agar aapka Gateway aapke terminal mein chal raha hai toh isko stop karein (Ctrl+C).

Fir, npm ka use karke PM2 ko globally install karein:

bash

npm install -g pm2

Aapne Node.js kaise install kiya hai iske based par, aapko isko bina sudo ke run karna padh sakta hai. Agar aapne humari nvm guide follow ki thi, toh sudo ka use NAHI karein.

Verify karein ki PM2 install ho gaya hai:

bash

pm2 -v

Step 2: PM2 ke saath Gateway start karein

Apne OpenClaw workspace directory (jahan aapki .env aur database.sqlite hain) mein navigate karein:

bash

cd ~/openclaw-workspace

PM2 ka use karke OpenClaw Gateway start karein. Hum is process ka naam “openclaw” rakhenge taaki yaad rakhna aasan ho:

bash

pm2 start npx --name openclaw -- openclaw start

Yahan '--' important hai. Yeh PM2 ko kahta hai ki 'openclaw start' arguments ko npx ke paas pass kare.

Aapko process status dikhane wala ek table dikhna chahiye:

[PM2] Starting /home/clawuser/.nvm/.../bin/npx in fork_mode\n...\n│ id │ name      │ status │ restart │ uptime │ cpu │ mem      │\n│ 0  │ openclaw  │ online │ 0       │ 0s     │ 0%  │ 25.0 MB  │

Step 3: Startup persistence enable karein (Reboot survival)

Abhi, jab aap apna laptop close karte hain toh PM2 OpenClaw ko chalata rahta hai. Lekin agar VPS khud restart hota hai (jaise, aapka hosting provider maintenance perform karta hai), toh PM2 automatically start nahi hoga.

Server boot hone par PM2 ko start karne ke liye, yeh run karein:

bash

pm2 startup

PM2 ek command print karega jo kuch aisi dikhegi: sudo env PATH=$PATH:/home/clawuser/.nvm/... pm2 startup systemd -u clawuser --hp /home/clawuser

PM2 dwara diye gaye command ko copy karein, aur apne terminal mein run karein.

Aakhir mein, current PM2 process list ko save karein taaki usko OpenClaw start karna yaad rahe:

bash

pm2 save

Step 4: Reboot Test

Apna setup robust hai ya nahi yeh janne ka sabse behtar tarika ise test karna hai.

Apna server reboot karein:

bash

sudo reboot
Server ko wapas online aane ke liye 2 minutes wait karein.
Apne server mein wapas SSH karein.
PM2 status check karein:

bash

pm2 status

Agar OpenClaw online show hota hai, toh aapka setup complete hai. Yeh 24/7 chalega.

Essential PM2 commands

Apne Gateway ko manage karte time aap in commands ka frequently use karenge.

Task	Command
Sabhi apps ka status dekhein	`pm2 status`
Live logs dekhein	`pm2 logs openclaw`
Gateway restart karein	`pm2 restart openclaw`
Gateway stop karein	`pm2 stop openclaw`
Detailed app info dekhein	`pm2 show openclaw`

Log inspection

Kyunki Gateway background mein chal raha hai, aapko automatically apni screen par errors print hote nahi dikhenge. Agar aapka bot reply karna band kar deta hai, toh aapka pehla step hamesha logs check karna hona chahiye:

bash

pm2 logs openclaw --lines 50

Yeh logs ki aakhri 50 lines dikhata hai aur fir naye logs ke liye watch karta hai. Log view exit karne ke liye Ctrl+C press karein.

Rollback: PM2 process ko remove kaise karein

Agar aap OpenClaw ko background mein chalana band karna chahte hain aur manual starts par wapas aana chahte hain:

Process stop karein:

bash

pm2 stop openclaw
Ise PM2 ki list se delete karein:

bash

pm2 delete openclaw
Empty list save karein taaki yeh reboot par start hone ki koshish na kare:

bash

pm2 save --force

Kya NAHI karna hai

PM2 ko root ke roop mein run mat karein. Ise hamesha apne normal user ke roop mein run karein. PM2 ko root ke roop mein run karne ka matlab hai OpenClaw root ke roop mein chalta hai, jo ki ek massive security risk hai.
PM2 ke bajaye screen ya tmux ka use mat karein. Halanki woh tools session ko alive rakhte hain, lekin agar Gateway crash hota hai toh woh use automatically restart nahi karte, na hi woh server reboots cleanly handle karte hain. PM2 ka use karein.

ClawReady.in is an independent educational resource and setup service. It is not affiliated with, endorsed by, or operated by OpenClaw.