Jack wrote: > On 3/4/20 8:41 AM, Dale wrote: >> All the timing of the above problems are very similar. I believe they >> have the same cause. When I finished my updates, I logged out, went to >> boot runlevel, used checkrestart to make sure everything that needed to >> be restarted was clean, restarted any that weren't and then when back to >> default runlevel. In the past this has always worked fine. Thing is, >> elogind is in the boot runlevel. I'm going to have to get used to >> restarting it manually I guess. Could elogind be the cause of all >> this? Would it be safe to put elogind in the default runlevel? That >> would solve the problem of me forgetting to restart it after upgrades. >> Or would some other service in the boot runlevel start it as a >> dependency anyway?? >> >> When I get to a point where I can logout and back in, I'll test >> restarting elogind to see if it helps. Thing is, I'm not really sure >> what all elogind does but from what little I know, it sounds like a good >> place to start. Thing that confuses me, checkrestart not showing it >> needed to be restarted. It's never failed me before. > > I was recently in a similar position (but not such serious effects) > but discovered that elogind refused to restart. The message was that > it wouldn't start because it was already started, but that implies > that it simply failed to stop, without producing any error message. I > didn't want to fight it any further, so I just rebooted. > > Jack > > >
So elogind is a pretty good suspect. One reason I'm asking about this, I'm trying to figure out how elogind fails. After all, if I'm stuck on a console, I can't use Seamonkey or anything to find help. I need to be able to recognize what is failing. So far, I've yet to find where elogind problems are logged. When you run into the problem with a stuck script, don't forget the zap option. I'd recommend using ps aux | grep <name> to make sure it is killed and if not kill it with kill first. After you use the zap option, it should start it normally, the start option. In case you have never heard of this, it looks like this: /etc/init.d/chronyd zap Hope that helps. Thanks for the reply. Dale :-) :-)
