✳ WORLDHQ.COM
← Return to Headquarters
Department of Unusual Computer Affairs

Linux.
Rather
well sorted.

Professional Linux consultancy for systems that are behaving strangely, servers that have developed opinions of their own, and administrators who would quite like to go home on time.

From a baffling boot failure to a storage system with commitment issues, WorldHQ brings methodical investigation, practical experience and a healthy respect for the command line.

Root cause analysis · Not root-cause astrology
ALL SYSTEMS NOMINAL* *STATEMENT UNDER INVESTIGATION
CHECK THE LOGS ✳ QUESTION THE OBVIOUS ✳ NEVER TRUST A BACKUP YOU HAVEN'T TESTED
Our areas of expertise

Practical skills.
Improbable incidents.

Linux is wonderfully logical. Unfortunately, the people, networks, disks, applications and occasional gremlins around it do not always read the documentation. We investigate, diagnose, repair and help prevent repeat performances.

01 / SYSTEMS

Linux Administration

From a fresh installation to a server that has been running for years and is now too important to reboot without a committee meeting.

  • Linux installation and configuration
  • systemd services and boot problems
  • journalctl, logging and logrotate
  • Package management and updates
  • Performance and resource analysis
02 / STORAGE

Disks, LVM & Filesystems

Storage problems have an uncanny talent for appearing precisely when nobody has a current backup. We prefer to meet them before that moment.

  • LVM volumes, volume groups and snapshots
  • RAID planning and recovery considerations
  • Filesystem capacity and performance
  • LUKS encryption and secure storage
  • Disk replacement and data migration
03 / NETWORKS

Networking & SSH

When a server can reach the internet but not the machine next to it, we follow the packets rather than consulting the nearest crystal ball.

  • IP addressing, routing and DNS
  • SSH configuration and public-key authentication
  • Firewalls and remote access
  • Service exposure and security hardening
  • Network fault diagnosis
04 / AUTOMATION

Bash & Automation

If a task is repetitive, tedious or likely to be forgotten at 2 am, there may be a perfectly good reason to automate it.

  • Bash scripts and command-line workflows
  • Scheduled jobs and unattended tasks
  • Shell completion and safer scripts
  • Monitoring and routine maintenance
  • Reducing human error through automation
05 / SECURITY

Security & Encryption

Security should be more than installing a firewall, choosing a mysterious password and hoping the internet has other plans for the evening.

  • SSH security and access restrictions
  • Least-privilege configuration
  • LUKS disk encryption
  • Service exposure and firewall rules
  • Logging, auditing and incident investigation
06 / INVESTIGATION

Troubleshooting & Recovery

The server says it is fine. The users say it is broken. The monitoring system says nothing at all. This is where the interesting work begins.

  • Boot failures and service outages
  • Log and error analysis
  • Disk, memory and CPU bottlenecks
  • Unexpected behaviour and intermittent faults
  • Root-cause analysis and corrective action
The WorldHQ method

Less guesswork.
More evidence.

We favour careful diagnosis, understandable explanations and practical fixes. A command that appears to work is encouraging. Knowing why it works is considerably better.

⌕

Investigate first

Establish what is happening, gather logs and inspect the configuration before making changes. Rebooting is not a diagnostic philosophy.

⌘

Explain the solution

Understand what failed, why it failed and how to avoid repeating the incident. Mystery is entertaining. Unnecessary operational mystery is not.

◈

Plan for recovery

Consider failure modes, backups, monitoring and documentation. Hope is an emotion, not a disaster recovery strategy.

Recovered from the archives

The service
insists it's fine.

A familiar WorldHQ incident. The service manager reports a running service, the application is unavailable, and the logs contain a small novel written entirely in errors.

The correct response is not to shout at the monitor. Usually.

# Begin the investigation
root@server:~# systemctl status reality.service
Active: active (running)
Application response: absolutely not

root@server:~# journalctl -u reality.service -b
Error: dependency unavailable
Error: configuration not found
Error: previous error not understood

root@server:~# systemctl cat reality.service
# Ah. There it is.

# No servers were shouted at during this investigation.
A small but important principle: We aim to leave you with a better-understood system, not a collection of mysterious commands that only work when performed by the person who originally typed them.
A note from the Department

Your Linux server should work for you.
Not the other way around.

Whether you're facing a stubborn service, a storage puzzle, a security concern or a Linux system that has developed an unusual interpretation of normal behaviour, WorldHQ can help you investigate the problem and find a practical way forward.

Linux consultancy by John Hodson, Principal Linux & Proxmox Specialist.
The root password remains classified.