New /tmp folder fails...

[schoeps]

can someone please report this to bugzilla? I dont have the infos...

It seems with a fresh WHM install, a /tmp mount point is created at 250 megs or so. Problem is that mysql is defaulted to that area to do operations like "repair" or "optimize". Therefore, if you db > than 250 megs, you will fill the tmp folder, which will never empty. If the database is bieng accessed by users, they will be held as "waiting". If you have a big site, they will gobble up all your sql connections. Since this problem does not resolve itself, you need to force it closed, marking the db as unusable since its flagged for repair. I think the old WHM used to just use the disk, no temp area.

so if you have a big DB, up the size of that temp file or pay the price

Bri

[cpanelkenneth]

can someone please report this to bugzilla? I dont have the infos...

It seems with a fresh WHM install, a /tmp mount point is created at 250 megs or so. Problem is that mysql is defaulted to that area to do operations like "repair" or "optimize". Therefore, if you db > than 250 megs, you will fill the tmp folder, which will never empty. If the database is bieng accessed by users, they will be held as "waiting". If you have a big site, they will gobble up all your sql connections. Since this problem does not resolve itself, you need to force it closed, marking the db as unusable since its flagged for repair. I think the old WHM used to just use the disk, no temp area.

so if you have a big DB, up the size of that temp file or pay the price

Bri

This loopback temp mount is only created if /tmp or /var/tmp is not already a separate partition.

MySQL can also be configured to use a different location than /tmp or /var/tmp. Please read http://dev.mysql.com/doc/refman/5.0/...ary-files.html for details.