<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi,</p>
<p>The Centos-7.6 update came out yesterday<br>
</p>
<p><a class="moz-txt-link-freetext" href="https://lwn.net/Articles/773680/">https://lwn.net/Articles/773680/</a><br>
</p>
<p>On many DAQ machines this update was automatically installed around 5AM on Dec 4. On most machines the update seemed to work ok, but I have at least two machines where the update seemed to go really wrong. I'm finding it hard to be very certain about what
is wrong, but here's a couple symptoms/clues:</p>
<p>1) The X-window (GNOME) crashed on the machines. I tried to restart GNOME <br>
</p>
<p>systemctl restart gdm.service</p>
<p>but it didn't work. system messages didn't provide me any clear clue:<br>
</p>
<p>Dec 5 11:53:44 daq03 systemd-logind: New session c4 of user gdm.<br>
Dec 5 11:53:44 daq03 gdm: GdmDisplay: display lasted 0.249658 seconds<br>
Dec 5 11:53:44 daq03 systemd-logind: Removed session c4.<br>
< repeated lines><br>
Dec 5 11:53:44 daq03 gdm: GLib: g_variant_new_string: assertion 'string != NULL' failed<br>
Dec 5 11:53:45 daq03 gdm: Child process -4877 was already dead.<br>
Dec 5 11:53:45 daq03 gdm: Child process 4873 was already dead.<br>
Dec 5 11:53:45 daq03 gdm: Unable to kill session worker process<br>
Dec 5 11:53:45 daq03 gdm: GdmDisplay: display lasted 0.136216 seconds<br>
Dec 5 11:53:45 daq03 gdm: GLib: g_variant_new_string: assertion 'string != NULL' failed<br>
Dec 5 11:53:45 daq03 gdm: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors</p>
<br>
<p>2) The ypbind service seemed to fail after the NetworkManager update:</p>
<p>Dec 4 04:55:29 daq10 yum[27323]: Updated: 1:NetworkManager-1.12.0-8.el7_6.x86_64<br>
Dec 4 04:55:29 daq10 yum[27323]: Updated: 1:NetworkManager-wifi-1.12.0-8.el7_6.x86_64<br>
Dec 4 04:55:29 daq10 dbus[909]: [system] Reloaded configuration<br>
<snip><br>
Dec 4 04:56:59 daq10 systemd: rpc-statd.service stop-sigterm timed out. Killing.<br>
Dec 4 04:56:59 daq10 systemd: rpc-statd.service: main process exited, code=killed, status=9/KILL<br>
Dec 4 04:56:59 daq10 systemd: Stopped NFS status monitor for NFSv2/3 locking..<br>
Dec 4 04:56:59 daq10 systemd: Unit rpc-statd.service entered failed state.<br>
Dec 4 04:56:59 daq10 systemd: rpc-statd.service failed.<br>
<snip><br>
Dec 4 04:56:59 daq10 systemd: Failed to start NIS/YP (Network Information Service) Clients to NIS Domain Binder.<br>
Dec 4 04:56:59 daq10 systemd: Unit ypbind.service entered failed state.<br>
Dec 4 04:56:59 daq10 systemd: ypbind.service failed.</p>
<p>Full message at end. <br>
</p>
<p>3) firewalld had failed, though it could be restarted</p>
[root@daq10 ~]# systemctl status firewalld<br>
● firewalld.service - firewalld - dynamic firewall daemon<br>
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)<br>
Active: failed (Result: exit-code) since Tue 2018-12-04 04:58:34 PST; 1 day 5h ago<br>
Docs: man:firewalld(1)<br>
Main PID: 995 (code=exited, status=1/FAILURE)<br>
<br>
Nov 20 21:55:20 daq10.triumf.ca systemd[1]: Starting firewalld - dynamic firewall daemon...<br>
Nov 20 21:55:20 daq10.triumf.ca systemd[1]: Started firewalld - dynamic firewall daemon.<br>
Dec 04 04:58:34 daq10.triumf.ca systemd[1]: firewalld.service: main process exited, code=exited, status=1/FAILURE<br>
Dec 04 04:58:34 daq10.triumf.ca systemd[1]: Unit firewalld.service entered failed state.<br>
Dec 04 04:58:34 daq10.triumf.ca systemd[1]: firewalld.service failed.<br>
<br>
<p>4) There are some error reports similar to this, though it is not clear that the problems are exactly the same.<br>
</p>
<pre class="messagepre" style="font-family: "lucida console", courier, monospace; color: rgb(0, 0, 0); font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"><a href="https://www.centos.org/forums/viewtopic.php?t=69009" style="color: rgb(128, 0, 128); text-decoration: none;">https://www.centos.org/forums/viewtopic.php?t=69009</a>
<a href="https://bugs.centos.org/view.php?id=15526" style="color: rgb(128, 0, 128); text-decoration: none;">https://bugs.centos.org/view.php?id=15526</a>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1644933" style="color: rgb(128, 0, 128); text-decoration: none;">https://bugzilla.redhat.com/show_bug.cgi?id=1644933</a>
</pre>
<p>I'm mostly confused about why the update was not a problem for most of our Centos-7.6 machines. Both the machines affected were desktop machines, though certainly other desktop machines were ok.<br>
</p>
<p>Is anyone else having problems with this update?<br>
</p>
<p>Cheers,<br>
Thomas</p>
<p><br>
</p>
<p><br>
</p>
<p>Full error message in log</p>
<p>Dec 4 04:55:29 daq10 yum[27323]: Updated: 1:NetworkManager-1.12.0-8.el7_6.x86_64<br>
Dec 4 04:55:29 daq10 yum[27323]: Updated: 1:NetworkManager-wifi-1.12.0-8.el7_6.x86_64<br>
Dec 4 04:55:29 daq10 dbus[909]: [system] Reloaded configuration<br>
Dec 4 04:55:29 daq10 systemd: Reloading.<br>
Dec 4 04:55:29 daq10 systemd: [/usr/lib/systemd/system/yum-autoupdate.service:11] Unknown lvalue 'ExecStopPre' in section 'Service'<br>
Dec 4 04:55:29 daq10 systemd: Failed to reload: Address already in use<br>
Dec 4 04:55:29 daq10 systemd: Reached target RPC Port Mapper.<br>
Dec 4 04:55:29 daq10 systemd: Stopping NIS/YP (Network Information Service) Clients to NIS Domain Binder...<br>
Dec 4 04:55:29 daq10 systemd: Stopping NFS status monitor for NFSv2/3 locking....<br>
Dec 4 04:55:29 daq10 systemd: Stopped NFS status monitor for NFSv2/3 locking..<br>
Dec 4 04:55:29 daq10 systemd: Starting Preprocess NFS configuration...<br>
Dec 4 04:55:29 daq10 systemd: Started Preprocess NFS configuration.<br>
Dec 4 04:55:29 daq10 systemd: Stopped NIS/YP (Network Information Service) Clients to NIS Domain Binder.<br>
Dec 4 04:55:29 daq10 systemd: Stopping RPC bind service...<br>
Dec 4 04:55:29 daq10 systemd: Stopped RPC bind service.<br>
Dec 4 04:55:29 daq10 systemd: Listening on RPCbind Server Activation Socket.<br>
Dec 4 04:55:29 daq10 systemd: Starting NFS status monitor for NFSv2/3 locking....<br>
Dec 4 04:55:29 daq10 systemd: Starting RPC bind service...<br>
Dec 4 04:55:29 daq10 systemd: Started RPC bind service.<br>
Dec 4 04:55:29 daq10 systemd: Starting NIS/YP (Network Information Service) Clients to NIS Domain Binder...<br>
Dec 4 04:55:29 daq10 systemd: Reloading.<br>
Dec 4 04:55:29 daq10 rpc.statd[9555]: Version 1.3.0 starting<br>
Dec 4 04:55:29 daq10 rpc.statd[9555]: Flags: TI-RPC<br>
Dec 4 04:55:29 daq10 systemd: [/usr/lib/systemd/system/yum-autoupdate.service:11] Unknown lvalue 'ExecStopPre' in section 'Service'<br>
Dec 4 04:55:29 daq10 systemd: Started NFS status monitor for NFSv2/3 locking..<br>
Dec 4 04:55:29 daq10 systemd: Stopping RPC bind service...<br>
Dec 4 04:55:29 daq10 systemd: Stopping NFS status monitor for NFSv2/3 locking....<br>
Dec 4 04:55:29 daq10 systemd: Stopped RPC bind service.<br>
Dec 4 04:55:29 daq10 setsebool: The allow_ypbind policy boolean was changed to 1 by root<br>
Dec 4 04:55:29 daq10 dbus[7600]: avc: received policyload notice (seqno=3)<br>
Dec 4 04:55:29 daq10 dbus[14521]: avc: received policyload notice (seqno=3)<br>
Dec 4 04:55:29 daq10 dbus[7767]: avc: received policyload notice (seqno=3)<br>
Dec 4 04:55:29 daq10 dbus[14740]: avc: received policyload notice (seqno=3)<br>
Dec 4 04:56:27 daq10 journal: Error releasing name com.redhat.NewPrinterNotification: Timeout was reached<br>
Dec 4 04:56:27 daq10 journal: Ignored exception from dbus method: Gio.IOErrorEnum: Timeout was reached<br>
Dec 4 04:56:27 daq10 journal: Ignored exception from dbus method: Gio.IOErrorEnum: Timeout was reached<br>
Dec 4 04:56:29 daq10 org.a11y.Bus: Reloaded configuration<br>
Dec 4 04:56:29 daq10 org.a11y.Bus: Reloaded configuration<br>
Dec 4 04:56:52 daq10 journal: Error releasing name com.redhat.PrinterDriversInstaller: Timeout was reached<br>
Dec 4 04:56:59 daq10 systemd: rpc-statd.service stop-sigterm timed out. Killing.<br>
Dec 4 04:56:59 daq10 systemd: rpc-statd.service: main process exited, code=killed, status=9/KILL<br>
Dec 4 04:56:59 daq10 systemd: Stopped NFS status monitor for NFSv2/3 locking..<br>
Dec 4 04:56:59 daq10 systemd: Unit rpc-statd.service entered failed state.<br>
Dec 4 04:56:59 daq10 systemd: rpc-statd.service failed.<br>
Dec 4 04:56:59 daq10 systemd: ypbind.service start operation timed out. Terminating.<br>
Dec 4 04:56:59 daq10 systemd: Closed RPCbind Server Activation Socket.<br>
Dec 4 04:56:59 daq10 systemd: Stopping RPCbind Server Activation Socket.<br>
Dec 4 04:56:59 daq10 systemd: Listening on RPCbind Server Activation Socket.<br>
Dec 4 04:56:59 daq10 systemd: Starting RPC bind service...<br>
Dec 4 04:56:59 daq10 systemd: Starting Preprocess NFS configuration...<br>
Dec 4 04:56:59 daq10 systemd: Started RPC bind service.<br>
Dec 4 04:56:59 daq10 systemd: Started Preprocess NFS configuration.<br>
Dec 4 04:56:59 daq10 systemd: Starting NFS status monitor for NFSv2/3 locking....<br>
Dec 4 04:56:59 daq10 systemd: Failed to start NIS/YP (Network Information Service) Clients to NIS Domain Binder.<br>
Dec 4 04:56:59 daq10 systemd: Unit ypbind.service entered failed state.<br>
Dec 4 04:56:59 daq10 systemd: ypbind.service failed.<br>
<br>
</p>
</body>
</html>