No announcement yet.

Hourly Cleanup #2 - V3.8.4 taking a *long* time to execute. PMs unusable

  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    I don't think dumping and reimporting your database fixed it, I think that what probably happened is that the cronjob responsible for Orphan PM cleanup was able to complete successfully at some point.

    While the query was not running, with the forum off: Once I created a new database, and imported a backup, that same query only took a few milliseconds. More thoughts?

    You are correct, the PM system is useless while that query is running. And the loads go up 100x. Question: what would happen if that query never ran? The old PMs would still be there taking up space?

    Our forum is really small, way smaller than a million post 'big board'.


    • #17
      Apparently *somehow* the ownership was set to root instead of mysql.

      Using this command within PuTTY (lowercase 'L' not '1'):
      [email protected] [~]# ls -l /var/lib/mysql
      Instead of this:
      drwx------  2 mysql mysql   18432 Jul  6 11:10 databasename/
      It was this.
      drwx------  2 root  root   18432 Jul  6 11:10 databasename/
      After this was run:
      [email protected] [~]# chown –R mysql:mysql /var/lib/mysqlat
      Ownership was set to mysql as it should have been.

      Then other things could be done within myphpadmin such as optimize & enable keys.

      I am extremely grateful to the person that helped me with this today, hopefully it will help others in the future.


      widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.