Reputation
350
Next privilege 500 Rep.
Access review queues
Badges
1 5
Newest
 Commentator
Impact
~5k people reached

  • 0 posts edited
  • 0 helpful flags
  • 4 votes cast
Jul
14
comment nginx proxy_pass eventually returns GATEWAY_TIMEOUT even though server is still active
I updated my answer with the format for the proxy_next_upsteam_tries option
Jul
14
revised nginx proxy_pass eventually returns GATEWAY_TIMEOUT even though server is still active
added 181 characters in body
Jul
14
comment nginx proxy_pass eventually returns GATEWAY_TIMEOUT even though server is still active
Awesome. Upgrading to 1.7.5 by itself likely won't fix the problem. Since the default proxy_retries is 0, you will have to edit nginx.conf and add the parameter with a number like 1 or 2. Thumbs up helps, but always let OP know what you did to finally fix the problem.
Jul
14
revised nginx proxy_pass eventually returns GATEWAY_TIMEOUT even though server is still active
added 459 characters in body
Jul
14
answered nginx proxy_pass eventually returns GATEWAY_TIMEOUT even though server is still active
Mar
10
comment Cooling for a very small server room?
Hi, Riah - sorry I missed the UPS. As others mentioned, a stand alone AC, with a hose that can exhaust outside of the room, is your best bet. Piping it through the ceiling tiles might be sufficient, but that will also heat that area very high, so you have to make sure there isn't anything up there that can break of catch fire from the excessive heat.
Mar
9
comment Cooling for a very small server room?
I think, without a UPS, PDU, and some Halon, you are creating a server room without the requisite power controls NOR fire suppression. This is fine if you don't care if/when the whole room goes up in smoke and you lose all your data, software, AND hardware.
Mar
9
answered AWS Command Line - Query Instance MS SQL Version
Feb
18
awarded  Commentator
Feb
18
comment vsftpd freezes after failed pam_script authentication
Sorry to hear. Can you log in if you do provide a password? It seems that if you succeed with a password and fail without one, the problem points to the need for additional directives somewhere, either in the vsftpd pam auth, or perhaps a different pam auth file.
Feb
18
awarded  Yearling
Feb
17
revised Windows Server Backup Error - Volumes Larger than 16.7TB cannot be protected?
added 298 characters in body
Feb
17
comment Windows Server Backup Error - Volumes Larger than 16.7TB cannot be protected?
Minus all you want - this answer is correct
Feb
17
answered Windows Server Backup Error - Volumes Larger than 16.7TB cannot be protected?
Feb
17
comment Windows Server Backup Error - Volumes Larger than 16.7TB cannot be protected?
That's an unfortunate misuse of the word 'backup'. The ITIL gods are getting angry, no doubt. But, as it turns out the FILE SIZE limit on NTFS is 16.7TB, so that is what the problem is - the backup (I am guessing) is one giant file and 16.7TB is the limit for that size. Microsoft and the other vendors can mangle it and call it a 'protection' or any other idiotic marketing slug they want, I'll still call it a 'backup'.
Feb
17
comment Windows Server Backup Error - Volumes Larger than 16.7TB cannot be protected?
It is a 'protected' message, not a space message, per se. The 'standard settings' is for a Windows server backup is to use DPM - Data Protection Manager. It appears there is a software limitation when using DPM. You might want to see if the settings will allow a byte-for-byte copy to take place, without so-called 'protection' enabled, assuming you have a way to restore a byte-for-byte copy if you need to.
Feb
17
answered vsftpd freezes after failed pam_script authentication
Jan
22
answered how do I find out what part of my ec2 storage is ephemeral
Sep
24
awarded  Editor
Sep
24
revised Apache, SERVER_NAME overridden by HTTP_HOST
Added dos script code to get ServerName value from httpd.conf