Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

why dose openstack output errlog to /var/log/messages even setting use_syslog=False ?

On compute node(RHEL7), /var/log/messages Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405' Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405' Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405' ...

The error itself is not important, I just want to know why dose openstack output errlog to /var/log/messages even setting use_syslog=False ? I think the log should be wrote to /var/log/ceilometer.log as I configed. Can someone plz tell me ? thanks a lot!

why dose openstack output errlog to /var/log/messages even setting use_syslog=False ?

On compute node(RHEL7), /var/log/messages /var/log/messages

Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405'
Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405'
Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405'
...

...

The error itself is not important, I just want to know why dose openstack output errlog to /var/log/messages even setting use_syslog=False ? I think the log should be wrote to /var/log/ceilometer.log as I configed. Can someone plz tell me ? thanks a lot!

why dose openstack output errlog to /var/log/messages even setting use_syslog=False ?

On compute node(RHEL7), /var/log/messages

Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405'
Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405'
Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405'
...

The error itself is not important, I just want to know why dose openstack output errlog to /var/log/messages even setting use_syslog=False ? I think the log should be wrote to /var/log/ceilometer.log as I configed. Can someone plz tell me ? thanks a lot!


2015/10/16 update:

I found that whether OpenStack writing log to "/var/log/messages" depends on the config option "use_stderr". This option--if it is set to ‘True’--seems will lead OpenStack to get a logger with a handler to write log to stderr. And OpenStack somehow redirects stderr to "/var/log/messages".

Now my confusion is: Obviously, the default value of "use_stderr" is 'True', and I can't find anywhere this value is overrided in OpenStack's source code if I don't change it in "/etc/xxx/xxx.conf". But the print result clearly shows the value of "use_stderr" in nova is 'False' and in cinder,ceilometer is 'True'. Can someone tell me why?

why dose openstack output errlog to /var/log/messages even setting use_syslog=False ?

On compute node(RHEL7), /var/log/messages

Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405'
Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405'
Aug 24 11:03:11 server2 ceilometer-agent-compute: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '15ee9651-af4c-4288-8c29-5fe720193405'
...
/var/log/messages
MM DD 03:46:44 osc-21 cinder-volume: 2015-12-21 03:46:44.033 21768 INFO cinder.volume.manager [req-7f198482-9a26-4131-95fb-3dc3b8e28cd3 - - - - -] Updating volume status
MM DD 03:46:44 osc-21 cinder-volume: 2015-12-21 03:46:44.058 21768 INFO cinder.volume.drivers.san.hp.hp_3par_common [req-7f198482-9a26-4131-95fb-3dc3b8e28cd3 - - - - -] HP3PARCommon 2.0.40, hp3parclient 3.2.1
MM DD 03:46:44 osc-21 cinder-volume: 2015-12-21 03:46:44.616 21768 INFO cinder.volume.drivers.san.hp.hp_3par_common [req-7f198482-9a26-4131-95fb-3dc3b8e28cd3 - - - - -] Disconnect from 3PAR REST and SSH 32041391-d5ca-4c04-a862-95298d98d379
MM DD 03:46:44 osc-21 cinder-volume: 2015-12-21 03:46:44.638 21768 INFO cinder.volume.drivers.san.hp.hp_3par_common [req-7f198482-9a26-4131-95fb-3dc3b8e28cd3 - - - - -] logout Done 32041391-d5ca-4c04-a862-95298d98d379
...

The error message itself is not important, I just want to know why dose openstack output errlog log to /var/log/messages even setting use_syslog=False ? ?
I think the log just should be wrote to /var/log/ceilometer.log /var/log/cinder/volume.log as I configed. configed.
Can someone plz tell me ? thanks a lot!


2015/10/16 update:

I found that whether OpenStack writing log to "/var/log/messages" depends on the config option "use_stderr".
This option--if it is set to ‘True’--seems will lead OpenStack to get a logger with a handler to write log to stderr.
And OpenStack somehow redirects stderr to "/var/log/messages".

Now my confusion is: is:
Obviously, the default value of "use_stderr" is 'True', and I can't find anywhere this value is overrided in OpenStack's source code if I don't change it in "/etc/xxx/xxx.conf". "/etc/xxx/xxx.conf".
But the print result clearly shows the value of "use_stderr" in nova is 'False' and in cinder,ceilometer is 'True'. cinder is 'True'.
Can someone tell me why?

why dose openstack cinder output errlog log to /var/log/messages even setting use_syslog=False ?

On compute node(RHEL7), /var/log/messages

MM DD 03:46:44 osc-21 cinder-volume: 2015-12-21 03:46:44.033 21768 INFO cinder.volume.manager [req-7f198482-9a26-4131-95fb-3dc3b8e28cd3 - - - - -] Updating volume status 
MM DD 03:46:44 osc-21 cinder-volume: 2015-12-21 03:46:44.058 21768 INFO cinder.volume.drivers.san.hp.hp_3par_common [req-7f198482-9a26-4131-95fb-3dc3b8e28cd3 - - - - -] HP3PARCommon 2.0.40, hp3parclient 3.2.1
MM DD 03:46:44 osc-21 cinder-volume: 2015-12-21 03:46:44.616 21768 INFO cinder.volume.drivers.san.hp.hp_3par_common [req-7f198482-9a26-4131-95fb-3dc3b8e28cd3 - - - - -] Disconnect from 3PAR REST and SSH 32041391-d5ca-4c04-a862-95298d98d379
MM DD 03:46:44 osc-21 cinder-volume: 2015-12-21 03:46:44.638 21768 INFO cinder.volume.drivers.san.hp.hp_3par_common [req-7f198482-9a26-4131-95fb-3dc3b8e28cd3 - - - - -] logout Done 32041391-d5ca-4c04-a862-95298d98d379
32041391-d5ca-4c04-a862-95298d98d379

...

The message itself is not important, I just want to know why dose openstack output log to /var/log/messages ?
I think the log just should be wrote to /var/log/cinder/volume.log as I configed.
Can someone plz tell me ? thanks a lot!


2015/10/16 update:

I found that whether OpenStack writing log to "/var/log/messages" depends on the config option "use_stderr".
This option--if it is set to ‘True’--seems will lead OpenStack to get a logger with a handler to write log to stderr.
And OpenStack somehow redirects stderr to "/var/log/messages".

Now my confusion is:
Obviously, the default value of "use_stderr" is 'True', and I can't find anywhere this value is overrided in OpenStack's source code if I don't change it in "/etc/xxx/xxx.conf".
But the print result clearly shows the value of "use_stderr" in nova is 'False' and in cinder is 'True'.
Can someone tell me why?