553
Linux processes (lemmy.world)
top 50 comments
sorted by: hot top controversial new old
[-] Blackout@kbin.run 107 points 2 years ago

It was little Bobby Tables

load more comments (1 replies)
[-] count_dongulus@lemmy.world 73 points 2 years ago

Alright who's running the database on the same machine as the server...👀

[-] tias@discuss.tchncs.de 68 points 2 years ago

If you can do this, do it. It's a huge boost to performance thanks to infinitely lower latency.

[-] jmcs@discuss.tchncs.de 11 points 2 years ago

And infinitely lower reliability because you can't have failovers (well you can, but people that run everything in the same host, won't). It's fine for something non critical, but I wouldn't do it with anything that pays the bills.

[-] tias@discuss.tchncs.de 24 points 2 years ago* (last edited 2 years ago)

I work for a company that has operated like this for 20 years. The system goes down sometimes, but we can fix it in less than an hour. At worst the users get a longer coffee break.

A single click in the software can often generate 500 SQL queries, so if you go from 0.05 ms to 1 ms latency you add half a second to clicks in the UI and that would piss our users off.

Definitely not saying this is the best way to operate at all times. But SQL has a huge problem with false dependencies between queries and API:s that make it very difficult to pipeline queries, so my experience has been that I/O-bound applications easily become extremely sensitive to latency.

[-] Katana314@lemmy.world 6 points 2 years ago

I’m going to guess quite a people here work on businesses where “sometimes breaks, but fixed in less than an hour” isn’t good enough for reliability.

load more comments (2 replies)
load more comments (2 replies)
load more comments (1 replies)
[-] crony@lemmy.cronyakatsuki.xyz 48 points 2 years ago

Most beginner selfhosters.

[-] adarza@lemmy.ca 34 points 2 years ago

and most every cpanel (and every other web host panel) box on the planet.

web, ftp, database, mail, dns, and more. all on one machine.

load more comments (1 replies)
load more comments (2 replies)
[-] cm0002@lemmy.world 70 points 2 years ago

Ok, now I need a 8 season animated show and at least 2 direct-to-TV movies of this

[-] bobs_monkey@lemm.ee 25 points 2 years ago

Best I can do is a Netflix series that gets cancelled halfway through season 2 and a fan-made animation spoof on YouTube

load more comments (3 replies)
[-] msage@programming.dev 60 points 2 years ago

Fuck MySQL, all my homies hate MySQL.

Postgres is the way to go.

[-] kitnaht@lemmy.world 26 points 2 years ago
[-] msage@programming.dev 14 points 2 years ago

Yes, Maria too.

Postgre is the way

load more comments (1 replies)
[-] Anticorp@lemmy.world 22 points 2 years ago

It was you! You killed it.

[-] msage@programming.dev 8 points 2 years ago

I do admit to moving the company cluster from MySQL to Postgres.

But only most of the traffic, some traces still remain, so the original MySQL still works

[-] esc27@lemmy.world 60 points 2 years ago

Random guess, a php error caused Apache to log a ridiculous number of errors to /var/log and on this system that isn’t its own partition so /var filled up crashing MySQL. The user wiped /var/log to free up space.

[-] harmsy@lemmy.world 6 points 2 years ago

That's not far off of something that happened to me once a few years ago. My computer suddenly started struggling one day, and I quickly figured out that my hard drive suddenly had 500 gigs or so of extra data somewhere. I had to find a tool that would let me see how much space a given folder was taking up, and eventually I found an absolutely HUMONGOUS error log file. After I cleared it out, the file rapidly filled up again when I used a program I'd been using all the time. I think it was Minecraft or something. Anyway, my duck tape solution was to just make that log file read-only, since the error in question didn't actually affect anything else.

[-] Honytawk@lemmy.zip 54 points 2 years ago

Plot twist: it was the user

[-] ICastFist@programming.dev 7 points 2 years ago

That's not even a plot twist, that's expected user behavior

[-] Buffalox@lemmy.world 50 points 2 years ago

All evidence point to suicide.

[-] Unbecredible@lemm.ee 28 points 2 years ago

I hadn't realized this was a .ru domain....

[-] MajorHavoc@programming.dev 21 points 2 years ago

Maybe it's a 'Windows' server...

[-] Blue_Morpho@lemmy.world 32 points 2 years ago

Systemd. SQL is now in Systemd.

[-] Samsy@lemmy.ml 9 points 2 years ago

Dont spoil. That's the secret in Episode 5.

[-] Lost_My_Mind@lemmy.world 26 points 2 years ago

I understand none of this.....

[-] Samsy@lemmy.ml 16 points 2 years ago

"Among us" but for Linux nerds.

[-] tias@discuss.tchncs.de 24 points 2 years ago

It was Java, coaxing the Linux OOM killer into doing the job

[-] tal@lemmy.today 22 points 2 years ago

It looks like the OOM killer has struck again.

[-] Rexelpitlum@discuss.tchncs.de 22 points 2 years ago

/var/log has been deleted, you say...

I think we all know what this means, don't we?

[-] Rexelpitlum@discuss.tchncs.de 14 points 2 years ago

Hint

ls -ld /var/log
drwxrwxr-x 18 root syslog 4096 Aug 11 08:13 /var/log

[-] verstra@programming.dev 8 points 2 years ago

I have no clue. Root nuked the logs? Why? OOM killer does not do that.

[-] Rexelpitlum@discuss.tchncs.de 13 points 2 years ago

Well, there is only one who could have erased all traces of the SIGKILL...

And only the SIGKILLER would have had reason to do so...

load more comments (2 replies)
[-] hemko@lemmy.dbzer0.com 7 points 2 years ago

That seems so obvious I think we're missing something

[-] Rexelpitlum@discuss.tchncs.de 9 points 2 years ago

Whatever, we have a suspect.

Bring in GDB to do the interrogation! And perhaps also call Nice, he can play the good cop...

[-] hemko@lemmy.dbzer0.com 6 points 2 years ago

Forgive me my ignorance, but since Apache is running as root, couldn't PHP inherit it's permissions?

[-] lawrence@lemmy.world 5 points 2 years ago

The Apache main process runs as root. When it receives a request, it spawns a child process that doesn't run as root. PHP runs as the same user as the Apache child process.

[-] jollyrogue@lemmy.ml 4 points 2 years ago

Or PHP runs in its own fastcgi like process under a different account.

[-] jordanlund@lemmy.world 22 points 2 years ago

This process has been murdered mysteriously.

[-] WhiskyTangoFoxtrot@lemmy.world 20 points 2 years ago
[-] uranibaba@lemmy.world 17 points 2 years ago

Will there be a follow up?

[-] Tamkish@programming.dev 14 points 2 years ago

I did it like this: 🔫 BANG WhooOooOoopty doOoO

[-] jlh@lemmy.jlh.name 12 points 2 years ago

It was the kubelet after MySQL failed his liveness probes

[-] bionicjoey@lemmy.ca 6 points 2 years ago
[-] ggppjj@lemmy.world 6 points 2 years ago

It was taking away resources from the coffee cam. Had to go.

[-] hakunawazo@lemmy.world 6 points 2 years ago

Like everytime with natives, it was a race condition cascade of table locks followed by mysql suicide caused by bad cronjob scripts implemented by the user.

load more comments (1 replies)
[-] TeoTwawki@lemmy.world 5 points 2 years ago

Mariadb did it with the candlestick in the library.

load more comments
view more: next ›
this post was submitted on 12 Aug 2024
553 points (96.8% liked)

Comic Strips

23840 readers
244 users here now

Comic Strips is a community for those who love comic stories.

Rules
  1. 😇 Be Nice!

    • Treat others with respect and dignity. Friendly banter is okay, as long as it is mutual; keyword: friendly.
  2. 🏘️ Community Standards

    • Comics should be a full story, from start to finish, in one post.
    • Posts should be safe and enjoyable by the majority of community members, both here on lemmy.world and other instances.
    • Any comic that would qualify as raunchy, lewd, or otherwise draw unwanted attention by nosy coworkers, spouses, or family members should be tagged as NSFW.
    • Moderators have final say on what and what does not qualify as appropriate. Use common sense, and if need be, err on the side of caution.
  3. 🧬 Keep it Real

    • Comics should be made and posted by real human beans, not by automated means like bots or AI. This is not the community for that sort of thing.
  4. 📽️ Credit Where Credit is Due

    • Comics should include the original attribution to the artist(s) involved, and be unmodified. Bonus points if you include a link back to their website. When in doubt, use a reverse image search to try to find the original version. Repeat offenders will have their posts removed, be temporarily banned from posting, or if all else fails, be permanently banned from posting.
    • Attributions include, but are not limited to, watermarks, links, or other text or imagery that artists add to their comics to use for identification purposes. If you find a comic without any such markings, it would be a good idea to see if you can find an original version. If one cannot be found, say so and ask the community for help!
  5. 📋 Post Formatting

    • Post an image, gallery, or link to a specific comic hosted on another site; e.g., the author's website.
    • Meta posts about the community should be tagged with [Meta] either at the beginning or the end of the post title.
    • When linking to a comic hosted on another site, ensure the link is to the comic itself and not just to the website; e.g.,
      ✅ Correct: https://xkcd.com/386/
      ❌ Incorrect: https://xkcd.com/
  6. 📬 Post Frequency/SPAM

    • Each user (regardless of instance) may post up to five (5 🖐) comics a day. This can be any combination of personal comics you have written yourself, or other author's comics. Any comics exceeding five (5 🖐) will be removed.
  7. 🏴‍☠️ Internationalization (i18n)

    • Non-English posts are welcome. Please tag the post title with the original language, and include an English translation in the body of the post; e.g.,
      Sí, por favor [Spanish/Español]
  8. 🍿 Moderation

    • We are human, just like most everybody else on Lemmy. If you feel a moderation decision was made in error, you are welcome to reach out to anybody on the moderation team for clarification. Keep in mind that moderation decisions may be final.
    • When reporting posts and/or comments, quote which rule is being broken, and why you feel it broke the rules.
Banned Artists

The following artists are banned from the community.

  1. Jago
  2. Stonetoss

It should be noted that when you make reports, it is your responsibility to provide rational reasoning why something should be removed. Saying it simply breaks community rules is not always good enough.

Web Accessibility

Note: This is not a rule, but a helpful suggestion.

When posting images, you should strive to add alt-text for screen readers to use to describe the image you're posting:

Another helpful thing to do is to provide a transcription of the text in your images, as well as brief descriptions of what's going on. (example)

Web of Links

founded 2 years ago
MODERATORS