Closed
Bug 812293
Opened 12 years ago
Closed 9 years ago
increase ephemeral port range on all persona servers
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
x86_64
Linux
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lloyd, Assigned: relud)
Details
this is a duplicate of bug 716940
We should increase the ephemeral port range on all persona servers, including client boxes, stage boxes, and production machines.
any reason I need seperate tickets for the different environments?
Reporter | ||
Comment 1•12 years ago
|
||
echo "1024 65535" > /proc/sys/net/ipv4/ip_local_port_range
Comment 2•12 years ago
|
||
(Just for future reference I'll note that while we were at 2.5M, we were 77% full on the ephemeral port range as it is currently set (32768, 61000). (from one netstat snapshot)).
Comment 3•12 years ago
|
||
We'll need this someday soon.
*should* be doable with the exisiting puppet sysctl provider. Need to see if there's a provision for a range versus discreet values.
yup
sysctl::set_value {
"net.ipv4.ip_local_port_range":
val => "1024 65535";
}
Comment 6•10 years ago
|
||
And to make this persistent add this line
net.ipv4.ip_local_port_range = 1024 65535
to /etc/sysctl.conf
Assignee | ||
Comment 7•10 years ago
|
||
persona stack 0618 in staging has been deployed with this change.
Assignee | ||
Updated•10 years ago
|
Assignee: gene → dthornton
Comment 8•10 years ago
|
||
Commited at
https://github.com/mozilla/identity-ops/commit/c85e208b6a465eac35e8725ba808b3bfd7ed2c31
and
https://github.com/mozilla/identity-ops/commit/68cb7a0705a527b936729c2c4ec79d4ad2d2918a
Deployed manually yesterday and it will be deployed using Chef today
Assignee | ||
Comment 9•10 years ago
|
||
prod stack 0620 in us-east-1 deployed on 6/20/14 at 3:45PM includes this change.
univ stacks in staging and prod don't have this change (yet)
Assignee | ||
Comment 10•9 years ago
|
||
fixed now
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•