Reputation
393
Top tag
Next privilege 500 Rep.
Access review queues
Badges
10 35
Impact
~67k people reached

  • 0 posts edited
  • 0 helpful flags
  • 37 votes cast
Feb
19
comment Incredibly high load average on a Centos server
Did it work? Updating the kernel (with subsequent reboot)?
Feb
19
comment Incredibly high load average on a Centos server
Lol, highest load avgs I ever seen.
Feb
18
comment Linux - NTP stopped working after recent update
@SaveTheRbtz: Can you make an answer so I can accept?
Feb
18
comment CentOS - semanage - Adding Custom Port Fails
Cool glad this helped. My response has become so Pavlovian with regards to search results on tech topics, if the result isn't part of the SO family, I keep searching until I find one.
Jan
26
comment Nagios - check_ntp_time - Offset Unknown
Awesome! I will check it out and get back to you.
Jan
26
comment Nagios - check_ntp_time - Offset Unknown
@utrecht: Yes it is, running CentOS 6.5
Jan
26
comment Nagios - check_ntp_time - Offset Unknown
@utrecht: No I have not. TBH it's been a long while since the post, I will try to check back into it asap.
Sep
19
comment Puppet 2.7.x - Global variable - Append
Interesting. I ended up having to add a static mapping for dev and prod pools to a config.yaml file just to get past the issue and move onto bigger things. Puppet and I have a love / hate relationship; I love that it keeps servers in check, but I hate the fact that simple design principles are not avail. I get that it's based upon DSL, and being a software guy I am procedural based, but 2.7 should have at least afforded us the ability to accomplish these simple feats. Moving onto puppet 3.x will be a huge undertaking, but if we get funded, I think we can make it happen. Thx for the post.
Sep
19
comment Puppet 2.7.x - Global variable - Append
Confirmed. When I tried to write to a file, the contents wouldn't be available until I ran it a 2nd time. Then I started running into permission issues (SELinux enabled), so then I decided to create an empty file in the modules/nginx/files dir, but this made no sense as I now had a file whose sole purpose was to act as a container for transitory data. In short, total hack.
Sep
17
comment Puppet 2.7.x - Global variable - Append
Lol. And spend another 3-4 months porting over all the modules? Don't have that kind of time nor resources.
Sep
17
comment Puppet 2.7.x - Global variable - Append
Concat looks promising, however it's only for 3.x, and I am currently on 2.7.x
Sep
17
comment Puppet 2.7.x - Global variable - Append
Question is straight forward, however in the interests of solving my problem, I also included 'the weeds'.
Sep
5
comment nginx - Load Balancer - Considerable lag when upstream node is offline/down
I never mentioned anything about having multiple load balancers, nor was it part of the OP. I wasn't asking how to implement fault tolerance at the load balancer level, I was asking why Ngninx fails to disregard an offline node in an upstream pool.
Sep
3
comment nginx - Load Balancer - Considerable lag when upstream node is offline/down
@gtirloni, I have actually tried that mod. I read the notes and it said it can support up to 1.2.9, and 1.5.x and 1.7.x, the problem is, the 1.5 and 1.7 versions are "mainline" meaning they aren't considered stable. So the latest stable release would be 1.2.9. I have this version running in my lab, but haven't had much time to test it.
Sep
3
comment nginx - Load Balancer - Considerable lag when upstream node is offline/down
Will do. Thanks. I'll report back with findings.
Sep
3
comment nginx - Load Balancer - Considerable lag when upstream node is offline/down
How is heartbeat going to help my situation? Heartbeat (or keepalived) would be great if I wanted to establish fault tolerance for my nginx load balancer. Single IP points to LB1, if LB1 is not reachable the IP automatically switches over to LB2. I set this up for my master-master mysql replication for a single master write, I don't see how it's relevant to my problem. However it does seem I should start reading up on HAProxy, although I have to believe, with all the nginx users out there, someone has encountered this same issue.
Sep
3
comment nginx - Load Balancer - Considerable lag when upstream node is offline/down
Obviously I am looking to scale, so could be many, down the road. HAProxy really isn't the route I want to take, as I prefer nginx as it can properly handle multiple vhosts and redirect to various clusters.
Sep
2
comment nginx - Load Balancer - Considerable lag when upstream node is offline/down
@Grumpy: It's not a question of unusual behavior nor performance, rather it's a question of handling pool outages. The newer versions of nginx force you to use nginx plus if you want active health checks.
Aug
31
comment nginx - Load Balancer - Considerable lag when upstream node is offline/down
As we are bootstrapping, we really can't afford a commercial level load balancer like an F5 at this point, maybe after first round closes. What I don't get is why the passive checks like max_fails and fail_timeout directives don't seem to work. According to nginx docs (nginx.org/en/docs/http/…) the active health check is available, but only with a "commercial subscription" at $1,350 a year. Surely someone else has had to have encountered this scenario.
Aug
31
comment nginx - Load Balancer - Considerable lag when upstream node is offline/down
That's what I am struggling with. It's my impression that nginx has a black box algorithm to determine if an upstream server is down, if so do not send another request to it for X number of seconds.