There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

jherazob ,
@jherazob@beehaw.org avatar

Meanwhile sysadmins:

https://media.tenor.com/qK4uJn-NnTUAAAAC/first-time-james-franco.gif

rattking ,
@rattking@lemmy.ml avatar

deleted_by_author

    •
    Bene7rddso ,

    Rookie numbers. And he needed the entire line

    LucyLastic ,

    Is he objecting or backing up?

    tamiya_tt02 ,

    Sounds like both.

    thisbenzingring ,

    Once I had a customer report that her computer was giving her out of disk space errors. This was weird because we script their My Documents and Desktop to network file shares. Like wtf could be using up the disk? While walking to their system I figured the drive was going bad. Nope.

    Just a 250+GB log file from a chat program that they used. Like OMG that was amazing

    kionite231 ,

    Can you mention which “chat program” was that?

    thisbenzingring ,

    it was an early version of Pidgin

    TipRing ,
    @TipRing@kbin.social avatar

    Just add
    : > logfile
    to crontab and run it once a minute, problem solved.

    quylaa ,

    Yeah I centralize all my server logs, they point to a nifty location called /dev/null. It’s so good at collection and compression, it never grows in size!

    DarkenLM ,

    The Void consumes all.

    kionite231 ,

    Infinite compression ratio O.O

    ICastFist ,
    @ICastFist@programming.dev avatar

    I’ve had that happen with database logs where I used to work, back in 2015-6.

    The reason was a very shitty system that, for some reason, threw around 140 completely identical delete queries per millisecond. When I say completely identical, I mean it. It’d end up something like this in the log:

    
<span style="color:#323232;">2015-10-22 13:01:42.226 = delete from table_whatever
</span><span style="color:#323232;">      where id = 1
</span><span style="color:#323232;">          and name = 'Bob'
</span><span style="color:#323232;">          and other_identifier = '123';
</span><span style="color:#323232;">2015-10-22 13:01:42.226 = delete from table_whatever
</span><span style="color:#323232;">      where id = 1
</span><span style="color:#323232;">          and name = 'Bob'
</span><span style="color:#323232;">          and other_identifier = '123';
</span><span style="color:#323232;">2015-10-22 13:01:42.226 = delete from table_whatever
</span><span style="color:#323232;">      where id = 1
</span><span style="color:#323232;">          and name = 'Bob'
</span><span style="color:#323232;">          and other_identifier = '123';
</span><span style="color:#323232;">-- repeated over and over with the exact same fucking timestamp, then repeated again with slightly different parameters and different timestamp
</span>

    Of course, “no way it’s our system, it handles too much data, we can’t risk losing it, it’s your database that’s messy”. Yeah, sure, I set up triggers to repeat every fucking delete query. Fucking morons. Since they were “more important”, database logging was disabled.

    stealthnerd ,

    Having query logging enabled on a production database is bonkers. The duplicate deletes are too but query logging is intended for troubleshooting only. It kills performance.

    ICastFist ,
    @ICastFist@programming.dev avatar

    Take a wild guess as to why it had to be enabled in the first place, and only for Delete queries.

    mostlypixels ,
    @mostlypixels@programming.dev avatar

    I saw php error logs cause a full disk in a few minutes (thankfully on a shared dev server), thanks to an accidental endless loop that just flooded everything with a wall of notices…

    And, working with a CMS that allows third-party plugins that don’t bother to catch exceptions, aggressive web crawlers are not a good thing to encounter on a weekend… 1 exception x 400000 product pages makes for a loooot of text.

    Bishma ,
    @Bishma@discuss.tchncs.de avatar

    Im my experience, if your logs are growing that fast for a reason, you’ll get to see it again… and again… and again. And show it to people going, “WTF, have you ever seen anything like this before?”

    seahorse OP ,
    @seahorse@midwest.social avatar

    In my case docker didn’t have a default max size that logs would stop at, so they just grew and grew exponentially. I also had the highest log level turned on to debug something so it was constantly logging a bunch of data.

    marcos ,

    exponentially

    Are logging the content of your log files?

    agent_flounder ,
    @agent_flounder@lemmy.one avatar

    logception

    FlaminGoku ,

    You’ll also have management breathing down your neck about the costs if it’s not absolutely necessary.

    Djtecha ,

    Built a centralized logging system to handle logging like this. Fun project but very much the result of bad logging hygiene.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •