Notes |
|
|
Resolved: the my.conf file had been changed to force a recovery and never changed back to the default value ('0').
[mysqld]
innodb_force_recovery = 4
As a safety measure, InnoDB prevents users from performing INSERT, UPDATE, or DELETE operations when innodb_force_recovery is greater than 0.
--------------------------------------------------------------------------------
Resolution:
[mysqld]
innodb_force_recovery = 0 |
|
|
(0003487)
|
caralo
|
2014-01-14 03:50
|
|
I have connected to mysql database and the system variable innodb_force_recovery was 0. Just in case it was not right, I have forced "innodb_force_recovery = 0" in my.cnf but I still get the same error. |
|
|
|
|
|
(0003489)
|
caralo
|
2014-01-14 08:54
|
|
I have applied the patch and but it doesnt work. I think that the problem is previous to reevaluation. It has to do with:
httpd.admin(0) ERROR: Odd number of elements in hash assignment at /usr/local/pf/html/pfappserver/lib/pfappserver/Base/Action/AdminRole.pm line 30.
(pfappserver::__ANON__)
The role change (and reevaluation) works perfectly if you change the role in the menu that opens when you press the mac of a node. But in this case you have to change the role one by one. If you want to change the role of many nodes at the same time, you should use the action menu but it doesnt work (changes the role but not the vlan) |
|