Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@PrivateGER Have to run it as root! Also, to unchattr, use the -i param.
Note: you CANNOT see the chattr status of a file with the generic ls command, you have to do "lsattr" and if you see an 'i' before one of the files, it's chattred. -
@PrivateGER Second note, sometimes when a program can't write log output it can crash so be careful with this 😅
-
@neeno what would you have done at 3am when all you want is sleep? Extinguish the fire out and deal with it next Thursday.
-
@brogrammerology That wasn't our responsibility and we didn't monitor that as it... wasn't our responsibility
-
@gitpush Nah, the logging was there for a reason, they just needed to fix this issue.
Waaaay too many but let's go with this one for now.
At my previous job there was a web application which was generating about 1gb of log data a second. Server was full and the 'fullstack engineers' we called had zero clue about backend stuff and couldn't fix it.
Me and another engineer worked our asses off to figure this out but eventually the logging stopped and it went back to normal.
Great, right?
For that moment. I was the on-call server engineer and at like 3am I got called awake because this shit was happening again.
Sleep drunk with my phone I ssh'd into the server, not sure about what to do at first but then suddenly: let's chattr the goddamn log file...
$ chattr +i /var/log/logfile
Bam, worked, done, back to sleep.
(this comment + param marks the file in a way that it can only be read until the mark is removed, so you can't write to it or move it or remove it or whatever)
rant
wk228