I have a Ansible play for PGBouncer that displays some output from a stats module built into PGBouncer.
My issue is that when Ansible prints the output to the terminal it mangles the newlines. Instead of seeing
----------
| OUTPUT |
----------
I see
----------\n| OUTPUT |\n----------
Does anyone know how to get Ansible to "pretty print" the output?
I understand that the disk queue should ideally be under the total number of disks within the system. How does this apply to RAID arrays?
Raid 0 I assume would be ideal queue = # of disks, RAID 10 / 1 = # of disks / 2, what about RAID 5, is it # of disks - 1?
What is happening exactly when the disk queue length exceeds this value, this is the number of writes waiting to be applied to the disks so why is any value above 0 OK?
Do you prefer to run their IIS webservers inside a DMZ that is part of the greater organisation's AD or do you prefer to sacrifice ease of management and user control over (possibly perceived) security?
We currently run our IIS boxes outside of the domain and this enables us to keep a one-way rule with our firewall (no traffic from DMZ to LAN except 1 SQL port). However, this means I now have to use non-AD authentication and manually synchronize passwords across boxes.
Which is more secure?
found an answer here Active Directory in a DMZ
I have a bunch of Dell servers with OpenManage installed.
If I access the RAID manager screens when it goes through the BIOS check, I can view each individual disk and see any issues. Specifically I can see the number of sectors on the disk marked as damaged.
I cannot seem to find this information within the OpenManage screens that you access once the server is up and running (the website on the server).
Does anyone know how I can access this information without bringing the server down and rebooting it? It seems like it should be trivial!
I just got some replacement drives for a server here, went to pop one in, and it turns out that the 72Gig for a Seagate is slightly below the 72gig of the Maxtors that we currently have.
Does anyone know if there is anything hidden on the drive causing this discrepancy? I'm facing a rebuild of the array if I can't find an extra 150MB on this disk. :)