Xitoring Document
Home
FAQ
Support
Register
Home
FAQ
Support
Register
  • Xitoring

    • Introduction
    • Release Notes
    • Xitoring Release Notes
    • Linux Xitogent Release Notes
    • Windows Xitogent Release Notes
    • Xitoring Mobile App Release Notes
    • Account Management
    • API Access & Automation
    • Team Management & Collaboration
    • Billing & Subscription Management
  • Getting Started

    • Getting Started with Xitoring
    • Workflows & Guides
    • Monitor Your First Server
    • Import / Migration
    • Migrate from UptimeRobot to Xitoring
    • Migrate from Pingdom to Xitoring
    • Migrate from Uptime.com to Xitoring
    • Migrate from BetterStack to Xitoring
  • Help & Support

    • FAQ & Troubleshooting
    • Glossary
  • Server Monitoring

    • Server Monitoring
    • Graphs
    • Live Statistics
    • Monitor Services
    • Auto-Triggers
  • Xitogent on Linux

    • Install Xitogent on Linux
    • Update Xitogent on Linux
    • Uninstall Xitogent on Linux
  • Xitogent on Windows

    • Install Xitogent on Windows
    • Uninstall Xitogent on Windows
    • Xitogent Service
    • Update Xitogent on Windows
    • Disk Performance (I/O)
  • Xitogent on Azure

    • Xitogent on Azure
    • Monitor Azure Linux VM
    • Monitor Azure Windows VM
  • Xitogent CLI

    • Xitogent CLI
    • Xitogent Pause/Unpause
    • Xitogent Status
    • Xitogent debug
    • Xitogent Diagnosis
    • Which data we collect
  • Xitoring CLI

    • Xitoring CLI
  • Uptime Monitoring

    • What is Uptime Monitoring
    • Monitoring Nodes (Geographic Locations)
    • What is Check
    • Auto-Discovery
    • Auto Fault Tolerance
    • Heartbeat Check
    • Ping Check
    • HTTP(S) Check
    • DNS Check
    • FTP Check
    • SMTP Check
    • IMAP Check
    • POP3 Check
    • TCP Check
    • UDP Check
  • SSL Monitoring

    • SSL Monitoring
  • Incidents

    • Incidents
    • Incident's Root Cause
    • Incidents Notification
    • Incident Notes
    • Resolving Incidents Manually
    • Incident Policy
  • Maintenance Schedule

    • Maintenance Schedule
  • Email Reports

    • Email Reports
  • Integrations

    • Integrations
    • Apache Integration
    • CoreDNS Integration
    • CouchDB Integration
    • Disk Health Integration
    • Docker Integration
    • Dovecot Integration
    • Exim Integration
    • HAProxy Integration
    • IIS Integration
    • InfluxDB Integration
    • Kafka Integration
    • KeyDB Integration
    • LiteSpeed Integration
    • MongoDB Integration
    • MySQL Integration
    • Netstat Integration
    • Nginx Integration
    • OpenLiteSpeed Integration
    • OpenVPN Integration
    • PHP-FPM Integration
    • Postfix Integration
    • PostgreSQL Integration
    • RabbitMQ integration
    • Redis Integration
    • MS SQL Server Integration
    • Supervisor Integration
    • Varnish Integration
    • Wireguard Integration
  • Notifications

    • Notifications
    • Creating Notification Roles
    • Email Integration
    • Mobile Push Notifications
    • SMS Integration
    • Phone call Integration
    • Webhook Integration
    • Integration for Slack
    • Telegram Integration
    • WhatsApp Integration
    • Mattermost Integration
    • Discord Integration
    • Google Chat Integration
    • Microsoft Teams Integration
    • Atlassian Opsgenie Integration
    • Splunk On-Call Integration
    • Pushover Integration
    • Pushbullet Integration
    • Gotify Integration
    • Ntfy Integration
    • Spike.sh Integration
    • PagerDuty Integration
    • Zapier Integration
    • AlertOps Integration
  • Status Page

    • Status page
  • 3rd Party Status Pages

    • Using 3rd party Status Pages
    • Atlassian Status Page Integration with Xitoring
    • Status.io Integration with Xitoring
    • Statuspal Integration with Xitoring
    • Instatus Integration with Xitoring
  • Dashboards

    • Main Dashboard
    • Custom Dashboards
  • Metrics

    • Metrics
  • MCP Server

    • Setup & Tool Reference

Xitogent debug

Xitogent debug CLI command is implemented to be helpful if you had any problem with running Xitogent on your server.

Purpose

This command is used to generate debug information about the Xitogent service. It checks the service status and config file data and also checks if the process is running. The command also attaches the last lines of the log file. The main purpose of this command is for clients to run it and send the output to the Xitogent support team for assistance in solving problems.

Output

The command will display the following information:

  • The status of the Xitogent service as reported by systemctl
  • The last lines of the xitogent.log file
  • The content of the xitogent.conf configuration file Verification of the UID and password, connection to the node, and test sequence.
  • The permissions of the Xitogent binary file
  • The process list containing the Xitogent daemon and the command process

Example:

xitogent debug

Below is an example of the output:

systemctl:
2021/01/25 13:05:22 ● xitogent.service - Xitogent Service
   Loaded: loaded (/etc/systemd/system/xitogent.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2021-01-25 13:02:51 UTC; 2min 30s ago
  Process: 22186 ExecStart=/usr/bin/xitogent start --daemon (code=exited, status=0/SUCCESS)
 Main PID: 22192 (xitogent)
    Tasks: 11
   Memory: 9.0M
   CGroup: /system.slice/xitogent.service
           └─22192 xitogent: daemon logRotationPeriod:0

Jan 25 13:02:51 dev-core systemd[1]: Starting Xitogent Service...
Jan 25 13:02:51 dev-core systemd[1]: Started Xitogent Service.
 
--------------------------------------------
xitogent.log:
2021/01/25 13:02:51 - - - - - - - - - - - - - - - 
2021/01/25 13:02:51 daemon started 22192 
Log rotation 24 period = hours
2021/01/25 13:02:51 +  1674651771 
2021/01/25 13:02:57 HTTP status:200 - Server data sent 
2021/01/25 13:04:02 HTTP status:200 - Server data sent 
2021/01/25 13:05:08 HTTP status:200 - Server data sent 
--------------------------------------------
xitogent.conf:
uid=xxxbfexxx0cf3b3dxxx955c41x9c34xx
password=zxxz30573a3exxx
node_url=https://lax01.xitoring.com/xitogent/v2/
log_file=/var/log/xitogent.log
--------------------------------------------
Result of Verifying uid and password, connection to node, and test sequence
2021/01/25 13:05:28 HTTP status:200 - Server data sent 
--------------------------------------------
xitogent permission:
2021/01/25 13:05:28 Result: -rwxr-xr-x 1 root root 8591600 Jan 25 13:02 /usr/bin/xitogent
 
--------------------------------------------
process:
2021/01/25 13:05:28 Result: root     22192  2.9  0.1 1259196 12588 ?       Ssl  13:02   0:04 xitogent: daemon logRotationPeriod:0
root     22884 25.5  0.1 1119928 12228 pts/6   Sl+  13:05   0:01 xitogent debug
root     22958  0.0  0.0 112812   932 pts/6    S+   13:05   0:00 grep xitogent

Troubleshooting

If you encounter any issues while using the Xitogent service, please run the xitogent debug command and send the output to the Xitogent support team through our ticket system. The output will provide important information that will assist our team in identifying and resolving the problem.

Please include the output, the description of the problem, and the steps you have taken to reproduce the issue.

Please be aware that the output contains sensitive data that should not be shared with unauthorized persons.

By providing this information, you will help us to solve your problem more quickly and efficiently. If you have any questions, please don't hesitate to (contact us).

Last Updated: 4/12/23, 8:04 PM
Prev
Xitogent Status
Next
Xitogent Diagnosis