Patch and Reboot the Hubble Application Server
The Hubble App Server Patch / Reboot Tool is a Windows utility that lets operations staff safely patch and reboot Hubble application servers. It connects to remote Linux servers over SSH, gracefully stops Docker containers, applies OS updates, and reboots the server in a guided, step-by-step flow.
Before You Start
On your Windows workstation, you require:
- Windows 10/11 or Windows Server 2022 or 2025
- The
HubbleAppServerPatch_Reboot.exefile - SSH (port 22) network access to the target server
On the target server, you require:
- A user account with sudo privileges
- Docker running with Hubble containers under /etc/hubble
Running the Tool
Step 1: Launch and Connect
- Double-click HubbleAppServerPatch_Reboot.exe. A console window will open.
- Enter the target server hostname or IP address.
- Enter your username and password. Password input is masked as you type.
- The tool connects via SSH. If the connection fails, verify your credentials and network access to port 22.
Step 2: Container Status Check
The tool automatically checks which Docker containers are currently running and displays the results. No changes are made at this point.
Step 3: Choose an Action
Select one of the following options:
| Option | Action | What It Does |
|---|---|---|
| 1 | Run patching commands (OS update) and reboot | Stops containers, applies OS updates, reboots server |
| 2 | Reboot server only (no patching) | Stops containers, reboots server |
| 3 | Exit | Closes the session without making any changes |
Step 4: Execution
If you select option 1 or 2, the tool will:
- Stop all Docker containers gracefully via /etc/hubble/stop.sh. Containers typically stop within a minute. The tool will wait up to 5 minutes if needed before timing out.
- (Option 1 only) Apply OS patches, automatically detecting the server OS. Docker packages are always excluded to avoid compatibility issues.
- Reboot the server and close the SSH session.
Note: After reboot, manually verify the server is healthy. See the Post-Reboot Checklist below.
Post-Reboot Checklist
Allow 2 to 5 minutes for the server to come back online, then verify the following:
| # | Check | How |
|---|---|---|
| 1 | Server is reachable via SSH | ssh username@host |
| 2 | Docker service is running | sudo systemctl status docker |
| 3 | All Hubble containers are running | sudo docker ps |
| 4 | If containers are not running, start them manually | cd /etc/hubble then sudo ./start.sh |
| 5 | Application is healthy | Access the Hubble application URL in a browser |
| 6 | Review patch results | Check hubble_app_patch.log on your workstation |
Logging
All actions are automatically logged to hubble_app_patch.log in the same folder as the tool. This file is preserved across runs, so you can always review the history of past operations.
Security Notes
- Credentials are only held in memory during the session and are never written to disk or the log file.
- Password input is masked with asterisks to prevent shoulder surfing.