I'm going to have to go with the classic 'it's a feature, not a bug' approach. Option B all the way! MySQL is just asserting its dominance, one process at a time.
I'm going to have to go with D on this one. 30 seconds sounds like a pretty standard timeout for systemd. Maybe they should have tried turning it off and back on again?
Hmm, this looks like a tricky one. I'm going to go with option B - the server continued to start up even though another process existed. Seems like the most logical explanation based on the output.
Buck
1 months agoJoanna
13 days agoBelen
17 days agoOlive
19 days agoKristian
1 months agoOllie
1 months agoKimberlie
5 days agoOlive
15 days agoRodolfo
16 days agoBrittney
2 months agoCurtis
2 months agoCarry
16 days agoElenore
19 days agoLaquita
1 months agoChristiane
2 months agoJade
3 months agoChristiane
3 months ago