Linux Agent Installation Guide

This document shows how to install and manage the Linux agent for Unmeshed Job Scheduling Platform. The agent is a Java-based application which runs natively on Linux machines and executes the scheduled jobs as configured on the Unmeshed Platform. The integration between agent and Unmeshed platform is protected by an access key and secret and happens over an HTTPS connection.

To add an agent, we require the installation of Unmeshed CLI. You can find the guide here.

Run the following commands and follow the prompts to complete the agent installation. It will download the required files automatically and place them in your selected folder.0

To uninstall the agent, you can use the CLI

The CLI has other commands that can list agents installed in the host. You'd only need a single agent installation typically, but if you need to install multiple agents for any reason, the CLI supports this in its prompts.

Go to the installation folder for your agent. Edit the processes.yaml file to configure your agent:

The file should contain the following configuration:

The UNMESHED_BASH_CUSTOM_WORKERS parameter allows you to create multiple custom bash workers with different configurations. This is useful when you need different concurrency limits or want to separate workloads by namespace.

Each worker specification follows the format: namespace:name:maxConcurrentWorkers:false

• namespace: The namespace for this worker (e.g., "default", "prod", "dev")
• name: The worker name identifier that will be used in job definitions
• maxConcurrentWorkers: Maximum number of concurrent jobs this worker can handle
• ioThread: Must be set to false for Linux agents (required parameter)

Single Custom Worker:

This configuration will query for jobs in the prod namespace with the name high-priority-bash and can run up to 100 concurrent tasks.

Multiple Custom Workers:

This configuration creates three workers:

• default:bash.servername.standard:50:false - Namespace default, jobs named standard-bash, concurrency of 50
• prod:bash.servername.priority:100:false - Namespace prod, jobs named high-priority-bash, concurrency of 100
• dev:bash.servername.testing:25:false - Namespace dev, jobs named testing-bash, concurrency of 25

No Custom Workers (Default):

The agent creates logs in the working directory. Look for the following log entry to confirm successful startup:

You should see a log entry similar to:

1. Service fails to start:

   • Check file permissions: ls -la <directory name used in installation>
   • Verify Java installation: java -version
   • Check service logs: sudo journalctl -u <service name used in installation> -n 50

2. Agent cannot connect to Unmeshed platform:

   • Verify network connectivity: ping <your-unmeshed-server>
   • Check authentication credentials in processes.yaml
   • Verify firewall settings

3. Permission denied errors:

   • Ensure the service user owns the <directory used in installation> directory
   • Check file permissions: chmod +x <directory used in installation>/start_monitor.sh

4. Java memory issues:

   • Adjust JVM memory settings in processes.yaml:
     • -Xms1024m (minimum heap size)
     • -Xmx1024m (maximum heap size)

The agent creates several log files:

• worker.log - Main worker process logs
• monitor.log - Monitor process logs
• systemd logs - Service management logs

1. File Permissions: Ensure only authorized users can access the agent configuration files
2. Network Security: Use HTTPS connections to the Unmeshed platform
3. Authentication: Keep your auth ID and token secure and rotate them regularly
4. Service User: Run the service with minimal required privileges
5. Firewall: Configure firewall rules to allow only necessary outbound connections

Adjust based on your system's CPU cores and workload:

Optimize network communication:

1. Service Auto-restart: The systemd service is configured to automatically restart if the process crashes
2. Log Rotation: Consider implementing log rotation for long-running deployments
3. Monitoring: Set up monitoring for the service status and resource usage
4. Backup: Regularly backup your processes.yaml configuration file
5. Updates: Keep your Linux system updated for security patches
6. Resource Monitoring: Monitor CPU, memory, and disk usage during operation

• Creating Client Credentials
• Worker Configuration
• Process Execution
• Agent Management
• Windows Agent Installation
• IBMi/AS400 Agent Installation