<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OhSudo — new Linux articles</title><description>New Linux articles from OhSudo: practical fixes for DevOps engineers, SysAdmins and IT folks.</description><link>https://ohsudo.com/</link><language>en-us</language><atom:link href="https://ohsudo.com/rss/linux.xml" rel="self" type="application/rss+xml"/><item><title>SELinux &quot;avc: denied&quot;: read the denial, then fix the label, the boolean or the port</title><link>https://ohsudo.com/articles/selinux-avc-denied/</link><guid isPermaLink="true">https://ohsudo.com/articles/selinux-avc-denied/</guid><description>Fix SELinux &quot;avc: denied&quot; on RHEL, Rocky and AlmaLinux: read the AVC line, then fix file labels with restorecon and semanage, booleans with setsebool, or ports.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>selinux</category><category>rhel</category><category>rocky-linux</category><category>almalinux</category><category>nginx</category><category>security</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>yum &quot;Cannot find a valid baseurl for repo&quot;: CentOS 7 reached end of life, so use the vault</title><link>https://ohsudo.com/articles/yum-cannot-find-a-valid-baseurl-for-repo/</link><guid isPermaLink="true">https://ohsudo.com/articles/yum-cannot-find-a-valid-baseurl-for-repo/</guid><description>Fix yum &quot;Cannot find a valid baseurl for repo: base/7/x86_64&quot; and the CentOS 8 mirrorlist error: point the repositories at vault.centos.org, then plan a migration.</description><pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>yum</category><category>dnf</category><category>centos</category><category>repositories</category><category>eol</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>apt &quot;dpkg was interrupted, you must manually run dpkg --configure -a&quot;: finish what was started</title><link>https://ohsudo.com/articles/dpkg-was-interrupted-configure-a/</link><guid isPermaLink="true">https://ohsudo.com/articles/dpkg-was-interrupted-configure-a/</guid><description>Fix apt &quot;E: dpkg was interrupted, you must manually run sudo dpkg --configure -a&quot;: run it, then fix what stops it: a full disk, broken packages or a failing script.</description><pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>apt</category><category>dpkg</category><category>ubuntu</category><category>debian</category><category>packages</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>apt &quot;GPG error: NO_PUBKEY&quot;: add the key the right way, without apt-key</title><link>https://ohsudo.com/articles/apt-gpg-error-no-pubkey/</link><guid isPermaLink="true">https://ohsudo.com/articles/apt-gpg-error-no-pubkey/</guid><description>Fix apt &quot;GPG error: The following signatures couldn&apos;t be verified: NO_PUBKEY&quot;: add the vendor&apos;s key to /etc/apt/keyrings with signed-by, and why apt-key is gone.</description><pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>apt</category><category>gpg</category><category>ubuntu</category><category>debian</category><category>repositories</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>apt &quot;E: Unable to locate package&quot;: update, enable the component, or find its real name</title><link>https://ohsudo.com/articles/e-unable-to-locate-package/</link><guid isPermaLink="true">https://ohsudo.com/articles/e-unable-to-locate-package/</guid><description>Fix apt &quot;E: Unable to locate package&quot;: run apt update, enable universe or contrib, find the right package name, add the vendor&apos;s repository, and handle Docker images.</description><pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>apt</category><category>ubuntu</category><category>debian</category><category>packages</category><category>repositories</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>&quot;error while loading shared libraries&quot; and &quot;GLIBC_2.xx not found&quot;: what the loader is telling you</title><link>https://ohsudo.com/articles/error-while-loading-shared-libraries-glibc-not-found/</link><guid isPermaLink="true">https://ohsudo.com/articles/error-while-loading-shared-libraries-glibc-not-found/</guid><description>Fix Linux &quot;error while loading shared libraries: cannot open shared object file&quot; and &quot;version GLIBC_2.xx not found&quot;: use ldd, install the library, run ldconfig, rebuild.</description><pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>ldd</category><category>ldconfig</category><category>glibc</category><category>shared-libraries</category><category>packages</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>&quot;umount: target is busy&quot;: find what holds the filesystem, and when umount -l is safe</title><link>https://ohsudo.com/articles/umount-target-is-busy/</link><guid isPermaLink="true">https://ohsudo.com/articles/umount-target-is-busy/</guid><description>Fix &quot;umount: target is busy&quot; on Linux: find the process with lsof or fuser, leave the folder, stop services, handle NFS and bind mounts, and know when umount -l is safe.</description><pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>umount</category><category>mount</category><category>lsof</category><category>fuser</category><category>filesystems</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>npm &quot;EACCES: permission denied&quot;: fix it without sudo</title><link>https://ohsudo.com/articles/npm-eacces-permission-denied/</link><guid isPermaLink="true">https://ohsudo.com/articles/npm-eacces-permission-denied/</guid><description>Fix npm EACCES permission denied on global installs and in projects: use a version manager or your own prefix, repair root-owned files, and avoid sudo.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>npm</category><category>nodejs</category><category>permissions</category><category>chown</category><category>docker</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>&quot;user is not in the sudoers file&quot;: how to get sudo back, even without the root password</title><link>https://ohsudo.com/articles/user-is-not-in-the-sudoers-file/</link><guid isPermaLink="true">https://ohsudo.com/articles/user-is-not-in-the-sudoers-file/</guid><description>Fix &quot;user is not in the sudoers file&quot;: add yourself to the sudo or wheel group with su, recover without a root password, use visudo safely and fix a broken sudoers file.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>sudo</category><category>sudoers</category><category>visudo</category><category>permissions</category><category>users</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>SSH &quot;Too many authentication failures&quot;: your agent offers too many keys</title><link>https://ohsudo.com/articles/ssh-too-many-authentication-failures/</link><guid isPermaLink="true">https://ohsudo.com/articles/ssh-too-many-authentication-failures/</guid><description>Fix SSH &quot;Received disconnect … Too many authentication failures&quot;: the agent offers every key before the right one. Use IdentitiesOnly and IdentityFile.</description><pubDate>Wed, 04 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>ssh</category><category>openssh</category><category>keys</category><category>ssh-agent</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>&quot;Argument list too long&quot;: delete or move thousands of files on Linux</title><link>https://ohsudo.com/articles/argument-list-too-long/</link><guid isPermaLink="true">https://ohsudo.com/articles/argument-list-too-long/</guid><description>Fix &quot;Argument list too long&quot; for rm, mv, cp or grep with a wildcard: why the kernel refuses, and how find -delete, find -exec + and xargs handle any number of files.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>bash</category><category>find</category><category>xargs</category><category>files</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>&quot;E: Could not get lock /var/lib/dpkg/lock-frontend&quot;: what is holding apt, and what to do</title><link>https://ohsudo.com/articles/could-not-get-lock-dpkg-lock-frontend/</link><guid isPermaLink="true">https://ohsudo.com/articles/could-not-get-lock-dpkg-lock-frontend/</guid><description>Fix &quot;Could not get lock /var/lib/dpkg/lock-frontend&quot; on Ubuntu and Debian: find the process holding it, wait safely, and repair an interrupted dpkg.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>apt</category><category>dpkg</category><category>ubuntu</category><category>debian</category><category>packages</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Cron job not running? Find the reason in the log, PATH and environment</title><link>https://ohsudo.com/articles/cron-job-not-running/</link><guid isPermaLink="true">https://ohsudo.com/articles/cron-job-not-running/</guid><description>Fix a cron job that does not run or fails silently: check the log, PATH and environment, % signs, /etc/cron.d rules, permissions and lost output.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>cron</category><category>crontab</category><category>scheduling</category><category>bash</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>&quot;Job for nginx.service failed because the control process exited with error code&quot;: how to find the cause</title><link>https://ohsudo.com/articles/job-for-service-failed-control-process-exited/</link><guid isPermaLink="true">https://ohsudo.com/articles/job-for-service-failed-control-process-exited/</guid><description>Fix &quot;Job for X.service failed because the control process exited with error code&quot;: read systemctl status and journalctl, test the config, and fix the usual causes.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>systemd</category><category>systemctl</category><category>journalctl</category><category>nginx</category><category>services</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>Linux process &quot;Killed&quot; with no error: find the OOM killer and stop it happening again</title><link>https://ohsudo.com/articles/linux-process-killed-oom-killer/</link><guid isPermaLink="true">https://ohsudo.com/articles/linux-process-killed-oom-killer/</guid><description>A process that just prints &quot;Killed&quot; (exit code 137) was usually stopped by the Linux OOM killer. Find it in the kernel log, see what used the memory, and fix it.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>oom</category><category>memory</category><category>swap</category><category>systemd</category><category>dmesg</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>pip &quot;error: externally-managed-environment&quot;: install Python packages the right way</title><link>https://ohsudo.com/articles/pip-error-externally-managed-environment/</link><guid isPermaLink="true">https://ohsudo.com/articles/pip-error-externally-managed-environment/</guid><description>Fix pip &quot;externally-managed-environment&quot; on Ubuntu 24.04 and Debian 12: use apt, a virtual environment or pipx, and know when --break-system-packages is acceptable.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>python</category><category>pip</category><category>venv</category><category>pipx</category><category>ubuntu</category><category>debian</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>&quot;Read-only file system&quot; on Linux: why the disk went read-only, and how to fix it safely</title><link>https://ohsudo.com/articles/read-only-file-system/</link><guid isPermaLink="true">https://ohsudo.com/articles/read-only-file-system/</guid><description>Fix &quot;Read-only file system&quot; errors: find the read-only mount, read dmesg to see why the kernel did it, then repair with fsck — and check whether the disk is failing.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>filesystems</category><category>ext4</category><category>fsck</category><category>mount</category><category>dmesg</category><category>disks</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>&quot;sudo: unable to resolve host&quot;: fix /etc/hosts after a hostname change</title><link>https://ohsudo.com/articles/sudo-unable-to-resolve-host/</link><guid isPermaLink="true">https://ohsudo.com/articles/sudo-unable-to-resolve-host/</guid><description>Fix &quot;sudo: unable to resolve host … Name or service not known&quot; on Ubuntu and Debian: add the hostname to /etc/hosts, and keep cloud-init from undoing it.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>sudo</category><category>hostname</category><category>etc-hosts</category><category>cloud-init</category><category>ubuntu</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>&quot;Too many open files&quot; on Linux: raise the right limit, or find the leak</title><link>https://ohsudo.com/articles/too-many-open-files/</link><guid isPermaLink="true">https://ohsudo.com/articles/too-many-open-files/</guid><description>Fix &quot;Too many open files&quot; (EMFILE): check a process&apos;s real limit in /proc, raise LimitNOFILE for systemd services, and tell a low limit from a file descriptor leak.</description><pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>ulimit</category><category>systemd</category><category>file-descriptors</category><category>nginx</category><category>nodejs</category><category>java</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>No space left on device: find what is filling your Linux disk</title><link>https://ohsudo.com/articles/no-space-left-on-device/</link><guid isPermaLink="true">https://ohsudo.com/articles/no-space-left-on-device/</guid><description>Fix &quot;No space left on device&quot; on Linux: find the biggest directories and files, free space safely, and handle the cases where df says there is space.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>disk-space</category><category>df</category><category>du</category><category>find</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>&quot;Permission denied&quot; when running a script: 5 causes and fixes</title><link>https://ohsudo.com/articles/permission-denied-running-script/</link><guid isPermaLink="true">https://ohsudo.com/articles/permission-denied-running-script/</guid><description>Fix &quot;bash: ./script.sh: Permission denied&quot; and &quot;bad interpreter&quot; on Linux: execute bits, noexec mounts, directory permissions, Windows line endings and shebangs.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>bash</category><category>permissions</category><category>chmod</category><category>scripts</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item><item><title>SSH &quot;Permission denied (publickey)&quot;: how to find the real cause</title><link>https://ohsudo.com/articles/ssh-permission-denied-publickey/</link><guid isPermaLink="true">https://ohsudo.com/articles/ssh-permission-denied-publickey/</guid><description>Fix SSH &quot;Permission denied (publickey)&quot;: read the server log, fix ~/.ssh permissions, check the key and sshd_config, and handle SELinux on RHEL.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate><category>Linux</category><category>ssh</category><category>openssh</category><category>keys</category><category>permissions</category><category>troubleshooting</category><author>contact@ohsudo.com (OhSudo)</author></item></channel></rss>