Tracking Package Updates and Reboot Status

Server Scout provides comprehensive monitoring of package updates and system reboot requirements, helping you maintain security and stability across your Linux infrastructure. This functionality is essential for tracking security patches and ensuring systems are properly restarted when required.

How Package Update Monitoring Works

Server Scout's collect_daily() function automatically checks for pending updates using your distribution's native package manager. This process runs once daily and queries the following package managers based on your system:

• RHEL/CentOS/Fedora: Uses dnf or yum to check for available updates
• Debian/Ubuntu: Uses apt to identify pending package updates
• SUSE/openSUSE: Utilises zypper for package status checks

The monitoring agent executes these commands safely without modifying your system, providing read-only visibility into available updates.

Reboot Status Detection

Server Scout employs different methods to detect when a system reboot is required:

Debian and Ubuntu Systems

On Debian-based distributions, Server Scout monitors the /var/run/reboot-required file:

# This file is created when packages require a system restart
ls -la /var/run/reboot-required

The system automatically creates this file when critical packages (kernel, systemd, glibc) are updated and need a restart to take effect.

RHEL, CentOS, and Fedora Systems

For Red Hat-based distributions, Server Scout uses the needs-restarting utility:

# Check if system reboot is needed
needs-restarting -r

# Check which services need restarting
needs-restarting -s

This tool, part of the yum-utils package, provides detailed information about restart requirements at both system and service levels.

Viewing Update Information

The server detail page displays comprehensive update and reboot status information in several key areas:

Update Summary Panel

1. Total Available Updates: Shows the count of all pending updates
2. Security Updates: Highlights critical security patches requiring attention
3. Last Update Check: Displays when the system last checked for updates

Reboot Status Indicator

The reboot status appears prominently with clear visual indicators:

• Green: No reboot required
• Amber: Reboot recommended for optimal performance
• Red: Reboot required for security or stability

Setting Up Update Alerts

Configure proactive alerts to stay informed about critical updates:

Security Update Alerts

1. Navigate to Settings > Alerts in your Server Scout dashboard
2. Select Create New Alert Rule
3. Choose Security Updates as the condition type
4. Set your threshold (e.g., alert when more than 5 security updates are pending)
5. Configure notification channels (email, Slack, webhook)

Reboot Required Alerts

Create alerts for systems requiring restarts:

Alert Type: Reboot Required
Condition: When reboot_required = true
Frequency: Immediate notification
Recipients: System administrators

Best Practices for Patch Management

Regular Update Schedules

Establish consistent update windows for different server categories:

• Development servers: Weekly updates with immediate reboots
• Staging environments: Bi-weekly updates with testing validation
• Production systems: Monthly updates during maintenance windows

Prioritising Security Updates

Server Scout's security update classification helps you prioritise patches:

1. Critical security updates: Apply within 24-48 hours
2. Important security updates: Apply within one week
3. Standard updates: Apply during regular maintenance cycles

Coordinating Reboots

When Server Scout indicates reboot requirements:

1. Plan maintenance windows around business requirements
2. Coordinate with application teams for service dependencies
3. Use staged approaches for clustered or load-balanced services
4. Verify service restoration post-reboot using Server Scout's monitoring

Monitoring After Updates

Post-update verification ensures system stability:

• Check Server Scout dashboards for service status changes
• Monitor system performance metrics for anomalies
• Verify that reboot-required flags are cleared
• Confirm all expected services are running

Automation Integration

Server Scout's API allows integration with configuration management tools:

# Example: Query pending updates via API
curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://app.serverscout.ie/servers/{server_id}/updates"

This enables automated patch management workflows whilst maintaining visibility through Server Scout's monitoring capabilities.

Regular monitoring of package updates and reboot status through Server Scout ensures your infrastructure remains secure, stable, and compliant with your organisation's maintenance policies.