[03:06] Bug #1561954 changed: Ubuntu Server install menu needs a 16.04 refresh

[03:24] Bug #1321068 changed: AMT powerdown "pt_status: not permitted" error in log [14:24] Is it possible to clean out a MAAS install? My MAAS setup seems to have become so sticky and slow, especially the Nodes page which is now unusable a lot of the time. And on the server I see that it has a cache of around 20G... [15:23] neiljerram: what version of maas are you using ? [15:24] 1.9.1 [15:29] neiljerram: have you imported a lot of images ? are your machines currently deploying ? or is it just sitting idled ? [15:29] neiljerram: ps faux | grep maas-regiond or ps faux | grep maas-clusterd ? [15:30] There are about 20 VMs and 20 bare metal machines available for MAAS to manage. [15:31] We've had this cluster running, with varying degrees of active usage, for over a year. [15:31] Recently I upgraded from 1.7 (I think - could have been 1.8) to 1.9.1, and unfortunately that seems to have made things worse. [15:32] ubuntu@calico15:~$ ps faux | grep maas-regiond [15:32] maas 611 2.0 3.0 139956 63836 ? Ssl 15:04 1:47 /usr/bin/python /usr/bin/twistd --nodaemon --pidfile= maas-regiond [15:32] maas 620 2.2 2.5 127544 53640 ? Ssl 15:04 1:57 /usr/bin/python /usr/bin/twistd --nodaemon --pidfile= maas-regiond [15:32] maas 623 1.7 2.7 147192 57492 ? Ssl 15:04 1:33 /usr/bin/python /usr/bin/twistd --nodaemon --pidfile= maas-regiond [15:32] maas 628 1.8 2.5 134540 52900 ? Ssl 15:04 1:37 /usr/bin/python /usr/bin/twistd --nodaemon --pidfile= maas-regiond [15:32] ubuntu 8650 0.0 0.0 4676 796 pts/0 S+ 16:31 0:00 \_ grep --color=auto maas-regiond [15:32] ubuntu@calico15:~$ ps faux | grep maas-clusterd [15:32] maas 586 0.6 1.5 83924 31500 ? Ssl 15:04 0:36 /usr/bin/python /usr/bin/twistd --nodaemon --uid=maas --gid=maas --pidfile= maas-clusterd [15:32] ubuntu 8676 0.0 0.0 4676 792 pts/0 S+ 16:32 0:00 \_ grep --color=auto maas-clusterd [15:34] Today I haven't been able to get any nodes information from the nodes web page (http://calico15/MAAS/#/nodes) at all. It just says "Loading..." forever. [16:05] neiljerram: try http://calico15:5240/MAAS [16:06] roaksoax, Well, that has certainly produced some information immediately! [16:07] roaksoax, I can see my nodes now. [16:07] roaksoax, What is the difference between the new and old port numbers? [16:11] mwenning: accessing to port 80 is apache2 forwarding to 5240 [16:11] err [16:11] neiljerram: ^^ [16:11] roaksoax, Aha, thanks. [16:17] roaksoax, But otherwise it's the same? I wonder why the forwarded access should apparently hang... [16:25] neiljerram: it is the same. Maybe apache2 is freaking out. There was a bug in apache2 that proxying would cause issues like you are seeing [16:25] roaksoax, Well I'm happy if I don't need apache2 in the loop any more! [16:27] neiljerram: you don't! just need to make sure that /etc/maas/clusterd.conf is pointing to the MAAS server on port :5240 [16:27] roaksoax, Cool, thank you. [17:02] Bug #1568041 opened: [2.0beta1] macaddress_set should be removed from the machines and devices API [17:02] Bug #1568045 opened: [2.0beta1] constraint_map should be removed from the machines acquire output [17:29] Bug #1568051 opened: ThreadPool context entry failure causes thread pool to break [19:17] Bug #1568102 opened: [2.0beta1] Network details page doesn't have CSS for editting