Custom Query (196 matches)
Results (61 - 63 of 196)
Ticket
|
Resolution
|
Summary
|
Owner
|
Reporter
|
#328 |
fixed
|
Monitor used connections on sql.mit.edu
|
|
adehnert
|
Description |
Now that #327 is fixed, we're somewhat less likely to notice when one user (probably hacked or DoSed?) is using a ton of connections. We should add monitoring of used connections, either max connections per user or total connections.
The check_mysql_query plugin in combination with the PROCESSLIST table in the information_schema database may be useful.
|
#22 |
fixed
|
NFS-mounted /tmp is a bad idea
|
|
andersk
|
Description |
(Imported from help.mit.edu #432614.)
andersk:
While upgrading packages on scripts4, I received strange errors that I think can be attributed to our shared /tmp directory. We need to find a better solution. (This has made me uncomfortable for a long time, I'm just adding this to our todo list.)
andersk:
This is now one of ghudson's selling points for cobwebs:
http://scripts.mit.edu/~ghudson/blog/?p=13
so we should fix it as soon as possible. :-)
Here are some options I see:
- Keep the NFS solution and try to hack something to solve the failover problem.
- Unshare /tmp and stop pretending we only have one server.
- Unshare /tmp, but move PHP sessions and other similar data to some other shared directory (involving one of the other solutions).
- Put /tmp in AFS somewhere.
- Experiment with Coda, which I believe is supposed to support what we need.
Thoughts?
I think I'm happiest with either 2 or 3+5. Did we ever find specific examples of popular scripts that depend on a shared /tmp?
jbarnold:
I think that we previously found that some scripts cache data in /tmp, and they expect this data to be either not-there or entirely-up-to-date; they do not expect it to be in an old state.
I think that #2 might hard to get right.
I've considered putting /tmp into AFS, and that option might be the best one.
|
#101 |
fixed
|
Nagios monitoring for LDAP replication
|
|
quentin
|
Description |
We should monitor LDAP replication to make sure all the servers can talk to all the servers. We can probably adapt http://directory.fedoraproject.org/wiki/Howto:ReplicationMonitoring to do what we want.
|
Note: See
TracQuery
for help on using queries.