=== Guest7726 is now known as wallyworld [09:01] rvba: I posted some notes on your MP. Could you have a look and see if I'm making any sense at all? [09:02] jtv: sure. === matsubara is now known as matsubara-lunch === matsubara-lunch is now known as matsubara === mrevell_ is now known as mrevell [13:53] negronjl: how was your presentation btw? === Aaton_off is now known as Aaton [17:25] roaksoax: ping [17:25] or Daviey: ping [17:41] negronjl: here [17:49] roaksoax: I'm having an issue with the mirror and was wondering if you can help me [17:49] negronjl: shoot [17:49] roaksoax: I re-created the mirror for maas and i am now unable to boot machines ( incorrect architecture ) [17:49] roaksoax: I re-created the mirrror with the ( already there ) create-mirror.sh [17:50] roaksoax: I have downloaded the mirrors for both i386 and amd64 ... any thoughts ? [17:50] roaksoax: just to be on the safe side ... I am now trying to boot without the mirror ( downloading over the wire ) [17:51] roaksoax: that seems to be working ... so there is something broken with my mirror [17:51] negronjl: uhmmm no idea [17:52] negronjl: smoser will be able to help you he was the one who created it [17:52] roaksoax: no worries .. I'll debug further ( or as smoser as well ) ... just thought that maybe you had encounter this in the past [17:55] oh yeah, i can always help. [17:56] what is the issue? [17:59] hi smoser ... I re-created the mirror for the maas deployment and it is now complaining about not having the right architecture [17:59] smoser: i am using apt-mirror ( actually the create-mirror.sh script in the maas server ) [17:59] what is complaining about not having the right arch? [17:59] negronjl, that was probably a bad idea [17:59] negronjl: we did hit it i think but smoser fixed it [18:00] smoser: which part was a bad idea ? [18:00] i think recreating the mirror. [18:00] smoser: i had to [18:00] heres what sucks [18:00] * we had a tiny link [18:00] * we needed a local mirror [18:00] * we tried to be smart and only get some portions of the full mirror [18:01] * that sucked. [18:01] negronjl, basically, the issue is that you need i386, and that create-mirror wasn't getting it. [18:01] smoser: i mirrored both i386 and amd64 [18:01] the best thing to do, if you have a nice big fat link, is to make that create-mirror script get a lot more stuff. [18:01] well, then what are you missing? [18:02] smoser: I am still using the create-mirror script .. I just modified the line for the installer ( it had deb-i386 and i added the amd64 one ) [18:02] smoser: if you have an apt-mirror config file that would get it all ( both archs to be sure ), it would help [18:02] smoser: i have 35M downlink so I can handle the download [18:03] smoser: once I have the entire mirror, updating it would be easier and we would have everything that we need. [18:03] so what are you missing? [18:03] what was complaining? [18:04] smoser: it appears to be downloading/using the i386 deb installer and, apparently that's not to the liking of the HP microserver [18:04] smoser: so I downloaded amd64 [18:04] smoser: that doesn't work either ... [18:05] smoser: I haven't tried deleting the i386 stuff and just downloading amd64 ... didn't want to do that if I didn't really have to [18:05] smoser: thoughts ? [18:07] negronjl, i'm a bit confused. [18:07] what is using the i386 deb installer? [18:07] sorry for not being up to date on what you're doing or the problems your having [18:10] smoser: no worries ... let me grab a chunk of syslog ( where the complains are ) and I'll pastebin them so we have a better idea ... give me a minute. [18:11] k [18:21] smoser: can't pastebinit 'cause the machine is not booting :) ... the error: unsupported archive [18:21] smoser: it is trying to load the i386 deb installer [18:22] smoser: and rejecting it ( wrong arch ) [18:22] smoser: This all works if I download it from the wire so, I may just have to let it install and see what it's using after when I can log on to the box [18:26] negronjl, but hwat is "wrong arch" ? [18:26] i need more data there. [18:27] smoser: i know ... me too :P I'm also trying to find out ... kind of a dumb error though ... wrong arch ...but it doesn't really tell me what it is expecting or what the _right_ arch is :/ [18:30] what are you trying to do right now? [18:30] enlistement? [18:30] and how much of our hacked setup are you still using? [18:31] because there is probably data there i dont remember. [18:31] s/data/hacks/ [18:32] smoser: I am trying to enlist ( I guess it is what is called when you first boot the machine so it shows as "Declared" ) [18:32] right. [18:32] smoser: I am using all of the setup ( 9 HP micro servers and one buster laptop ) [18:33] s/buster/busted/ [18:33] so that should probably work. i dont knwo why it would show wrong arch. [18:33] by default enlistment *is* with i386 [18:33] so that is expected [18:33] (the reason is that i386 boots on amd64, and you dont know what the system is, so you take least common denominator) [18:33] once enlisted it should be recognized as amd64 [18:34] smoser: ok .. I'll try to get more information about it. At least I know that it "should" be the i386 one ... === matsubara is now known as matsubara-afk [19:58] smoser: i got past the wrong arch issue but, now the iscsi is trying the wrong address ( an address that I had previously used ). Can you tell me how to have that changed to the correct address ? Or where the that setting would be ? [20:00] you might want to dpkg-reconfdigure maas [20:00] i think that might do it. [20:00] the IP addresses are rendered into /var/lib/tftp (i think) ... grep down that path. [20:01] but they start with the setting of the 'server' that you should be able to set with dpkg-reconfigure [20:02] you might have to 'maas-import-isos --update' [20:02] but i dont think so [21:21] smoser: sorry ... missed your reply ... thx. I'll try that