Sorry for cross posting but I cannot find it anywhere but on the
development list.
According to Sage's post in January (mon config commands)
2018-01-11 15:09:55.390 7f5a3cff9700 -1 set_mon_vals failed to set
admin_socket = /tmp/ceph-asok.GBZTV0/$name.$pid.asok: Configuration
option 'admin_socket' may not be modified at runtime
(That warning appears because the CLI process observed the config change
as it happened, and isn't able to update the admin_socket setting at
runtime.)
Here is where I have a problem. I have following settings on the client
side
[client]
admin_socket = /var/run/ceph/$name.$pid.asok
[client.libvirt]
admin socket = /var/run/ceph/$cluster-$type.$id.$pid.$cctid.asok # must
be writable by QEMU and allowed by SELinux or AppArmor
log file = /var/log/ceph/qemu-guest-$pid.log # must be writable by QEMU
and allowed by SELinux or AppArmor
# Please do not change this file directly since it is managed by Ansible
and will be overwritten
[global]
# let's force the admin socket the way it was so we can properly check
for existing instances
# also the line $cluster-$name.$pid.$cctid.asok is only needed when
running multiple instances
# of the same daemon, thing ceph-ansible cannot do at the time of writing
admin socket = "$run_dir/$cluster-$name.asok"
bluestore_block_db_size = 42949672960
bluestore_block_wal_size = 1073741824
cluster network = 10.1.42.0/23
fsid = 163eda65-1556-4bf0-b2cd-36f0c4715d4b
log file = /dev/null
mon cluster log file = /dev/null
mon host = 10.1.40.61,10.1.40.62,10.1.40.63
public network = 10.1.40.0/23
Also
ceph config dump
2018-09-01 08:24:41.199 7f590d7fa700 -1 set_mon_vals failed to set
admin_socket = $run_dir/$cluster-$name.asok: Configuration option
'admin_socket' may not be modified at runtime
2018-09-01 08:24:41.199 7f590d7fa700 -1 set_mon_vals failed to set
bluestore_block_db_size = 34359738368: Configuration option
'bluestore_block_db_size' may not be modified at runtime
WHO MASK LEVEL OPTION VALUE
RO
global advanced admin_socket
$run_dir/$cluster-$name.asok *
global dev bluestore_block_db_size 34359738368
*
global dev bluestore_block_wal_size 1073741824
*
global advanced cluster_network 10.1.42.0/23
*
global basic log_file /dev/null
*
global advanced mon_cluster_log_file /dev/null
*
global advanced public_network 10.1.40.0/23
*
mgr unknown mgr/balancer/mode crush-compat
*
mgr unknown mgr/dashboard/enabled true
*
mgr unknown mgr/dashboard/password
$2b$12$Y0iZgrPhj2Gc3op7iGYaUOJolfPCGG.skxEAbzmjo9FII8LTKOeOC *
mgr unknown mgr/dashboard/username cephadmin
*
client.libvirt advanced admin_socket
/var/run/ceph/$cluster-$type.$id.$pid.$cctid.asok *
client.libvirt basic log_file
/var/log/ceph/qemu-guest-$pid.log *
As you see I get those error messages every time I run any CLI command
like ceph -s or rbd ls.
From what I see my client is affected by both , entries into a config
database and into a config file. Commenting out
admin_socket = /var/run/ceph/$name.$pid.asok
removes the message about it. But since bluestore is in config database
client still gets the that message ( set_mon_vals failed to set
bluestore_block_db_size = 34359738368: Configuration option
'bluestore_block_db_size' may not be modified at runtime) when using rbd
ls for example.
I also have similar messages on the storage nodes but only if I add
client_admin_socket to the config. However I am not getting complaints
about bluestore_block_db_size
To summarize it:
1. Why am I seeing this messages when I execute client commands?
2. Since those messages are legitimate configurations what daemons do I
need to restart so ceph accepts admin_socket (restarting mons didn't
help, I have seen a client creating a socket with PID, but messages
still continue)
3. Client spits bluestore_block_db_size when it starts, but server
daemons are not, why and how to fix it?
I am sorry for the long post, I have been a long hammer / jewel user,
just trying to make sense out of new mimic cluster we are trying to test.
