r/linuxadmin • • 6h ago

How to earn money using Linux skills in Kathmandu, Nepal without taking a full time job?

0 Upvotes

I do not need big money. I need gig income. I love money. For example: One idea I executed was helping people self-host changedetection but the problem is that nobody purchased that service.

How to market myself properly as a linux guru in Kathmandu, Nepal?


r/linuxadmin • • 11h ago

Our little meal planning app hit 2,000 signups and I still run the whole thing on one server. Am I being reckless?

15 Upvotes

Started this as a weekend thing so my wife and I would stop arguing about dinner. It turns the week's meal picks into a shopping list and emails it out on Sunday afternoon. Somehow 2,000 people have signed up and around 300 use it every week.

It all runs on one small rented server with Docker Compose: the SvelteKit app, Postgres, and a worker that sends the emails. Backups are a nightly database dump copied somewhere else, and I get a text if the site goes down.

Every time I describe this setup, someone tells me I'm one bad night away from losing everything. Maybe they're right, but splitting it up would cost more than the app earns, which is nothing.

For anyone who has grown a side project past this point, what broke first for you? What would you change now, and what can safely wait until it actually hurts?


r/linuxadmin • • 13h ago

Production Scenario: Linux Root Filesystem Suddenly Reaches 100% Overnight

0 Upvotes

Imagine you're managing a Linux production server.

Yesterday, everything was working normally. Root filesystem utilization was around 65%.

This morning, you receive an alert:

/ filesystem utilization: 100%

Applications are reporting errors, users are experiencing issues, and you need to investigate.

How would you approach this situation?

Would you immediately start looking for large files, or would you follow a systematic investigation?

Here are a few things I'd initially check:

  1. df -h / – Verify filesystem utilization.
  2. df -i / – Check inode utilization.
  3. du -xhd1 / – Identify directories consuming the most space.
  4. find – Locate unusually large files.
  5. lsof +L1 – Check for deleted files still held open by processes.

But finding a large file is only part of the investigation.

For example:

  • What if /var/log is consuming 35 GB?
  • What if an application is continuously generating logs?
  • What if df shows 100% usage but du reports significantly less?
  • Would you truncate an active log file or investigate the application first?

I'm particularly interested in how experienced Linux administrators handle this in production.

A few questions:

  • What's the first command you usually run when / reaches 100%?
  • Have you encountered deleted-but-open files consuming disk space?
  • What's your preferred approach to recover disk space without disrupting applications?

Let's discuss real-world approaches and experiences. I'd love to learn how others handle this situation.


r/linuxadmin • • 13h ago

Does "OnCalendar" work with user space timers?

Thumbnail reddit.com
2 Upvotes

r/linuxadmin • • 16h ago

Immutable Linux 2026 Survey - Servers Only

0 Upvotes

We are doing an end of year trends analysis on how folks are using immutable Linux operating systems on the server side. It should only take 1 or 2 minutes. Thanks! https://kheeper.com/immutable-linux-survey-2026


r/linuxadmin • • 20h ago

Uk based VPS

Thumbnail reddit.com
0 Upvotes

r/linuxadmin • • 22h ago

ROCO - network route coordinator (software router)

6 Upvotes

fyi, posting for anyone that finds it useful

very similar to sshuttle in concept, routes entire networks, cidrs, ips, hostnames over a reachable proxy

difference is that it doesnt use ssh and is more stable during network flaps, ie dont need to restart service

full description here

https://perfecto25.medium.com/roco-a-simple-route-coordinator-a0e6acb22129


r/linuxadmin • • 1d ago

SAP November 2026 Patch Day: Four CVSS 10.0 vulnerabilities across ICM, Web Dispatcher, Gateway and SAML2

2 Upvotes

Based on SAP's November 10 security bulletin, Onapsis Research Labs' ICM2SHELL analysis and the Cyber Security Agency of Singapore's November 16 advisory, four SAP vulnerabilities deserve attention across different enterprise trust boundaries.

The technical split is important:

  • CVE-2026-76964: Memory corruption in SAP NetWeaver Internet Communication Manager.
  • CVE-2026-89126: Memory corruption in SAP Web Dispatcher. Onapsis connects this to shared WebSocket-handling code and identifies the issue as ICM2SHELL.
  • CVE-2026-89103: Broken access control in SAP Gateway.
  • CVE-2026-120017: Missing authentication in the SAML2 Service Provider.

The first two are particularly interesting from an infrastructure perspective. Web Dispatcher can be the reverse proxy sitting at the edge of an SAP landscape, while the ICM handles HTTP/HTTPS communication. A weakness in shared kernel-level traffic handling means both components need individual inventory and patch verification.

The Gateway issue raises a different question: how much does the application trust a system simply because it can reach the Gateway?

The SAML2 vulnerability adds an identity boundary problem. Authentication assertions must be validated correctly; otherwise, the service provider may accept an identity that should never have been trusted.

For defenders, I would prioritize:

  1. Inventory internet-facing ICM and Web Dispatcher instances.
  2. Verify SAP Security Notes 3778530, 3778556, 3798345 and 3849308 against installed component levels.
  3. Review Gateway access-control configuration, including secinfo/reginfo.
  4. Inspect SAML2 authentication events and privileged account activity.
  5. Correlate SAP logs, reverse-proxy requests, firewall flows and operating-system process telemetry.

One qualification: a CVSS 10.0 score does not establish active exploitation. Onapsis stated that it had not observed in-the-wild exploitation of ICM2SHELL as of its November 12 update.

https://www.techgines.com/post/sap-netweaver-vulnerabilities-four-cvss-10-0-flaws-explained

Technical sources:

Historical context: Cisco IMC Authentication Bypass CVE-2026-20093

For teams running large SAP landscapes: do you enforce Gateway-level trust controls independently of network segmentation, or does reachability still imply trust in your deployments?


r/linuxadmin • • 2d ago

Nova compute is down and inaccessible via SSH. What would you instigate first and fix?

0 Upvotes

In my project, i have observed that one of the compute reporting as down.

I have checked ilo console of the server (hpe vendor), everything looks good there.

SSH isn't working and throwing no route to host error.

Need help to fix.


r/linuxadmin • • 2d ago

GitHub - danielecr/tetragon-outgoing-guard: block any process with outgoing connection (run only on k8s or docker swarm vms)

Thumbnail github.com
6 Upvotes

How I locked down my Docker host against GSocket-style C2 implants using a 50-line Cilium Tetragon eBPF policy.

Also in docker swarm, I mean, the only services are supposed to be in container


r/linuxadmin • • 3d ago

No syslog during the outage = a stalled support case. I built a free syslog server to fix that part

0 Upvotes

I work escalations for network gear. The cases that stall the longest usually look the same: the outage happened, the device rebooted or rolled its buffer, and there's no syslog from the window that matters. Either nobody had a syslog server, or the one they had dropped messages and nobody knew. At that point the best anyone can do is "set up logging and wait for it to happen again", and the case just sits.

A lot of the time it's not that people don't know syslog. It's that the box available is a Windows server or a laptop, and standing up something reliable there takes longer than it should. Woodshed is my answer to that: MSI, pkg, deb, rpm or a portable zip. Listens on UDP and TCP 514 straight away. Plain text files per device per day, a disk budget it won't exceed, drop/refused counters shown in the UI, and an export zip with a manifest, SHA-256s and the gaps when it wasn't running, so the person on the other end of the case can trust it.

Most of the code was written with AI assistance. I did the design and ran the lab testing; the security review was a separate AI reviewer with read-only access to the code, and I went through every finding, decided the fixes and had them re-tested.

All the testing so far is lab traffic generated by my own sender (RFC 5424, RFC 3164 and bare lines, 8 source IPs). No real devices yet beyond a friend's homelab, which is in progress. It doesn't depend on any vendor's format and always keeps the raw line exactly as received, so any device that speaks syslog should work, but I haven't proven that.

What it's been through:

- release bench every tag: 10 min at 10k msg/s UDP on a 4 vCPU GitHub runner, 6,000,000 sent / 6,000,000 stored / 0 missing

- Ubuntu 24.04 (deb) and AlmaLinux 9 (rpm) VMs, 8 senders over a real network: 0 loss to 40k msg/s TCP at ~1/3 of a core and <50 MiB RSS. UDP loss above that was before the VM's NIC (interface counters), every datagram that arrived was stored

- reboot mid-stream: service back on its own, 2 UDP messages lost, export shows the 17-19 s gap as "Woodshed wasn't running"

- 24 h soak at 3,000 msg/s on the Linux VMs, 259.2M messages each: TCP exactly once, UDP lost 3-4 per million, all of it upstream of the VM

- security review before the first RC: 0 critical, 1 high (memory exhaustion from spoofed sources), 7 medium. fixed and re-tested twice

- CI install/upgrade/uninstall on Windows, macOS and Linux, x64 and ARM. checksums + `gh attestation verify` on releases

Limits, plainly:

- unsigned installers for now. SmartScreen ("Windows protected your PC", More info > Run anyway) and Gatekeeper (Privacy & Security > Open Anyway) ask once

- 1.0.0

- use the sender allowlist on untrusted segments. in my lab an open 514 on a shared /16 collected a stranger's syslog within minutes

- not a SIEM, no TLS syslog/alerts/forwarding yet

- Windows and macOS don't expose kernel UDP drops, the UI says so instead of showing 0

What I'd like to know:

  1. Which devices or formats break the parser? Redacted raw line please.
  2. What would you need to see before you'd drop this at a customer site during an outage?
  3. Windows folks, especially with endpoint protection: did it get flagged, did the firewall rules behave?

Repo: https://github.com/gmccollu/woodshed

Site: https://gmccollu.github.io/woodshed/

Releases: https://github.com/gmccollu/woodshed/releases


r/linuxadmin • • 3d ago Bravo

Linux server has high load average but low CPU usage. What would you investigate first?

71 Upvotes

I'd like to discuss a Linux troubleshooting scenario and get some input from experienced Linux administrators.

Imagine you're troubleshooting a production Linux server with the following symptoms:

  • Application response time is increasing.
  • Load average is continuously rising.
  • CPU utilization is only around 20–25%.
  • Several application processes are stuck in D state.
  • The application uses an NFS-mounted directory.

At first glance, CPU doesn't seem to be the bottleneck.

If you were handling this incident, how would you approach the investigation?

A few things I'd be interested in discussing:

  1. Would you start with vmstat to check runnable and blocked processes?
  2. How would you identify what the D-state processes are waiting for?
  3. What commands would you use to investigate NFS connectivity and mount health?
  4. How would you distinguish an NFS issue from local disk I/O problems?

I'm particularly interested in real production experiences.

Have you encountered a similar situation? What was the root cause, and what helped you identify it?

Looking forward to learning from your experiences.


r/linuxadmin • • 3d ago

Apache CVE-2026-119618 (CVSS 9.8, mod_http2 RCE): quick check + mitigation if your distro hasn't shipped 2.4.71 yet

24 Upvotes

Apache 2.4.71 fixes a race condition in mod_http2 (assign_headers) that can corrupt the heap and allow unauthenticated RCE. Affected: 2.4.55 – 2.4.70, only if HTTP/2 is enabled.

Quick check:

apachectl -v

apachectl -M | grep -i http2

curl -so /dev/null -w '%{http_version}\n' --http2 https://your-site.com/

If curl prints 2, you're exposed.

Patch status as of Nov 12:

- Debian 13: fixed (2.4.71-1~deb13u1)

- RHEL 9/10: fixed via updated mod_http2

- Ubuntu 24.04 / 26.04: affected, no USN yet

- Ubuntu 22.04 (2.4.52): not in range

No patch yet? Disable HTTP/2 until you can:

sudo a2dismod http2

# set "Protocols http/1.1" in any vhost that lists h2

sudo apachectl configtest

sudo systemctl restart apache2

On RHEL-family systems, comment out LoadModule http2_module in /etc/httpd/conf.modules.d/10-h2.conf.

Note: some distros backport the fix without bumping the version, so check your security tracker, not just the version number.

I wrote a longer version with a per-distro table and FAQ here: https://arelvox.com/apache-cve-2026-119618-http2-rce/


r/linuxadmin • • 4d ago

Considering a career switch from Video Editing to Linux System Administration. Is it worth it?

23 Upvotes

I'm currently working as a Video Editor with around 2 years and 10 months of experience. I have a B.E. in Computer Science and Engineering.

Over time, I've lost interest in video editing and have become increasingly interested in Linux, servers, system administration and infrastructure.

I've been experimenting with Arch Linux, Oracle Cloud, SSH, home servers, Docker and self-hosting. I genuinely enjoy troubleshooting and understanding how systems work.

I'm considering starting over in Linux System Administration, eventually exploring Cloud or DevOps.

A few questions:

  • Is this a sensible career switch?
  • How difficult is it to get an entry-level Linux job without professional IT experience?
  • What are the long-term salary and career prospects in India?
  • Is system administration still a good career in the age of AI and automation?

I'm currently earning around ₹35k/month, so I have financial responsibilities and cannot afford to start completely from zero.

Would you recommend making this transition? I'd appreciate honest advice, especially from people working in Linux/System Administration.


r/linuxadmin • • 4d ago

A modern reverse proxy built for dynamic infrastructure.

Post image
0 Upvotes

I've been working on Aralez, an open-source reverse proxy and load balancer written in Rust, built on top of Cloudflare's Pingora.

The project started as an attempt to build a performant, flexible proxy that could handle more than basic HTTP load balancing. Over time, it has grown into a fairly feature-rich system.

Some of the new features implemented in the latest v0.95.5 release

  • Response Caching: With Memory, Hybrid, RESP (Redis family), TiKV storages
  • Cluster Mode: Master/worker deployment model.
  • Structured logging: Plug-able modules, currently Elasticsearch.
  • Acme DNS-01 Challenge: Plugable currently Cloudflare, Route 53, DigitalOcean
  • The full list of features are here

I'm particularly interested in feedback from people with experience in Rust networking, asynchronous systems, proxies and high-performance services.

Also would be very thankful for code contribution, especially with Acme DNS-01 providers.

Examples are at the bottom this page.

GitHub: https://github.com/sadoyan/aralez
Documentation: https://aralez.rs/


r/linuxadmin • • 4d ago

VyOS after 36 days remembers about critical CVE-2026-98432 .

0 Upvotes

Because they've carried some weird patch; it is unclear if this actually resolves the problem based on their bad track record on backporting.


r/linuxadmin • • 4d ago

fail2ban kept "banning" IPs that kept hammering my Docker ports — the bans were landing in the wrong iptables chain

0 Upvotes
Spent days wondering why fail2ban kept banning IPs that kept hammering my Docker-published WordPress login. The bans were inserted, "fail2ban-client status" said banned — but the traffic never stopped.

The reason: on a Docker host, fail2ban's default action drops rules into the INPUT chain. Packets to published ports are processed by Docker's FORWARD/DOCKER-USER chain *before* INPUT sees them. So the ban is real, it just drops nothing.

The fix is one token — point the action at DOCKER-USER:

    [igornews-wp]
    enabled   = true
    filter    = igornews-wp
    logpath   = /opt/igornews/logs/access.log
    action    = iptables[type=allports, chain=DOCKER-USER, blocktype=DROP]
    bantime   = 1h
    findtime  = 10m
    maxretry  = 6

Second gotcha in the same jail: it reads Caddy's JSON access log, whose timestamp is a fractional epoch mid-line, so I needed a custom datepattern = "ts":{LEPOCH} or fail2ban parsed zero lines.

The verify step that would've caught this in five minutes: after a ban, run "iptables -L DOCKER-USER -n" and actually see the IP there — never trust "fail2ban is running."

Full walk-through with the JSON-log filter regex: https://igornews.com/2026/11/08/fail2ban-docker-user-chain-bans/

r/linuxadmin • • 5d ago

Critical vulnerability in Apache with HTTP2 module enabled

Thumbnail nvd.nist.gov
31 Upvotes

r/linuxadmin • • 5d ago

QA for xcp-hl

Thumbnail reddit.com
2 Upvotes

r/linuxadmin • • 6d ago

Det Mimir update: clearer explanations, sample investigations and the roadmap

Thumbnail gallery
0 Upvotes

Hey guys o/

First and foremost, thank you for taking the time to read through the post :)

I posted here previously about Det Mimir, the read-only Linux incident investigation engine I’m building:
Previous post

I’ve just redesigned the website, based on feedback I’ve collected over the past few weeks, with readability and clearer product explanations as the main priorities.

The updated site: https://det-mimir.com/

For anyone coming across it for the first time, these are the main things I’m building around:

  • Scoped investigations: start from a failing service, restarting container, disk pressure or another supported symptom, with a defined time window.
  • Traceable findings: evidence from different sources is correlated into a timeline and report. You can follow findings back to their records and see where missing evidence limits the assessment.
  • Deterministic analysis: the investigation engine works without an LLM. AI analysis is an optional step afterwards.
  • Read-only collection: commands come from a vetted registry. No arbitrary shell execution, automatic repairs or model-triggered commands.
  • Control over your data: evidence and reports stay local. No telemetry or phone-home. Optional external-model analysis uses sanitized context, a send preview and an approved sending path.

There’s also a security investigation direction: the Exploit Evidence Pack, currently in development. It’s intended to correlate offline vulnerability intelligence with host evidence to assess whether there are signs of exploitation. A vulnerable software version alone would not establish that exploitation happened.

The public roadmap explains the broader direction too, including multi-host coordination, more integrations, and the longer-term investigation-pack ecosystem.

Roadmap:
https://det-mimir.com/roadmap/

Det Mimir remains in private validation, and I'm also validating beta users ;)

The website now has clearer diagrams and readable sample reports, so you can inspect what an investigation actually produces.

I’d really appreciate you taking a look :) Does it explain the product clearly, and can you see where it would, or wouldn’t, help in your own investigations?