Thanks, I actually restarted all of the VMs, but I'm still getting all these nulls. Here's my broker-log.conf file:
[loggers] keys=root [handlers] keys=syslog,logfile [formatters] keys=long,sysform [logger_root] level=ERROR handlers=syslog,logfile propagate=0 [handler_syslog] level=ERROR class=handlers.SysLogHandler formatter=sysform args=('/dev/log', handlers.SysLogHandler.LOG_USER) [handler_logfile] class=logging.handlers.TimedRotatingFileHandler args=('/var/log/ovirt-hosted-engine-ha/broker.log', 'd', 1, 7) level=ERROR formatter=long [formatter_long] format=%(threadName)s::%(levelname)s::%(asctime)s::%(module)s::%(lineno)d::%(name)s::(%(funcName)s) %(message)s [formatter_sysform] format=ovirt-ha-broker %(name)s %(levelname)s %(message)s datefmt=
I'm puzzled.
Thanks Didi and Strahil
On 11/25/21 6:32 PM, Strahil Nikolov wrote:
--The broker logs can be changed... No need to shutdown the VM.
Just use the hosted-engine tool to put the vm in global maintenance, then change the log level and restart the broker/agent service.
After several minutes (wait at least 5 min) 'hosted-engine --vm-status' should show that the situation is OK and you can remove the maintenance.
Best Regards,Strahil Nikolov
On Thu, Nov 25, 2021 at 18:05, Valerio Luccio<valerio.luccio@nyu.edu> wrote:_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AIVNDIUJ7THFY5GQ5TIFP7FYSXNQTWE2/
Valerio Luccio | ||
High Performance Computing | 10 Astor Place, Room 416D | |
New York University | New York, NY 10003 |
"In an open world, who needs windows or gates ?"