Hi, I tried creating the directory but then it complained about missing log files. I think I'm just going to block out the logwatch file. It's annoying that the default config bleats out. Thanks for the feedback. -derek Darrell Budic <budic@onholyground.com> writes:
OVS is an optional tech preview in 4.1.x, you don’t need it. It is annoying about the logwatch errors though…
I think I created the directory to avoid the errors, I forgot exactly what it was, sorry.
-------------------------------------------------------------------------- From: Derek Atkins <derek@ihtfp.com> Subject: [ovirt-users] OVS not running / logwatch error after upgrade from 4.0.6 to 4.1.8 Date: January 19, 2018 at 10:44:56 AM CST To: users
Hi, I recently upgraded my 1-host ovirt deployment from 4.0.6 to 4.1.8. Since then, the host has been reporting a cron.daily error:
/etc/cron.daily/logrotate:
logrotate_script: line 4: cd: /var/run/openvswitch: No such file or directory
This isn't surprising, since:
# systemctl status openvswitch ● openvswitch.service - Open vSwitch Loaded: loaded (/usr/lib/systemd/system/openvswitch.service; disabled; vendor preset: disabled) Active: inactive (dead)
The host was just upgraded by "yum update". Was there anything special that needed to happen after the update? Do I *NEED* OVS running? The VMs all seem to be behaving properly.
Thanks,
-derek
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant