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