Am 07.02.24 um 13:07 schrieb Christoph Pleger:
Hello,
Am Mittwoch, dem 07.02.2024 um 12:27 +0100 schrieb Michael Biebl:
Am 07.02.24 um 11:32 schrieb Christoph Pleger:
Hello,
systemd-time-wait-sync.service is running but has not completed.
I wonder if that is
https://bugs.debian.org/cgi-bin/
Hello,
Am Mittwoch, dem 07.02.2024 um 12:27 +0100 schrieb Michael Biebl:
> Am 07.02.24 um 11:32 schrieb Christoph Pleger:
> > Hello,
> >
> > >
> > > systemd-time-wait-sync.service is running but has not completed.
> > > I wonder if that is
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Am 07.02.24 um 11:32 schrieb Christoph Pleger:
Hello,
systemd-time-wait-sync.service is running but has not completed.
I wonder if that is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940840
https://github.com/systemd/systemd/issues/14061
Which NTP service do you use?
I am using chrony
Hello,
> - what is the hardware?
Qemu VM
> - what release of what operating system is in use?
Debian bullseye
> - what happened just before things 'suddenly' stopped working? Did
you
> upgrade the machine, or install some new software, or just reboot
it
> or what?
I rebooted the machine, m
Hello,
>
> systemd-time-wait-sync.service is running but has not completed.
> I wonder if that is
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940840
> https://github.com/systemd/systemd/issues/14061
>
> Which NTP service do you use?
I am using chrony, because the server is offering time
Christoph Pleger wrote:
> Hello,
>
> on one of my server machines, suddenly many systemd units (e.g. cron,
> autofs) do not start any more, neither at boot nor when trying to
> start manually with "systemctl start ", this hangs till I abort
> with Ctrl-C - though the commands defined in ExecStart
On Tue 06 Feb 2024 at 09:51:02 (+0700), Max Nikulin wrote:
> On 06/02/2024 03:46, Michael Biebl wrote:
> > If you are not using systemd-timesyncd, you could also consider
> > disabling systemd-time-wait-sync.service (via systemctl disable).
>
> My guess is that this board does not have RTC,
I don
On 06/02/2024 03:46, Michael Biebl wrote:
If you are not using systemd-timesyncd, you could also consider
disabling systemd-time-wait-sync.service (via systemctl disable).
My guess is that this board does not have RTC, so NTP is a must have and
dependency on time synchronization is intentional
On Mon, 2024-02-05 at 17:28 +0100, Christoph Pleger wrote:
> Hello,
>
> > > Does anyone have an idea what is possibly wrong?
> >
> > Look for more information.
>
> This is the output of systemctl list-jobs :
>
> JOB UNIT TYPE STATE
> 102 autofs.service
Am 05.02.24 um 21:38 schrieb Michael Biebl:
This is the output of systemctl list-jobs :
JOB UNIT TYPE STATE
102 autofs.service start waiting
82 mlocate.timer start waiting
80 e2scrub_all.timer star
This is the output of systemctl list-jobs :
JOB UNIT TYPE STATE
102 autofs.service start waiting
82 mlocate.timerstart waiting
80 e2scrub_all.timerstart waiting
117 cron.service
On 05/02/2024 23:28, Christoph Pleger wrote:
This is the output of systemctl list-jobs :
JOB UNIT TYPE STATE
102 autofs.service start waiting
82 mlocate.timerstart waiting
80 e2scrub_all.timerst
Hello,
> > Does anyone have an idea what is possibly wrong?
>
> Look for more information.
This is the output of systemctl list-jobs :
JOB UNIT TYPE STATE
102 autofs.service start waiting
82 mlocate.timerstart waiti
пн, 5 февр. 2024 г. в 20:57, Christoph Pleger
:
> Unfortunately, there is no useful further information:
>
> systemctl status
> ● autofs.service - Automounts filesystems on demand
> Loaded: loaded (/lib/systemd/system/autofs.service; enabled;
> vendor preset>
> Active: inactive (dead)
>
Hello,
Am Montag, dem 05.02.2024 um 07:18 -0500 schrieb Greg Wooledge:
> On Mon, Feb 05, 2024 at 12:53:33PM +0100, Christoph Pleger wrote:
> > on one of my server machines, suddenly many systemd units (e.g. cron,
> > autofs)
> > do not start any more, neither at boot nor when trying to start manu
On Mon, Feb 05, 2024 at 12:53:33PM +0100, Christoph Pleger wrote:
> on one of my server machines, suddenly many systemd units (e.g. cron, autofs)
> do not start any more, neither at boot nor when trying to start manually
> with "systemctl start ", this hangs till I abort with Ctrl-C -
> Does anyon
Hello,
on one of my server machines, suddenly many systemd units (e.g. cron, autofs)
do not start any more, neither at boot nor when trying to start manually
with "systemctl start ", this hangs till I abort with Ctrl-C -
though the commands defined in ExecStart work when I type them in directly.
F
17 matches
Mail list logo
