Table of Contents
Logging
The Backup Ninja agent log file is located under at /var/log/bartender.log:
$ tail -f /var/log/bartender.log
2019-10-16T01:51:10.245Z info Job "bmj7f19uxxxxxxxxxxxx": Job completed.
2019-10-16T01:51:37.429Z info Loaded 1 configs from the cloud
2019-10-16T02:07:18.171Z info Agent stopped.
2019-10-16T02:07:18.203Z info Starting an agent v1.0.0-203...
2019-10-16T02:07:19.578Z info Authenticating agent to agent-auth-api.s9s-dev.net:443
2019-10-16T02:07:20.846Z info Loaded 1 job configurations from /var/lib/backup-agent/jobs/
2019-10-16T02:07:20.848Z info Agent started.
2019-10-16T02:07:20.848Z info Starting scheduler.
2019-10-16T02:07:20.848Z info Starting agent status reporting.
2019-10-16T02:07:22.699Z info Received configuration update (14)You can get more debugging information and agent activity.
You can change the log level and log file location in configuration file, /etc/bartender.yaml. Just use the following flags in the configuration file:
| Flag | Description |
|---|---|
log_level |
The log level. Default is info. Supported levels are: debug, info, warn, error, dpanic, panic, fatal. |
log_file |
Log file location. Default value is /var/log/bartender.log. Could be an actual path to a file or stderr/stdout. |
Health check
You have multiple ways to confirm that the agent is running, as shown in the following sections.
Process
Verify by running the OS process check:
$ ps aux | grep bartender
root 16082 0.0 2.0 442096 21304 ? Ssl 02:07 0:01 /usr/sbin/bartenderService
Verify by using service manager:
Redhat-based OSDebian-based OS
$ systemctl status bartender
● bartender.service - Backups and restore agent
Loaded: loaded (/etc/systemd/system/bartender.service; bad; vendor preset: disabled)
Active: active (running) since Sat 2019-10-19 02:38:03 UTC; 11min ago
Main PID: 25722 (bartender)
CGroup: /system.slice/bartender.service
└─25722 /usr/sbin/bartender
Oct 19 02:38:03 CentOS7 systemd[1]: Stopped Backups and restore agent.
Oct 19 02:38:03 CentOS7 systemd[1]: Started Backups and restore agent.$ service bartender status
● bartender.service - Backups and restore agent
Loaded: loaded (/etc/systemd/system/bartender.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-10-18 22:46:28 UTC; 4h 4min ago
Main PID: 76 (bartender)
Tasks: 10 (limit: 4915)
CGroup: /system.slice/bartender.service
└─76 /usr/sbin/bartender
Oct 18 22:46:28 Ubuntu18 systemd[1]: bartender.service: Failed to reset devices.list: Op
Oct 18 22:46:28 Ubuntu18 systemd[1]: Started Backups and restore agent. Further Assistance
If you have any issues that required assistance, kindly contact our support team by filling up the Backup Ninja Support form.