Skip to main content

Process uptime - Linux

How to find the uptime of a Linux Process

1. Login to the server as root.

2. Run the below provided command

ps -eo pid,comm,lstart,etime,time,args | grep process-name


PID - Process ID .ie. the ID of the process that we are searching.

comm - Display the process name.

lstart - The time at which the process is started.

etime - The time elapsed once the process is started.

args - command with options and arguments.

process-name - The process for which we need to check uptime.

For eg :

:~$ ps -eo pid,comm,lstart,etime,time,args | grep cron
  937 cron            Fri Jan 30 09:42:17 2015       37:36 00:00:00 cron

The cron deamon is running in the server from 9:42 AM and is alive for 37 minutes till now.
Check the etime field. (37:36)

This is how we can detect the uptime of a process in Linux.

Added on Jan 30 10.26 AM   

Popular posts from this blog

Qmail cheat sheet

1) To check the mail queue in plesk from command line, you can use the command :


2) You can examine the queue with qmail-qread.


3) From the qread command you get the message id . In the above example , let us assume one of the id is 524514 . Now you can find the file holding the email in/var/qmail/queue with find command.

# find /var/qmail/queue -iname 524514


/var/qmail/queue/mess/22/524514 (mail headers)


4) From the mail header you get the IP address

vi /var/qmail/queue/mess/22/524514


Shortcut for the cool guys

find /var/qmail/queue -iname queu_id | grep mess | xargs less


4) If you wish …

Logical volume vmxxxx_img is used by another device - Error on LVM removal

Hi Folks,

I've faced error while trying to remove an LVM from the server.

The exact LVM error will be "Logical volume vmxxxx_img is used by another device" on executing the lvremove command.

Feel free to remove the following steps to remove the LVM from the server.

Note: Please remember to replace <id> with your VMID in the below section.

dmsetup ls dmsetup info -c xen-vm<id>_img dmsetup remove xen-vm<id>_img lvremove -f /dev/xen/vm<id>_img ----------------------------------------------------------

File system corrupted on the OpenVZ container.

It happens rarely but when it does, it is hard to handle. The OpenVZ VM's are usually stable in nature, but I've encountered situations where OpenVZ VM was showing file system error and was refusing to start.

You can follow the below steps to recover the VM.

1. ~# vzctl stop ctid

2. # ploop mount /vz/private/ctid/root.hdd/DiskDescriptor.xml
3. now do a df -h and you will get the ploop id for the VM.
4. fdisk -l /dev/ploop12345
5. e2fsck /dev/ploop12345p1
6. ploop umount -d /dev/ploop12345
7. vzctl start ctid