Services and processes

JelinaOS uses industry-standard service management to manage all system services and applications centrally. Common operations cover most daily maintenance tasks.

Core services

The following services work together while a device runs; actual service names may vary by device:

Service	Purpose
Container runtime (docker / containerd)	Runtime foundation for containerized applications
Device agent (jelina-jelinvisor)	Cloud connectivity, status reporting, and update execution
Application service host (jelina-services-host)	Hosts application services in the /app area and coordinates recovery on faults
Registration service (jelina-register)	Device cloud registration
Watchdog (jelina-watchdog)	System health protection
Secure channel	Encrypted connection between device and cloud
Disk space monitor (jelina-free-space-monitor)	Storage health monitoring and protection
Time synchronization (jelina-time-sync)	Synchronizes system and hardware clocks
System mounts (jelina-bind-mount / jelina-mount-overlay-*)	Mounts kernel files and the application area
Update rollback (jelina-rollback@)	Rolls back system/kernel updates

Common operations

# View service status
systemctl status <service-name>

# Start / stop / restart
systemctl start <service-name>
systemctl stop <service-name>
systemctl restart <service-name>

# Configure startup at boot
systemctl enable <service-name>
systemctl disable <service-name>

System configuration

System configuration is centralized and supports layered overrides:

• /etc/jelina.conf — Default system configuration.
• /etc/jelina.conf.d/*.conf — Override files loaded in order; later files take precedence.

After configuration changes, restart the relevant services as needed for changes to take effect.

Inspect processes

ps aux                # View all processes
top                   # Monitor processes in real time, sorted by CPU/memory

View logs

# View service logs
journalctl -u <service-name>

# Follow logs in real time
journalctl -u <service-name> -f

# View the last 100 lines
journalctl -u <service-name> -n 100

Device agent logs are recorded separately for cloud connectivity troubleshooting:

tail -f /var/log/jelinvisor

Manage startup at boot

There are two ways to enable automatic application startup:

Method	Applies to	Description
Containerized applications	Containers	Configure --restart always to restore automatically with the system
Native applications	ProgramSets/services	Declarative configuration or systemctl enable

Cloud service management

With JelinaCloud connected, you can also:

• Restart device services: Restart application services across all devices in a fleet.
• Shut down/restart devices: Perform remote shutdown and restart.
• Control devices: Perform detailed operations on individual devices.

See fleet management and remote maintenance.

Troubleshooting suggestions

• If a service fails to start, inspect its logs first to identify the cause.
• Check dependent services; containerized applications depend on the container runtime.
• Services with restart policies recover automatically after abnormal exits. Use logs to determine why they restarted.