I had to bypass relayd to roll prod stable. Down to apache. Taking care of http and https. By redirect. Now this setup (if I can call it) is stable.
. P.S. Looks like we have to move forward from here. > 21 dec. 2017 kl. 21:58 skrev Maxim Bourmistrov <[email protected]>: > > > Sorry, but I have to say > Releases after 5.9 are NOT production stable. > (Until all bugs are smashed within stack changes and SMP unlock). > After 5.9 - cost money and effort. > MONEY. > > //mxb > >> 21 dec. 2017 kl. 20:29 skrev Maxim Bourmistrov <[email protected]>: >> >> Hey, >> After upgrading from 6.0-stable to 6.2-stable (syspatch) existing setup >> started to hang. >> As of burst of emails from me following is known: >> >> Relayd is a main process to take CPU. >> Also running ospfd and bgpd (for blocklist distrib) >> >> With 6.0, relayd used to have two or more procs with high CPU usage (99,9% - >> 100%, per core). >> Now, setup is just adjusted to conform new reality with TLS protocol, all >> just hangs. >> No core (even it is enabled in sysctl), no panic - nothing. >> Syslog sending to remote shows nothing. >> >> I know, it is now enough for any debug and troubleshooting at all. >> Just FYI. >> >> Any ideas are welcome. >> >> //mxb >
