Errors in syslog after first reboot once upgraded to 2.5.3
wailer
75 Posts
October 22, 2020, 11:19 amQuote from wailer on October 22, 2020, 11:19 amHi,
We recently upgraded from 2.4.0 to 2.5.3 , this is a 3-node cluster.
nodes 2 and 3 were having a high load and we decided to reboot node 2, cluster health was clean.
Now syslog is full of these errors:
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.139 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.143 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.223 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.223 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.407 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.407 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtime
Any hint what is going on?
Hi,
We recently upgraded from 2.4.0 to 2.5.3 , this is a 3-node cluster.
nodes 2 and 3 were having a high load and we decided to reboot node 2, cluster health was clean.
Now syslog is full of these errors:
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.139 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.143 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.223 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.223 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.407 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.407 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtime
Any hint what is going on?
admin
2,930 Posts
October 22, 2020, 12:20 pmQuote from admin on October 22, 2020, 12:20 pmit is a Ceph bug relating to moving config values from ceph.conf file to central monitor db, some values were allowed in the global section of the config file cannot be stored globally in monitor db.
if you upgrade to 2.6, it should fix it. alternatively try:
ceph config rm global bluestore_block_db_size
ceph config-key rm config/global/bluestore_block_db_size
ceph config rm mon setuser_match_path
ceph config-key rm config/mon/setuser_match_path
ceph config set osd bluestore_block_db_size 64424509440
it is a Ceph bug relating to moving config values from ceph.conf file to central monitor db, some values were allowed in the global section of the config file cannot be stored globally in monitor db.
if you upgrade to 2.6, it should fix it. alternatively try:
ceph config rm global bluestore_block_db_size
ceph config-key rm config/global/bluestore_block_db_size
ceph config rm mon setuser_match_path
ceph config-key rm config/mon/setuser_match_path
ceph config set osd bluestore_block_db_size 64424509440
Last edited on October 22, 2020, 12:21 pm by admin · #2
wailer
75 Posts
October 22, 2020, 1:04 pmQuote from wailer on October 22, 2020, 1:04 pmThank you,
Just to confirm, we set value for bluestore_block_db_size but not for setuser_match_path, right?
Thank you,
Just to confirm, we set value for bluestore_block_db_size but not for setuser_match_path, right?
admin
2,930 Posts
Errors in syslog after first reboot once upgraded to 2.5.3
wailer
75 Posts
Quote from wailer on October 22, 2020, 11:19 amHi,
We recently upgraded from 2.4.0 to 2.5.3 , this is a 3-node cluster.
nodes 2 and 3 were having a high load and we decided to reboot node 2, cluster health was clean.
Now syslog is full of these errors:
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.139 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.143 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.223 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.223 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.407 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.407 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtimeAny hint what is going on?
Hi,
We recently upgraded from 2.4.0 to 2.5.3 , this is a 3-node cluster.
nodes 2 and 3 were having a high load and we decided to reboot node 2, cluster health was clean.
Now syslog is full of these errors:
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.139 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.143 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.223 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.223 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.407 7f251a79e700 -1 set_mon_vals failed to set bluestore_block_db_size = 64424509440: Configuration option 'bluestore_block_db_size' may not be modified at runtime
Oct 22 13:14:09 CEPH-12 ceph-mon[2354]: 2020-10-22 13:14:09.407 7f251a79e700 -1 set_mon_vals failed to set setuser_match_path = /var/lib/ceph/$type/$cluster-$id: Configuration option 'setuser_match_path' may not be modified at runtime
Any hint what is going on?
admin
2,930 Posts
Quote from admin on October 22, 2020, 12:20 pmit is a Ceph bug relating to moving config values from ceph.conf file to central monitor db, some values were allowed in the global section of the config file cannot be stored globally in monitor db.
if you upgrade to 2.6, it should fix it. alternatively try:
ceph config rm global bluestore_block_db_size
ceph config-key rm config/global/bluestore_block_db_size
ceph config rm mon setuser_match_path
ceph config-key rm config/mon/setuser_match_path
ceph config set osd bluestore_block_db_size 64424509440
it is a Ceph bug relating to moving config values from ceph.conf file to central monitor db, some values were allowed in the global section of the config file cannot be stored globally in monitor db.
if you upgrade to 2.6, it should fix it. alternatively try:
ceph config rm global bluestore_block_db_size
ceph config-key rm config/global/bluestore_block_db_size
ceph config rm mon setuser_match_path
ceph config-key rm config/mon/setuser_match_path
ceph config set osd bluestore_block_db_size 64424509440
wailer
75 Posts
Quote from wailer on October 22, 2020, 1:04 pmThank you,
Just to confirm, we set value for bluestore_block_db_size but not for setuser_match_path, right?
Thank you,
Just to confirm, we set value for bluestore_block_db_size but not for setuser_match_path, right?
admin
2,930 Posts