2,068 reputation
1616
bio website labsphoenix.com
location
age
visits member for 3 years, 1 month
seen 22 hours ago

I manage networks.


23h
comment How to deploy in amazon ec2 through bitbucket
What's your error messages?
Jan
1
awarded  Revival
Dec
13
awarded  Yearling
Sep
30
awarded  Explainer
Sep
24
awarded  Autobiographer
Sep
23
awarded  Custodian
Sep
23
reviewed Approve What is Kernel Times
Sep
22
comment Unable to redirect STDOUT in a remote screen session via SSH
See my answer ; Screen output isn't what you are expecting. Start a shell inside screen and it will work.
Sep
22
answered Unable to redirect STDOUT in a remote screen session via SSH
Sep
16
answered Rapid failover from one data center to another when the first goes down?
Sep
5
comment Website not coming up only for airtel broadband
I've looked at all the Airtel broadband published DNS servers and I don't get any errors / differences. What IP are you using as DNS servers with them ?
Sep
5
comment Website not coming up only for airtel broadband
10 minutes for humsaathsaath.com ; 1hrs for www.humsaathsaath.com Everything seems ok.
Sep
5
comment Website not coming up only for airtel broadband
most likely Airtel Broadband is his own internet providers. He's been working with the domain name with old & new setting ; airtel must have the old IP in cache. Waiting for expiry is the normal way of doing.
Sep
5
answered Website not coming up only for airtel broadband
Aug
25
comment Nginx : Images takes too long to load. (1sec to download a 50KB image)
Would you be using a very high compression flag for gzip ?
Aug
25
awarded  Populist
Aug
24
comment Deploying new code live
You don't need to restart the server, just reload it. The delays are created due to the 'mv' command. Look at my suggestion with 28+ votes bellows- you just need a symbolic link (you can even put it one level lower (ie: /var/www/(current)/html ; current being the symlink)).
Aug
21
comment Deploying new code live
My point was that the question stipulate that he wanted to remove the downtime. This just artificially hide it from the user and actually lengthen it, due to backlog processing. Your downtime, using this method, is longer than it would have been in his previous procedure. To be able to withstand this technique you need to be able to hold a very high 'free capacity' pool in your production system (ie: able to deal with 5x the current traffic). This isn't cost effective. There's better way to scale if you need burstable capacity.
Aug
18
comment Deploying new code live
Please note that in any high traffic website, this will could very easily kill your Apache service. 200 rq/s will very easily trash your connection pool as soon as you will 'unlock' your Apache process after the move (if the move take a while)
Aug
16
awarded  Good Answer