<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">On 10/27/19 8:34 AM, Mike Bibbings
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ceccd90b-7e47-03b5-0be6-1b447da7fcaa@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 27/10/2019 01:42, James Abernathy
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:78FB086F-348F-4F0B-AE14-E88FE5EC8C95@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="">I’ve had to fix the race conditions with Ubuntu
18.04 and network tuners use with mythtv-backend v30. Changing
the systemd services configuration resolved that. I have not
thought about that for some time.</div>
<div class=""><br class="">
</div>
<div class="">However, I now have what appears to be similar
issues with Raspbian Buster on a Raspberry Pi 4 with
mythtv-Light and mythtv-backend. There are lot’s of Raspbian
race conditions related to networking at boot.</div>
<div class=""><br class="">
</div>
<div class="">If I build a straight forward FE/BE combo using
mythtv-light and adding backend, mariadb, etc. I occasionally
have no HDHR tuners after a boot. I can fix this by systemctl
stop/start mythtv-backend. I can also fix this with a
raspi-config and set the boot/wait on the networking option.
That’s the same option you need to set so your can do NFS
mounts in the fstab at boot.</div>
<div class=""><br class="">
</div>
<div class="">So at first I thought changing raspi-config was
the solution, but I kept loosing the lxpanel after a boot.
Couldn’t fix it unless I turned off the boot/wait on
networking. </div>
<div class=""><br class="">
</div>
<div class="">Now I’m looking at fixing this like we did on
Ubuntu 18.04. </div>
<div class=""><br class="">
</div>
<div class="">Has anyone had similar issues on Raspbian </div>
<br class="">
<div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;" class="">Jim
Abernathy<br class="">
<a href="mailto:jfabernathy@gmail.com" class=""
moz-do-not-send="true">jfabernathy@gmail.com</a><br
class="">
<br class="">
<br class="">
</div>
</div>
</blockquote>
<p><br>
</p>
<p>Out of interest what does running "systemd-analyze
critical-chain" show ?<br>
</p>
<p>On my Pi4 I get:</p>
<p><tt>pi@pi4-20191006:~ $ systemd-analyze critical-chain </tt><tt><br>
</tt><tt>The time after the unit is active or started is printed
after the "@" character.</tt><tt><br>
</tt><tt>The time the unit takes to start is printed after the
"+" character.</tt><tt><br>
</tt><tt><br>
</tt><tt>graphical.target @18.780s</tt><tt><br>
</tt><tt>└─multi-user.target @18.779s</tt><tt><br>
</tt><tt> └─mythtv-backend.service @18.778s</tt><tt><br>
</tt><tt> └─mariadb.service @17.491s +1.281s</tt><tt><br>
</tt><tt> └─network.target @17.483s</tt><tt><br>
</tt><tt> └─dhcpcd.service @5.230s +12.249s</tt><tt><br>
</tt><tt> └─basic.target @4.994s</tt><tt><br>
</tt><tt> └─sockets.target @4.994s</tt><tt><br>
</tt><tt> └─avahi-daemon.socket @4.994s</tt><tt><br>
</tt><tt> └─sysinit.target @4.990s</tt><tt><br>
</tt><tt> └─systemd-timesyncd.service @4.504s
+483ms</tt><tt><br>
</tt><tt> └─systemd-tmpfiles-setup.service
@4.363s +120ms</tt><tt><br>
</tt><tt> └─local-fs.target @4.356s</tt><tt><br>
</tt><tt> └─boot.mount @4.298s +54ms</tt><tt><br>
</tt><tt> └─<a
class="moz-txt-link-abbreviated"
href="mailto:systemd-fsck@dev-disk-by\x2dpartuuid-83c29599\x2d01.service"
moz-do-not-send="true">systemd-fsck@dev-disk-by\x2dpartuuid-83c29599\x2d01.service</a>
@3.890s +399ms</tt><tt><br>
</tt><tt>
└─dev-disk-by\x2dpartuuid-83c29599\x2d01.device @3.390s</tt><tt><br>
</tt></p>
<p><br>
</p>
<p>Mike<br>
</p>
<br>
</blockquote>
pi@rpimythtv:~ $ systemd-analyze critical-chain<br>
The time after the unit is active or started is printed after the
"@" character.<br>
The time the unit takes to start is printed after the "+" character.<br>
<br>
graphical.target @13.320s<br>
└─multi-user.target @13.319s<br>
└─hciuart.service @6.360s +6.888s<br>
└─basic.target @6.354s<br>
└─sockets.target @6.353s<br>
└─dbus.socket @6.353s<br>
└─sysinit.target @6.344s<br>
└─sys-fs-fuse-connections.mount @11.282s +26ms<br>
└─systemd-modules-load.service @870ms +79ms<br>
└─systemd-journald.socket @773ms<br>
└─system.slice @734ms<br>
└─-.slice @734ms<br>
<p><br>
</p>
<p>Here's what I got!</p>
<p>Jim A</p>
<p><br>
</p>
</body>
</html>