[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
Well, no weird thing, yes, probably it just restart interface,
this is wrong if other interface config is changed...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in netplan:
Triaged
Status in heartbeat package in Ubuntu:
Won't Fix
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Won't Fix
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in keepalived source package in Focal:
Confirmed
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
- ALL related HA software has a small problem if interfaces are being
managed by systemd-networkd: nic restarts/reconfigs are always going
to wipe all interfaces aliases when HA software is not expecting it to
(no coordination between them.
- keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
smarter in this case because it has a service monitor that will
restart the virtual IP resource, in affected node & nic, before
considering a real failure, but other HA service might consider a real
failure when it is not.
[test case]
- comment #14 is a full test case: to have 3 node pacemaker, in that
example, and cause a networkd service restart: it will trigger a
failure for the virtual IP resource monitor.
- other example is given in the original description for keepalived.
both suffer from the same issue (and other HA softwares as well).
[regression potential]
- this backports KeepConfiguration parameter, which adds some
significant complexity to networkd's configuration and behavior, which
could lead to regressions in correctly configuring the network at
networkd start, or incorrectly maintaining configuration at networkd
restart, or losing network state at networkd stop.
- Any regressions are most likely to occur during networkd start,
restart, or stop, and most likely to involve missing or incorrect ip
address(es).
- the change is based in upstream patches adding the exact feature we
needed to fix this issue & it will be integrated with a netplan change
to add the needed stanza to systemd nic configuration file
(KeepConfiguration=)
[other info]
original description:
---
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the machine,
# (doesn't have to be hostname).
vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
vrrp_mcast_group6 ff02::12 # optional, default ff02::12
enable_traps # enable SNMP traps
}
vrrp_sync_group collection
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
If problem is in timestamp, then this is netplan problem- why it
regenerates files with no changes?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in netplan:
Triaged
Status in heartbeat package in Ubuntu:
Won't Fix
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Won't Fix
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in keepalived source package in Focal:
Confirmed
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
- ALL related HA software has a small problem if interfaces are being
managed by systemd-networkd: nic restarts/reconfigs are always going
to wipe all interfaces aliases when HA software is not expecting it to
(no coordination between them.
- keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
smarter in this case because it has a service monitor that will
restart the virtual IP resource, in affected node & nic, before
considering a real failure, but other HA service might consider a real
failure when it is not.
[test case]
- comment #14 is a full test case: to have 3 node pacemaker, in that
example, and cause a networkd service restart: it will trigger a
failure for the virtual IP resource monitor.
- other example is given in the original description for keepalived.
both suffer from the same issue (and other HA softwares as well).
[regression potential]
- this backports KeepConfiguration parameter, which adds some
significant complexity to networkd's configuration and behavior, which
could lead to regressions in correctly configuring the network at
networkd start, or incorrectly maintaining configuration at networkd
restart, or losing network state at networkd stop.
- Any regressions are most likely to occur during networkd start,
restart, or stop, and most likely to involve missing or incorrect ip
address(es).
- the change is based in upstream patches adding the exact feature we
needed to fix this issue & it will be integrated with a netplan change
to add the needed stanza to systemd nic configuration file
(KeepConfiguration=)
[other info]
original description:
---
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the machine,
# (doesn't have to be hostname).
vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
vrrp_mcast_group6 ff02::12 # optional, default ff02::12
enable_traps # enable SNMP traps
}
vrrp_sync_group collection {
grou
[Touch-packages] [Bug 1599446] Re: 16.04, wrong units start order
Excellent result :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1599446 Title: 16.04, wrong units start order Status in systemd package in Ubuntu: Won't Fix Bug description: Hello! squid uses ldap and mysql for authorization , so I added them to squid dependencies: ### BEGIN INIT INFO # Provides: squid # Required-Start:$network $remote_fs $syslog mysql slapd After=systemd-journald.socket basic.target systemd-journald-dev-log.socket mysql.service remote-fs.target network-online.target nss-lookup.target system.slice sysinit.target slapd.service And symlinks are created in right order: S03slapd S04mysql S05squid But really squid is started before mysql (mariadb) and slapd are started: journalctl -u squid -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:44:41 SAMT. -- июл 06 13:10:31 inetgw2 systemd[1]: Starting LSB: Squid HTTP Proxy version 3.x... journalctl -u slapd -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:45:36 SAMT. -- июл 06 13:10:42 inetgw2 systemd[1]: Starting LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)... journalctl -u mysql -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:45:46 SAMT. -- июл 06 13:10:42 inetgw2 systemd[1]: Starting LSB: Start and stop the mysql database server daemon... июл 06 13:10:43 inetgw2 mysql[2647]: * Starting MariaDB database server mysqld i.e. real start order is: sqiud slapd mysql Expected result is folowing slapd mysql squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1599446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832933] [NEW] upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd
Public bug reported: Hello! After upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 openssl 1.1.1-1ubuntu2.1~18.04.2 on Ubuntu 18.04 server clients can't connect to ejabberd server: 2019-06-15 15:56:26.431 [warning] <0.858.0>@ejabberd_c2s:process_terminated:290 (tls|<0.858.0>) Failed to secure c2s connection: TLS failed: client renegotiations forbidden ejabberd version is18.01-2 which is from Ubuntu 18.04. As far as I know ejabberd can work with openssl 1.1.1 only from 18.09 https://blog.process-one.net/ejabberd-18-09/ OpenSSL 1.1.1 support Either ejabberd in 18.04 should be updated or openssl should not be upgraded to 1.1.1 on 18.04 . Thank you! ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: ejabberd openssl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832933 Title: upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 breaks ejabbrd Status in openssl package in Ubuntu: New Bug description: Hello! After upgrade to libssl1.1 1.1.1-1ubuntu2.1~18.04.2 openssl 1.1.1-1ubuntu2.1~18.04.2 on Ubuntu 18.04 server clients can't connect to ejabberd server: 2019-06-15 15:56:26.431 [warning] <0.858.0>@ejabberd_c2s:process_terminated:290 (tls|<0.858.0>) Failed to secure c2s connection: TLS failed: client renegotiations forbidden ejabberd version is18.01-2 which is from Ubuntu 18.04. As far as I know ejabberd can work with openssl 1.1.1 only from 18.09 https://blog.process-one.net/ejabberd-18-09/ OpenSSL 1.1.1 support Either ejabberd in 18.04 should be updated or openssl should not be upgraded to 1.1.1 on 18.04 . Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821566] Re: cron ignores whole crontab if one line has error
Well, this design is wrong then, because I'm talking about /etc/crontab ,not about /etc/cron.d directory. System crontab ( /etc/crontab ) is protected by access rights, so it can't be changed by malicious user. And any error causes cron almost stop working, because in my case /etc/crontab contains all jobs. So , if malicious user has access to it he can stop cron from working, and, thus, stop mailing access reports to me, this is security hole :-) I.e. this is not implementation bug, but design bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1821566 Title: cron ignores whole crontab if one line has error Status in cron package in Ubuntu: Invalid Bug description: Ubuntu 18.04. Let's create error entry in /etc/crontab: 00 09 * * 4 1 root /usr/local/bin/geoiprenew.sh restart cron systemctl restart cron мар 25 10:29:02 ovpn1 cron[12403]: Error: bad username; while reading /etc/crontab мар 25 10:29:02 ovpn1 cron[12403]: (*system*) ERROR (Syntax error, this crontab file will be ignored) Expected behavoir is only line with error is ignired. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1821566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821566] [NEW] cron ignores whole crontab if one line has error
Public bug reported: Ubuntu 18.04. Let's create error entry in /etc/crontab: 00 09 * * 4 1 root /usr/local/bin/geoiprenew.sh restart cron systemctl restart cron мар 25 10:29:02 ovpn1 cron[12403]: Error: bad username; while reading /etc/crontab мар 25 10:29:02 ovpn1 cron[12403]: (*system*) ERROR (Syntax error, this crontab file will be ignored) Expected behavoir is only line with error is ignired. Thank you! ** Affects: cron (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1821566 Title: cron ignores whole crontab if one line has error Status in cron package in Ubuntu: New Bug description: Ubuntu 18.04. Let's create error entry in /etc/crontab: 00 09 * * 4 1 root /usr/local/bin/geoiprenew.sh restart cron systemctl restart cron мар 25 10:29:02 ovpn1 cron[12403]: Error: bad username; while reading /etc/crontab мар 25 10:29:02 ovpn1 cron[12403]: (*system*) ERROR (Syntax error, this crontab file will be ignored) Expected behavoir is only line with error is ignired. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1821566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768416] [NEW] ath9k_htc Reason: 3=DEAUTH_LEAVING
Public bug reported: After upgrade from 16.04 to 18.04 I can't use wifi. It is ath9k_htc usb. I got error Reason: 3=DEAUTH_LEAVING I used workaround from https://unix.stackexchange.com/questions/386925/aborting-authentication- by-local-choice-reason-3-deauth-leaving-when-trying ln -s /dev/null /etc/systemd/network/99-default.link And got it working, but, I think , this should be fixed. Thank you! ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1768416 Title: ath9k_htc Reason: 3=DEAUTH_LEAVING Status in network-manager package in Ubuntu: New Bug description: After upgrade from 16.04 to 18.04 I can't use wifi. It is ath9k_htc usb. I got error Reason: 3=DEAUTH_LEAVING I used workaround from https://unix.stackexchange.com/questions/386925/aborting- authentication-by-local-choice-reason-3-deauth-leaving-when-trying ln -s /dev/null /etc/systemd/network/99-default.link And got it working, but, I think , this should be fixed. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1768416/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700232] Re: aa-logprof ignores dbus access
:-( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1700232 Title: aa-logprof ignores dbus access Status in apparmor package in Ubuntu: Fix Released Bug description: [76401.788233] audit: type=1107 audit(1498111942.039:17): pid=507 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="Hello" mask="send" name="org.freedesktop.DBus" pid=4955 label="/usr/sbin/ejabberdctl//su" peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=? Is not recognized by aa-logprof . Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1700232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700232] Re: aa-logprof ignores dbus access
Will it be fixed in 16.04 LTS? Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1700232 Title: aa-logprof ignores dbus access Status in apparmor package in Ubuntu: Fix Released Bug description: [76401.788233] audit: type=1107 audit(1498111942.039:17): pid=507 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="Hello" mask="send" name="org.freedesktop.DBus" pid=4955 label="/usr/sbin/ejabberdctl//su" peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=? Is not recognized by aa-logprof . Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1700232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723907] Re: 16.04 server can't reboot
two other servers had uptime 56 days. also rebooted without problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1723907 Title: 16.04 server can't reboot Status in systemd package in Ubuntu: Incomplete Bug description: Hello! I run 5 (five) Ubuntu 16.04 VMs on Centos7 host, i.e. inside of kvm. After several months of uptime I can't shutdown or reboot any of this VMs- if I type reboot or shutdown then it runs forever... No error messages, nothing... Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1723907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723907] Re: 16.04 server can't reboot
OK, 59 days is not enough: root@jabber:~# uptime 13:30:35 up 59 days, 23:59, 1 user, load average: 0,01, 0,02, 0,00 root@jabber:~# sync root@jabber:~# sync root@jabber:~# reboot Connection to jabber closed by remote host. Connection to jabber closed. I.e. reboot is OK, will try tomorrow on 2 other servers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1723907 Title: 16.04 server can't reboot Status in systemd package in Ubuntu: Incomplete Bug description: Hello! I run 5 (five) Ubuntu 16.04 VMs on Centos7 host, i.e. inside of kvm. After several months of uptime I can't shutdown or reboot any of this VMs- if I type reboot or shutdown then it runs forever... No error messages, nothing... Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1723907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723907] Re: 16.04 server can't reboot
As I said - several months. Right now it is just days, because I rebooted them by "powering off" from virt-manager. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1723907 Title: 16.04 server can't reboot Status in systemd package in Ubuntu: Incomplete Bug description: Hello! I run 5 (five) Ubuntu 16.04 VMs on Centos7 host, i.e. inside of kvm. After several months of uptime I can't shutdown or reboot any of this VMs- if I type reboot or shutdown then it runs forever... No error messages, nothing... Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1723907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723907] Re: 16.04 server can't reboot
Hello! I don't see any specific in my setup, it is just Centos 7. VMs are created from virt-manager. Btw, other VM, namely Oracle Linux, which uses systemd too, can be rebooted without problems. And yes, reboot works after 2-3 days uptime. And I don't think this is VM related, I just mentioned this to make sure it is not hardware related. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1723907 Title: 16.04 server can't reboot Status in systemd package in Ubuntu: Incomplete Bug description: Hello! I run 5 (five) Ubuntu 16.04 VMs on Centos7 host, i.e. inside of kvm. After several months of uptime I can't shutdown or reboot any of this VMs- if I type reboot or shutdown then it runs forever... No error messages, nothing... Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1723907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723907] [NEW] 16.04 server can't reboot
Public bug reported: Hello! I run 5 (five) Ubuntu 16.04 VMs on Centos7 host, i.e. inside of kvm. After several months of uptime I can't shutdown or reboot any of this VMs- if I type reboot or shutdown then it runs forever... No error messages, nothing... Thank you! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1723907 Title: 16.04 server can't reboot Status in systemd package in Ubuntu: New Bug description: Hello! I run 5 (five) Ubuntu 16.04 VMs on Centos7 host, i.e. inside of kvm. After several months of uptime I can't shutdown or reboot any of this VMs- if I type reboot or shutdown then it runs forever... No error messages, nothing... Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1723907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1188475] Re: ldap group doesn't work
About comment 6- in my opinion this highly depends on your implementation and
policy.
I work for not so large company, I'd say small - just about 4200 employers-, so
our policy can be wrong - it says not show users their rights, i.e. intruder
needs to try ;-)
>From another point of view- ldap connection credentials are supplied in
>config, so application have to use them, not others.
Your point of view is right too- as I said this depends on your policy.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
Status in Cyrus-sasl2:
Fix Released
Status in cyrus-sasl2 package in Ubuntu:
Confirmed
Bug description:
Hello!
I wrote almost the same mail to sasl mail list, but , I guess, it is
good to fix in 12.04...
This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04
Problem is that after user is authentificated with ldap bind , ldap
connection for checking user in group ( lak_group_member function )
is made with this user's bind, not bind parameters from config file.
User can not ( and have not in our case- I don't know why , but this is
not real problem ) have access to ldap groups.
And so, authentication is always fail.
I added unbind and anonymous bind ( enough in our case):
/var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig
lak.c
--- lak.c.orig2013-06-07 09:15:20.098788278 +0400
+++ lak.c2013-06-07 09:22:31.504774185 +0400
@@ -1342,6 +1342,10 @@
if (rc != LAK_OK)
goto done;
+lak_unbind (lak );
+rc = lak_bind(lak, "");
+
+
rc = ldap_search_st(lak->ld, group_search_base,
lak->conf->group_scope, group_filter, (char **) group_attrs, 0,
&(lak->conf->timeout), &res);
switch (rc) {
case LDAP_SUCCESS:
but, it is obvoius that rebind should be done with credintials from
config, but this is over my head :-(
Could you, please, fix this bug correctly?
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1188475/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1188475] Re: ldap group doesn't work
Hello!
I'm not Debian user, so I don't think this is good idea to open bug report for
product I don't use.
And I don't see any reasons why Ubuntu can't provide support for it's packages
and have to rely on Debian :-(
Anyway, fix will be in next release, so it will work out of box in 20.04
:-D
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
Status in Cyrus-sasl2:
Fix Released
Status in cyrus-sasl2 package in Ubuntu:
Confirmed
Bug description:
Hello!
I wrote almost the same mail to sasl mail list, but , I guess, it is
good to fix in 12.04...
This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04
Problem is that after user is authentificated with ldap bind , ldap
connection for checking user in group ( lak_group_member function )
is made with this user's bind, not bind parameters from config file.
User can not ( and have not in our case- I don't know why , but this is
not real problem ) have access to ldap groups.
And so, authentication is always fail.
I added unbind and anonymous bind ( enough in our case):
/var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig
lak.c
--- lak.c.orig2013-06-07 09:15:20.098788278 +0400
+++ lak.c2013-06-07 09:22:31.504774185 +0400
@@ -1342,6 +1342,10 @@
if (rc != LAK_OK)
goto done;
+lak_unbind (lak );
+rc = lak_bind(lak, "");
+
+
rc = ldap_search_st(lak->ld, group_search_base,
lak->conf->group_scope, group_filter, (char **) group_attrs, 0,
&(lak->conf->timeout), &res);
switch (rc) {
case LDAP_SUCCESS:
but, it is obvoius that rebind should be done with credintials from
config, but this is over my head :-(
Could you, please, fix this bug correctly?
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1188475/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1188475] Re: ldap group doesn't work
Why invalid?
Please get into ubuntu current code :-)
https://github.com/cyrusimap/cyrus-sasl/pull/428
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
Status in cyrus-sasl2 package in Ubuntu:
Confirmed
Bug description:
Hello!
I wrote almost the same mail to sasl mail list, but , I guess, it is
good to fix in 12.04...
This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04
Problem is that after user is authentificated with ldap bind , ldap
connection for checking user in group ( lak_group_member function )
is made with this user's bind, not bind parameters from config file.
User can not ( and have not in our case- I don't know why , but this is
not real problem ) have access to ldap groups.
And so, authentication is always fail.
I added unbind and anonymous bind ( enough in our case):
/var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig
lak.c
--- lak.c.orig2013-06-07 09:15:20.098788278 +0400
+++ lak.c2013-06-07 09:22:31.504774185 +0400
@@ -1342,6 +1342,10 @@
if (rc != LAK_OK)
goto done;
+lak_unbind (lak );
+rc = lak_bind(lak, "");
+
+
rc = ldap_search_st(lak->ld, group_search_base,
lak->conf->group_scope, group_filter, (char **) group_attrs, 0,
&(lak->conf->timeout), &res);
switch (rc) {
case LDAP_SUCCESS:
but, it is obvoius that rebind should be done with credintials from
config, but this is over my head :-(
Could you, please, fix this bug correctly?
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1188475/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700231] Re: 16.04 , apparmor denies dbus communications even with flags=(complain)
Well, may be this is not bug, but expected behaviour.
/etc/apparmor.d/usr.sbin.ejabberdctl
contains
/usr/sbin/ejabberdctl {
profile su {
...
}
}
I.e. there is profile su inside.
If I add:
/usr/sbin/ejabberdctl flags=(complain) {
it doesn't changeprofile su behaviour.
I have to add
profile su flags=(complain) {
then it works.
Problem here is that it breaks idea of scope, because profile su is _inside_,
but does not use flags from outside.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1700231
Title:
16.04 , apparmor denies dbus communications even with flags=(complain)
Status in apparmor package in Ubuntu:
Incomplete
Bug description:
While investigating
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699681
found that apparmor denies dbus communications even with flags=(complain) ,
which is wrong behaviour.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1700231/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700232] Re: aa-logprof ignores dbus access
btw, it is 2.10.95-0ubuntu2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1700232 Title: aa-logprof ignores dbus access Status in apparmor package in Ubuntu: New Bug description: [76401.788233] audit: type=1107 audit(1498111942.039:17): pid=507 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="Hello" mask="send" name="org.freedesktop.DBus" pid=4955 label="/usr/sbin/ejabberdctl//su" peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=? Is not recognized by aa-logprof . Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1700232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700232] Re: aa-logprof ignores dbus access
OK, then Ubuntu 16.04 needs an update. Note: I use Ubuntu, so this is why here is tag apparmor (Ubuntu). Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1700232 Title: aa-logprof ignores dbus access Status in apparmor package in Ubuntu: New Bug description: [76401.788233] audit: type=1107 audit(1498111942.039:17): pid=507 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="Hello" mask="send" name="org.freedesktop.DBus" pid=4955 label="/usr/sbin/ejabberdctl//su" peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=? Is not recognized by aa-logprof . Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1700232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700231] [NEW] 16.04 , apparmor denies dbus communications even with flags=(complain)
Public bug reported: While investigating https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699681 found that apparmor denies dbus communications even with flags=(complain) , which is wrong behaviour. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1700231 Title: 16.04 , apparmor denies dbus communications even with flags=(complain) Status in apparmor package in Ubuntu: New Bug description: While investigating https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699681 found that apparmor denies dbus communications even with flags=(complain) , which is wrong behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1700231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700232] [NEW] aa-logprof ignores dbus access
Public bug reported: [76401.788233] audit: type=1107 audit(1498111942.039:17): pid=507 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="Hello" mask="send" name="org.freedesktop.DBus" pid=4955 label="/usr/sbin/ejabberdctl//su" peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=? Is not recognized by aa-logprof . Ubuntu 16.04 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1700232 Title: aa-logprof ignores dbus access Status in apparmor package in Ubuntu: New Bug description: [76401.788233] audit: type=1107 audit(1498111942.039:17): pid=507 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="Hello" mask="send" name="org.freedesktop.DBus" pid=4955 label="/usr/sbin/ejabberdctl//su" peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=? Is not recognized by aa-logprof . Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1700232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699672] Re: systemctl status Failed to read server status: Connection timed out
And I have systemd-logind[505]: Failed to abandon session scope: Connection timed out in log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1699672 Title: systemctl status Failed to read server status: Connection timed out Status in systemd package in Ubuntu: New Bug description: I run 5 Ubuntu 16.04 as kvm VMs on centos 7. Yesterday, after installing updates, I can't reboot them, because systemd connection timeout. After reboot systemctl status worked fine, but today I get on one of these servers: systemctl status Failed to read server status: Connection timed out I guess after some time I'll have this on all of them. Looks like bug. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699672] Re: systemctl status Failed to read server status: Connection timed out
btw, solution mentioned here https://github.com/systemd/systemd/issues/1961 to remove session dirs doesnt help ** Bug watch added: github.com/systemd/systemd/issues #1961 https://github.com/systemd/systemd/issues/1961 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1699672 Title: systemctl status Failed to read server status: Connection timed out Status in systemd package in Ubuntu: New Bug description: I run 5 Ubuntu 16.04 as kvm VMs on centos 7. Yesterday, after installing updates, I can't reboot them, because systemd connection timeout. After reboot systemctl status worked fine, but today I get on one of these servers: systemctl status Failed to read server status: Connection timed out I guess after some time I'll have this on all of them. Looks like bug. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699672] [NEW] systemctl status Failed to read server status: Connection timed out
Public bug reported: I run 5 Ubuntu 16.04 as kvm VMs on centos 7. Yesterday, after installing updates, I can't reboot them, because systemd connection timeout. After reboot systemctl status worked fine, but today I get on one of these servers: systemctl status Failed to read server status: Connection timed out I guess after some time I'll have this on all of them. Looks like bug. Thank you! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1699672 Title: systemctl status Failed to read server status: Connection timed out Status in systemd package in Ubuntu: New Bug description: I run 5 Ubuntu 16.04 as kvm VMs on centos 7. Yesterday, after installing updates, I can't reboot them, because systemd connection timeout. After reboot systemctl status worked fine, but today I get on one of these servers: systemctl status Failed to read server status: Connection timed out I guess after some time I'll have this on all of them. Looks like bug. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1188475] Re: ldap group doesn't work
Hello!
I created pull request in cyrus sasl repository
https://github.com/cyrusimap/cyrus-sasl/pull/428
If you don't patch debian packages, then why debian should do this,
let cyrus developers fix it ;-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
Status in cyrus-sasl2 package in Ubuntu:
Triaged
Bug description:
Hello!
I wrote almost the same mail to sasl mail list, but , I guess, it is
good to fix in 12.04...
This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04
Problem is that after user is authentificated with ldap bind , ldap
connection for checking user in group ( lak_group_member function )
is made with this user's bind, not bind parameters from config file.
User can not ( and have not in our case- I don't know why , but this is
not real problem ) have access to ldap groups.
And so, authentication is always fail.
I added unbind and anonymous bind ( enough in our case):
/var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig
lak.c
--- lak.c.orig2013-06-07 09:15:20.098788278 +0400
+++ lak.c2013-06-07 09:22:31.504774185 +0400
@@ -1342,6 +1342,10 @@
if (rc != LAK_OK)
goto done;
+lak_unbind (lak );
+rc = lak_bind(lak, "");
+
+
rc = ldap_search_st(lak->ld, group_search_base,
lak->conf->group_scope, group_filter, (char **) group_attrs, 0,
&(lak->conf->timeout), &res);
switch (rc) {
case LDAP_SUCCESS:
but, it is obvoius that rebind should be done with credintials from
config, but this is over my head :-(
Could you, please, fix this bug correctly?
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1188475/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1188475] Re: ldap group doesn't work
Hello!
Still have this bug on 16.04.
Have to use my old patch, because there is the same bug...
Why???!!!
:-(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
Status in cyrus-sasl2 package in Ubuntu:
New
Bug description:
Hello!
I wrote almost the same mail to sasl mail list, but , I guess, it is
good to fix in 12.04...
This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04
Problem is that after user is authentificated with ldap bind , ldap
connection for checking user in group ( lak_group_member function )
is made with this user's bind, not bind parameters from config file.
User can not ( and have not in our case- I don't know why , but this is
not real problem ) have access to ldap groups.
And so, authentication is always fail.
I added unbind and anonymous bind ( enough in our case):
/var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig
lak.c
--- lak.c.orig2013-06-07 09:15:20.098788278 +0400
+++ lak.c2013-06-07 09:22:31.504774185 +0400
@@ -1342,6 +1342,10 @@
if (rc != LAK_OK)
goto done;
+lak_unbind (lak );
+rc = lak_bind(lak, "");
+
+
rc = ldap_search_st(lak->ld, group_search_base,
lak->conf->group_scope, group_filter, (char **) group_attrs, 0,
&(lak->conf->timeout), &res);
switch (rc) {
case LDAP_SUCCESS:
but, it is obvoius that rebind should be done with credintials from
config, but this is over my head :-(
Could you, please, fix this bug correctly?
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1188475/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669254] [NEW] 16.04 apparmor, aa-logprof and log files
Public bug reported: First of all I'd like to say that by default /etc/apparmor/logprof.conf contains logfiles = /var/log/audit/audit.log /var/log/syslog /var/log/messages from which only syslog exists in 16.04. And there is kern.log , which seems to be better suited for reading apparmor kernel messages. Why not change this in distribution? Thank you! ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1669254 Title: 16.04 apparmor, aa-logprof and log files Status in apparmor package in Ubuntu: New Bug description: First of all I'd like to say that by default /etc/apparmor/logprof.conf contains logfiles = /var/log/audit/audit.log /var/log/syslog /var/log/messages from which only syslog exists in 16.04. And there is kern.log , which seems to be better suited for reading apparmor kernel messages. Why not change this in distribution? Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1669254/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629203] Re: aa-logprof does not include #include in profiles
No, it was far before..., SLES8 or 9, I reported bug in xfs filesystem to Novell which resulted in kernel crash, and to SGI, SGI fixed it :-), I patched SUSE's kernel with SGI patch, compiled, and I informed Novell that bug is fixed... Then, after several weeks, Novell updated kernel- and- surprise!- bug is here. Why? they I claimed I did not waited for their binary kernel with fix to test, so fix was not included in newer kernels :-D And only after I tested their binaries they included fix... At least this is how I remember this - it was more then 10 years ago. After that I decided that I have no reasons to use SLES , because it became too "enterprise" for me , i.e. too much useless efforts to use it in real life ;-) >declare this bugreport as user error - you broke it No, I didn't, not me shipped empty profile in mariadb-server package :-P > It would also mean that aa-logprof must know where those variables are > defined, and ask the user about including this file in the global area. Well, when aa-logprof asks me about including some abstraction, it may know that this abstraction needs some includes, right? May be we need some dependency mechanism here? I.e. info in include which other includes it needs? Or, may be, just simple- if aa-logprof user decided to add standard include by aa-logprof advice, aa-logprof can also add tunables/global, if >this will annoy people who for some reason don't want it then aa-logrof may just warn about this, but, anyway including abstraction without tunables/global will result in broken profile... Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1629203 Title: aa-logprof does not include #include in profiles Status in AppArmor: New Status in apparmor package in Ubuntu: New Bug description: Ubuntu 16.04, fresh profile, systemctl reload apparmor says errors: сен 30 11:24:33 inetgw1 apparmor[13771]: Found reference to variable PROC, but is never declared This is because there is no #include in profile. Question here is- why? Why aa-logprof did not add it while adding includes? Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1629203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629203] Re: aa-logprof does not include #include in profiles
OK, here it is
1. sudo apt-get install mariadb-server
2. /usr/sbin/mysqld {
}
3. systemctl reload apparmor
4. systemctl start mysql
5. sudo aa-logprof
Reading log entries from /var/log/syslog.
Updating AppArmor profiles in /etc/apparmor.d.
Enforce-mode changes:
Profile: /usr/sbin/mysqld
Path: /etc/ld.so.cache
Mode: r
Severity: 1
1 - #include
2 - #include
3 - #include
4 - #include
5 - #include
6 - #include
7 - #include
8 - #include
9 - #include
10 - #include
11 - #include
[12 - /etc/ld.so.cache]
(A)llow / [(D)eny] / (I)gnore / (G)lob / Glob with (E)xtension / (N)ew /
Abo(r)t / (F)inish / (M)ore
Profile: /usr/sbin/mysqld
Path: /etc/ld.so.cache
Mode: r
Severity: 1
[1 - #include ]
2 - #include
3 - #include
4 - #include
5 - #include
6 - #include
7 - #include
8 - #include
9 - #include
10 - #include
11 - #include
12 - /etc/ld.so.cache
(A)llow / [(D)eny] / (I)gnore / (G)lob / Glob with (E)xtension / (N)ew /
Abo(r)t / (F)inish / (M)ore
Adding #include to profile.
= Changed Local Profiles =
The following local profiles were changed. Would you like to save them?
[1 - /usr/sbin/mysqld]
(S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes b/w
(C)lean profiles / Abo(r)t
Writing updated profile for /usr/sbin/mysqld.
6.
sudo systemctl reload apparmor
Job for apparmor.service failed because the control process exited with error
code. See "systemctl status apparmor.service" and "journalctl -xe" for details.
cat usr.sbin.mysqld
# Last Modified: Sun Oct 2 18:04:36 2016
# This file is intensionally empty to disable apparmor by default for newer
# versions of MariaDB, while providing seamless upgrade from older versions
# and from mysql, where apparmor is used.
#
# By default, we do not want to have any apparmor profile for the MariaDB
# server. It does not provide much useful functionality/security, and causes
# several problems for users who often are not even aware that apparmor
# exists and runs on their system.
#
# Users can modify and maintain their own profile, and in this case it will
# be used.
#
# When upgrading from previous version, users who modified the profile
# will be promptet to keep or discard it, while for default installs
# we will automatically disable the profile.
/usr/sbin/mysqld {
#include
}
If
>In theory, the tunables/global include should always be added
it is not added by aa-logprof...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1629203
Title:
aa-logprof does not include #include in profiles
Status in apparmor package in Ubuntu:
New
Bug description:
Ubuntu 16.04, fresh profile,
systemctl reload apparmor
says errors:
сен 30 11:24:33 inetgw1 apparmor[13771]: Found reference to variable PROC,
but is never declared
This is because there is no #include
in profile.
Question here is- why? Why aa-logprof did not add it while adding
includes?
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1629203/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629203] Re: aa-logprof does not include #include in profiles
well, about funny, I was first SLES user in my country, this is why I have such nickname ;-) but I don't use SUSE anylonger, since it was bought by Novell it became nightmare. Anyway, I'll try to reproduce it tomorrow and I'll provide you all step- by-step info, or , may be even today- I use 16.04 at home desktop, if I'll have time. About mariadb profile in 16.04, well, it is installed from Ubuntu repo and it contains just: cat /etc/apparmor.d/usr.sbin.mysqld # This file is intensionally empty to disable apparmor by default for newer # versions of MariaDB, while providing seamless upgrade from older versions # and from mysql, where apparmor is used. # # By default, we do not want to have any apparmor profile for the MariaDB # server. It does not provide much useful functionality/security, and causes # several problems for users who often are not even aware that apparmor # exists and runs on their system. # # Users can modify and maintain their own profile, and in this case it will # be used. # # When upgrading from previous version, users who modified the profile # will be promptet to keep or discard it, while for default installs # we will automatically disable the profile. That's simple :-D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1629203 Title: aa-logprof does not include #include in profiles Status in apparmor package in Ubuntu: New Bug description: Ubuntu 16.04, fresh profile, systemctl reload apparmor says errors: сен 30 11:24:33 inetgw1 apparmor[13771]: Found reference to variable PROC, but is never declared This is because there is no #include in profile. Question here is- why? Why aa-logprof did not add it while adding includes? Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1629203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629203] Re: aa-logprof does not include #include in profiles
I created profile for mariadb , which is empty in Ubuntu 16.04 by using aa-logprof, just added path and complain flag to it, and, after aa-logprof suggested to include includes like abstractions/base I got above error. I guess this is quite easy to reproduce... Never had such problem before, so it I spent quite long time to find where problem is, so, I think, automation tools like aa-logprof have to generate working profiles. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1629203 Title: aa-logprof does not include #include in profiles Status in apparmor package in Ubuntu: New Bug description: Ubuntu 16.04, fresh profile, systemctl reload apparmor says errors: сен 30 11:24:33 inetgw1 apparmor[13771]: Found reference to variable PROC, but is never declared This is because there is no #include in profile. Question here is- why? Why aa-logprof did not add it while adding includes? Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1629203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629203] Re: aa-logprof does not include #include in profiles
oops, forget to write: and this aa-logprof behavior is , obviously, wrong and should be fixed, imho. thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1629203 Title: aa-logprof does not include #include in profiles Status in apparmor package in Ubuntu: New Bug description: Ubuntu 16.04, fresh profile, systemctl reload apparmor says errors: сен 30 11:24:33 inetgw1 apparmor[13771]: Found reference to variable PROC, but is never declared This is because there is no #include in profile. Question here is- why? Why aa-logprof did not add it while adding includes? Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1629203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629203] [NEW] aa-logprof does not include #include in profiles
Public bug reported: Ubuntu 16.04, fresh profile, systemctl reload apparmor says errors: сен 30 11:24:33 inetgw1 apparmor[13771]: Found reference to variable PROC, but is never declared This is because there is no #include in profile. Question here is- why? Why aa-logprof did not add it while adding includes? Thank you! ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1629203 Title: aa-logprof does not include #include in profiles Status in apparmor package in Ubuntu: New Bug description: Ubuntu 16.04, fresh profile, systemctl reload apparmor says errors: сен 30 11:24:33 inetgw1 apparmor[13771]: Found reference to variable PROC, but is never declared This is because there is no #include in profile. Question here is- why? Why aa-logprof did not add it while adding includes? Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1629203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1468103] Re: rc.local runs earlier than cloud-init.service
>the notion of "the last thing during boot" is not well-defined with a
partially ordered and parallel init system like systemd or upstart (or
even sysvinit+startpar).
systemd needs to be fixed then.
because rc.local worked well with upstart.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1468103
Title:
rc.local runs earlier than cloud-init.service
Status in cloud-init package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Invalid
Bug description:
per https://www.debian.org/doc/manuals/debian-faq/ch-customizing.en.html
| The rc.local script is executed at the end of each multiuser runlevel.
Generally speaking people expect rc.local to be run as "the last thing
in boot".
currently it is being run by systemd much earlier.
Provided in the attached is user-data that tells cloud-init to write a
file in /usr/local/bin/rc-local-message and edit set rc.local to
execute it.
On current wily, under most scenarios the script will not be executed
as rc.local will most likely run before the cloud-init service has a
chance to update /etc/rc.local.
To reproduce:
a.) launch an instance with provided user-data
Expected behavior would be:
1. /run/rc-local-message exists with contents of /proc/uptime at the time
it was run
2. /rc-local-message.mark exists with the number of times this script has
been run ('1' after first boot)
3. /var/log/rc-local-message.log exists with a message like:
[/var/log/rc-local-message.log] === successful boot 1
4. console log should also have message like in 3 with '/dev/console'
4 is broken as rc.local output is not sent to console as reported
separately at bug 1468102.
Related bugs:
* bug 1468102: rc.local output does not go to console
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: systemd 220-7ubuntu1
ProcVersionSignature: User Name 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
Date: Tue Jun 23 20:21:50 2015
Ec2AMI: ami-0434
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-0002
Ec2Ramdisk: ari-0002
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: OpenStack Foundation OpenStack Nova
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
SourcePackage: systemd
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2014.1.4:cvnBochs:ct1:cvr:
dmi.product.name: OpenStack Nova
dmi.product.version: 2014.1.4
dmi.sys.vendor: OpenStack Foundation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1468103/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599446] [NEW] 16.04, wrong units start order
Public bug reported: Hello! squid uses ldap and mysql for authorization , so I added them to squid dependencies: ### BEGIN INIT INFO # Provides: squid # Required-Start:$network $remote_fs $syslog mysql slapd After=systemd-journald.socket basic.target systemd-journald-dev-log.socket mysql.service remote-fs.target network-online.target nss-lookup.target system.slice sysinit.target slapd.service And symlinks are created in right order: S03slapd S04mysql S05squid But really squid is started before mysql (mariadb) and slapd are started: journalctl -u squid -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:44:41 SAMT. -- июл 06 13:10:31 inetgw2 systemd[1]: Starting LSB: Squid HTTP Proxy version 3.x... journalctl -u slapd -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:45:36 SAMT. -- июл 06 13:10:42 inetgw2 systemd[1]: Starting LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)... journalctl -u mysql -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:45:46 SAMT. -- июл 06 13:10:42 inetgw2 systemd[1]: Starting LSB: Start and stop the mysql database server daemon... июл 06 13:10:43 inetgw2 mysql[2647]: * Starting MariaDB database server mysqld i.e. real start order is: sqiud slapd mysql Expected result is folowing slapd mysql squid ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1599446 Title: 16.04, wrong units start order Status in systemd package in Ubuntu: New Bug description: Hello! squid uses ldap and mysql for authorization , so I added them to squid dependencies: ### BEGIN INIT INFO # Provides: squid # Required-Start:$network $remote_fs $syslog mysql slapd After=systemd-journald.socket basic.target systemd-journald-dev-log.socket mysql.service remote-fs.target network-online.target nss-lookup.target system.slice sysinit.target slapd.service And symlinks are created in right order: S03slapd S04mysql S05squid But really squid is started before mysql (mariadb) and slapd are started: journalctl -u squid -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:44:41 SAMT. -- июл 06 13:10:31 inetgw2 systemd[1]: Starting LSB: Squid HTTP Proxy version 3.x... journalctl -u slapd -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:45:36 SAMT. -- июл 06 13:10:42 inetgw2 systemd[1]: Starting LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)... journalctl -u mysql -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:45:46 SAMT. -- июл 06 13:10:42 inetgw2 systemd[1]: Starting LSB: Start and stop the mysql database server daemon... июл 06 13:10:43 inetgw2 mysql[2647]: * Starting MariaDB database server mysqld i.e. real start order is: sqiud slapd mysql Expected result is folowing slapd mysql squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1599446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576215] Re: Network Manager regularly thinks my wifi is a wired device
*** This bug is a duplicate of bug 1574347 *** https://bugs.launchpad.net/bugs/1574347 Just reported the same bug, i.e. dup. Looks like current network manager in 16.04 contains "fix" from above, but I still have this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576215 Title: Network Manager regularly thinks my wifi is a wired device Status in network-manager package in Ubuntu: Confirmed Bug description: When I boot up my network doesn't automatically connect. I instead see when I click the network manager applet that it's got no Wifi devices listed. It thinks my wireless card is an ethernet device. This isn't true and I have no ethernet devices in my system. When this situation happens if I issue /etc/init.d/network-manager restart it comes back up thinking it's a wireless device and happily associates with my saved SSID. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 28 09:03:13 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160406-0 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-13 (14 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160406-07:32 IpRoute: NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp58s0 ethernet connecting (getting IP configuration) /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 1c8c4cab-09d7-4a42-bfc4-aed14caf6a46 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598662] [NEW] network manager recognises usb wifi connection as wired usb sometimes
Public bug reported: Hello! I have usb wifi card on atheros chipset, namely ath9k. Sometimes (not very often) network manager thinks it is not wifi, but wired connection, and, definitely, does not connects. Workaround are- remove and insert wifi card or rmmod ath9k_htc modprobe ath9k_htc Not hard, but annoying... Thank you! ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1598662 Title: network manager recognises usb wifi connection as wired usb sometimes Status in network-manager package in Ubuntu: New Bug description: Hello! I have usb wifi card on atheros chipset, namely ath9k. Sometimes (not very often) network manager thinks it is not wifi, but wired connection, and, definitely, does not connects. Workaround are- remove and insert wifi card or rmmod ath9k_htc modprobe ath9k_htc Not hard, but annoying... Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1598662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
OK, I'm trying reboot and reboot and now I think this is kernel bug and it is multipath related... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets Status in systemd package in Ubuntu: Incomplete Bug description: I have 4 servers running the latest 16.04 updates from the development branch (as of right now). Each server is connected to NetApp storage using iscsi software initiator. There are a total of 56 volumes spread across two NetApp arrays. Each volume has 4 paths available to it which are being managed by device mapper. While logged into the iscsi sessions all I have to do is reboot the server and I get a hang. I see a message that says: "Reached target Shutdown" followed by "systemd-shutdown[1]: Failed to finalize DM devices, ignoring" and then I see 8 lines that say: "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" NOTE: the actual values of the *'s differ for each line above. This seems like a bug somewhere but I am unaware of any additional logging that I could turn on to pinpoint the problem. Note I also have similar setups that are not doing iscsi and they don't have this problem. Here is a screenshot of what I see on the shell when I try to reboot: https://www.dropbox.com/s/93mv7cj8asspcpa/ShutdownCapture.JPG?dl=0 This is being tracked in NetApp bug tracker CQ number 860251. If I log out of all iscsi sessions before rebooting then I do not experience the hang: iscsiadm -m node -U all We are wondering if this could be some kind of shutdown ordering problem. Like the network devices have already disappeared and then iscsi tries to perform some operation (hence the ping timeouts). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584629] [NEW] Failed to start LSB: Load O2CB cluster services at system boot.
Public bug reported: Ubuntu 16.04. Sometimes (not every boot) o2cb failed to start: systemctl status o2cb ● o2cb.service - LSB: Load O2CB cluster services at system boot. Loaded: loaded (/etc/init.d/o2cb; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Пн 2016-05-23 11:46:43 SAMT; 2min 12s ago Docs: man:systemd-sysv-generator(8) Process: 1526 ExecStart=/etc/init.d/o2cb start (code=exited, status=1/FAILURE) май 23 11:46:43 inetgw1 systemd[1]: Starting LSB: Load O2CB cluster services at system boot май 23 11:46:43 inetgw1 o2cb[1526]: Loading filesystem "configfs": OK май 23 11:46:43 inetgw1 o2cb[1526]: Mounting configfs filesystem at /sys/kernel/config: mount: configfs is already май 23 11:46:43 inetgw1 o2cb[1526]:configfs is already mounted on /sys/kernel/config май 23 11:46:43 inetgw1 o2cb[1526]: Unable to mount configfs filesystem май 23 11:46:43 inetgw1 o2cb[1526]: Failed май 23 11:46:43 inetgw1 systemd[1]: o2cb.service: Control process exited, code=exited status=1 май 23 11:46:43 inetgw1 systemd[1]: Failed to start LSB: Load O2CB cluster services at system boot.. май 23 11:46:43 inetgw1 systemd[1]: o2cb.service: Unit entered failed state. май 23 11:46:43 inetgw1 systemd[1]: o2cb.service: Failed with result 'exit-code'. next try is successful: systemctl status o2cb ● o2cb.service - LSB: Load O2CB cluster services at system boot. Loaded: loaded (/etc/init.d/o2cb; bad; vendor preset: enabled) Active: active (exited) since Пн 2016-05-23 11:49:07 SAMT; 1s ago Docs: man:systemd-sysv-generator(8) Process: 2101 ExecStart=/etc/init.d/o2cb start (code=exited, status=0/SUCCESS) май 23 11:49:07 inetgw1 systemd[1]: Starting LSB: Load O2CB cluster services at system boot май 23 11:49:07 inetgw1 o2cb[2101]: Loading stack plugin "o2cb": OK май 23 11:49:07 inetgw1 o2cb[2101]: Loading filesystem "ocfs2_dlmfs": OK май 23 11:49:07 inetgw1 o2cb[2101]: Mounting ocfs2_dlmfs filesystem at /dlm: OK май 23 11:49:07 inetgw1 o2cb[2101]: Setting cluster stack "o2cb": OK май 23 11:49:07 inetgw1 o2cb[2101]: Starting O2CB cluster inetgw: OK май 23 11:49:07 inetgw1 systemd[1]: Started LSB: Load O2CB cluster services at system boot.. I guess this is startup dependency problem. Thank you! ** Affects: ocfs2-tools (Ubuntu) Importance: Undecided Status: New ** Package changed: systemd (Ubuntu) => ocfs2-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1584629 Title: Failed to start LSB: Load O2CB cluster services at system boot. Status in ocfs2-tools package in Ubuntu: New Bug description: Ubuntu 16.04. Sometimes (not every boot) o2cb failed to start: systemctl status o2cb ● o2cb.service - LSB: Load O2CB cluster services at system boot. Loaded: loaded (/etc/init.d/o2cb; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Пн 2016-05-23 11:46:43 SAMT; 2min 12s ago Docs: man:systemd-sysv-generator(8) Process: 1526 ExecStart=/etc/init.d/o2cb start (code=exited, status=1/FAILURE) май 23 11:46:43 inetgw1 systemd[1]: Starting LSB: Load O2CB cluster services at system boot май 23 11:46:43 inetgw1 o2cb[1526]: Loading filesystem "configfs": OK май 23 11:46:43 inetgw1 o2cb[1526]: Mounting configfs filesystem at /sys/kernel/config: mount: configfs is already май 23 11:46:43 inetgw1 o2cb[1526]:configfs is already mounted on /sys/kernel/config май 23 11:46:43 inetgw1 o2cb[1526]: Unable to mount configfs filesystem май 23 11:46:43 inetgw1 o2cb[1526]: Failed май 23 11:46:43 inetgw1 systemd[1]: o2cb.service: Control process exited, code=exited status=1 май 23 11:46:43 inetgw1 systemd[1]: Failed to start LSB: Load O2CB cluster services at system boot.. май 23 11:46:43 inetgw1 systemd[1]: o2cb.service: Unit entered failed state. май 23 11:46:43 inetgw1 systemd[1]: o2cb.service: Failed with result 'exit-code'. next try is successful: systemctl status o2cb ● o2cb.service - LSB: Load O2CB cluster services at system boot. Loaded: loaded (/etc/init.d/o2cb; bad; vendor preset: enabled) Active: active (exited) since Пн 2016-05-23 11:49:07 SAMT; 1s ago Docs: man:systemd-sysv-generator(8) Process: 2101 ExecStart=/etc/init.d/o2cb start (code=exited, status=0/SUCCESS) май 23 11:49:07 inetgw1 systemd[1]: Starting LSB: Load O2CB cluster services at system boot май 23 11:49:07 inetgw1 o2cb[2101]: Loading stack plugin "o2cb": OK май 23 11:49:07 inetgw1 o2cb[2101]: Loading filesystem "ocfs2_dlmfs": OK май 23 11:49:07 inetgw1 o2cb[2101]: Mounting ocfs2_dlmfs filesystem at /dlm: OK май 23 11:49:07 inetgw1 o2cb[2101]: Setting cluster stack "o2cb": OK май 23 11:49:07 inetgw1 o2cb[2101]: Starting O2CB cluster inetgw: OK май 23 11:49:07 inetgw1 systemd[1]: Started LSB: Load O2CB cluster services at
[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
Because it is not always reproduced, I guess this is dependency problem. Looked into /etc/init.d/iscsid # Required-Stop: $network $local_fs sendsigs I guess we need $remote_fs here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets Status in systemd package in Ubuntu: Incomplete Bug description: I have 4 servers running the latest 16.04 updates from the development branch (as of right now). Each server is connected to NetApp storage using iscsi software initiator. There are a total of 56 volumes spread across two NetApp arrays. Each volume has 4 paths available to it which are being managed by device mapper. While logged into the iscsi sessions all I have to do is reboot the server and I get a hang. I see a message that says: "Reached target Shutdown" followed by "systemd-shutdown[1]: Failed to finalize DM devices, ignoring" and then I see 8 lines that say: "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" NOTE: the actual values of the *'s differ for each line above. This seems like a bug somewhere but I am unaware of any additional logging that I could turn on to pinpoint the problem. Note I also have similar setups that are not doing iscsi and they don't have this problem. Here is a screenshot of what I see on the shell when I try to reboot: https://www.dropbox.com/s/93mv7cj8asspcpa/ShutdownCapture.JPG?dl=0 This is being tracked in NetApp bug tracker CQ number 860251. If I log out of all iscsi sessions before rebooting then I do not experience the hang: iscsiadm -m node -U all We are wondering if this could be some kind of shutdown ordering problem. Like the network devices have already disappeared and then iscsi tries to perform some operation (hence the ping timeouts). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
>Looks like iscsi not always stopped before network interfaces are down. No, just reproduced this, iscsi was logged out... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets Status in systemd package in Ubuntu: Incomplete Bug description: I have 4 servers running the latest 16.04 updates from the development branch (as of right now). Each server is connected to NetApp storage using iscsi software initiator. There are a total of 56 volumes spread across two NetApp arrays. Each volume has 4 paths available to it which are being managed by device mapper. While logged into the iscsi sessions all I have to do is reboot the server and I get a hang. I see a message that says: "Reached target Shutdown" followed by "systemd-shutdown[1]: Failed to finalize DM devices, ignoring" and then I see 8 lines that say: "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" NOTE: the actual values of the *'s differ for each line above. This seems like a bug somewhere but I am unaware of any additional logging that I could turn on to pinpoint the problem. Note I also have similar setups that are not doing iscsi and they don't have this problem. Here is a screenshot of what I see on the shell when I try to reboot: https://www.dropbox.com/s/93mv7cj8asspcpa/ShutdownCapture.JPG?dl=0 This is being tracked in NetApp bug tracker CQ number 860251. If I log out of all iscsi sessions before rebooting then I do not experience the hang: iscsiadm -m node -U all We are wondering if this could be some kind of shutdown ordering problem. Like the network devices have already disappeared and then iscsi tries to perform some operation (hence the ping timeouts). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
I have the same problem , target is HPE MSA, and problem happens not every time, about in 1/5 of reboots- I run 16.04 , so I just tested... Looks like iscsi not always stopped before network interfaces are down. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets Status in systemd package in Ubuntu: Incomplete Bug description: I have 4 servers running the latest 16.04 updates from the development branch (as of right now). Each server is connected to NetApp storage using iscsi software initiator. There are a total of 56 volumes spread across two NetApp arrays. Each volume has 4 paths available to it which are being managed by device mapper. While logged into the iscsi sessions all I have to do is reboot the server and I get a hang. I see a message that says: "Reached target Shutdown" followed by "systemd-shutdown[1]: Failed to finalize DM devices, ignoring" and then I see 8 lines that say: "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" NOTE: the actual values of the *'s differ for each line above. This seems like a bug somewhere but I am unaware of any additional logging that I could turn on to pinpoint the problem. Note I also have similar setups that are not doing iscsi and they don't have this problem. Here is a screenshot of what I see on the shell when I try to reboot: https://www.dropbox.com/s/93mv7cj8asspcpa/ShutdownCapture.JPG?dl=0 This is being tracked in NetApp bug tracker CQ number 860251. If I log out of all iscsi sessions before rebooting then I do not experience the hang: iscsiadm -m node -U all We are wondering if this could be some kind of shutdown ordering problem. Like the network devices have already disappeared and then iscsi tries to perform some operation (hence the ping timeouts). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449842] [NEW] 15.04 doesn't recognize md raid on boot sometimes
Public bug reported: Hello! I have root on ssd, but home on md mirror and lvm over it, about 30% times I boot system systemd stops on searching for lvm volumes on md device, which, I guess it can't recognize, only pressing reset helps, it even can't reboot in alt-ctrl-del. I don't know how to look into boot logs of this systemd. If you'll tell me, I'll do next time. Thank you! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Package changed: ubiquity (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1449842 Title: 15.04 doesn't recognize md raid on boot sometimes Status in systemd package in Ubuntu: New Bug description: Hello! I have root on ssd, but home on md mirror and lvm over it, about 30% times I boot system systemd stops on searching for lvm volumes on md device, which, I guess it can't recognize, only pressing reset helps, it even can't reboot in alt-ctrl-del. I don't know how to look into boot logs of this systemd. If you'll tell me, I'll do next time. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
