Need help?

Our experts have had an average response time of 13.14 minutes in February 2024 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Transaction Log Details in the onapp Database

by | Sep 17, 2021

Looking for how to get the transaction Log Details in the onapp Database? We can help you with this!

Here at Bobcares, we often handle requests from our customers to fix similar OnApp issues.

Today, let see how our Support Engineers fix this as a part of our Server Virtualization Technologies and Services.
 

Transaction Log Details in the onapp Database

 
We noticed so many cases of our customers that UI logs have been cleaned to make the UI look less messy. This is also helpful for hiding the transactions from the end-user view. After that, this won’t show the logs. But still, it is possible to view the log through the database.

We can use Virtual Machine identifier to see the transactions table with the following command to choose the log output we want to view:

mysql> select id, action, status, created_at, identifier from transactions where identifier='tbhgfglxilpehn';
+-----+----------------------------+----------+---------------------+----------------+
| id | action | status | created_at | identifier |
+-----+----------------------------+----------+---------------------+----------------+
| 197 | configure_operating_system | complete | 2015-02-23 18:01:38 | tbhgfglxilpehn |
| 198 | startup_virtual_machine | complete | 2015-02-23 18:01:38 | tbhgfglxilpehn |
| 199 | run_recipe_on_vm | failed | 2015-02-23 18:01:38 | tbhgfglxilpehn |
+-----+----------------------------+----------+---------------------+----------------+
3 rows in set (0.00 sec)

Now, we can select a specific transaction to view the output as follows:

mysql> select log_output from transactions where id=199\G
*************************** 1. row ***************************
log_output: [2015-02-23 18:06:00 UTC] Waiting for VS to boot...
[2015-02-23 18:06:00 UTC] VS is booted.
[2015-02-23 18:06:00 UTC] Waiting for VM to respond on port 22...
Fatal: VM network is down for 3600
Executing Rollback...
1 row in set (0.00 sec)

We can also use the same command if we have a disk identifier and want to see the disk-related task:

mysql> select id, action, status, created_at, identifier from transactions where identifier='g14vm6e7wcg07k';
+-----+--------------+----------+---------------------+----------------+
| id | action | status | created_at | identifier |
+-----+--------------+----------+---------------------+----------------+
| 194 | build_disk | complete | 2015-02-23 18:01:38 | g14vm6e7wcg07k |
| 196 | provisioning | complete | 2015-02-23 18:01:38 | g14vm6e7wcg07k |
+-----+--------------+----------+---------------------+----------------+
2 rows in set (0.00 sec)

After that, we can select a specific transaction to view the output.

We can also use other ways to filter the output only for completed or failed transactions:

mysql> select id, action, status, created_at, identifier from transactions where status='failed';
+-----+-------------------------+--------+---------------------+----------------+
| id | action | status | created_at | identifier |
+-----+-------------------------+--------+---------------------+----------------+
| 2 | create_hypervisor | failed | 2014-08-08 19:45:36 | hwy5hqseskdap3 |
| 54 | destroy_virtual_machine | failed | 2014-08-12 18:24:29 | ju1lulver2ta9r |
...
| 233 | take_incremental_backup | failed | 2015-04-06 15:06:28 | qug61mtcvhwlzm |
| 234 | take_incremental_backup | failed | 2015-04-07 15:06:26 | iyi6rra39f56jh |
+-----+-------------------------+--------+---------------------+----------------+
49 rows in set (0.00 sec)

[Need more assistance with OnApp queries? We’d be happy to do it for you]
 

Conclusion

 
In short, today we saw how our Support Techs help our customers to get the transaction Log Details in the onapp Database.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Categories

Tags

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF