Frequently Asked Questions

Linux

1. What are the permission requirements for installing or uninstalling UniAgent?

Answer:

The user must have root privileges to install and uninstall.
If SELinux is present, it must be disabled during installation. If SELinux is enabled after installing the agent, UniAgent must be reinstalled.
Ensure that no security software installed on the host is blocking the installation.

2. How to determine if UniAgent is installed successfully?

Answer:

The directory /opt/tingyun-oneagent is created.

The installation log output is as follows:

[root@localhost opt]# sudo ./Tingyun-OneAgent.sh 
 Unzip to /tmp/tingyun-oneagent-11037 ...
 Detected arch: X86_64
 Detected glibc version: 2.17
 Installation started, PID 11077.
 Copy files...
 Oneagent UUID: 030d3a76cf504f8afd836cf64f22b036
 We detected that SELinux is disabled in your system so we're skipping module installation.
Please note that if you enable SELinux later deep monitoring will stop working and you'll need to reinstall tingyun-oneagent.
 Setup preload settings...
 Symlink /lib/libinterceptor.so -> /opt/tingyun-oneagent/lib/libinterceptor.x86.so created
Symlink /lib64/libinterceptor.so -> /opt/tingyun-oneagent/lib/libinterceptor.so created
 Verifying system compatibility...
 Compatibility is OK
 Refreshing dynamic linker run-time bindings using ldconfig
 Setup auto start service...
 Detected init system: systemd, version: systemd 219
 Checking if agent is connected to the server...
 Connection status: success
 The installation has completed successfully
 # Installation complete, starting OneAgent
 Starting oneagent...
 tingyun-oneagent service started
 
 Use the following commands to maintain the service.
 
 start    : sudo systemctl start tingyun-oneagent
 stop     : sudo systemctl stop tingyun-oneagent
 status   : sudo systemctl status tingyun-oneagent
uninstall: sudo /opt/tingyun-oneagent/uninstall.sh

3. Is installation inside Docker containers supported?

Answer: Currently, you do not need to copy the installation package into Docker for installation. Install on the host, and it will automatically monitor applications inside Docker containers.

4. Why are some processes not detected by UniAgent?

Answer: Possible reasons include:

The monitoring technology does not support the process. See the Support List for UniAgent's monitoring scope.
Ensure the server is running and the process has started.
There may be a delay in interaction between UniAgent and the Guanyun AIOps platform. If so, try again later.
Ensure the process is not disabled on the Deployment Management > UniAgents page in the dashboard.

5. How to determine if the program is running normally?

If the following message appears during installation, it is running normally:
```
Checking if agent is connected to the server...
Connection status: success
```

After installation, run ps -ef|grep oneagent. If the following processes exist, it is running normally:

[root@localhost oneagent]# ps -ef|grep oneagent
root     11739     1  0 12:04 ?        00:00:00 /bin/sh /opt/tingyun-
oneagent/bin/watchdog start
root     11756 11739  0 12:04 ?        00:00:10 /opt/tingyun-oneagent/bin/oneagent

Log in to the Guanyun AIOps dashboard, and on the Deployment Management > UniAgents page, check if the host information for the installed UniAgent appears as expected. If so, the program is running normally.

6. Downloading UniAgent returns a 401 error, e.g.:

[root@k8s-node2 opt]# wget -O Tingyun-OneAgent.sh 'http://10.128.5.245:8080/server-config/config/deploy/download/shellfile?version=1.1.0-beta2&token=fec88dd7-ad0b-49e0-a948-06969405d2fd'
--2020-11-03 16:57:48--  http://10.128.5.245:8080/server-config/config/deploy/download/shellfile?version=1.1.0-beta2&token=fec88dd7-ad0b-49e0-a948-06969405d2fd
Connecting to 10.128.5.245:8080... connected.
HTTP request sent, awaiting response... 401 
Authorization failed.

Reason: The token has expired. The token is valid for 10 minutes.

Solution: Refresh the page and obtain a new download link.

7. Glibc version is below 2.12, installation fails

Unzip to /tmp/tingyun-oneagent-20277 …
Detected arch: X86_64
Detected glibc version: 2.11.3
Error: The glibc version: 2.11.3 detected on your system isn’t supported.
Error: We need at least glibc 2.12

Solution:

Use a machine with glibc version >= 2.12.
Use the Java agent for deployment.

8. Check if communication between UniAgent and Agent Collector is normal

Run the following command as root:

/opt/tingyun-oneagent/bin/installtool --net-check

If the following message appears, communication is normal:

9. No host information in the dashboard due to network issues between UniAgent and Agent Collector

If the following message appears, it means the network between UniAgent and Agent Collector is not connected:

Setup auto start service...
Detected init system: systemd, version: systemd 219
Checking if agent is connected to the server...
Warning: Connection status:  Error: http://10.128.5.245:7665/redirect?version=3.2.0&
license=GkfLmRm1PRkJGNjE => Connection refused
Warning: Please check the config in the /opt/tingyun-oneagent/conf/oneagent.yml or the
network status

Solution: Restore network connectivity between the host running UniAgent and the Agent Collector host.

10. The network between UniAgent and Agent Collector is normal, but there is no host information in the dashboard

Solution: Verify that the network between the Agent Collector and DC is normal, and that the deployed Collector appears in the dashboard's Collector list.

11. Troubleshooting after issues occur

If the UniAgent service keeps restarting abnormally, check the service log with:

sudo journalctl -f -u tingyun-oneagent

If UniAgent is abnormal, you can stop the service with:

systemctl stop tingyun-oneagent

12. Linux preload module explanation

Preload is a Linux system-supported module preloading technology. When the process loader loads a process, it first inserts the specified preload module, then inserts other modules required by the process. The preload module is always after the loader and before other modules in the module list.

13. How to check if a process has loaded the agent and the location of the agent log

To check if a process has loaded the agent:

cat /proc/1156/maps |grep tingyun

To check the agent log path:

ls -l /proc/1156/fd |grep tingyun

Windows

1. What permissions are required to install or uninstall the agent?

Installation and uninstallation must be performed with administrator privileges.
Ensure that no antivirus software on the host is blocking the installation or uninstallation process.

2. What is the installation path for UniAgent?

The installation path is C:\Program Files\tingyun\monitor.

3. Is monitoring applications inside Docker containers supported?

Currently, monitoring applications inside Docker containers is not supported. Only applications deployed directly on the host are supported.

4. Why are some processes not detected by UniAgent?

Possible reasons:

The monitoring technology does not support the process. Currently, Windows UniAgent only supports: Java applications, .NET Web applications, and .NET Core Web applications.
Ensure the server is running and the process has started.
There may be a delay in interaction between UniAgent and the Guanyun AIOps platform. If so, try again later.
Ensure the process is not disabled on the Deployment Management > UniAgent page in the dashboard.

5. What is the process name for IIS websites?

The process name for IIS websites is w3wp.exe, and the process username is the name of the website's application pool.

6. How to troubleshoot if a process is not being monitored?

For version 2.5.4.0 and above, you can run C:\Program Files\tingyun\monitor\bin\manager.exe to check the detection result:

Check if the system service is running normally.

Antivirus software may block the agent's system service. Ensure the service named TingyunMonitor is in the running state.

If the TingyunMonitor service does not exist, reinstall the agent and ensure it is not blocked by antivirus software during installation.

If the TingyunMonitor service is stopped, open the service list and start the service.
Check if the UniAgent type device in Device Manager is running normally.

The path to open Device Manager may vary by OS:
- Computer -> Properties -> Device Manager
- or This PC -> Manage -> Device Manager
- or This PC -> Properties -> Device Manager
- or Control Panel -> System and Security -> Device Manager
- or Control Panel -> Hardware and Sound -> Device Manager
Antivirus software may block agent device operations during installation. Ensure the UniAgent type device is running normally.

If the UniAgent type device does not exist, reinstall the agent and ensure it is not blocked by antivirus software during installation.

Linux​

Windows​

Linux

Windows