Forum Activity for @brian

emergency after core update mysql uses 100% cpu

Installation and Configuration

Pause the queues then - that won't hurt anything.

emergency after core update mysql uses 100% cpu

Installation and Configuration

I think you've got things in a bit of a mess - here's what I would do:

1) Put your site in maintenance mode so you don't have people hitting pages and lists on your site
2) Make sure you are not running a repair from the browser (repair.php) OR the command line
3) restart MySQL
4) log in to your site and do an Integrity Check with repair modules checked. This could take a bit to run if you have very large tables - i.e. give it 30 minutes if needed
5) when finished exit maintenance mode
updated by @brian: 08/30/17 10:27:50AM

emergency after core update mysql uses 100% cpu

Installation and Configuration

All those processes are "Waiting for table level lock", which means the table has been locked. I'm guessing you are running a repair from the command line?

emergency after core update mysql uses 100% cpu

Installation and Configuration

If you have checked the "repair modules" option, the DB tables are all upgraded to InnoDB - this could take a bit on the server if you have a very large amount of data - you want to just let it run - don't jump in there and restart stuff. You can do:


when logged in to MySQL as the root user and see what queries are being run - make sure any ALTER TABLE queries are complete before you shutdown or restart the server.

Jamroom 6.1 has been released!

Announcements


That's what I like to hear - thanks Steve!

Jamroom 6.1 has been released!

Announcements


It's just for the Video module - YouTube and Vimeo are not affected.

Dependent Listeners

Jamroom Developers

Awesome - glad that it is working now

Dependent Listeners

Jamroom Developers

Sorry - should have mentioned you need to run an integrity check after making the change - the priority is stored in the module table in the DB, and updates with an integrity check.

Let me know if that helps.

Dependent Listeners

Jamroom Developers

Each module in Jamroom can be given a "priority" - this determines the load order of the module, and thus determines the order that event listeners are called when multiple modules have registered to listen to a specific event. In this case, if you look in the jrComment/include.php file at the "meta" function that the comment modules priority is set to "250" (which is low). the very lowest priority is 255, so in your custom module meta function just make sure you set your module priority to be 251 - that way your event listener will always run AFTER the comment module listener.

Let me know if that helps.

Thanks!

Jamroom 6.1 has been released!

Announcements

As long as everything gets updated and you get the integrity check run, you should be good