[SOLVED] zmupdate.pl from 1.34.19 to 1.34.20 hangs

[ibrewster]

I just tried updating my Ubuntu system from zone minder 1.34.19 to 1.34.20, and it seems that the zmupdate.pl script is just hanging. It shows the following:

Code: Select all

Database successfully backed up to /tmp/zm/zm-1.34.19.dump, proceeding to upgrade.

Upgrading database to version 1.34.20
Loading config from DB 230 entries
Saving config to DB 230 entries

and then never gets any further. Top doesn't show any significant process activity, and if I look at the processlist table in mysql (actually running mariadb), I see the following entries:

| 48 | zoneminder | localhost | zm | Query | 455 | Waiting for table metadata lock | LOCK TABLE Config WRITE | 455175.794 | 0 | 0 | 0.000 | 77944 | 247880 | 0 | 530 | LOCK TABLE Config WRITE | 2834 |
| 39 | zoneminder | localhost:39240 | zm | Sleep | 565 | | NULL | 565129.064 | 0 | 0 | 0.000 | 77944 | 255024 | 0 | 109 | NULL | 1991 |
| 38 | zoneminder | localhost:39236 | zm | Sleep | 565 | | NULL | 565126.114 | 0 | 0 | 0.000 | 77944 | 255008 | 0 | 110 | NULL | 2115 |

which make it seem as though it is locked up waiting for a table metadata lock. If something else has that lock I'm certainly not aware of it. How can I fix this and get my zoneminder installation back? Would it make sense/be possible to downgrade back to 1.34.19?

[ibrewster]

Never mind. I just tried restarting mariadb a couple of times (why a couple? I have no idea), and the zmupgrade.pl process ran through normally. Not sure what got blocked there, but apparently something did that was cleared by a mariadb restart. Sorry for the noise.