This had me laughing.
This had me laughing. Not the FreeBSD bit. That bit is serious. The 'didn't run all the fancy things' bit. That was funny. The problem is: in Linux, pretty soon, you cannot do without the fancy bits anymore. I run a bunch of servers. Servers need a firewall. Nothing fancy, just iptables. Right? I'm running Ubuntu servers. They have 'firewalld' installed. Firewalld uses dark magic to manipulate iptables and ip routes. Oh, it's all great when it works, for as long as it works. You can simple open up a port by issuing a firewalld-cmd command. Until you can't. Until firewalld-cmd says it can't connect to firewalld even though it thinks it is running. And firewalld can't restart because it thinks the configuration files are wrong. I'm not a Linux newbie by any standard, but I could not solve this problem. After restarting firewalld, all the routes on the machine were gone. And thank god for iLO. This is on a production server providing secondary services to 200.000 users. Soon after, I found similar issues on our loadbalancers, webservers, database servers, all running firewalld. There was no other solution other than to reboot the server. I tried debugging firewalld and ran into (no particular order) apparmor, dbus, python, firewalld-cmd, firewalld, network-manager and libvirtd. No where was a hint to be found of why firewalld didn't work. I don't consider this to be anything fancy. This is supposed to be a simple wrapper around iptables. It is supposed to 'just work'. It is supposed to leave clear logs about what it is trying to do in /var/log/syslog. Sure, I'm getting old and cranky. But I'm really tired of having to get called out of my bed at 03:00 am because of this 'innovation' that tries to solve edgecases. And solves them badly.
Posted by mverwijs on Feb 10, 2015, 8:45 AM
Tags
Related issues
- > Because they don't believe the disasters were inflicted by them.
- Hehe, yeah I'm not sure when John Stewart would have worked there or what the pain points were for him, but he worked there for a bit.
- https://www.apple.com/shop/product/mxcl3ll/a/magic-keyboard-...
- If first-order hybrids made up only a small proportion of the total population of humans and Neanderthals, then the probability that a pa...
- Well, I'd be interested to hear what some of those nuances are, personally.
- My biggest Amazon annoyance.
Raise real-world problems, find people facing the same issue, and discuss solutions.8,000 issues0 comments
hackernews (E-commerce)
> Because they don't believe the disasters were inflicted by them.
Hehe, yeah I'm not sure when John Stewart would have worked there or what the pain points were for him, but he worked there for a bit.
https://www.apple.com/shop/product/mxcl3ll/a/magic-keyboard-...
If first-order hybrids made up only a small proportion of the total population of humans and Neanderthals, then the probability that a pa...
Well, I'd be interested to hear what some of those nuances are, personally.
My biggest Amazon annoyance.
> There's not really an unmet need for innovation in broadband delivery; the issue is running new wires broadband has costs, and in a lot...
Speaking of Amazon's account process, I have a really annoying problem with theirs.
This had me laughing.
This had me laughing. Not the FreeBSD bit. That bit is serious. The 'didn't run all the fancy things' bit. That was funny. The problem is: in Linux, pretty soon, you cannot do without the fancy bits anymore. I run a bunch of servers. Servers need a firewall. Nothing fancy, just iptables. Right? I'm running Ubuntu servers. They have 'firewalld' installed. Firewalld uses dark magic to manipulate iptables and ip routes. Oh, it's all great when it works, for as long as it works. You can simple open up a port by issuing a firewalld-cmd command. Until you can't. Until firewalld-cmd says it can't connect to firewalld even though it thinks it is running. And firewalld can't restart because it thinks the configuration files are wrong. I'm not a Linux newbie by any standard, but I could not solve this problem. After restarting firewalld, all the routes on the machine were gone. And thank god for iLO. This is on a production server providing secondary services to 200.000 users. Soon after, I found similar issues on our loadbalancers, webservers, database servers, all running firewalld. There was no other solution other than to reboot the server. I tried debugging firewalld and ran into (no particular order) apparmor, dbus, python, firewalld-cmd, firewalld, network-manager and libvirtd. No where was a hint to be found of why firewalld didn't work. I don't consider this to be anything fancy. This is supposed to be a simple wrapper around iptables. It is supposed to 'just work'. It is supposed to leave clear logs about what it is trying to do in /var/log/syslog. Sure, I'm getting old and cranky. But I'm really tired of having to get called out of my bed at 03:00 am because of this 'innovation' that tries to solve edgecases. And solves them badly.
Comments (0)
No comments yet. Start the discussion.