As a rule of thumb, whenever I see that a server is acting strangely I just ‘df -h‘: I learned the hard way that a full filesystem can make unpredictable and mysterious things! 😣
Same. I don't know that much about Linux, but when something is acting up, the things I check are usually 1. Have I tried turning it off and on again? 2. Is there enough RAM? 3. Is there enough disk space? 4. Is there someone smarter than me who could fix this?
I agree with you, I just leave the option one as last resource because the smarter people could gain advantages from information lost in reboot, and I think that understand the origin of probles is more important that simply fix it :-)
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
As a rule of thumb, whenever I see that a server is acting strangely I just ‘df -h‘: I learned the hard way that a full filesystem can make unpredictable and mysterious things! 😣
Same. I don't know that much about Linux, but when something is acting up, the things I check are usually 1. Have I tried turning it off and on again? 2. Is there enough RAM? 3. Is there enough disk space? 4. Is there someone smarter than me who could fix this?
I agree with you, I just leave the option one as last resource because the smarter people could gain advantages from information lost in reboot, and I think that understand the origin of probles is more important that simply fix it :-)
If that looks ok, follow it up with
df -ibecause you can have available space without having any blocks left. That caught me out a couple of times.