[09:35] <ameetgandhare> I am trying to reimage nodes from MAAS controller. The machine is put in to "declared": state. After which I put the node in commissioning state, and restart the node. I find that the pxe boot starts and then my squid-deb-proxy dies and the commissioning failed .
[09:35] <ameetgandhare> Please help me find the problem
[09:38] <dimitern> rvba, ping
[09:39] <ameetgandhare> the MAAS web gui reports "Failed State" for the node being commissioned.
[09:39] <ameetgandhare> Please help me fix the problem.
[09:42] <rvba> ameetgandhare: If your squid-deb-proxy dies and you think it's the problem, you need to look into its log.  Note that you don't need to restart the node manually, if you provide the BMC credential, MAAS should take care of booting up the node for you.
[09:42] <rvba> Hi dimitern.
[09:45] <ameetgandhare> The squid-deb-proxy dies when node that wants to join the MAAS cluster tries to connect to the proxy for downloading files from internet.
[09:47] <ameetgandhare> I am not finding any infirmation in /var/log/squid-deb-proxy .
[09:47] <ameetgandhare> This is happening in the commisioning state of the node.
[09:49] <ameetgandhare> Also I need to restart the node everytime when MAAS web-gui puts the node in "commissioning" mode.
[09:49] <ameetgandhare> MAAS does not do that.
[09:49] <rvba> ameetgandhare: the proxy's logs are in /var/log/maas/proxy/.
[09:49] <ameetgandhare> ok. thanks
[09:50] <ameetgandhare> But I don't have any directory called proxy inside /var/log/maas/ . I am running Ubuntu 14.04 with MAAS
[09:58] <ameetgandhare> I have an oops file which is created for approximately same time that the proxy crashed in /var/log/maas/oops . How can I analyze it?
[10:01] <rvba> The OOPS report is a bson file.  strings <oops_file> will give you a view of the content.
[10:13] <ameetgandhare> thanks
[16:38] <plop> hello