Re: [systemd-devel] systemd v228 errors: "Failed to enqueue exit.target job: Transaction contains conflicting jobs 'start' and 'stop'" ?

2016-03-10 Thread Andrei Borzenkov 
11.03.2016 04:53, PGNet Dev пишет:
> I'm booting a
> 
> systemctl --version
> systemd 228
> +PAM +AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP
> +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS
> +KMOD -IDN
> 
> OS instance.  Atm, it's a Xen DomU vm guest.
> 
> It's a DIY-build instance of current systemd for a stable distro
> release; @ distro has no apparent interest in supporting it.  Despite
> that, I'm trying to get it working and cleaned up for my own use.
> 
> On boot, I see these in logs
> 
> dmesg
> ...
> [  374.429270] systemd[1617]: Failed to enqueue exit.target job:
> Transaction contains conflicting jobs 'start' and 'stop' for
> shutdown.target. Probably contradicting requirement dependencies
> configured.


Try

systemctl --user list-dependencies exit.target
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Transaction contains conflicting jobs 'restart' and 'stop'

2016-03-10 Thread Andrei Borzenkov 
11.03.2016 00:11, Orion Poplawski пишет:
> Uoti Urpala  pp1.inet.fi> writes:
> 
>>
>> On Thu, 2016-03-10 at 17:51 +, Orion Poplawski wrote:
>>> Orion Poplawski  cora.nwra.com> writes:
  
 # systemctl restart firewalld
 Failed to restart firewalld.service: Transaction contains
 conflicting jobs
 'restart' and 'stop' for fail2ban.service. Probably contradicting
 requirement dependencies configured.
>>
>>> It appears that this is a trigger for this issue.  Removing the
>>> conflicts=iptables.service removes it.  This seems like a bug to me
>>> though -
>>> why is iptables being brought in if the PartOf= is a one-way dep?
>>
>> I guess it's because it's because firewalld.service has
>> "Conflicts=iptables.service", and thus (re)starting firewalld.service
>> stops iptables.service; fail2ban.service has PartOf to both, thus both
>> the restart and stop are propagated, and conflict.
> 
> Can't the stop of iptables be dropped because the service is already stopped
> (or more likely not even present)?
> 
>> Claiming a PartOf relationship to both of two conflicting services is
>> the problem here. I doubt such a use case was what PartOf was designed
>> to support.
> 
> 
> The problem is that fail2ban can work with either iptables.service or
> fail2ban.service, and we don't know which one the use wants to use.  And we
> need fail2ban to be restarted if either firewalld or iptables is restarted.
> If there is some other supported way of achieving this, that would be
> welcome.  Otherwise this strikes be as something that should be able to be
> handled as is.


One possible implementation is to have firewall.target and make all
otehr services (firewalld, iptables and fail2ban) PartOf this target.
You would then start/stop firewall.target instead of individual services.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] systemd v228 errors: "Failed to enqueue exit.target job: Transaction contains conflicting jobs 'start' and 'stop'" ?

2016-03-10 Thread PGNet Dev 

I'm booting a

systemctl --version
systemd 228
		+PAM +AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP 
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS 
+KMOD -IDN


OS instance.  Atm, it's a Xen DomU vm guest.

It's a DIY-build instance of current systemd for a stable distro 
release; @ distro has no apparent interest in supporting it.  Despite 
that, I'm trying to get it working and cleaned up for my own use.


On boot, I see these in logs

dmesg
...
		[  374.429270] systemd[1617]: Failed to enqueue exit.target job: 
Transaction contains conflicting jobs 'start' and 'stop' for 
shutdown.target. Probably contradicting requirement dependencies configured.
		[  698.686714] systemd[1834]: Failed to enqueue exit.target job: 
Transaction contains conflicting jobs 'stop' and 'start' for 
exit.target. Probably contradicting requirement dependencies configured.
		[  698.729596] systemd[1848]: Failed to enqueue exit.target job: 
Transaction contains conflicting jobs 'stop' and 'start' for 
systemd-exit.service. Probably contradicting requirement dependencies 
configured.
		[  698.767659] systemd[1861]: Failed to enqueue exit.target job: 
Transaction contains conflicting jobs 'stop' and 'start' for 
shutdown.target. Probably contradicting requirement dependencies configured.
		[  698.801234] systemd[1871]: Failed to enqueue exit.target job: 
Transaction contains conflicting jobs 'stop' and 'start' for 
systemd-exit.service. Probably contradicting requirement dependencies 
configured.
		[  698.843302] systemd[1884]: Failed to enqueue exit.target job: 
Transaction contains conflicting jobs 'stop' and 'start' for 
systemd-exit.service. Probably contradicting requirement dependencies 
configured.

...

Currently,

locate exit.target shutdown.target systemd-exit.service
/usr/lib/systemd/system/shutdown.target
/usr/lib/systemd/system/shutdown.target.wants

/usr/lib/systemd/system/shutdown.target.wants/dracut-shutdown.service
/usr/lib/systemd/user/exit.target
/usr/lib/systemd/user/shutdown.target
/usr/lib/systemd/user/systemd-exit.service

	rpm -q --whatprovides $( locate exit.target shutdown.target 
systemd-exit.service )

systemd-228-18.1.x86_64
systemd-228-18.1.x86_64
dracut-037-68.1.x86_64
systemd-228-18.1.x86_64
systemd-228-18.1.x86_64
systemd-228-18.1.x86_64

Where

cat /usr/lib/systemd/user/exit.target
[Unit]
Description=Exit the Session
Documentation=man:systemd.special(7)
DefaultDependencies=no
Requires=systemd-exit.service
After=systemd-exit.service
AllowIsolate=yes

cat /usr/lib/systemd/system/shutdown.target
[Unit]
Description=Shutdown
Documentation=man:systemd.special(7)
DefaultDependencies=no
RefuseManualStart=yes

cat 
/usr/lib/systemd/system/shutdown.target.wants/dracut-shutdown.service
[Unit]
Description=Restore /run/initramfs
Documentation=man:dracut-shutdown.service(8)
After=getty@tty1.service display-manager.service
Before=systemd-reboot.service shutdown.target
DefaultDependencies=no
ConditionPathExists=/run/initramfs/.need_shutdown
ConditionPathExists=!/run/initramfs/bin/sh

[Service]
ExecStart=-/usr/lib/dracut/dracut-initramfs-restore
Type=oneshot
RemainAfterExit=yes

cat /usr/lib/systemd/user/shutdown.target
[Unit]
Description=Shutdown
Documentation=man:systemd.special(7)
DefaultDependencies=no
RefuseManualStart=yes

cat /usr/lib/systemd/user/systemd-exit.service
[Unit]
Description=Exit the Session
Documentation=man:systemd.special(7)
DefaultDependencies=no
Requires=shutdown.target
After=shutdown.target multi-user.target

[Service]
Type=oneshot
WorkingDirectory=/
ExecStart=/usr/bin/kill -s SIGRTMIN+24 $MANAGERPID

The deps are a bit convoluted at 1st look.

What in that config's causing the

Transaction contains conflicting jobs 'start' and 'stop'

fails?

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

[systemd-devel] udev timeout notification

2016-03-10 Thread Benjamin Marzinski 
If udev times out while processing an event, so that the event won't
have the added all the properties to the database, it there some way
that udev notifies listeners to the udev event that processing didn't
complete?

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

Re: [systemd-devel] Transaction contains conflicting jobs 'restart' and 'stop'

2016-03-10 Thread Uoti Urpala 
On Thu, 2016-03-10 at 17:51 +, Orion Poplawski wrote:
> Orion Poplawski  cora.nwra.com> writes:
> > 
> > # systemctl restart firewalld
> > Failed to restart firewalld.service: Transaction contains
> > conflicting jobs
> > 'restart' and 'stop' for fail2ban.service. Probably contradicting
> > requirement dependencies configured.

> It appears that this is a trigger for this issue.  Removing the
> conflicts=iptables.service removes it.  This seems like a bug to me
> though -
> why is iptables being brought in if the PartOf= is a one-way dep?

I guess it's because it's because firewalld.service has
"Conflicts=iptables.service", and thus (re)starting firewalld.service
stops iptables.service; fail2ban.service has PartOf to both, thus both
the restart and stop are propagated, and conflict.

Claiming a PartOf relationship to both of two conflicting services is
the problem here. I doubt such a use case was what PartOf was designed
to support.

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

Re: [systemd-devel] Why does sysv generator translate Required-Start keyword into an After= ordering dep only ?

2016-03-10 Thread Andrei Borzenkov 
10.03.2016 18:05, Francis Moreau пишет:
> On Tue, Mar 8, 2016 at 10:19 AM, Andrei Borzenkov  wrote:
>> 08.03.2016 11:33, Francis Moreau пишет:
>>> On Tue, Mar 8, 2016 at 9:23 AM, Andrei Borzenkov  
>>> wrote:
 08.03.2016 11:07, Francis Moreau пишет:
> On Tue, Mar 8, 2016 at 7:51 AM, Andrei Borzenkov  
> wrote:
>> 07.03.2016 10:04, Francis Moreau пишет:
>>> Hello,
>>>
>>> Sorry for the long delay.
>>>
>>> On Fri, Feb 26, 2016 at 5:05 AM, Andrei Borzenkov  
>>> wrote:
 26.02.2016 00:55, Francis Moreau пишет:
>
> But now I'm wondering how the following case is handled: a sysinit
> script "a" has "Required-Start: b". But "b" is a native systemd
> service. I don't think the tool that enable/disable sysv services can
> enable and order correctly the native service.
>

 What difference does it make?
>>>
>>> The difference is that in my current understanding nothing will pull 
>>> "b" in.
>>
>> That was answered in part you trimmed off. sysvinit never actively
>> pulled "b" in either so nothing really changed here.
>>
>
> In my understanding insserv is part of the sysvinit implementation.
>
> Therefore to enable a service with sysvinit, we do:
>
>  - insserv a (this will create Sa *and* Sb" with yy < xx)

 That would be new to me. insserv creates links ("enables") exactly those
 services that you specify. So if you say "insserv a" you will get only
 "a" enabled; this /may/ rearrange other services including "b" if they
 are already enabled but this will not enable "b".

>>>
>>> That's how I understood Lennart's excerpt I was referring to previously.
>>>
>>
>> Hmm ... I tested on SLES11 and indeed, while "insserv a" will not enable
>> "b" it will refuse to enable "a" if "b" is not enabled. And conversely
>> it will not disable "b" if "a" is enabled.
>>
>> So at least it tries to ensure that set of enabled services is consistent.
> 
> Is this system uses systemd ?
> 

No; it is too old for this. It is classical sysvinit.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Transaction contains conflicting jobs 'restart' and 'stop'

2016-03-10 Thread Orion Poplawski 
Orion Poplawski  cora.nwra.com> writes:
> 
> Can someone please explain this to me?
> 
> # systemctl restart firewalld
> Failed to restart firewalld.service: Transaction contains conflicting jobs
> 'restart' and 'stop' for fail2ban.service. Probably contradicting
> requirement dependencies configured.
>
> # cat /usr/lib/systemd/system/fail2ban.service
> [Unit]
> PartOf=iptables.service firewalld.service
> 
> # cat /usr/lib/systemd/system/firewalld.service
> [Unit]
> Conflicts=iptables.service ip6tables.service ebtables.service

It appears that this is a trigger for this issue.  Removing the
conflicts=iptables.service removes it.  This seems like a bug to me though -
why is iptables being brought in if the PartOf= is a one-way dep?

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

[systemd-devel] systemd 215: NFS mount marked successfully even if it's not (and other NFS mounts issues)

2016-03-10 Thread Sandro Tosi 
Hey!

we are seeing some weird behavior of systemd 215 (I know it's a rather
old version, but it's the one on Debian Jessie, so it has quite a big
audience) with NFS mounts. We had a lengthy and helpful discussion[1]
with the Debian systemd maintainers (CC'ed) about that and in one of
the last messages[2] we spotted something that sounds really weird and
we'd like you to have a look:

Feb 23 06:50:43 SERVER systemd[1]: Mounting /mnt/NFSSERVER1_VOL...
Feb 23 06:50:43 SERVER systemd[1]: About to execute: /bin/mount -n
XXX.YYY.32.75:/vol/vol3 /mnt/NFSSERVER1_VOL -t nfs -o
ro,intr,nolock,tcp,rdirplus,noatime,_netdev
Feb 23 06:50:43 SERVER systemd[1]: mnt-NFSSERVER1_VOL.mount changed
dead -> mounting
Feb 23 06:50:43 SERVER systemd[574]: Executing: /bin/mount -n
XXX.YYY.32.75:/vol/vol3 /mnt/NFSSERVER1_VOL -t nfs -o
ro,intr,nolock,tcp,rdirplus,noatime,_netdev
Feb 23 06:52:13 SERVER systemd[1]: mnt-NFSSERVER1_VOL.mount mounting
timed out. Stopping.
Feb 23 06:52:13 SERVER systemd[1]: mnt-NFSSERVER1_VOL.mount changed
mounting -> mounting-sigterm
Feb 23 06:52:13 SERVER systemd[1]: Child 574 belongs to mnt-NFSSERVER1_VOL.mount
Feb 23 06:52:13 SERVER systemd[1]: mnt-NFSSERVER1_VOL.mount mount
process exited, code=killed status=15
Feb 23 06:52:13 SERVER systemd[1]: mnt-NFSSERVER1_VOL.mount changed
mounting-sigterm -> mounted
Feb 23 06:52:13 SERVER systemd[1]: Job mnt-NFSSERVER1_VOL.mount/start
finished, result=done
Feb 23 06:52:13 SERVER systemd[1]: Mounted /mnt/NFSSERVER1_VOL.
Feb 23 06:52:13 SERVER systemd[1]: Starting Remote File Systems.
Feb 23 06:52:13 SERVER systemd[1]: remote-fs.target changed dead -> active
Feb 23 06:52:13 SERVER systemd[1]: Job remote-fs.target/start
finished, result=done
Feb 23 06:52:13 SERVER systemd[1]: Reached target Remote File Systems.
Feb 23 06:52:13 SERVER systemd[1]: mnt-NFSSERVER1_VOL.mount changed
mounted -> failed

so it appears the mount is marked as mounted, while there was actually an error.

We started the conversation at [1] with other NFS issues: some mounts
were not mounted or appeared mounted twice, and they might all be
related to some underlying problem with NFS shares and (maybe) this
specific version of systemd or some other systems component, and your
help in debugging and fixing them is greatly appreciated!

we are willing to run tests or change configuration as needed, but it
might be a bit difficult to upgrade to a newer version of systemd.

Attached is the first few minutes of boot of the machine from where we
extracted the log above (it's anonymized, but it should preserve all
the useful information), and let me know if you need more details
(some of them are in the thread at [1]) or some config changes.

[1] 
http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2016-January/thread.html#10382
+ 
http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2016-February/thread.html#10734
[2] 
http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2016-February/010870.html

Thanks a ton in advance!

Please keep me (and the Debian systemd maints) in CC, as I'm not
subscribed to this list

Cheers,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi


boot.log.gz
Description: GNU Zip compressed data
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Why does sysv generator translate Required-Start keyword into an After= ordering dep only ?

2016-03-10 Thread Francis Moreau 
On Tue, Mar 8, 2016 at 10:19 AM, Andrei Borzenkov  wrote:
> 08.03.2016 11:33, Francis Moreau пишет:
>> On Tue, Mar 8, 2016 at 9:23 AM, Andrei Borzenkov  wrote:
>>> 08.03.2016 11:07, Francis Moreau пишет:
 On Tue, Mar 8, 2016 at 7:51 AM, Andrei Borzenkov  
 wrote:
> 07.03.2016 10:04, Francis Moreau пишет:
>> Hello,
>>
>> Sorry for the long delay.
>>
>> On Fri, Feb 26, 2016 at 5:05 AM, Andrei Borzenkov  
>> wrote:
>>> 26.02.2016 00:55, Francis Moreau пишет:

 But now I'm wondering how the following case is handled: a sysinit
 script "a" has "Required-Start: b". But "b" is a native systemd
 service. I don't think the tool that enable/disable sysv services can
 enable and order correctly the native service.

>>>
>>> What difference does it make?
>>
>> The difference is that in my current understanding nothing will pull "b" 
>> in.
>
> That was answered in part you trimmed off. sysvinit never actively
> pulled "b" in either so nothing really changed here.
>

 In my understanding insserv is part of the sysvinit implementation.

 Therefore to enable a service with sysvinit, we do:

  - insserv a (this will create Sa *and* Sb" with yy < xx)
>>>
>>> That would be new to me. insserv creates links ("enables") exactly those
>>> services that you specify. So if you say "insserv a" you will get only
>>> "a" enabled; this /may/ rearrange other services including "b" if they
>>> are already enabled but this will not enable "b".
>>>
>>
>> That's how I understood Lennart's excerpt I was referring to previously.
>>
>
> Hmm ... I tested on SLES11 and indeed, while "insserv a" will not enable
> "b" it will refuse to enable "a" if "b" is not enabled. And conversely
> it will not disable "b" if "a" is enabled.
>
> So at least it tries to ensure that set of enabled services is consistent.

Is this system uses systemd ?

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