19 Jul
2018
19 Jul
'18
9:08 a.m.
I encounter this highly annoying message and 90 second shutdown delay too often.
Why does TDM object to cmdline shutdown or reboot commands from login on the
vttys? How can it be stopped? The immediate inducement to write this comes from
Buster, but it happens in Stretch and openSUSE too, both in UEFI and legacy
contexts.
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
19 Jul
19 Jul
12:11 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2018/07/19 05:08 PM, Felix Miata wrote:
I encounter this highly annoying message and 90 second
shutdown delay too often. Why does TDM object to cmdline
shutdown or reboot commands from login on the vttys? How can it be stopped? The immediate
inducement to write this
comes from Buster, but it happens in Stretch and openSUSE too, both in UEFI and legacy
contexts.
Thanks systemd...........
The best you can do is to reduce the timeout from 90 s to small value.
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAltQgAQACgkQKnW3yore
1c/g4hAAs7X8Pl6qPZy1RZZ+GUhBqD8/lhNGjivc+mGJl7SlQSVyikeV51PeWcXt
tkvHoaTcy1j9o6KjS5NpmwuEF+JVkg3kEYmfFnfbJxdJnejfDU3Qmqmq31i+K+rT
UjMMnAcmXS/NeTKaFGKAXyc0zt+t2RZTN6bKU6BG47XFQzSgsILz3QQf2Jf1SkzW
1SzzfmzppO2cAMvmjYqMrmWvvIvIS/HTkH3xTml2mFC4q8ZNEHZgolYgcpplewxW
49KI4tnkUJojpcMJlB6mAspCj6G1uJv3ETkszrp6ommnKaugaEpDIoDYPVnyoU72
SUX/M+LhDAjhnIVeIS2ox//cBwzDwNaH1amYWUthlCr1vamab2P8JRFUv9gJZJZ/
MrQgo9SfwDojeqfaHuTnQc2fmvzSQZfAcp7Mr9DOciDdDajU5t2KfySljSgBiLQW
SfTFyTwhP+NArZvtdIwt/W+NY3a4KcpzFKOynkBbhkRBWf5Y5kCzMxcBQlavy7Hx
ZCJzpCGOxTLn0m4a2kyJod7+UoIGXt/yk3Fx8TuqtNkwcTYf8WaH2oYT/oe04vlI
d2WZ4vAAtKVpAE6D2gvK1oj89+J2QY0KnlyXHPYLnTSeS5ohQIaYXKD9aEv6CMXb
NLz5WRJRy/kbBW2yUjvMquLn1PimFB1JwNnSCXVeqykUbXEDGrM=
=wpQ8
-----END PGP SIGNATURE-----
3:47 p.m.
On Thursday 19 July 2018 07:11:52 am Michele Calgaro wrote:
On 2018/07/19 05:08 PM, Felix Miata wrote:
Not sure what exact command you're running, but do also add a halt flag if
it's available.
"option to halt services before rebooting. "shutdown -h now" is a graceful
shutdown, and "reboot -h now" is a graceful reboot."
--Source unknown (CentOS)
MySQL likes to break tables otherwise...
Best,
Michael
I encounter this highly annoying message and 90
second shutdown delay too
often. Why does TDM object to cmdline shutdown or reboot commands from
login on the vttys? How can it be stopped? The immediate inducement to
write this comes from Buster, but it happens in Stretch and openSUSE too,
both in UEFI and legacy contexts.
Thanks systemd...........
The best you can do is to reduce the timeout from 90 s to small value.
5:16 p.m.
Michael composed on 2018-07-19 10:47 (UTC-0500):
Michele Calgaro wrote:
> Felix Miata wrote:
> > I encounter this highly annoying message and
90 second shutdown delay too
> > often. Why does TDM object to cmdline shutdown or reboot commands from
> > login on the vttys? How can it be stopped? The immediate inducement to
> > write this comes from Buster, but it happens in Stretch and openSUSE too,
> > both in UEFI and legacy contexts.
> Thanks systemd...........
> The best you can do is to reduce the timeout from 90 s to small value.
Reduce the timeout of exactly what/where? This happens with the openSUSEes and
the Debians.
Continuous Ctrl-Alt-Delete should force immediate response, but not unusually it
makes the situation worse, freezing after 90 seconds instead of the expectation,
necessitating power or reset button.
Not sure what exact command you're running, but do
also add a halt flag if
it's available.
"option to halt services before rebooting.
"shutdown -h now" is a graceful
shutdown, and "reboot -h now" is a graceful reboot."
--Source unknown (CentOS)
# alias | egrep 'boo|ff'
alias Off='cd; umount -a; shutdown -h now'
alias Reboot='cd; umount -a; shutdown -r now'
These I do whilst logged out of the TDM greeter, so it shouldn't be doing
anything but waiting. It shouldn't matter what it's waiting for, whether an
attempt to log in or a direction to reboot or shutdown.
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
20 Jul
20 Jul
2:16 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Reduce the timeout of exactly what/where? This happens
with the openSUSEes and the
Debians./etc/systemd/system.comf
Uncomment and change like this:
DefaultTimeoutStartSec=5s
DefaultTimeoutStopSec=5s
This should reduce the wait time to 5 seconds.
> "option to halt services before rebooting.
"shutdown -h now" is a graceful shutdown, and "reboot -h now" is a
> graceful reboot."
The problem is after this point and I have not been able
to understand what triggers it. If you google, you will find
a lot of similar complains for whatever other job.....
cheers
Michele
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAltRRd4ACgkQKnW3yore
1c9jpA/+OjpycrddTee+etMgL91gs3alYAflLx6qRdiGCJ1SCrcOwdFyY4SNGjvh
01sxP4aHCW7Ouzx5IkvWfLKnyQPMCy3qHFeaVpw0k/HPhOz+vEDRKl8punAw4QY3
HJCl4NltoctxOAtMSL7SgWrnxnLKEab5SOftvLFNNqEDUqs0gC5u1K/CmY4wmCAv
BWtGyNwcp2MU5XH+QWHUWc9YeTCXAR6QlAJy620da4AciU795J4T58qhf72rR7Vu
vaULhyd78JD7iZzGskzDHmI6CDQBw/A5uBL0x0UoRg8h9mziH80YcOpbYi7PaRYm
480JSZMYMe+cP7YRt2X3QcN2/CFsBQCNkNnDLrt7q9UDtb/Tz5Wm8FIIIouqLyjo
d5Cw3z7xNchs4kbCi4LzJn1jZzbsTapmO6iIaEk3Vja3jTd+jpZAqHaziy8ofqMQ
Zyz50oKMvc9zMoxh4UwvJf3klcj+Xog8NkYLp4zFoZWCQK6XdPqo1Y1zOCrLZH+b
GtubTwUHEWjO+LLwltHF+h3mrFlRfgHcMMSLeAU72wAe+DoOpeYWSMn8CxESpgtf
YP0jk/QH9AWpjm+R/q5ju/aNhPjxvU6/tDdmPXxAd+z7X+uNKgDvbSm0EhmZ07AI
gCRlsz1O8Y5wH6cjCxVJKtoS6RBtwwK72ZOpTqJJ3uvEjLlGDdI=
=1z+6
-----END PGP SIGNATURE-----
24 Jul
24 Jul
2:23 a.m.
Michele Calgaro composed on 2018-07-20 10:16 (UTC+0800):
> Reduce the timeout of exactly what/where? This
happens with the openSUSEes and the
> Debians./etc/systemd/system.comf
Uncomment and change like this:
DefaultTimeoutStartSec=5s
DefaultTimeoutStopSec=5s
This should reduce the wait time to 5 seconds.
Bad idea. This system has no SDD. I did exactly that, and bunches of startup
units failed
# journalctl -b -1 | grep ailed | wc -l
14
among which local-fs.target/start, leaving me in emergency mode.
I switched Start to 15 and it seems to have booted normally, even though
# journalctl -b | grep ailed | wc -l
returned 12. I switched it to 75, and still got 12. So I switched it back
to its original 90, and it still got 12. So I switched back to 5. Next boot
produced 15, but all seemed totally normal.
Oh what fun is systemd. :-p
(but no reboot/shutdown delays since playing with system.conf either)
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
8:10 a.m.
Am Dienstag, 24. Juli 2018 schrieb Felix Miata:
Michele Calgaro composed on 2018-07-20 10:16
(UTC+0800):
Oh well ... have you seen this?
English:
https://translate.google.de/translate?sl=de&tl=en&js=y&prev=_t&…
Deutsch: http://www.danisch.de/blog/2018/07/10/systemd-war-eine-massive-fehlentschei…
Nik
> Reduce the timeout of exactly what/where?
This happens with the openSUSEes and the
> Debians./etc/systemd/system.comf
Uncomment and change like this:
DefaultTimeoutStartSec=5s
DefaultTimeoutStopSec=5s
This should reduce the wait time to 5 seconds.
Bad idea. This system has no SDD. I did exactly that, and bunches of startup
units failed
# journalctl -b -1 | grep ailed | wc -l
14
among which local-fs.target/start, leaving me in emergency mode.
I switched Start to 15 and it seems to have booted normally, even though
# journalctl -b | grep ailed | wc -l
returned 12. I switched it to 75, and still got 12. So I switched it back
to its original 90, and it still got 12. So I switched back to 5. Next boot
produced 15, but all seemed totally normal.
Oh what fun is systemd. :-p
(but no reboot/shutdown delays since playing with system.conf either)
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
8:31 p.m.
Felix Miata composed on 2018-07-23 22:23 (UTC-0400):
Michele Calgaro composed on 2018-07-20 10:16
(UTC+0800):
>> Reduce the timeout of exactly what/where? This
happens with the openSUSEes and the
>> Debians./etc/systemd/system.comf
> Uncomment and change like this:
> DefaultTimeoutStartSec=5s
> DefaultTimeoutStopSec=5s
> This should reduce the wait time to 5 seconds.
Bad idea. This system has no SDD. I did exactly that,
and bunches of startup
units failed
# journalctl -b -1 | grep ailed | wc -l
14
among which local-fs.target/start, leaving me in
emergency mode.
I switched Start to 15 and it seems to have booted normally, even though
# journalctl -b | grep ailed | wc -l
returned 12. I switched it to 75, and still got 12. So
I switched it back
to its original 90, and it still got 12. So I switched back to 5. Next boot
produced 15, but all seemed totally normal.
Oh what fun is systemd. :-p
(but no reboot/shutdown delays since playing with
system.conf either)
Spoke too soon. It just sat there 90 seconds reporting "watchdog did not stop!"
before it rebooted.
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
20 Jul
20 Jul
7:14 a.m.
New subject: a stop job is running for Trinity Display Manager (xxx/1min30sec)
Felix Miata wrote:
These I do whilst logged out of the TDM greeter, so it
shouldn't be doing
anything but waiting. It shouldn't matter what it's waiting for, whether
an attempt to log in or a direction to reboot or shutdown.
I had same experience - it just arbitrary decides to wait forever. Most of
the time it was waiting for cryptsetup to close encrypted volume or mount
to umount nfs share. After some time I switched to sysv init and all
troubles are gone. Now systemd is sitting ashamed in the corner waiting to
do something and it is good so.
regards
2109
days inactive
2114
days old
8 comments
5 participants
participants (5)
-
deloptes -
Dr. Nikolaus Klepp -
Felix Miata -
Michael -
Michele Calgaro