how to keep eth link down across reboots ?

[lejeczek]

Hi guys.

Perhaps not strictly _systemd_ question but community here 
surely is capable - a matter of me being lucky - how would 
you keep an Ethernet link/port powered down?
I was thinking I'll try first _udev_ rules - given other 
tools/managers are told to stay away from the link/port
Is there a better, best way to put such link/port down & 
keep it that way - naturally, please steer clear of "unplug 
the cable" type of ideas.


many thanks, L.

[systemd-devel] LUKS - lost token?

[lejeczek]

Hi guys.

I know this is most likely not best suited question for this 
list, but I'm hoping some experts might be able to help.


I have a LUKS device which had keyslot with pass-phrase 
removed and token for TPM keyslot removed too - I think this 
is the case, for none of my passphrase works and device is 
as below:


I hope there is a way to save & bring it back to live - 
device is open right now and I've access to filesystem, 
obviously goal would be to avoid re-format/crypt.


Would it be needed to create a new token for that TPM 
keyslot - if it's tpm - with _systemd-cryptenroll_  or any 
other way?


-> $ cryptsetup luksDump /dev/nvme0n1p3
LUKS header information
Version:   2
Epoch:     83
Metadata area:     16384 [bytes]
Keyslots area:     1678 [bytes]
UUID:  3a879268-84fd-4b48-a5d4-960cccb0caa9
Label:     (no label)
Subsystem:     (no subsystem)
Flags:   (no flags)

Data segments:
  0: crypt
    offset: 16777216 [bytes]
    length: (whole device)
    cipher: aes-xts-plain64
    sector: 512 [bytes]

Keyslots:
  1: luks2
    Key:    512 bits
    Priority:   normal
    Cipher: aes-xts-plain64
    Cipher key: 512 bits
    PBKDF:  pbkdf2
    Hash:   sha512
    Iterations: 1000
    Salt:   a4 5b 6b cc a8 f1 6b e8 b7 3b e2 3d ca 8d 
43 fb
    10 52 62 b9 99 45 70 16 bd e1 0f 7a 6c 7f 
3d 11

    AF stripes: 4000
    AF hash:    sha512
    Area offset:290816 [bytes]
    Area length:258048 [bytes]
    Digest ID:  0
Tokens:
Digests:
  0: pbkdf2
    Hash:   sha256
    Iterations: 183317
    Salt:   ef 56 aa 59 c2 64 66 c7 49 57 31 4b a7 7d 
00 3c
    fe 00 89 2e b9 e9 da bc 69 1d 19 59 96 a9 
27 aa
    Digest: 79 aa 0c 8a 29 64 9c 83 bb 5a f8 5c b5 c6 
b0 9c
    5e 54 80 49 bd 21 f6 b4 5b 49 65 39 bd 6f 
5f 20

Re: [systemd-devel] user unit with delayed users homes mount - ?

[lejeczek]

On 16/10/2022 16:34, Lennart Poettering wrote:

On Fr, 14.10.22 10:59, lejeczek (pelj...@yahoo.co.uk) wrote:


Hi guys.

I'm on Centos 8 S with systemd 239.
Users homes are mounted at later (latest?) stage off NFS so when such a user
logs in then:

-> $ systemctl --user status -l xyz.service
Unit xyz.service could not be found.
-> $ systemctl --user daemon-reload
-> $ systemctl --user status -l xyz.service
● xyz.service - Podman container-xyz.service
    Loaded: loaded (/apps/appownia/.config/systemd/user/xyz.service; enabled;
vendor preset: enabled)
    Active: inactive (dead)
  Docs: man:podman-generate-systemd(1)

Is it possible and if so then how, to make "systemd" account for such a
"simple" case - where home dir is net mounted very late?

I don't get this scenario. You talk to the systemd --user instance,
which is the per-user instance, so $HOME of that user should be
mounted at that time. But then you issue a reload and new stuff
appears and you appear to suggest that now the user's $HOME was
mounted?
Yes, it appears that systemd 'misses' user's units - @ boot 
time I guess and later does not do anything about them 
'homes' getting mounted later(too late for systemd?)
When I login to that user it seems that systemd sees no 
unit's - at that point homes are mounted of course - and I 
have to poke systemd manually with:

-> $ systemctl --user daemon-reload
at which point, it seems, system re-check user's home
It is PCS service/daemon which is a part of or rather 
manages, a couple of other daemons which together do a HA.

For 'pcs' I've tried
[Unit]
Before=systemd-logind.service
Before=systemd-user-sessions.service

but do not avail.


So what now? Usually, the assumption is that first the user logs in,
which is the point where $HOME must be mounted at the latest, and then
systemd --user gets started off it and the user's login session is
allowed to begin.
I really do not know what to assume - I can only tell you 
what happens.
Ideal scenario - which I'm hoping it is possible to make 
work - is when a given user does not have to log in at at.
As you can see in this case, it is a container(podman) unit 
which I hope a 'lingered' session shall manage without user 
interventions.


many thanks, L>


Lennart

--
Lennart Poettering, Berlin

Re: [systemd-devel] user unit with delayed users homes mount - ?

[lejeczek]

On 14/10/2022 12:02, Andrei Borzenkov wrote:

On Fri, Oct 14, 2022 at 12:59 PM lejeczek  wrote:

Hi guys.

I'm on Centos 8 S with systemd 239.
Users homes are mounted at later (latest?) stage off NFS so when such a user 
logs in then:

-> $ systemctl --user status -l xyz.service
Unit xyz.service could not be found.
-> $ systemctl --user daemon-reload
-> $ systemctl --user status -l xyz.service
● xyz.service - Podman container-xyz.service
Loaded: loaded (/apps/appownia/.config/systemd/user/xyz.service; enabled; 
vendor preset: enabled)
Active: inactive (dead)
  Docs: man:podman-generate-systemd(1)

Is it possible and if so then how, to make "systemd" account for such a 
"simple" case - where home dir is net mounted very late?


Without knowing how exactly your home directories are mounted it is
rather hard to answer. Are they mounted from within /etc/fstab?

Homes are mounted by other daemons started later(by systemd).

thanks, L.

[systemd-devel] user unit with delayed users homes mount - ?

[lejeczek]

Hi guys.

I'm on Centos 8 S with systemd 239.
Users homes are mounted at later (latest?) stage off NFS so 
when such a user logs in then:


-> $ systemctl --user status -l xyz.service
Unit xyz.service could not be found.
-> $ systemctl --user daemon-reload
-> $ systemctl --user status -l xyz.service
● xyz.service - Podman container-xyz.service
   Loaded: loaded 
(/apps/appownia/.config/systemd/user/xyz.service; enabled; 
vendor preset: enabled)

   Active: inactive (dead)
 Docs: man:podman-generate-systemd(1)

Is it possible and if so then how, to make "systemd" account 
for such a "simple" case - where home dir is net mounted 
very late?


many thanks, L.

Re: [systemd-devel] troubleshooting Clevis

[lejeczek]

On 12/10/2021 16:54, Lennart Poettering wrote:

On Di, 12.10.21 16:17, lejeczek (pelj...@yahoo.co.uk) wrote:


I have 'clevis' set to get luks pin from 'tang' but unlock does not happen
at/during boot time and I wonder if someone can share thoughts on how to
investigate that?
I cannot see anything obvious fail during boot, moreover, manual
'clevis-luks-unlock' works no problems.

This is the systemd mailing list, not the clevis/tang mailing
list. Please contact the clevis/tang community instead.

May ask of any possible plans where systemd would, somehow similarly to
'tpm', utilize 'tang'(or similar) technique to unlock luks encrypted
devices?

You mean that networked unlock feature? I mean, it's not always clear
what belongs and systemd and what does not. But outside of data
centers I am not sure tang/clevis really has much use, and that's
quite a limited userbase, so I'd say: no this should be done outside
of systemd. Maybe a plugin for libcryptsetup's "token" feature.
I cannot speak for datacentre conglomerates but I'd dare to 
pose a theory that increasingly more small setups, like mine 
with three nodes, start to find homes in our homes.
In my basic setup where 'tang' on my laptops serves 'clevis' 
(or would if it worked) to unlock home HA cluster (also with 
Shamir's Secret Sharing implemented) having 'systemd' 
integrate all these techniques/method would be, not only for 
big datacentres, fantastic in my opinion.

many thanks for all everybody's work. L.


Lennart

--
Lennart Poettering, Berlin

Re: [systemd-devel] troubleshooting Clevis

[lejeczek]

On 28/09/2021 12:33, Lennart Poettering wrote:

On Di, 28.09.21 12:26, lejeczek (pelj...@yahoo.co.uk) wrote:


Hi guys.

I have 'clevis' set to get luks pin from 'tang' but unlock does not happen
at/during boot time and I wonder if someone can share thoughts on how to
investigate that?
I cannot see anything obvious fail during boot, moreover, manual
'clevis-luks-unlock' works no problems.

This is the systemd mailing list, not the clevis/tang mailing
list. Please contact the clevis/tang community instead.
May ask of any possible plans where systemd would, somehow 
similarly to 'tpm', utilize 'tang'(or similar) technique to 
unlock luks encrypted devices?
ps. clevis + tang seem "broken" in CentOS stream & f35, 
unlocking @boot time to be specific, is not working.

many thanks, L.


Lennart

--
Lennart Poettering, Berlin

[systemd-devel] troubleshooting Clevis

[lejeczek]

Hi guys.

I have 'clevis' set to get luks pin from 'tang' but unlock 
does not happen at/during boot time and I wonder if someone 
can share thoughts on how to investigate that?
I cannot see anything obvious fail during boot, moreover, 
manual 'clevis-luks-unlock' works no problems.


many thanks, L.

[systemd-devel] when mount is delayed - start unit which depends on it - ?

[lejeczek]

Hi guys.

I'm trying to have unit to start...
well,
I have a luks device which waits for manual passphrase 
input, when that happens 'systemd' mounts, without user 
intervention(which is great), that luks device.

fstab:
/dev/mapper/luks.devs /devs   ext4 
noatime,nobarrier,noatime,x-systemd.device-timeout=2,nofail 1 2
and now I'll have many units/services which depend on that 
mount, because they need to get to paths to get their 
configs & other bits.


Question - how do I make such a unit to re/start when 
'systemd' does the mount? Naturally, ideally without any 
ways external to 'systemd'.


I'm on CentOS with 'systemd-239-50.el8.x86_64'.

many thanks, L.

Re: [systemd-devel] luks - a particular device systemd treats differently?

[lejeczek]

On 02/06/2021 13:46, Lennart Poettering wrote:

On Mi, 02.06.21 10:00, lejeczek (pelj...@yahoo.co.uk) wrote:

Conditional check - systemctl is-failed ... - works for all devices but that
one.

I am sorry, but I don#t really follow.

I understand though that once of the instances of
systemd-cryptsetup@.service fails for you? Please provide the full
logs off that unit. "journalctl -u ".

Lennart

--
Lennart Poettering, Berlin
And the crypttab & fstab snippets are clear and explanatory? 
If yes then it's only that:
luks devices I open manually, not at boot time, after an 
actual real human login with:


systemctl is-failed 
"systemd-cryptsetup@luks\x2d_DEVICEservice" -q && {
systemctl restart 
"systemd-cryptsetup@luks\x2d_DEVICEs.service" && fsck.ext4

/dev/mapper/luks-DEVICE && mount /DEVICE; }

so I have, let say four devices in total and only one which 
for some reason does not reports as "failed"


If I get "systemctl is-failed" correctly - "is-failed" 
returns true and then there rest of code above gets going, 
"restart" gets me prompt for passphrase and the rest...

a) and that happens for all devices but that one.
b) but I expect all devices.. since
c) crypttab & fstab are identical for all four devices in 
terms of options/params.


And if do below for that one device, after reboot and before 
manual intervention:


-> $ systemctl is-failed 
"systemd-cryptsetup@luks\x2ddevs.service"

inactive

Sorry mate if you still won't get it, I cannot explain 
myself any better or different way.

thanks,
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] luks - a particular device systemd treats differently?

[lejeczek]

On 01/06/2021 22:05, Lennart Poettering wrote:

On Di, 01.06.21 16:55, lejeczek (pelj...@yahoo.co.uk) wrote:


Hi guys.

I have a crypttabl here:

luks-devs /dev/mapper/dev1-devs /etc/.etc.enc.loop/crypttab.key
discard,nofail,timeout=3s,noauto
luks-home /dev/mapper/dev1-home /etc/.etc.enc.loop/crypttab.key
discard,nofail,timeout=3s,noauto
...
plus a few more lines with all options just as those two. I have a fstab
here:

/dev/mapper/luks-home /home   ext4
noauto,nofail,noatime,nobarrier,noatime,x-systemd.device-timeout=3s 1 2
/dev/mapper/luks-devs /devs   ext4
noauto,nofail,noatime,nobarrier,noatime,x-systemd.device-timeout=3s 1 2
...

when I check devices manually here:
...
systemctl is-failed "systemd-cryptsetup@luks\x2ddevs.service" -q && {
systemctl restart "systemd-cryptsetup@luks\x2ddevs.service" && fsck.ext4
/dev/mapper/luks-devs && mount /devs; }

then I get asked for passphrase and the rest gets going (intentional, as
those luks devs do not get opened at boot time) for all the devices except
for "devs"
As  I understand systemd here does not see, mark that one device as "failed"
and I have no idea why systemd would do that for that one device.
Would somebody care to share so ideas?

I am not sure I properly grok what you are trying to say, but: did you
check the logs?

Lennart

--
Lennart Poettering, Berlin
Yes I did, in logs is nothing in terms of errors or warning, 
well, I could not find anything.
This I'll say if I try to rephrase my words earlier - I have 
an number of luks devices which _all_ are "ignored" at boot 
(as snippets from crypttab & fstab show) and are meant to be 
opened & mounted only manually: so I check to open & mount 
as above snippet shows and...

for all devices but one, I get from 'systemd' to mount manually.
Conditional check - systemctl is-failed ... - works for all 
devices but that one.

Why?? no idea.
Would there be something specific I should be looking in 
logs for?

many thanks, L.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] luks - a particular device systemd treats differently?

[lejeczek]

Hi guys.

I have a crypttabl here:

luks-devs /dev/mapper/dev1-devs 
/etc/.etc.enc.loop/crypttab.key discard,nofail,timeout=3s,noauto
luks-home /dev/mapper/dev1-home 
/etc/.etc.enc.loop/crypttab.key discard,nofail,timeout=3s,noauto

...
plus a few more lines with all options just as those two. I 
have a fstab here:


/dev/mapper/luks-home /home   ext4 
noauto,nofail,noatime,nobarrier,noatime,x-systemd.device-timeout=3s 
1 2
/dev/mapper/luks-devs /devs   ext4 
noauto,nofail,noatime,nobarrier,noatime,x-systemd.device-timeout=3s 
1 2

...

when I check devices manually here:
...
systemctl is-failed 
"systemd-cryptsetup@luks\x2ddevs.service" -q && { systemctl 
restart "systemd-cryptsetup@luks\x2ddevs.service" && 
fsck.ext4 /dev/mapper/luks-devs && mount /devs; }


then I get asked for passphrase and the rest gets going 
(intentional, as those luks devs do not get opened at boot 
time) for all the devices except for "devs"
As  I understand systemd here does not see, mark that one 
device as "failed" and I have no idea why systemd would do 
that for that one device.

Would somebody care to share so ideas?
many thanks, L


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] depending on user units

[lejeczek]

Hi guys.

While surfing the web for answers I thought I would try to 
call on experts - how, if possible at all, to make systemd 
service unit depend on users' unit/services?


many thanks, L.


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemd-run / Failed to create bus connection: Input/output error

[lejeczek]

On 03/05/2021 16:04, Lennart Poettering wrote:

On Fr, 30.04.21 14:33, lejeczek (pelj...@yahoo.co.uk) wrote:


Hi guys.

I'm do on my pretty vanilla, so I'd like to think, setup this:

-> $ systemd-run --machine=qemu-8-c8kubernode1 /bin/cat /etc/centos-release
Failed to create bus connection: Input/output error

Someone would care to decipher that for me or/and shed bit more light on
possible troubleshooting?

which host OS, which payload OS? which host systemd, which payload
systemd? is this an nspawn container? is the container fully booted up?

Lennart

--
Lennart Poettering, Berlin

it's all CentOS Stream with systemd 239 (239-45.el8)
Container(s) is libvirtd managed(started by) and yes it's 
fully booted up.

many thanks, L.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] systemd-run / Failed to create bus connection: Input/output error

[lejeczek]

Hi guys.

I'm do on my pretty vanilla, so I'd like to think, setup this:

-> $ systemd-run --machine=qemu-8-c8kubernode1 /bin/cat 
/etc/centos-release

Failed to create bus connection: Input/output error

Someone would care to decipher that for me or/and shed bit 
more light on possible troubleshooting?

many thanks, L.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] is such a 'failed' state?

[lejeczek]

On 28/03/2021 20:26, Reindl Harald wrote:



Am 28.03.21 um 21:19 schrieb lejeczek:
I have a service (which for some reason, I suspect 
SELinux, does not start at boot) which reports as:


-> $ systemctl status -l lsyncd | cat
● lsyncd.service - Live Syncing (Mirror) Daemon
    Loaded: loaded 
(/usr/lib/systemd/system/lsyncd.service; enabled; vendor 
preset: disabled)

   Drop-In: /etc/systemd/system/lsyncd.service.d
    └─override.conf
    Active: inactive (dead) since Sun 2021-03-28 15:01:16 
EDT; 8min ago

  Main PID: 922 (code=exited, status=0/SUCCESS)

Mar 28 15:01:16 c8kubernode2.private.pawel systemd[1]: 
Started Live Syncing (Mirror) Daemon.
Mar 28 15:01:16 c8kubernode2.private.pawel lsyncd[922]: 
15:01:16 Normal: --- Startup, daemonizing ---
Mar 28 15:01:16 c8kubernode2.private.pawel lsyncd[922]: 
15:01:16 Normal: --- Startup, daemonizing ---
Mar 28 15:01:16 c8kubernode2.private.pawel lsyncd[981]: 
Normal, --- TERM signal, fading ---
Mar 28 15:01:16 c8kubernode2.private.pawel systemd[1]: 
lsyncd.service: Succeeded.


and the service has:
[Service]
Restart=on-failure
RestartSec=30
TimeoutSec=30

I expected systemd to restart the service but that does 
not happen. Services restarts okey with manual intervention.
Is it because service, even though it's not running, is 
not really in 'failed' state or root cause is something 
else?


post the complete unit file
you don't even show us the Type

do you have an [Install] section with a active traget to 
begin with?


Type=simple
EnvironmentFile=-/etc/sysconfig/lsyncd
...
[Install]
WantedBy=multi-user.target


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] is such a 'failed' state?

[lejeczek]

Hi guys.

I have a service (which for some reason, I suspect SELinux, 
does not start at boot) which reports as:


-> $ systemctl status -l lsyncd | cat
● lsyncd.service - Live Syncing (Mirror) Daemon
   Loaded: loaded (/usr/lib/systemd/system/lsyncd.service; 
enabled; vendor preset: disabled)

  Drop-In: /etc/systemd/system/lsyncd.service.d
   └─override.conf
   Active: inactive (dead) since Sun 2021-03-28 15:01:16 
EDT; 8min ago

 Main PID: 922 (code=exited, status=0/SUCCESS)

Mar 28 15:01:16 c8kubernode2.private.pawel systemd[1]: 
Started Live Syncing (Mirror) Daemon.
Mar 28 15:01:16 c8kubernode2.private.pawel lsyncd[922]: 
15:01:16 Normal: --- Startup, daemonizing ---
Mar 28 15:01:16 c8kubernode2.private.pawel lsyncd[922]: 
15:01:16 Normal: --- Startup, daemonizing ---
Mar 28 15:01:16 c8kubernode2.private.pawel lsyncd[981]: 
Normal, --- TERM signal, fading ---
Mar 28 15:01:16 c8kubernode2.private.pawel systemd[1]: 
lsyncd.service: Succeeded.


and the service has:
[Service]
Restart=on-failure
RestartSec=30
TimeoutSec=30

I expected systemd to restart the service but that does not 
happen. Services restarts okey with manual intervention.
Is it because service, even though it's not running, is not 
really in 'failed' state or root cause is something else?


many thanks, L.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] service runs - but it's not really there

[lejeczek]

On 29/01/2021 13:02, Reindl Harald wrote:



Am 29.01.21 um 13:55 schrieb lejeczek:

● user@0.service - User Manager for UID 0
    Loaded: loaded 
(/usr/lib/systemd/system/user@.service; static; vendor

preset: disabled)
    Active: active (running) since Thu 2021-01-28 
17:13:01 GMT; 2h 34min ago

  Main PID: 854314 (systemd)
    Status: "Startup finished in 44ms."
 Tasks: 35
    Memory: 69.3M
    CGroup: /user.slice/user-0.slice/user@0.service
    ├─init.scope
    │ ├─854314 /usr/lib/systemd/systemd --user
    │ └─854319 (sd-pam)
    └─syncthing.service

exists and gets auto started by "systemd" without any 
asking really.

This is really very bad, no?
What am I missing here?
systemd at the very least will spawn your per-user dbus 
daemon, which
is needs to be available for many programs to function. 
Even others

require systemd themselves.

Lennart

--
Lennart Poettering, Berlin
I think I found it, in my opinion a very cheeky bastard - 
syncthing - who does this:


[Install]
WantedBy=default.target

which results in:

-> $ llr /etc/systemd/user/default.target.wants/
total 0
lrwxrwxrwx. 1 root root 39 Jan 26 10:39 syncthing.service 
-> /usr/lib/systemd/user/syncthing.service


So those of you on RHEL and derivatives (I assume that 
same rpm goes to all those) - suffices to install 
"syncthing" an you have your "roor" does as above and if 
you are not aware then the "root" does that with you not 
even knowing.


As a matter of sharing opinions - is that a good & 
healthy practice to make & distribute packages like that?


what is your problem?

it's an ordinary user session and not some mystery of 
"root does as above"


RTFM 
https://www.freedesktop.org/software/systemd/man/u...@.service.html 
instead talking about "very cheeky bastard - syncthin"
I doubt I can explain or express it any better, If you do 
not get it it's fine.

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] service runs - but it's not really there

[lejeczek]

On 28/01/2021 21:32, Lennart Poettering wrote:

On Do, 28.01.21 20:06, lejeczek (pelj...@yahoo.co.uk) wrote:


Hi guys

This absolutely boggled my mind, my brain exploded, but go easy on me as I
ain't an expert.
I have, meaning the "root" but other users too, _NO_ "~/.config/systemd" -
thus, how I understand it, no service definitions which are user-made, yet
this..

● user@0.service - User Manager for UID 0
    Loaded: loaded (/usr/lib/systemd/system/user@.service; static; vendor
preset: disabled)
    Active: active (running) since Thu 2021-01-28 17:13:01 GMT; 2h 34min ago
  Main PID: 854314 (systemd)
    Status: "Startup finished in 44ms."
     Tasks: 35
    Memory: 69.3M
    CGroup: /user.slice/user-0.slice/user@0.service
    ├─init.scope
    │ ├─854314 /usr/lib/systemd/systemd --user
    │ └─854319 (sd-pam)
    └─syncthing.service

exists and gets auto started by "systemd" without any asking really.
This is really very bad, no?
What am I missing here?

systemd at the very least will spawn your per-user dbus daemon, which
is needs to be available for many programs to function. Even others
require systemd themselves.

Lennart

--
Lennart Poettering, Berlin
I think I found it, in my opinion a very cheeky bastard - 
syncthing - who does this:


[Install]
WantedBy=default.target

which results in:

-> $ llr /etc/systemd/user/default.target.wants/
total 0
lrwxrwxrwx. 1 root root 39 Jan 26 10:39 syncthing.service -> 
/usr/lib/systemd/user/syncthing.service


So those of you on RHEL and derivatives (I assume that same 
rpm goes to all those) - suffices to install "syncthing" an 
you have your "roor" does as above and if you are not aware 
then the "root" does that with you not even knowing.


As a matter of sharing opinions - is that a good & healthy 
practice to make & distribute packages like that?

many thanks, L.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] service runs - but it's not really there

[lejeczek]

Hi guys

This absolutely boggled my mind, my brain exploded, but go 
easy on me as I ain't an expert.
I have, meaning the "root" but other users too, _NO_ 
"~/.config/systemd" - thus, how I understand it, no service 
definitions which are user-made, yet this..


● user@0.service - User Manager for UID 0
   Loaded: loaded (/usr/lib/systemd/system/user@.service; 
static; vendor preset: disabled)
   Active: active (running) since Thu 2021-01-28 17:13:01 
GMT; 2h 34min ago

 Main PID: 854314 (systemd)
   Status: "Startup finished in 44ms."
    Tasks: 35
   Memory: 69.3M
   CGroup: /user.slice/user-0.slice/user@0.service
   ├─init.scope
   │ ├─854314 /usr/lib/systemd/systemd --user
   │ └─854319 (sd-pam)
   └─syncthing.service

exists and gets auto started by "systemd" without any asking 
really.

This is really very bad, no?
What am I missing here?
many thanks, L.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Antw: [EXT] Re: successful mount starts a service - how?

[lejeczek]

On 19/01/2021 07:50, Ulrich Windl wrote:

Andrei Borzenkov  schrieb am 19.01.2021 um 06:30 in

Nachricht <3a365c71-004e-031e-4153-80c376d80...@gmail.com>:

19.01.2021 04:00, lejeczek пишет:

hi guys.

I'm fiddling with it but have run out of options/ideas.
What I would like to have is systemd starts a service when a device, in
my case a crypt-luks device, gets mounted which mount would happen by
manual 'cryptsetup open'

I am not aware that "cryptsetup open" mounts anything. I do not even see
any option to specify mount point in its invocation. Please show exact
command you are using that "mounts" encrypted container.

But it will make some device (/dev/mapper) to appear.

I'm on centos Stream with systemd 239 (239-43.el8)
OS after boot:
1)
-> $ systemctl status -l devs.mount
● devs.mount - /devs
   Loaded: loaded (/etc/fstab; generated)
   Active: inactive (dead)
    Where: /devs
 What: /dev/mapper/luks-devs
 Docs: man:fstab(5)
   man:systemd-fstab-generator(8)

Jan 19 10:24:45 swir.private.pawel systemd[1]: Dependency 
failed for /devs.
Jan 19 10:24:45 swir.private.pawel systemd[1]: devs.mount: 
Job devs.mount/start failed with result 'dependency'.

2)
-> $ cryptsetup open /dev/mapper/cl_swir-devs luks-devs
3)
-> $ systemctl status -l devs.mount
● devs.mount - /devs
   Loaded: loaded (/etc/fstab; generated)
   Active: active (mounted) since Tue 2021-01-19 10:27:09 
GMT; 48s ago

    Where: /devs
 What: /dev/mapper/luks-devs
...
In fstab:
/dev/mapper/luks-devs /devs   ext4 
context="system_u:object_r:root_t:s0",nofail,noatime,nobarrier,noatime,x-systemd.device-timeout=3s 
0 2


Crypt-luks device got mounted without me doing only no. 2. 
and which is fantastic. Here systemd wisdom does something 
which us users would do but as a result do not have to.


Now, how to "bind" a sevice to "that" so such a service 
would wait for and then auto start(but also stop when device 
is umounted)?

I've tried in such a service' unit a variations of these:

After=devs.mount
BindsTo=devs.mount
PartOf=devs.mount
RequiresMountsFor=/devs

But now I've run out of ideas.

many thanks, L


I see when that manual action takes place then systemd changes status of
a home.mount (which is in fstab) to "active" - and it's here where I
hope systemd would auto-start a service.
Is such a "simple" thing possible?
many thanks, L
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel



___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] successful mount starts a service - how?

[lejeczek]

hi guys.

I'm fiddling with it but have run out of options/ideas.
What I would like to have is systemd starts a service when a 
device, in my case a crypt-luks device, gets mounted which 
mount would happen by manual 'cryptsetup open'
I see when that manual action takes place then systemd 
changes status of a home.mount (which is in fstab) to 
"active" - and it's here where I hope systemd would 
auto-start a service.

Is such a "simple" thing possible?
many thanks, L
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] indirectly related - pacemaker service

[lejeczek]

hi guys,

something I was hoping one expert could shed bit more light onto - I
have a pacemaker cluster composed of three nodes. One one always has a
problem with pacemaker - it's tools would say thing like:

$ crm_mon --one-shot
Connection to cluster failed: Transport endpoint is not connected
$ pcs status --all
Error: cluster is not currently running on this node

but systemd reports relevant demons as up and running with on tiny
exceptions! On "working" nodes it's:

$ systemctl status -l pacemaker
● pacemaker.service - Pacemaker High Availability Cluster Manager
   Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; disabled;
vendor preset: disabled)
   Active: active (running) since Fri 2019-05-10 15:39:40 BST; 2 weeks 5
days ago
 Docs: man:pacemakerd
  
https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/index.html

 Main PID: 28664 (pacemakerd)
   CGroup: /system.slice/pacemaker.service
   ├─  28664 /usr/sbin/pacemakerd -f
   ├─  28670 /usr/libexec/pacemaker/cib
   ├─  28671 /usr/libexec/pacemaker/stonithd
   ├─  28672 /usr/libexec/pacemaker/lrmd
   ├─  28673 /usr/libexec/pacemaker/attrd
   ├─  28674 /usr/libexec/pacemaker/pengine
   ├─  28676 /usr/libexec/pacemaker/crmd
   ├─1503698 /bin/sh /usr/lib/ocf/resource.d/heartbeat/LVM monitor
   ├─1503717 /bin/sh /usr/lib/ocf/resource.d/heartbeat/LVM monitor
   ├─1503718 vgs -o tags --noheadings equalLogic-2.2
   └─1503719 tr -d  

but on that one single failing node:

$ systemctl status -l pacemaker.service 
● pacemaker.service - Pacemaker High Availability Cluster Manager
   Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; enabled;
vendor preset: disabled)
   Active: active (running) since Wed 2019-05-29 17:08:40 BST; 2min 19s ago
 Docs: man:pacemakerd
  
https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/index.html

 Main PID: 48729 (pacemakerd)
    Tasks: 1
   Memory: 3.3M
   CGroup: /system.slice/pacemaker.service
   └─48729 /usr/sbin/pacemakerd -f
 
May 29 17:08:41 rider.private pacemakerd[48729]:   notice: Tracking
existing cib process (pid=39234)
May 29 17:08:41 rider.private pacemakerd[48729]:   notice: Tracking
existing stonithd process (pid=39235)
May 29 17:08:41 rider.private pacemakerd[48729]:   notice: Tracking
existing lrmd process (pid=39236)
May 29 17:08:41 rider.private pacemakerd[48729]:   notice: Tracking
existing attrd process (pid=39238)
May 29 17:08:41 rider.private pacemakerd[48729]:   notice: Tracking
existing pengine process (pid=39240)
May 29 17:08:41 rider.private pacemakerd[48729]:   notice: Tracking
existing crmd process (pid=39241)
May 29 17:08:41 rider.private pacemakerd[48729]:   notice: Quorum acquired

You can clearly see the difference, right? Systems are virtually
identical, same Dell's server model, same Centos 7.6 and packages from
same default repos.

Does that difference between systemds status for pacemaker signify anything?

many thanks, L.



pEpkey.asc
Description: application/pgp-keys
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Restart=on-failure & service failure "Dependency failed for"

[lejeczek]

dear devel

I have a service which fails "Dependency failed for Pacemaker High
Availability Cluster Manager" but that dependency is up & okey(corosync)
(cannot say why pacemaker's systemctl thinks that some dep failed)

So I thought I'd help pacemaker.service by adding:

[Service]
TimeoutStopSec=5min
Restart=on-failure
RestartSec=60

but that does not seem to work.

Is that because Restart=on-failure does not cover such a scenario where
a dependency fails?

If yes is there any way to cover such a scenarios?

many thanks, L.



pEpkey.asc
Description: application/pgp-keys
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] systemd-tmpfiles-setup.service inside LXC fails

[lejeczek]

hi everyone

I guess it fails as below due to container restrictions, I 
use/run it from libvirtd.
I read on https://libvirt.org/drvlxc.html in "Filesystem 
mounts":

"..
/sys the host "sysfs" instance remounted read-only
.."

$ systemctl status -l systemd-tmpfiles-setup.service
● systemd-tmpfiles-setup.service - Create Volatile Files and 
Directories
   Loaded: loaded 
(/usr/lib/systemd/system/systemd-tmpfiles-setup.service; 
static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2018-01-10 
13:05:45 UTC; 4min 48s ago

 Docs: man:tmpfiles.d(5)
   man:systemd-tmpfiles(8)
  Process: 36 ExecStart=/usr/bin/systemd-tmpfiles --create 
--remove --boot --exclude-prefix=/dev (code=exited, 
status=1/FAILURE)

 Main PID: 36 (code=exited, status=1/FAILURE)

Jan 10 13:05:45 lxc-ipa2-swir.priv.xx.xx.priv.xx.xx.x 
systemd[1]: Starting Create Volatile Files and Directories...
Jan 10 13:05:45 lxc-ipa2-swir.priv.xx.xx.priv.xx.xx.x 
systemd-tmpfiles[36]: Failed to create file 
/sys/fs/selinux/checkreqprot: Read-only file system
Jan 10 13:05:45 lxc-ipa2-swir.priv.xx.xx.priv.xx.xx.x 
systemd[1]: systemd-tmpfiles-setup.service: main process 
exited, code=exited, status=1/FAILURE
Jan 10 13:05:45 lxc-ipa2-swir.priv.xx.xx.priv.xx.xx.x 
systemd[1]: Failed to start Create Volatile Files and 
Directories.
Jan 10 13:05:45 lxc-ipa2-swir.priv.xx.xx.priv.xx.xx.x 
systemd[1]: Unit systemd-tmpfiles-setup.service entered 
failed state.
Jan 10 13:05:45 lxc-ipa2-swir.priv.xx.xx.priv.xx.xx.x 
systemd[1]: systemd-tmpfiles-setup.service failed.


Would you know it can be fixed?
many thanks, L.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] udev - ignore/hide persistent storage

[lejeczek]

On 31/03/17 08:00, Lennart Poettering wrote:

On Thu, 30.03.17 21:40, lejeczek (pelj...@yahoo.co.uk) wrote:


sorry guys to bother you, but
  I'll see myself going slowly mad next week, for I've been reading and
tryingand trying..

and I fail to tell udev to ignore a device and not to create symlinks.
I need someone to 100% confirm this should work in v.219.
The way Ithink(or hope) it should work islike:

ENV{ID_SERIAL}=="c50033d225e1", ENV{UDISKS_IGNORE}="1"

udisks is not involved with creating device symlinks, that's all done
by udev itself.

To disable the persistent symlinks it shuld be sufficient to set the
UDEV_DISABLE_PERSISTENT_STORAGE_RULES_FLAG udev property early enough
in the rules, this then has the effect that
60-persistent-storage.rules is skipped.

Lennart

apologies, there is quite a few webpages talking explicitly 
about udisk, take just that ENV I mentioned alone, plenty of 
docs suggesting above, so I thought..
Is it just fedora/rhel do without udisk or those docs/posts 
with udisk are obsolete all together?

thanks.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] udev - ignore/hide persistent storage

[lejeczek]

sorry guys to bother you, but
 I'll see myself going slowly mad next week, for I've been 
reading and tryingand trying..


and I fail to tell udev to ignore a device and not to create 
symlinks.

I need someone to 100% confirm this should work in v.219.
The way Ithink(or hope) it should work islike:

ENV{ID_SERIAL}=="c50033d225e1", ENV{UDISKS_IGNORE}="1"

although I've tried number of different options in my .rules 
file.
I think that with sas or wwin address it would go to the 
lowest level of all those identification layers, thus most 
persistent.
But all the udev test I ran I saw: ACTION=add and symlinks 
would be created by 60-persistent-storage.rules mostly. 
(centos 7.3)


Is it possible to have udev ignore scsi/sas disks with the 
use of sas(or similarly low) addresses?


many thank,
L

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] how make systemd NOT to clutter dmesg?

[lejeczek]

On 27/02/17 16:43, Reindl Harald wrote:



Am 27.02.2017 um 17:18 schrieb lejeczek:

yes, correct, something did, in /etc/grub2.cfg

systemd.log_level=debug systemd.log_target=kmsg

even tough nothing of above is to be found in 
/etc/default/grub
What I found and messaged Centos list about, long agao, 
but it might be
interesting to anybody who.. uses Oracle's kernel-uek 
which a long time

ago I'm pretty sure put:
MAKEDEBUG=yes
into /etc/sysconfig/kernel
but what I've had commented out for long long time, and 
many new kernels

installed since then.
I'll get rid of UEK for peace of mind's sake


it has *nothing* to do with UEK
one of the last CentOS updates here did the same *only* on 
one machine


however, next time when you report issues start by 
mentioning you operating system, the patch-level and 
version of your operating system and uncutted loglines 
which you are talking about in the initial post


with that informations i would have been able to point you 
directly to /etc/sysconfig/kernel - you can't assume that 
anybody is guessing what you are talking about when you 
hold back any informations


gee, sorry, maybe I made it vague? I just said it was NOT 
sysconfig/kernel but /etc/grub2.cfg
I mentioned sysconfig/kernel and that "I've had commented 
out for long long time" and UEK because I believed UEK put 
it MAKEDEBUG=yes and tampered with /etc/grub2.cfg



___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] how make systemd NOT to clutter dmesg?

[lejeczek]

On 27/02/17 12:04, Lennart Poettering wrote:

On Mon, 27.02.17 11:03, lejeczek (pelj...@yahoo.co.uk) wrote:



On 27/02/17 10:10, Reindl Harald wrote:


Am 27.02.2017 um 10:55 schrieb lejeczek:

hi there

I'm trying to solve problem which to you guys must be trivial, but
it's
a puzzle to me.
I've searched the net & man pages but ... failed to find how/where
systemd is told to put stuff like:

Got message type...

seriously - could you at least post *one* uncutted message

I said, it seemed the whole lot went there.. does it not make it simpler?
I did not want to clutter the mailing list, here:


[67142.383939] systemd[1]: Got notification message for unit httpd.service
[67142.383956] systemd[1]: httpd.service: Got notification message from PID
7722 (READY=1, STATUS=Total requests: 0; Current requests/sec: 0; Current
traffic:   0 B/sec)

Seems something turned on debug logging for you. There are multiple
ways how you might have turned it on. systemd.log_level=debug on the
kernel cmdline (just "debug" works too). There's also a config option
in system.conf. You can even turn it off and on dynamically with
"systemd-analyze set-log-level"...

How you turned it on I have no idea, but note that systemd will never
turn debug logging on on its own, so it's clearly your admin (or some
tool he used) on your system that is at fault.

Lennart


yes, correct, something did, in /etc/grub2.cfg

systemd.log_level=debug systemd.log_target=kmsg

even tough nothing of above is to be found in /etc/default/grub
What I found and messaged Centos list about, long agao, but 
it might be interesting to anybody who.. uses Oracle's 
kernel-uek which a long time ago I'm pretty sure put:

MAKEDEBUG=yes
into /etc/sysconfig/kernel
but what I've had commented out for long long time, and many 
new kernels installed since then.

I'll get rid of UEK for peace of mind's sake.



___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] how make systemd NOT to clutter dmesg?

[lejeczek]

On 27/02/17 10:10, Reindl Harald wrote:



Am 27.02.2017 um 10:55 schrieb lejeczek:

hi there

I'm trying to solve problem which to you guys must be 
trivial, but it's

a puzzle to me.
I've searched the net & man pages but ... failed to find 
how/where

systemd is told to put stuff like:

Got message type...


seriously - could you at least post *one* uncutted message


I said, it seemed the whole lot went there.. does it not 
make it simpler?

I did not want to clutter the mailing list, here:


[67142.383939] systemd[1]: Got notification message for unit 
httpd.service
[67142.383956] systemd[1]: httpd.service: Got notification 
message from PID 7722 (READY=1, STATUS=Total requests: 0; 
Current requests/sec: 0; Current traffic:   0 B/sec)

[67142.383963] systemd[1]: httpd.service: got READY=1
[67142.383972] systemd[1]: httpd.service: got STATUS=Total 
requests: 0; Current requests/sec: 0; Current traffic:   0 B/sec
[67142.384152] systemd[1]: Sent message type=signal 
sender=n/a destination=n/a 
object=/org/freedesktop/systemd1/unit/httpd_2eservice 
interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=212382 reply_cookie=0 error=n/a
[67142.384245] systemd[1]: Sent message type=signal 
sender=n/a destination=n/a 
object=/org/freedesktop/systemd1/unit/httpd_2eservice 
interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=212383 reply_cookie=0 error=n/a
[67142.384902] systemd-logind[4006]: Got message type=signal 
sender=:1.0 destination=n/a 
object=/org/freedesktop/systemd1/unit/httpd_2eservice 
interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=212382 reply_cookie=0 error=n/a
[67142.385056] systemd-logind[4006]: Got message type=signal 
sender=:1.0 destination=n/a 
object=/org/freedesktop/systemd1/unit/httpd_2eservice 
interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=212383 reply_cookie=0 error=n/a
[67144.428328] systemd[1]: Got notification message for unit 
php-fpm.service
[67144.428343] systemd[1]: php-fpm.service: Got notification 
message from PID 4054 (READY=1, STATUS=Processes active: 0, 
idle: 5, Requests: 0, slow: 0, Traffic: 0req/sec)

[67144.428349] systemd[1]: php-fpm.service: got READY=1
[67144.428359] systemd[1]: php-fpm.service: got 
STATUS=Processes active: 0, idle: 5, Requests: 0, slow: 0, 
Traffic: 0req/sec
[67144.429383] systemd-logind[4006]: Got message type=signal 
sender=:1.0 destination=n/a 
object=/org/freedesktop/systemd1/unit/php_2dfpm_2eservice 
interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=212384 reply_cookie=0 error=n/a
[67144.429520] systemd-logind[4006]: Got message type=signal 
sender=:1.0 destination=n/a 
object=/org/freedesktop/systemd1/unit/php_2dfpm_2eservice 
interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=212385 reply_cookie=0 error=n/a
[67152.394629] systemd[1]: Got notification message for unit 
httpd.service
[67152.394645] systemd[1]: httpd.service: Got notification 
message from PID 7722 (READY=1, STATUS=Total requests: 0; 
Current requests/sec: 0; Current traffic:   0 B/sec)

[67152.394653] systemd[1]: httpd.service: got READY=1
[67152.394662] systemd[1]: httpd.service: got STATUS=Total 
requests: 0; Current requests/sec: 0; Current traffic:   0 B/sec
[67152.394843] systemd[1]: Sent message type=signal 
sender=n/a destination=n/a 
object=/org/freedesktop/systemd1/unit/httpd_2eservice 
interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=212386 reply_cookie=0 error=n/a
[67152.394936] systemd[1]: Sent message type=signal 
sender=n/a destination=n/a 
object=/org/freedesktop/systemd1/unit/httpd_2eservice 
interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=212387 reply_cookie=0 error=n/a
[67152.396849] systemd-logind[4006]: Got message type=signal 
sender=:1.0 destination=n/a 
object=/org/freedesktop/systemd1/unit/httpd_2eservice 
interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=212386 reply_cookie=0 error=n/a
[67152.396906] systemd-logind[4006]: Got message type=signal 
sender=:1.0 destination=n/a 
object=/org/freedesktop/systemd1/unit/httpd_2eservice 
interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=212387 reply_cookie=0 error=n/a
[67152.397988] systemd[1]: Got notification message for unit 
systemd-logind.service
[67152.397997] systemd[1]: systemd-logind.service: Got 
notification message from PID 4006 (WATCHDOG=1)
[67152.398004] systemd[1]: systemd-logind.service: got 
WATCHDOG=1
[67152.398416] systemd[1]: Got notification message for unit 
systemd-machined.service
[67153.547185] systemd-logind[4006]: Got message type=signal 
sender=:1.0 destination=n/a 
object=/org/freedesktop/systemd1/unit/ctdb_2eservice 
interface=org.freedesktop.DBus.Properties 
member=PropertiesChanged cookie=212389 reply_cookie=0 error=n/a
[67153.547451] systemd-logind[4006]: Got message type=signal 
sender=:1.0 destination=n/a 
object=

[systemd-devel] how make systemd NOT to clutter dmesg?

[lejeczek]

hi there

I'm trying to solve problem which to you guys must be 
trivial, but it's a puzzle to me.
I've searched the net & man pages but ... failed to find 
how/where systemd is told to put stuff like:


Got message type...

but basically seems like the whole lot, into the dmesg?
I have one box which has clean dmesg and the other which has 
everything from systemd, I cannot figure what makes this 
different behaviour.


many thanks,
L.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] SCHED_FIFO

[lejeczek]

hi

I have ctdb use team net devices but there is a problem: 
https://bugzilla.redhat.com/show_bug.cgi?id=1421378


2017/02/21 15:20:34.923629 [16515]: Unable to set scheduler 
to SCHED_FIFO (Operation not permitted)


I do: system edit ctdb
there:

[Service]
ExecStartPre=/bin/sh -c "echo 1 > 
/sys/fs/cgroup/cpu/system.slice/cpu.rt_runtime_us"

#LimitRTPRIO=infinity
#LimitRTTIME=10

TimeoutStartSec=300
Restart=on-failure
RestartSec=20

But Limit options don't work for me.
Would you know if it can be tweaked with systemd's help?
thx,
L
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] gluster & libvritd

[lejeczek]

sorry guys, I bugged libvirtd but... weirdly, quiet there, 
so I'm hoping an expert here would share a thought.


I've a few VM guest which work/run perfectly fine, I 
believe, except for autostart.
Configuration of system, gluster and libvirt is pretty 
regular and not complex.

Errors I see:
...
failed to initialize gluster connection (src=0x7f9424266350 
priv=0x7f94242922b0): Transport endpoint is
internal error: Failed to autostart VM 'rhel-work2': failed 
to initialize gluster connection (src=0x7f9
failed to initialize gluster connection (src=0x7f942423fef0 
priv=0x7f9424256320): Transport endpoint is
internal error: Failed to autostart VM 'rhel-work3': failed 
to initialize gluster connection (src=0x7f9
failed to initialize gluster connection (src=0x7f9424261b20 
priv=0x7f94242a18b0): Transport endpoint is
internal error: Failed to autostart VM 'rhel-work1': failed 
to initialize gluster connection (src=0x7f9

...

I tried to make systemd libvirtd to wait for gluster:

After=glusterd.service

but if that's all required then, well, still fails.
Would you have any suggestions?
Many thanks,
L.

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] oneshot & restart

[lejeczek]

hi all
I'm reading man pages but cannot see whether there is a 
conflict there,

a unit:

[Service]
Type=oneshot
RemainAfterExit=yes
TimeoutSec=0

$ systemctl edit
[Service]
Restart=on-failure
RestartSec=90
TimeoutSec=10

and I see:

   Loaded: error (Reason: Invalid argument)
  Drop-In: /etc/systemd/system/ipa.service.d
   └─override.conf
   Active: active (exited) since Wed 2017-01-18 11:25:08 
GMT; 25min ago

 Main PID: 17579 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/ipa.service

btw. I'm reading man page on edit
"... to extend or override the specified unit."
Is it that - override.conf extends by what is not in the 
original unit file and overrides what is there in the original ?


many thanks,
L.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] service startup time ?

[lejeczek]

sorry to bother devel, I've sroogled up but failed to find 
an answer to this simple question - can I get the time that 
a service takes to start? Also at what time after kernel 
loaded service commenced its startup?


many thanks,

L.


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] dhcpd (via systemd) @boottime which does not wait for the interface..

[lejeczek]

hi devels

I have my dhcpd to serve nothing but virbr0 (libvirt), OS is Centos 7.2
Dhcpd would not start, complaining like this:

No subnet declaration for virbr0 (no IPv4 addresses).
** Ignoring requests on virbr0.  If this is not what
   you want, please write a subnet declaration
   in your dhcpd.conf file for the network segment
   to which interface virbr0 is attached. **

and systemctl -l shows:
...
systemd[1]: start request repeated too quickly for dhcpd.service
...

but suffices to restart dhcpd and all works!
I've ##SELECTION_END##customized systemd's service conf, I've put:

After=libvirtd.service
Requisite=libvirtd.service

but this did not help.
Would you share your thoughts?
many thanks.
L.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] an enhancement request/suggestion

[lejeczek]

dear devel

could we please have journalctl -o cat not loose coloring 
the output feature?


many thanks
P
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] confine user(s) to a core with systemd + cgroup

[lejeczek]

sorry to bother developers
I've been reading, asking forums, etc, but failed to find an 
answer to one quick question:


how do I put users, their whole session from the moment they 
login into a cgroup cpuset?


I thought it would be CPUAffinity responsible for it either in
systemd-user-sessions or(and) in systemd-logind, but it does 
not work.


thanks
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel