[Bug 1902448] [NEW] systemd owfs.service wrong umount path
Public bug reported: owfs.service use wrong path to umount: ExecStop=/usr/bin/umount %t/owfs # ls -las /usr/bin/umount ls: cannot access '/usr/bin/umount': No such file or directory Correct path to umount is: /bin/umount Main effect of this bug - unable to stop owfs service correctly: # systemctl status owfs ● owfs.service - 1-wire filesystem FUSE mount Loaded: loaded (/lib/systemd/system/owfs.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-11-02 02:24:13 +07; 16s ago Docs: man:owfs(1) Main PID: 38938 (owfs) Tasks: 3 (limit: 9473) Memory: 1.4M CGroup: /system.slice/owfs.service └─38938 /usr/lib/owfs/owfs -c /etc/owfs.conf -c /etc/owfs.conf --allow_other /run/owfs ноя 02 02:24:13 fatman systemd[1]: Starting 1-wire filesystem FUSE mount... ноя 02 02:24:13 fatman systemd[1]: owfs.service: Supervising process 38938 which is not our child. We'll most likely not notice when it exits. ноя 02 02:24:13 fatman systemd[1]: Started 1-wire filesystem FUSE mount. # systemctl stop owfs # systemctl status owfs ● owfs.service - 1-wire filesystem FUSE mount Loaded: loaded (/lib/systemd/system/owfs.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2020-11-02 02:24:33 +07; 1s ago Docs: man:owfs(1) Process: 39004 ExecStop=/usr/bin/umount /run/owfs (code=exited, status=203/EXEC) Main PID: 38938 ноя 02 02:24:13 fatman systemd[1]: owfs.service: Supervising process 38938 which is not our child. We'll most likely not notice when it exits. ноя 02 02:24:13 fatman systemd[1]: Started 1-wire filesystem FUSE mount. ноя 02 02:24:33 fatman systemd[1]: Stopping 1-wire filesystem FUSE mount... ноя 02 02:24:33 fatman systemd[39004]: owfs.service: Failed to execute command: No such file or directory ноя 02 02:24:33 fatman systemd[39004]: owfs.service: Failed at step EXEC spawning /usr/bin/umount: No such file or directory ноя 02 02:24:33 fatman systemd[1]: owfs.service: Control process exited, code=exited, status=203/EXEC ноя 02 02:24:33 fatman systemd[1]: owfs.service: Killing process 38938 (owfs) with signal SIGKILL. ноя 02 02:24:33 fatman systemd[1]: owfs.service: Killing process 38938 (owfs) with signal SIGKILL. ноя 02 02:24:33 fatman systemd[1]: owfs.service: Failed with result 'exit-code'. ноя 02 02:24:33 fatman systemd[1]: Stopped 1-wire filesystem FUSE mount. # lsb_release -rd Description:Ubuntu 20.10 Release:20.10 # apt-cache policy owfs owfs: Installed: 3.2p3+dfsg1-6 Candidate: 3.2p3+dfsg1-6 Version table: *** 3.2p3+dfsg1-6 500 500 http://ru.archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu groovy/universe i386 Packages 100 /var/lib/dpkg/status ** Affects: owfs (Ubuntu) Importance: Undecided Status: New ** Patch added: "owfs.patch" https://bugs.launchpad.net/bugs/1902448/+attachment/5430114/+files/owfs.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902448 Title: systemd owfs.service wrong umount path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/owfs/+bug/1902448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852747] Re: mdcheck_start.service trying to start unexisting file
Everything work as expected: # systemctl status mdcheck_start.timer ● mdcheck_start.timer - MD array scrubbing Loaded: loaded (/lib/systemd/system/mdcheck_start.timer; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-09-29 09:25:28 +07; 5 days ago Trigger: n/a Triggers: ● mdcheck_start.service # systemctl status mdcheck_start.service ● mdcheck_start.service - MD array scrubbing Loaded: loaded (/lib/systemd/system/mdcheck_start.service; static; vendor preset: enabled) Active: activating (start) since Sun 2020-10-04 06:40:59 +07; 5h 17min ago TriggeredBy: ● mdcheck_start.timer Main PID: 3696570 (mdcheck) Tasks: 2 (limit: 9481) Memory: 1.7M CGroup: /system.slice/mdcheck_start.service ├─3696570 /bin/bash /usr/share/mdadm/mdcheck --duration 6 hours └─3724586 sleep 120 Oct 04 06:40:59 fatman systemd[1]: Starting MD array scrubbing... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852747 Title: mdcheck_start.service trying to start unexisting file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1852747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852747] Re: mdcheck_start.service trying to start unexisting file
Test finished =) # dpkg -l mdadm | grep mdadm ii mdadm 4.1-5ubuntu1.2 amd64tool to administer Linux MD arrays (software RAID) Problem with mdadm_continue.timer is fixed now: # systemctl status mdcheck_continue.timer ● mdcheck_continue.timer - MD array scrubbing - continuation Loaded: loaded (/lib/systemd/system/mdcheck_continue.timer; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-09-29 09:25:28 +07; 35s ago Trigger: n/a Triggers: ● mdcheck_continue.service Sep 29 09:25:28 fatman systemd[1]: Started MD array scrubbing - continuation. Moreover it automatically continue previous check on latest version install. # journalctl ... Sep 29 09:25:28 fatman systemd[1]: Started MD array scrubbing - continuation. Sep 29 09:25:28 fatman systemd[1]: Starting MD array scrubbing - continuation... Sep 29 09:25:28 fatman systemd[1]: mdcheck_start.timer: Succeeded. Sep 29 09:25:28 fatman systemd[1]: Stopped MD array scrubbing. Sep 29 09:25:28 fatman systemd[1]: Stopping MD array scrubbing. Sep 29 09:25:28 fatman systemd[1]: Started MD array scrubbing. Sep 29 09:25:28 fatman systemd[1]: mdmonitor-oneshot.timer: Succeeded. Sep 29 09:25:28 fatman systemd[1]: Stopped Reminder for degraded MD arrays. Sep 29 09:25:28 fatman systemd[1]: Stopping Reminder for degraded MD arrays. Sep 29 09:25:28 fatman systemd[1]: Started Reminder for degraded MD arrays. Sep 29 09:25:28 fatman root[2983618]: mdcheck continue checking /dev/md0 from 1604272336 Sep 29 09:25:28 fatman kernel: md: data-check of RAID array md0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852747 Title: mdcheck_start.service trying to start unexisting file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1852747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852747] Re: mdcheck_start.service trying to start unexisting file
I enabled -proposed and installed the package: # dpkg -l mdadm | grep mdadm ii mdadm 4.1-5ubuntu1.1 amd64tool to administer Linux MD arrays (software RAID) # dpkg -L mdadm | grep -i mdcheck /lib/systemd/system/mdcheck_continue.service /lib/systemd/system/mdcheck_continue.timer /lib/systemd/system/mdcheck_start.service /lib/systemd/system/mdcheck_start.timer /usr/share/mdadm/mdcheck # ls -altr /usr/share/mdadm/mdcheck -rwxr-xr-x 1 root root 3884 Sep 24 18:54 /usr/share/mdadm/mdcheck Original bug is fixed now. But I see another problem with systemd files - mdcheck_continue.timer is misconfigured and will never be started: # systemctl status mdcheck_continue.timer ● mdcheck_continue.timer - MD array scrubbing - continuation Loaded: loaded (/lib/systemd/system/mdcheck_continue.timer; static; vendor preset: enabled) Active: inactive (dead) Trigger: n/a Triggers: ● mdcheck_continue.service # systemctl enable mdcheck_continue.timer The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. I suppose, that I need to create another bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852747 Title: mdcheck_start.service trying to start unexisting file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1852747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852747] Re: mdcheck_start.service trying to start unexisting file
Hooray! Debian mdadm maintainers fixed that bug in version 4.1-6. This version currently available in Debian Sid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852747 Title: mdcheck_start.service trying to start unexisting file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1852747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852747] Re: mdcheck_start.service trying to start unexisting file
Thanks for your help, Guilherme. I've opened a Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960132 It contains new version of patch, without removing "checkarray" script, as you suggest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852747 Title: mdcheck_start.service trying to start unexisting file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1852747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852747] Re: mdcheck_start.service trying to start unexisting file
** Bug watch added: Debian Bug tracker #960132 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960132 ** Also affects: mdadm (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960132 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852747 Title: mdcheck_start.service trying to start unexisting file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1852747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852747] Re: mdcheck_start.service trying to start unexisting file
Here is a patch that fixes missed scripts, but didn't touch docs. ** Patch added: "mdcheck-fix.patch" https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1852747/+attachment/5309729/+files/mdcheck-fix.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852747 Title: mdcheck_start.service trying to start unexisting file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1852747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852747] Re: mdcheck_start.service trying to start unexisting file
Current version of mdadm package contain checkarray script instead of mdcheck. Workaround: create /etc/cron.d/mdadm as it was in previous versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852747 Title: mdcheck_start.service trying to start unexisting file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1852747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659689] Re: /usr/bin/ikec:*** Error in `ikec': double free or corruption (out): ADDR ***
Workaround: add "-a" to command line -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659689 Title: /usr/bin/ikec:*** Error in `ikec': double free or corruption (out): ADDR *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ike/+bug/1659689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658786] [NEW] apcupsd with snmp driver show DWAKE in wrong units
Public bug reported: # lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 # apt-cache policy apcupsd apcupsd: Installed: 3.14.14-0.2 Candidate: 3.14.14-0.2 Version table: *** 3.14.14-0.2 500 500 http://ru.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages 100 /var/lib/dpkg/status apcaccess show DWAKE value in timeticks: # apcaccess | grep DWAKE DWAKE: 6000 Seconds Correct value is 100 times lower - 60 seconds. ** Affects: apcupsd (Ubuntu) Importance: Undecided Status: New ** Patch added: "mib.patch" https://bugs.launchpad.net/bugs/1658786/+attachment/4808241/+files/mib.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658786 Title: apcupsd with snmp driver show DWAKE in wrong units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apcupsd/+bug/1658786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658780] [NEW] apcupsd unable to do killpower with snmp driver
Public bug reported: # lsb_release -rd Description:Ubuntu 16.10 Release:16.10 # apt-cache policy apcupsd apcupsd: Installed: 3.14.14-0.2 Candidate: 3.14.14-0.2 Version table: *** 3.14.14-0.2 500 500 http://ru.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages 100 /var/lib/dpkg/status Symptoms: apcupsd --killpower unable to do killpower with SNMP driver Issue was observed on: UPS: Smart-UPS 2200 SNMP module: MN:AP9619 HR:A10 MD:11/02/2005 AOS: 3.7.3 (02/02/2010), StatApp(name: sumx): 3.7.2 (02/02/2010) tcpdump after "apcupsd --killpower" exec: <...lines with getting UPS state...> IP 192.168.1.38.57389 > 192.168.1.5.161: C=xxx SetRequest(33) .1.3.6.1.4.1.318.1.1.1.6.1.1=2 IP 192.168.1.5.161 > 192.168.1.38.57389: C=xxx GetResponse(33) noSuchName@1 .1.3.6.1.4.1.318.1.1.1.6.1.1=2 Main cause - upsBasicControlConserveBattery is incorrect. Correct OID for upsBasicControlConserveBattery is .1.3.6.1.4.1.318.1.1.1.6.1.1.0 (additional ".0" at the end) I have tested this OID manually with snmpset - it's working correct. Here tcpdump of this tests with comments: IP 192.168.1.38.59474 > 192.168.1.5.161: C=xxx SetRequest(35) .1.3.6.1.4.1.318.1.1.1.6.1.1.0=2 IP 192.168.1.5.161 > 192.168.1.38.59474: C=xxx GetResponse(35) genErr@1 .1.3.6.1.4.1.318.1.1.1.6.1.1.0=2 // it's ok. UPS not on battery power. IP 192.168.1.5.49315 > 192.168.1.38.162: Trap(108) .1.3.6.1.4.1.318 192.168.1.5 enterpriseSpecific s=5 26777240 .1.3.6.1.4.1.318.2.3.3.0="UPS: On battery power in response to an input power problem." IP 192.168.1.38.35216 > 192.168.1.5.161: C=xxx SetRequest(35) .1.3.6.1.4.1.318.1.1.1.6.1.1.0=2 IP 192.168.1.5.161 > 192.168.1.38.35216: C=xxx GetResponse(35) .1.3.6.1.4.1.318.1.1.1.6.1.1.0=2 // UPS correctly going to sleep Same problem with upsAdvControlUpsOff - correct OID .1.3.6.1.4.1.318.1.1.1.6.2.1.0 (additional ".0" at the end). In attach - patch with trying to fixing this problem in simplest way. ** Affects: apcupsd (Ubuntu) Importance: Undecided Status: New ** Patch added: "oids.patch" https://bugs.launchpad.net/bugs/1658780/+attachment/4808234/+files/oids.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658780 Title: apcupsd unable to do killpower with snmp driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apcupsd/+bug/1658780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
