Stuck with OnApp transactions set to pending? We can help you.
As part of our Server Virtualization Technologies and Services, we assist our customers with several OnApp queries.
Today, let us see how our Support Techs fix it.
OnApp transactions set to pending
Sometimes, you can see that all transactions set to pending and nothing will run on onapp.
View transactions of a virtual server:
To view transactions for a virtual server follow below steps:
- Firstly, go to your Control Panel > Cloud > Virtual Servers menu.
- Then, click the label of the virtual server you’re interested in.
- The details screen for that virtual server shows recent transactions in the Activity Log section.
To cancel pending tasks, click the Cancel All Pending Tasks for this virtual server button.
You can also view the details of a particular log item by clicking its Ref number.
The page that loads shows the log output and the following details:
date – time in the [YYYY][MM][DD]T[hh][mm][ss]Z format action – the action name status – the action status (Complete, Warn, Pending, or Failed) ref – the log item’s Ref number target – the action target started at – the time when the action was started completed at – the time when the action was completed template – template of the server the action refers to compute resource – the label of compute resource initiator – the user who initiated the action
If you want to see only the detailed output, you can hide log info with the arrow button in the upper right corner.
How to resolve OnApp transactions set to pending?
Today, let us see the steps followed by our Support Techs to resolve it.
You can fix the transaction by Restarting the OnApp Daemon
- Firstly, SSH to the CP server.
- You should see the backups and transaction going when running the following command below. If you don’t, then the OnApp daemon is not running.
ps aux | grep onapp
- If you see that the OnApp daemon isn’t running, you will need to stop OnApp first with the command below:
service onapp stop
- Now, CD to the directory below:
- Look for the onapp_daemon.rb.pid. If you see it and the PID # is zero, then the daemon is not running, so we will kill it and then restart it with the commands below:
rm -rf onapp_daemon.rb.pid
- Now, start onapp:
service onapp start
- You should see something like the following:
Starting SSH Key Server... Agent pid 27822 Identity added: /onapp/interface/config/keys/private (/onapp/interface/config/keys/private) Starting All Runners (Schedules, Transactions, Backups and Hypervisor, Cluster Monitor) ... Starting Hypervisor Data Receiver... Starting VNC Proxy..
- Now ls -l the /onapp/interface/tmp/pids/ directory and you should see all of the following below now. That means that the deamon is back up and running correctly.
ls -l total 16 -rw-r--r-- 1 onapp onapp 0 Feb 6 09:16 0.852188522247947.14689 -rw-r--r-- 1 onapp onapp 6 Feb 8 11:35 onapp_daemon.rb.pid -rw-r--r-- 1 onapp onapp 5 Feb 8 11:35 receiver.pid -rw-r--r-- 1 root root 6 Feb 8 11:35 ssh-agent.pid -rw-r--r-- 1 root root 6 Feb 8 11:35 vnc_proxy.pid
[Need help with the process? We’d be happy to assist]
In short, today we saw how our Support Techs resolve Transaction pending issue on OnApp.