Custom Query (196 matches)

We relatively often hit the cap on number of database connections. We should set max_user_connections (​http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_max_user_connections; ​http://dev.mysql.com/doc/refman/5.0/en/user-resources.html) in addition to max_connections (​http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_max_connections). Hopefully, this will mean that a single runaway account doesn't block other users from accessing sql.mit.edu.

This was previously brought up on -c scripts -i 2129340 on Sept. 26, 2012.

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.

We currently have several autoinstallers that aren't up-to-date with their upstream. We should keep them updated.

Some options include:

• making updating things easier, through technical measures and/or better documenting Wizard
• make this a non-issue by desupporting a bunch of autoinstallers (at the moment, this would probably mean gallery2 and phpbb, since MediaWiki? and WordPress? are uber-popular, and Git, Trac, TurboGears?, Django, and Rails probably all just ~symlink to Fedora packages)
• make this less of an issue by advertising two tiers of support, and relegating the things we barely care about and suck at updating to a lower tier of support