> On Fri, 24 May 2024 17:44:03 -0700, andrew bezella
> said:
> metad.rules` to patch. the patch wouldn't apply anyway as the logic has
> changed considerably. however, it now respects the value of
> `event_activation` in lvm.conf:
Thanks for the detailed feedback. I've now re
up?
> mdadm -W --stop /dev/md5 had exit code 1
> (STDERR) mdadm: Cannot get exclusive access to /dev/md5:Perhaps a
> running process, mounted filesystem or active volume group?
> Command had non-zero exit code
>
[...]
> if/when FAI migrates to systemd this may raise its head agai
KWORM chroot.
--
Markus
From: linux-fai on behalf of Markus
Rexhepi-Lindberg
Sent: Friday, September 15, 2023 11:47
To: fully automatic installation for Linux
Subject: Re: usermod: group 'systemd-journal' does not exist (only with FAI
script)
cloud-images/-/blob/master/config_space/sid/hooks/updatebase.BASE
> https://salsa.debian.org/cloud-team/debian-cloud-images/-/blob/master/config_space/sid/scripts/CLOUD/20-enable-systemd-resolved
>
>
> > Now, you would think that is easy :
> > 1. Add systemd-resolved to pac
-systemd-resolved
> Now, you would think that is easy :
> 1. Add systemd-resolved to package_config
> 2. Add "$ROOTCMD systemctl enable systemd-resolved" to scripts
> However, the instant I make those two changes, my build breaks.
--
regards Thomas
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die
eigentliche Nachricht steht dadurch in einem Anhang.
This message was wrapped to be DMARC compliant. The actual message
text is therefore in an attachment.--- Begin Message ---
What's the secret to adding systemd-resolved
Sent: Friday, September 15, 2023 11:31
To: linux-fai@uni-koeln.de
Cc: Laura Smith
Subject: usermod: group 'systemd-journal' does not exist (only with FAI script)
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die
eigentliche Nachricht steht dadurch in einem Anhang.
Th
-a -G sudo,adm,systemd-journal $USERN
$ROOTCMD chpasswd --encrypted <<< "${USERN}:${USERP}"
fi
This fails with error "usermod: group 'systemd-journal' does not exist".
But this makes zero sense.
1) The group clearly exists in Bookworm
cat /etc/group | fgre
>>>>> On Wed, 29 Apr 2020 15:22:35 +1200, Andrew Ruthven
>>>>> said:
> [ 67.003059] systemd-udevd[2520]: sdb1: Failed to process device,
> ignoring: Resource temporarily unavailable
After grep'ing all my FAI logs, I found one match in my la
Hey,
I've just switched to using a Buster nfsroot and I sometimes encounter
issues on rebuilding machines, while setup-storage is running errors
like this appear:
[ 67.003059] systemd-udevd[2520]: sdb1: Failed to process device,
ignoring: Resource temporarily unavailable
And then
>>>>> On Thu, 23 Jan 2020 16:58:27 -0800, andrew bezella
>>>>> said:
> and i was wondering if the removal of "$target" in the "-f" test for
> `systemd-machine-id-setup` was intentional? since the next line is
> "$ROOT
0755
--- a/scripts/DEBIAN/40-misc
+++ b/scripts/DEBIAN/40-misc
@@ -28,7 +28,8 @@ elif [ -f $target/lib/systemd/system/getty@.service ]; then
sed -i -e 's#sbin/agetty --noclear#sbin/agetty -f /etc/issue.linuxlogo
--noclear#' $target/lib/systemd/system/getty@.service
fi
-if [ ! -f $t
d sample config...)
Maybe I should start to check your sample config scripts on a regular
basis ;-)
Regards
René
On 12.01.2017 15:37, Thomas Lange wrote:
On Thu, 12 Jan 2017 14:31:00 +0100, René Bleisch
said:
> I just stumbled over a systemd/journald related problem which may also
affect
>>>>> On Thu, 12 Jan 2017 14:31:00 +0100, René Bleisch
>>>>> said:
> I just stumbled over a systemd/journald related problem which may also
affect FAI installations.
> Some days ago, when booting a freshly installed PC (Debian jessie) for
the first
Hi,
I just stumbled over a systemd/journald related problem which may also
affect FAI installations.
Some days ago, when booting a freshly installed PC (Debian jessie) for
the first time, journald could not be started, which means there is no
error logging at all:
"systemd[1]: Fail
Hi Rene,
> I'm also running several jessie-clients now without serious problems,
> I'm using dracut too.
>
> I dont see any "systemd-tmpfiles" messages in my syslogs.
>
> Just a question: are you trying to use "pure" systemd or both syste
Hi Dirk
I'm also running several jessie-clients now without serious problems,
I'm using dracut too.
I dont see any "systemd-tmpfiles" messages in my syslogs.
Just a question: are you trying to use "pure" systemd or both systemd
and sys-v-init together?
As far a
Hi Thomas,
> > Any suggestions, ideas, workable solutions, ...?
> Why don't you just remove the fstab entry for /run?
systemd creates it, if it is not part of fstab...
Then this service
systemd-tmpfiles-setup.service
creates the needed files, e.g. for ssh it uses:
/usr/
>>>>> On Fri, 19 Jun 2015 08:29:35 +0200, Dirk Geschke
>>>>> said:
> Hi FAI-users,
> I'm just testing to migrate to Debian Jessie and I'm still unsure
> if I should go with systemd yet. Whereas I'm still using sys-v-init
e:
Jun 18 17:25:48 train1 systemd-tmpfiles[163]: Failed to create directory
/var/cache: Read-only file system
Jun 18 17:25:48 train1 systemd-tmpfiles[163]: Failed to create directory
/var/cache/man: No such file or directory
Jun 18 17:25:48 train1 systemd-tmpfiles[163]: Failed to create direct
Did you consider the "nofail" Option for your /etc/fstab entries which might
fail/shouldn't fail?
> Am 19.06.2015 um 08:29 schrieb Dirk Geschke :
>
> Hi FAI-users,
>
> I'm just testing to migrate to Debian Jessie and I'm still unsure
> if I should g
Hi FAI-users,
I'm just testing to migrate to Debian Jessie and I'm still unsure
if I should go with systemd yet. Whereas I'm still using sys-v-init
on the server, I started with systemd on the clients.
Actually I failed with a race condition in mounting the file systems
a
Am 03.06.2015 um 11:29 schrieb Thomas Lange:
>> On Wed, 03 Jun 2015 11:25:52 +0200, Moritz Struebe
>> said:
> > So, why not set init=/sbin/fai as kernel parameter. That should nicely
> > work around all these ugly hacks. Or did I miss something?
> I never had the bravery to test
> On Wed, 03 Jun 2015 11:25:52 +0200, Moritz Struebe
> said:
> So, why not set init=/sbin/fai as kernel parameter. That should nicely
> work around all these ugly hacks. Or did I miss something?
I never had the bravery to test this. Not sure if this will really work.
--
regard
ed?
> No, we do not need rcS. It's sufficient to just start fai, but
> no other services via init.d or upstart or systemd. Currently FAI
> cares about starting all needed services.
>
So, why not set init=/sbin/fai as kernel parameter. That should nicely
work around all these ugly hacks
i, but
no other services via init.d or upstart or systemd. Currently FAI
cares about starting all needed services.
--
regards Thomas
Am 11.05.2015 um 08:35 schrieb Moritz Struebe:
> Yea, we have had the same problem with vivid. You need to install it in
> in a seperate apt-run. Aptitude's conflict resolution sucks! We did this
> by adding an extra hook to /etc/fai/nfsroot-hooks/ containing
> $ROOTCMD apt-get install upstart-sysv
$ROOT_CMD ln -s /dev/null /etc/systemd/system/lightdm.service?
(mask it out in the system override directory)
(not quite same as disabling).
I think minimally, you need to:
$ROOT_CMD /bin/rm -f
/etc/systemd/system/multi-user.target.wants/lightdm.service (or whatever
it's called)
(pres
I am using Debian Jessie and things are going well, with a couple
exceptions. I am installing lightdm, but on some systems I want to
disable it. I was trying to do:
systemctl disable lightdm
However, systemd knows this is a chroot environment and the command
fails. I've also trie
Hi
On 09/30/2014 08:33 AM, Ingo Wichmann wrote:
> did anyone already install a systemd based distro? Is it possible to
> (re)start systemd services from the fai chroot?
we install our nodes with a systemd based base.tgz but without systemd
within FAI, therefore I don't know if
Hi,
did anyone already install a systemd based distro? Is it possible to
(re)start systemd services from the fai chroot?
Ingo
--
Linuxhotel GmbH, Geschäftsführer Dipl.-Ing. Ingo Wichmann
HRB 20463 Amtsgericht Essen, UStID DE 814 943 641
Antonienallee 1, 45279 Essen, Tel.: 0201 8536-600, http
31 matches
Mail list logo
