[Bug 1738155] Re: Calling reboot or poweroff on a node-red snap is fail
Note: I also add plugs: "shutdown,core-support, process-control",but it is no longer effective. Thanks for any help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738155 Title: Calling reboot or poweroff on a node-red snap is fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1738155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738155] Re: Calling reboot or poweroff on a node-red snap is fail
Note: In the node-red snap to run "poweroff" is meaning: I post a flow into web(node-red client) to run "poweroff" command, but it is no longer effective. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738155 Title: Calling reboot or poweroff on a node-red snap is fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1738155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738155] [NEW] Calling reboot or poweroff on a node-red snap is fail
Public bug reported: OS:Ubuntu 16.04.3-amd64 when I run command "reboot" or "poweroff" in the node-red snap.It is no longer effective. my snapcraft.yaml: name: nodered version: 1.00 summary: A visual tool for wiring the Internet of Things description: Node-RED is a tool for wiring together hardware devices, APIs and online services in new and interesting ways. confinement: strict grade: stable apps: red: daemon: simple command: bin/launch plugs: - network-bind - network - network-observe parts: red: plugin: nodejs node-packages: - node-red - node-red-dashboard filesets: othermodules: [ -lib/node_modules/npm ] stage: [ $othermodules ] settings: plugin: dump source: settings filesets: settings: - . organize: start.sh : bin/launch snap: - . filesets: all: [ . ] when I run "poweroff" in the node-red snap, the syslog will show: Dec 14 04:07:34 zy-PR-VR4 bor.red[1905]: 14 Dec 04:07:34 - [info] [exec:command] poweroff Dec 14 04:07:34 zy-PR-VR4 kernel: [ 186.060923] kauditd_printk_skb: 25 callbacks suppressed Dec 14 04:07:34 zy-PR-VR4 kernel: [ 186.060927] audit: type=1400 audit(1513242454.177:329): apparmor="ALLOWED" operation="exec" profile="snap.bor.red" name="/bin/systemctl" pid=2453 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 ouid=0 target="snap.bor.red//null-/bin/systemctl" Dec 14 04:07:34 zy-PR-VR4 kernel: [ 186.061474] audit: type=1400 audit(1513242454.177:330): apparmor="ALLOWED" operation="file_inherit" profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none Dec 14 04:07:34 zy-PR-VR4 kernel: [ 186.061480] audit: type=1400 audit(1513242454.181:331): apparmor="ALLOWED" operation="file_inherit" profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl" Dec 14 04:07:34 zy-PR-VR4 kernel: [ 186.061483] audit: type=1400 audit(1513242454.181:332): apparmor="ALLOWED" operation="file_inherit" profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none Dec 14 04:07:34 zy-PR-VR4 kernel: [ 186.061487] audit: type=1400 audit(1513242454.181:333): apparmor="ALLOWED" operation="file_inherit" profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl" Dec 14 04:07:34 zy-PR-VR4 kernel: [ 186.061489] audit: type=1400 audit(1513242454.181:334): apparmor="ALLOWED" operation="file_inherit" profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none Dec 14 04:07:34 zy-PR-VR4 kernel: [ 186.061493] audit: type=1400 audit(1513242454.181:335): apparmor="ALLOWED" operation="file_inherit" profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl" Dec 14 04:07:34 zy-PR-VR4 kernel: [ 186.061496] audit: type=1400 audit(1513242454.181:336): apparmor="ALLOWED" operation="file_mmap" profile="snap.bor.red//null-/bin/systemctl" name="/bin/systemctl" pid=2453 comm="poweroff" requested_mask="rm" denied_mask="rm" fsuid=0 ouid=0 it looks the command is runing in the ubuntu 16.04.3, but it does not effective. --- when I run "dmesg" in the node-red snap, the syslog will show: bor.red[1905]: 14 Dec 04:10:02 - [info] [exec:command] dmesg Dec 14 04:10:02 zy-PR-VR4 kernel: [ 334.739205] kauditd_printk_skb: 90 callbacks suppressed Dec 14 04:10:02 zy-PR-VR4 kernel: [ 334.739207] audit: type=1400 audit(1513242602.837:463): apparmor="ALLOWED" operation="exec" profile="snap.bor.red" name="/bin/dmesg" pid=2552 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 ouid=0 target="snap.bor.red//null-/bin/dmesg" Dec 14 04:10:02 zy-PR-VR4 kernel: [ 334.739385] audit: type=1400 audit(1513242602.837:464): apparmor="ALLOWED" operation="file_inherit" profile="snap.bor.red//null-/bin/dmesg" pid=2552 comm="dmesg" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none Dec 14 04:10:02 zy-PR-VR4 kernel: [ 334.739387] audit: type=1400 audit(1513242602.837:465): apparmor="ALLOWED" operation="file_inherit" pr
[Bug 1591043] Re: xubuntu 16.04 on the haswell platform random restart
I fix the bug.. I only rm /dev/watchdog.. because when systemd receive the reboot signal, the systemd will call /dev/watchdog!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591043 Title: xubuntu 16.04 on the haswell platform random restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1591043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541450] Re: overlayroot read-only mode apparmor dhclient DENIED
I think I fix the issue. [ 22.126997] audit: type=1400 audit(1502779554.863:21): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 profile="/usr/lib/NetworkManager/nm-dhcp- helper" name="etc/ld.so.cache" You can find that the path which is looking for is relative path "name="etc/ld.so.cache"" , so I added attach_disconnected=/ to /etc/apparmor.d/sbin.dhclient. Sorry, it's been so long to feedback information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541450 Title: overlayroot read-only mode apparmor dhclient DENIED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1541450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1591043] Re: xubuntu 16.04 on the haswell platform random restart
I have two haswell pc，they have same issue,and the pc is no overclocked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591043 Title: xubuntu 16.04 on the haswell platform random restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1591043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1591043] Re: xubuntu 16.04 on the haswell platform random restart
The pc install win7 is no problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591043 Title: xubuntu 16.04 on the haswell platform random restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1591043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1591043] [NEW] xubuntu 16.04 on the haswell platform random restart
Public bug reported: Recently，I am use the xubuntu 16.04 on the haswell platform.I found my haswell's device random restart,when log in the xubuntu about 10 minutes,but it doesn't happen every time. The random reboot is similar to use the watchdog(directly power off and then automatically power on ). Now,I can't find any message about this issue. Any help will be grateful. ** Affects: xfdesktop4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591043 Title: xubuntu 16.04 on the haswell platform random restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1591043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541450] Re: overlayroot read-only mode apparmor dhclient DENIED
I find the relevant information about this issue.
"Unless specifically directed to connect the path,OR if in a chroot and
doing chroot relative paths and the path resolves to the namespace root
(would be connected outside of chroot) and specifically directed to
connect paths to namespace root."
"we could extend attach_disconnected so that we can define the attach
root. Eg, we can use profile foo (attach_disconnected=/mnt) {} such that
'/bin/bash' maps to '/mnt/bin/bash'."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541450
Title:
overlayroot read-only mode apparmor dhclient DENIED
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1541450/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541450] Re: overlayroot read-only mode apparmor dhclient DENIED
Dear Seth Arnold, Recently, I use this method " attach_disconnected " in the virtualbox.However, this method does not seem stable, often unable to get online. Best Regard, zy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541450 Title: overlayroot read-only mode apparmor dhclient DENIED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1541450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541450] Re: overlayroot read-only mode apparmor dhclient DENIED
Dear Seth Arnold, OH,It`s amazing.with the attach_disconnected, It is seem to work . It`s a good way to solve the trouble.Thank you for your answer. if I find some valuable thing about the trouble,I will be post here. Best Regard, zy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541450 Title: overlayroot read-only mode apparmor dhclient DENIED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1541450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541450] Re: overlayroot read-only mode apparmor dhclient DENIED
Following the above description. I have known a solution: ~$ sudo ln -s /etc/apparmor.d/sbin.dhclient /etc/apparmor.d/disable/ ~$ sudo /etc/init.d/apparmor reload ~$ sudo /etc/init.d/apparmor restart ~$ sudo /etc/init.d/networking restart ~$ sudo dhclient enp0s3 but I think this method is insecurity.I want to know Why did it happen?And How to fix it. I am using "ubuntu-15.10-desktop-amd64.iso" and "overlayroot". need any help Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541450 Title: overlayroot read-only mode apparmor dhclient DENIED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1541450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541450] [NEW] overlayroot read-only mode apparmor dhclient DENIED
Public bug reported: Dear all: I am using the overlayroot and working on read-only mode ,and then I can`t connect network and dhclient . cat /var/log/kernel.log below Feb 3 23:17:53 zy-VirtualBox kernel: [ 49.049090] audit: type=1400 audit(1454512673.592:44): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 profile="/sbin/dhclient" name="etc/ld.so.cache" pid=1217 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 3 23:17:53 zy-VirtualBox kernel: [ 49.049253] audit: type=1400 audit(1454512673.592:45): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 profile="/sbin/dhclient" name="lib/x86_64-linux-gnu/libirs- export.so.91.0.0" pid=1217 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 when I use "dhclient enp0s3",the error message is "dhclient: error while loading shared libraries: libirs-export.so.91: cannot stat shared object: Permission denied" need any help Thanks zy ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541450 Title: overlayroot read-only mode apparmor dhclient DENIED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1541450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
