search for: comend

On 9/11/20 5:29 PM, Quinn Comendant wrote: > Those have always reported success (even before I removed the OnFailure option): In that case, I'd revert the change you made, unlock the root account so that you can use the emergency shell, let the system boot to an emergency shell, and collect the output of "systemctl...

Every 5 minutes. This moment(before sysvolreset,) machine is ok . This comend is valid now ? *In DC01 Problem does not exist with sysvol. Regards; On 10-01-2018 14:51, lingpanda101 via samba wrote: > On 1/10/2018 11:42 AM, Carlos via samba wrote: >> HI >> >> Rsync >> >> DC1 to DC2 / DC3 >> >> root / usr / bin / rsync -XAaz --...

On 1/11/2018 10:45 AM, Carlos via samba wrote: > Hi > > Any ? > > Regards; > > > On 10-01-2018 15:11, Carlos wrote: >> >> Every 5 minutes. >> >> This moment(before sysvolreset,) machine is ok . This comend is valid >> now ? >> >> *In DC01 Problem does not exist with sysvol. >> >> Regards; >> >> >> >> On 10-01-2018 14:51, lingpanda101 via samba wrote: >>> On 1/10/2018 11:42 AM, Carlos via samba wrote: >>>> HI >>>>...

On 9/11/20 4:51 PM, Quinn Comendant wrote: > Does anyone know what initrd-parse-etc.service does? Or have suggestions how to troubleshoot that unit specifically? Run "systemctl daemon-reload && echo success" and verify that it reports success, and not errors. Check the output of "systemctl status init...

Hello all, I've got an odd problem that doesn't seem to be mentioned anywhere. I have several identical CentOS 7 servers (GCE instances). I recently ran `yum update` and rebooted all of them. All the servers came back fine except one. I opened a connection to the serial console of the broken server, and was greeted with this prompt: ? Cannot open access to console, the root

Hi Quinn, Am Do., 10. Sept. 2020 um 04:49 Uhr schrieb Quinn Comendant < quinn at strangecode.com>: > [...] > I don't see any significant errors in the boot log, but I would appreciate > if anyone has a moment to help me look for issues. Here's a copy of the > serial console boot log ? you can find the "Press Enter to continue"...

Hi Thomas, On 10 Sep 2020 10:06:01, Thomas Bendler wrote: > If I'm not mistaken, problems after UTMP point to problems with X/ hardware > configuration. So I guess you might find more information when you also > have a look at the log files of systemd. I don't see any hardware issues. Here's the output from `journalctl -p 5 -xb`: https://write.as/2vjgz6pfmopg7fnf.txt The

...ar issue on 7.6 - the LVM timeouts were too short and it was timing out as we had a lot of multipath devices. Once those were up , you could just continue. journalctl will show you what has happened. Best Regards, Strahil Nikolov ? ?????????, 10 ????????? 2020 ?., 18:57:02 ???????+3, Quinn Comendant <quinn at strangecode.com> ??????: Hi Thomas, On 10 Sep 2020 10:06:01, Thomas Bendler wrote: > If I'm not mistaken, problems after UTMP point to problems with X/ hardware > configuration. So I guess you might find more information when you also > have a look at the log...

On 9/12/20 1:04 PM, Quinn Comendant wrote: > I don't see any errors from `systemctl status initrd-parse-etc.service` or > `journalctl -b 0` (I've pasted the full output here:https://write.as/at21opjv3o9fin1t.txt) I see errors in the journalctl output.? Look into these: Sep 12 19:41:12 myhost systemd-vconsole-set...

On 9/12/20 1:04 PM, Quinn Comendant wrote: > [root at myhost ~] systemctl status initrd-switch-root.service > ? initrd-switch-root.service - Switch Root > Loaded: loaded (/usr/lib/systemd/system/initrd-switch-root.service; static; vendor preset: disabled) > Active: failed (Result: signal) since Sat 2020-09-12 1...

Hi Any ? Regards; On 10-01-2018 15:11, Carlos wrote: > > Every 5 minutes. > > This moment(before sysvolreset,) machine is ok . This comend is valid > now ? > > *In DC01 Problem does not exist with sysvol. > > Regards; > > > > On 10-01-2018 14:51, lingpanda101 via samba wrote: >> On 1/10/2018 11:42 AM, Carlos via samba wrote: >>> HI >>> >>> Rsync >>> >>> DC1...

...> On 1/11/2018 10:45 AM, Carlos via samba wrote: >> Hi >> >> Any ? >> >> Regards; >> >> >> On 10-01-2018 15:11, Carlos wrote: >>> >>> Every 5 minutes. >>> >>> This moment(before sysvolreset,) machine is ok . This comend is >>> valid now ? >>> >>> *In DC01 Problem does not exist with sysvol. >>> >>> Regards; >>> >>> >>> >>> On 10-01-2018 14:51, lingpanda101 via samba wrote: >>>> On 1/10/2018 11:42 AM, Carlos via samba wrot...

HI Rsync DC1 to DC2 / DC3 root / usr / bin / rsync -XAaz --delete-after / opt / samba / var / locks / sysvol root @ DCXX: / opt / samba / var / Run Windows "gpupdate / force", information error permission (show ID GPO, any gpos ...). Yes, the only gpo, with errors. Regards; On 10-01-2018 14:29, lingpanda101 via samba wrote: > On 1/10/2018 8:59 AM, Carlos via samba wrote:

Update: I found a workaround to prevent entering emergency shell during boot for no reason. I've simply cleared the `OnFailure=` option for initrd-parse-etc.service (which was previously set to `OnFailure=emergency.target`). Now the server boots successfully without dropping into an emergency shell. This is a total hack, and I'm a little embarrassed that it's the only solution that

On 11 Sep 2020 17:23:00, Gordon Messmer wrote: > Run "systemctl daemon-reload && echo success" and verify that it > reports success, and not errors. > > Check the output of "systemctl status initrd-cleanup" too. Those have always reported success (even before I removed the OnFailure option): [~] sudo systemctl daemon-reload && echo success

On 12 Sep 2020 11:40:48, Gordon Messmer wrote: > In that case, I'd revert the change you made, unlock the root account > so that you can use the emergency shell, let the system boot to an > emergency shell, and collect the output of "systemctl status > initrd-parse-etc.service" and "journalctl -b 0". Ok, I was able to log in as root in the emergency shell.