---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Validate Linux installation

# Validate Linux installation {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

After installing the Agent Client Collector on a Linux
system, validate the installation by ensuring it was completed properly.

## Before you begin

Install the Agent Client Collector on a Linux system
(see [Install Agent Client Collector on a Linux system](https://servicenow-prod.fluidtopics.net/gnStIIij9QHlEGg9eHnQWA "Install Agent Client Collector using a package distribution tool. Before that, you can manually install the Agent Client Collector on a few machines to verify that your agents contain the correct policies and checks.")).

Role required: agent_client_collector_admin

## Procedure

1. Run the `# systemctl status acc` command.  
   The active (running) indicator appears when the service is running properly.

       # systemctl status acc
       ● acc.service - Agent-Now ACC
       Loaded: loaded (/usr/lib/systemd/system/acc.service; enabled; vendor preset: disabled)
       Active: active (running) since Mon 2022-04-25 14:10:24 UTC; 6 months 23 days ago
       Main PID: 2693 (acc)
       Tasks: 10 (limit: 512)
       Memory: 143.4M (limit: 192.0M)
       CPU: 12h 57min 50.442s
       CGroup: /system.slice/acc.service
       └─2693 /usr/share/servicenow/agent-client-collector/bin/acc start --config-file
       /etc/servicenow/agent-client-collect...

2. View the encrypted api-key and agent-key-id in use by running the `grep -E
   '^api-key|agent-key-id'
   /etc/servicenow/agent-client-collector/acc.yml` command.  

       # grep -E '^api-key|agent-key-id' /etc/servicenow/agent-client-collector/acc.yml
       api-key: "encrypted:adskfjldfjlasd+ajflksadjmoreunreadablestringasdfdfkdjksdjaasdfas"
       agent-key-id: b4ac2ab4ac2b4ac2b4ac2b4ac2b4ac2b4ac2b4ac2b4ac2b4ac2b4ac2b4ac2b4a

   Note:  
   The grep command must appear on a single line.
3. View the agent's connection with its backend URL by running the `grep
   'successfully connected'
   /var/log/servicenow/agent-client-collector/acc.log` command.  

       # grep 'successfully connected' /var/log/servicenow/agent-client-collector/acc.log
       2022-11-17T19:03:17.94 [INFO] [agent] successfully connected to the url:
       wss://MY_BACKEND_FQDN:MY_BACKEND_PORT/ws/events

   Note:  
   The grep command must appear on a single line.
4. Verify the unique agent ID by running the `# echo $(hexdump -e '/1
   "%02x"' /var/cache/servicenow/agent-client-collector/agent_now_id)` command.  

       # echo $(hexdump -e '/1 "%02x"' /var/cache/servicenow/agent-client-collector/agent_now_id)
       14b4443df6d2394d

   The indicated agent ID appears on the Agents page in an instance (AllAgent Client CollectorAgents) with Status = Up and Host data collection = Collected (both appearing in green).
   Figure 1. Linux agents - green status   

*[\>]: and then