debian-u...@howorth.org.uk wrote:
> "Thomas Schmitt" <scdbac...@gmx.net> wrote:
> > Hi,
> >
> > John Cassidy wrote:
> > > > Could not execute systemctl: at /usr/bin/deb-systemd-invoke
> > > > line 148.
> >
> > Greg Wooledge wrote:
> > > That's a very strange and specific error message. Is your
> > > systemctl command missing, or has incorrect permissions or
> > > something?
> >
> > I rather guess that it is due to the perl thingies
> >
> > @instance_args, $action, @start_unit
> >
> > in
> >
> > system('systemctl', '--quiet', @instance_args, $action,
> > @start_units) == 0 or die("Could not execute systemctl: $!");
>
> But the error says that it could not execute systemctl, which suggests
> to me some specific problem with that binary rather than a problem
> with its args.
Actually, looking at https://perldoc.perl.org/functions/system suggests
that the first and most important thing to print out is the value of $?
rather than $!
> However it won't do any harm to print the args as you suggest. You
> could use "warn" instead of "print STDERR".
>
> > at
> >
> > https://sources.debian.org/src/init-system-helpers/1.67/script/deb-systemd-invoke/#L148
> >
> > One should make them visible and then re-try the Redis installation
> > after possibly removing the debris of the nearly completed
> > installation. We'd need a perl programmer to tell the exact command
> > to insert before line 148 to make the systemctl command parameters
> > visible before the execution attempt. Something like
> > print STDERR "systemctl --quiet, @instance_args, $action,
> > @start_units\n";
> >
> >
> > The problem seems not uncommon:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010893
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076530
> >
> >
> > Have a nice day :)
> >
> > Thomas
> >
>
