Date: Sun, 3 Apr 2022 22:27:59 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Peter <pmc@citylink.dinoex.sub.org> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Slow startup from D19488 (rtsol: sendmsg: Permission denied) Message-ID: <CAN6yY1uscuL4EzGOyvXSqH26o7NJH1xJKk2vm=Cj7D_zcnrw4Q@mail.gmail.com> In-Reply-To: <Ykb9gvmgy8alA5n8@gate.intra.daemon.contact> References: <YkN2acB17mOkMlF5@gate.intra.daemon.contact> <alpine.BSF.2.00.2203292154240.68830@ai.fobar.qr> <YkOcv0SQ5Wlr/6Qt@gate.intra.daemon.contact> <CAN6yY1uhryDh7b-TRLNCXeSmPMCMBva_NXaDackfpSgbgP9FOA@mail.gmail.com> <Ykb9gvmgy8alA5n8@gate.intra.daemon.contact>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000095287805dbcd673c Content-Type: text/plain; charset="UTF-8" On Fri, Apr 1, 2022 at 6:36 AM Peter <pmc@citylink.dinoex.sub.org> wrote: > On Wed, Mar 30, 2022 at 08:59:24PM -0700, Kevin Oberman wrote: > > ! > ! I am a bit puzzled as after two years you are the first one to report > ! > ! that problem to my knowledge for either base system or jails. > ! > > ! > This is what greatly wonders me, too. So I was stronly thinking > ! > that I am doing something wrong or unusual. But I cannot figure > ! > it out, it just seems that the detrimental effect of the change > ! > cannot be avoided (e.g. "service jail start" takes quite long now - > ! > there's a lot of them). > > ! This may be irrelevant, but updating to the stable branch is not > ! recommended as it is not regularly tested. Updating to 13.0-Release and > ! then to stable is less likely to be problematic. > > Hi Kevin, > > (You are Kevin Oberman the network guru ?!?) > > Maybe a decade or so ago. After over a decade of retirement, I'm not sure how BGP is spelled. And why would the network fib? JK. I do recall what a Forwarding Information Base is. You're essentially right, and I would normally agree. And it is not > irrelevant, but then, it's apparently not related to this specific > issue. > > The point is: I am not interested in 13.0. I am interested in > 13.1. So I put up a pilot early, in order to report potential issues > (as I reported here the issue with the fix for PR 76398). At that > point this had to be stable/13. > > Then on saturday I tried to use fib, and I figured that fib is not > fully implenented in 12.3, but apparently it is in 13. So I decided > to give it a try and move my backbone to 13 - and to the same version > that is already running on the pilot system, so that there is some > base to compare things. > > Now there are issues - but it doesn't appear that these issues would > be very different between stable/13 and releng/13.1. And -as can be > read above- it neither looks like these issues would just disappear > by themselves in the release, without someone looking for them. > (The broken "ipfw fwd" is probably also present in 13.0 and will very > likely still be present in 13.1 - and I don't believe much in testing > because you can only test what you already expect to fail.) > > I am indeed pondering about the best approach. Over the last years > I was only doing release upgrades (after I had run into ugly ZFS > problems somewhere in Rel.10, caused by an intermediately broken > Stable *and* broken memory chips). > Now I am considering to do upgrades some 2-3 months ahead of the > release, so if there are problems that hit here, there is a chance > to spare the general public one or two troubles. > > cheerio, > PMc > Well, that does explain a bit. I'm not sure of the best way to troubleshoot this. It is extremely unlikely that it's broken on STABLE and fixed in 13.1-BETA or RC. Sorry I can't be more useful. If I had experience with FIBs on FreeBSD. It's not the same as RIBs and FIBs on Junipers. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --00000000000095287805dbcd673c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon= t-family:tahoma,sans-serif;font-size:small">On Fri, Apr 1, 2022 at 6:36 AM = Peter <<a href=3D"mailto:pmc@citylink.dinoex.sub.org">pmc@citylink.dinoe= x.sub.org</a>> wrote:<br></div></div><div class=3D"gmail_quote"><blockqu= ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px= solid rgb(204,204,204);padding-left:1ex">On Wed, Mar 30, 2022 at 08:59:24P= M -0700, Kevin Oberman wrote:<br> <br> ! > ! I am a bit puzzled as after two years you are the first one to rep= ort<br> ! > ! that problem to my knowledge for either base system or jails.<br> ! ><br> ! > This is what greatly wonders me, too. So I was stronly thinking<br> ! > that I am doing something wrong or unusual. But I cannot figure<br> ! > it out, it just seems that the detrimental effect of the change<br> ! > cannot be avoided (e.g. "service jail start" takes quite l= ong now -<br> ! > there's a lot of them).<br> <br> ! This may be irrelevant, but updating to the stable branch is not<br> ! recommended as it is not regularly tested. Updating to 13.0-Release and<b= r> ! then to stable is less likely to be problematic.<br> <br> Hi Kevin,<br> <br> =C2=A0 (You are Kevin Oberman the network guru ?!?)<br> <br></blockquote><div><span class=3D"gmail_default" style=3D"font-family:ta= homa,sans-serif;font-size:small"></span></div><div><span class=3D"gmail_def= ault" style=3D"font-family:tahoma,sans-serif;font-size:small">Maybe a decad= e or so ago. After over a decade of retirement,=C2=A0 I'm not sure how = BGP is spelled</span><span class=3D"gmail_default" style=3D"font-family:tah= oma,sans-serif;font-size:small">. And why would the network fib?</span></di= v><div><span class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif= ;font-size:small"><br></span></div><div><span class=3D"gmail_default" style= =3D"font-family:tahoma,sans-serif;font-size:small">JK. I do recall what a F= orwarding Information Base is.<br></span></div><div><span class=3D"gmail_de= fault" style=3D"font-family:tahoma,sans-serif;font-size:small"><br></span><= /div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo= rder-left:1px solid rgb(204,204,204);padding-left:1ex"> =C2=A0 You're essentially right, and I would normally agree. And it is = not<br> irrelevant, but then, it's apparently not related to this specific<br> issue.<br> <br> The point is: I am not interested in 13.0. I am interested in<br> 13.1. So I put up a pilot early, in order to report potential issues<br> (as I reported here the issue with the fix for PR 76398). At that<br> point this had to be stable/13.<br> <br> Then on saturday I tried to use fib, and I figured that fib is not<br> fully implenented in 12.3, but apparently it is in 13. So I decided<br> to give it a try and move my backbone to 13 - and to the same version<br> that is already running on the pilot system, so that there is some<br> base to compare things.<br> <br> Now there are issues - but it doesn't appear that these issues would<br= > be very different between stable/13 and releng/13.1. And -as can be<br> read above- it neither looks like these issues would just disappear<br> by themselves in the release, without someone looking for them.<br> (The broken "ipfw fwd" is probably also present in 13.0 and will = very<br> likely still be present in 13.1 - and I don't believe much in testing<b= r> because you can only test what you already expect to fail.)<br> <br> I am indeed pondering about the best approach. Over the last years<br> I was only doing release upgrades (after I had run into ugly ZFS<br> problems somewhere in Rel.10, caused by an intermediately broken<br> Stable *and* broken memory chips). <br> Now I am considering to do upgrades some 2-3 months ahead of the<br> release, so if there are problems that hit here, there is a chance<br> to spare the general public one or two troubles.<br> <br> cheerio,<br> PMc<br> </blockquote></div><br clear=3D"all"><div style=3D"font-family:tahoma,sans-= serif;font-size:small" class=3D"gmail_default">Well, that does explain a bi= t. I'm not sure of the best way to troubleshoot this. It is extremely u= nlikely that it's broken on STABLE and fixed in 13.1-BETA or RC. <br></= div><div style=3D"font-family:tahoma,sans-serif;font-size:small" class=3D"g= mail_default"><br></div><div style=3D"font-family:tahoma,sans-serif;font-si= ze:small" class=3D"gmail_default">Sorry I can't be more useful. If I ha= d experience with FIBs on FreeBSD. It's not the same as RIBs and FIBs o= n Junipers.<br></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><div= dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"l= tr">Kevin Oberman, Part time kid herder and retired Network Engineer<br>E-m= ail: <a href=3D"mailto:rkoberman@gmail.com" target=3D"_blank">rkoberman@gma= il.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1= B055683</div></div></div></div></div></div></div></div></div> --00000000000095287805dbcd673c--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1uscuL4EzGOyvXSqH26o7NJH1xJKk2vm=Cj7D_zcnrw4Q>