public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Dirk Kulmsee <Kulmsee@capricomp.de>
To: development@lists.ipfire.org
Subject: Guardian does not start after upddate to Core 167 testing
Date: Mon, 11 Apr 2022 20:09:46 +0000	[thread overview]
Message-ID: <sig.21000f07c8.1d5c53f863f74d14ae834b226a20e7d7@capricomp.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

Hi all,
just upgraded to Core Update 167 Development Build: master/24c8e6a6. Now the guardian does not start due to a missing Perl module: 

[root(a)ipfire ~]# /etc/init.d/guardian start
Starting Guardian...
Can't locate Net/IP.pm in @INC (you may need to install the Net::IP module) (@INC contains: /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.32.1 /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi /usr/lib/perl5/5.32.1) at /usr/lib/perl5/site_perl/5.32.1/Guardian/Base.pm line 9.
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.32.1/Guardian/Base.pm line 9.
Compilation failed in require at /usr/sbin/guardian line 30.                                                                                        [ FAIL ]

Keep up your good work everybody!

Mit freundlichen Grüßen 

Dirk Kulmsee
_________________________________________________________________

  CAPRICOMP             DIRK KULMSEE (kulmsee(a)capricomp.de)
                        Am Zehnthof 149
- COMPUTER              44141 Dortmund
- NETZWERKE             Telefon: +49-231-99951318
- IT-SERVICE            Telefax: +49-231-99951315 
_________________________________________________________________



             reply	other threads:[~2022-04-11 20:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 20:09 Dirk Kulmsee [this message]
2022-04-12 10:55 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=sig.21000f07c8.1d5c53f863f74d14ae834b226a20e7d7@capricomp.de \
    --to=kulmsee@capricomp.de \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox