[2.0a4] maas-rackd missing presumed lost
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Undecided
|
Andres Rodriguez |
Bug Description
After updating to MAAS 2.0a4 I seem to have lost maas-rackd, but I'm not sure where.
systemd suggests maas-rackd is running although there is an error in its logs related to PAM-CGFS that I don't understand:
mark@maas:
[sudo] password for mark:
● maas-rackd.service - MAAS Cluster Controller
Loaded: loaded (/lib/systemd/
Active: active (running) since Wed 2016-03-30 11:21:36 BST; 4min 32s ago
Docs: https:/
Process: 2885 ExecStartPre=
Process: 2865 ExecStartPre=
Process: 2834 ExecStartPre=
Main PID: 2889 (sh)
Tasks: 8 (limit: 512)
Memory: 83.4M
CPU: 11.283s
CGroup: /system.
├─2889 /bin/sh -c exec /usr/bin/authbind --deep /usr/bin/twistd3 --nodaemon --pidfile= maas-rackd 2>&1 | tee -a $LOGFILE
├─2892 /usr/bin/python3 /usr/bin/twistd3 --nodaemon --pidfile= maas-rackd
└─2893 tee -a /var/log/
Mar 30 11:24:46 maas sudo[4495]: maas : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=
Mar 30 11:24:46 maas sudo[4495]: pam_unix(
Mar 30 11:25:37 maas sudo[4529]: maas : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=
Mar 30 11:25:37 maas sudo[4529]: pam_unix(
Mar 30 11:25:37 maas sudo[4530]: maas : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=
Mar 30 11:25:37 maas sudo[4530]: pam_unix(
Mar 30 11:25:37 maas sudo[4531]: maas : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=
Mar 30 11:25:37 maas sudo[4531]: pam_unix(
Mar 30 11:25:37 maas PAM-CGFS[4531]: Failed to create a cgroup for user root
Mar 30 11:25:37 maas sudo[4531]: pam_unix(
However there are no log files for it:
mark@maas:
total 54456
lrwxrwxrwx 1 root root 16 Mar 29 09:53 apache2 -> /var/log/apache2
-rw-r--r-- 1 syslog syslog 18350 Mar 30 11:24 maas.log
-rw-r--r-- 1 syslog syslog 104904 Mar 30 06:36 maas.log.1
-rw-r--r-- 1 syslog syslog 20516 Mar 29 06:23 maas.log.2.gz
drwxr-x--- 2 proxy proxy 4096 Mar 30 06:38 proxy
-rw-r--r-- 1 maas maas 55591104 Mar 30 11:26 regiond.log
drwxr-xr-x 2 syslog syslog 4096 Mar 28 20:24 rsyslog
It looks like many of the services are up:
tcp 0 0 *:5248 *:* LISTEN 2892/python3
tcp 0 0 *:5250 *:* LISTEN 2815/python3
tcp 0 0 *:5251 *:* LISTEN 2822/python3
tcp 0 0 *:5252 *:* LISTEN 2807/python3
tcp 0 0 *:3109 *:* LISTEN 3097/conserver
tcp 0 0 *:5253 *:* LISTEN 2811/python3
tcp 0 0 *:7911 *:* LISTEN 3625/dhcpd
tcp 0 0 *:40455 *:* LISTEN 3099/conserver
tcp 0 0 maas.mallards:
tcp 0 0 localhost:domain *:* LISTEN 2770/named
tcp 0 0 *:ssh *:* LISTEN 2844/sshd
tcp 0 0 *:5240 *:* LISTEN 2815/python3
tcp 0 0 *:5240 *:* LISTEN 2811/python3
tcp 0 0 *:5240 *:* LISTEN 2807/python3
tcp 0 0 *:5240 *:* LISTEN 2822/python3
tcp 0 0 *:3128 *:* LISTEN 2899/squid3
tcp 0 0 localhost:
tcp 0 0 localhost:smtp *:* LISTEN 3571/master
tcp 0 0 localhost:953 *:* LISTEN 2770/named
tcp 0 0 localhost:954 *:* LISTEN 2770/named
tcp 0 0 *:iscsi-target *:* LISTEN 2794/tgtd
tcp6 0 0 [::]:8000 [::]:* LISTEN 2899/squid3
tcp6 0 0 [::]:http [::]:* LISTEN 3437/apache2
tcp6 0 0 [::]:domain [::]:* LISTEN 2770/named
tcp6 0 0 [::]:ssh [::]:* LISTEN 2844/sshd
tcp6 0 0 localhost:
tcp6 0 0 localhost:smtp [::]:* LISTEN 3571/master
tcp6 0 0 [::]:iscsi-target [::]:* LISTEN 2794/tgtd
However commissioning is not succeeding and the absence of rackd logs makes it a little difficult to debug :)
Related branches
- Andres Rodriguez (community): Approve
- LaMont Jones (community): Needs Fixing
- Lee Trager (community): Needs Information
-
Diff: 502 lines (+133/-92)22 files modifieddebian/changelog (+5/-1)
debian/control (+0/-1)
debian/extras/99-maas (+0/-5)
debian/maas-common.dirs (+2/-0)
debian/maas-common.postinst (+13/-6)
debian/maas-common.postrm (+5/-1)
debian/maas-dhcp.dirs (+2/-0)
debian/maas-dhcp.maas-dhcpd6.service (+1/-1)
debian/maas-dhcp.postinst (+3/-0)
debian/maas-dhcp.postrm (+1/-2)
debian/maas-rack-controller.dirs (+2/-0)
debian/maas-rack-controller.maas-rackd.service (+2/-2)
debian/maas-rack-controller.postinst (+42/-11)
debian/maas-rack-controller.postrm (+25/-11)
debian/maas-region-api.install (+0/-1)
debian/maas-region-api.maas-regiond-worker@.service (+1/-1)
debian/maas-region-api.maas-regiond.service (+1/-1)
debian/maas-region-api.postinst (+15/-13)
debian/maas-region-api.postrm (+9/-2)
debian/maas-region-api.preinst (+4/-0)
debian/maas-region-controller.postinst (+0/-6)
debian/maas-region-controller.postrm (+0/-27)
Changed in maas: | |
assignee: | nobody → Andres Rodriguez (andreserl) |
Changed in maas: | |
status: | New → Fix Committed |
Changed in maas: | |
milestone: | none → 2.1.0 |
status: | Fix Committed → Fix Released |
milestone: | 2.1.0 → none |
I noticed that /var/log/maas was owned by root.root. Chowning that directory to maas.maas and restarting maas-rackd enabled the rackd.log to get written. Looks like this bug is really about having the packaging ensure the permissions of /var/log/maas are appropriate.