Commissioning failure

Users
,
21

The file is quite large, can I email the files to an email?

22

you could compress it, upload somewhere like google drive or dropbox, or post it as a GitHub gist or pastebin, right?

23

https://drive.google.com/drive/folders/1ToGq4-nof88BiKthEq-iQVVVtH4kOTAh?usp=sharing

Google drive link cc @ack @billwear

24

don’t reshare the contents of that file.

1 Like
25

Hello @billwear @ack, any luck with those files?

26

not yet. still looking.

27

I’m going to upload /var/snap/maas/common/log/http/error.log, found some network unreachable.
errors.

28

yep. i noticed the bind9 start failure, but couldn’t correlate it to anything else yet.

29

Yes, would love to know why that is as well.

1 Like
30

I have uploaded http/error.log as well.

1 Like
31

One other issue, is there a way to update /etc/netplan/50-cloud-init.yaml to register it mac address to a windows DHCP server. We see where during the enlisting and commissioning steps, it’ first register the server with a name of Ubuntu and it’s mac address and then during commissioning and deployment it registers with a UUID (longer windows mac address format). Why not update with the new name and the mac address after the initial step? @billwear @ack

32

can you upload the named.log? we’re trying to figure out the bind issue.

33

@billwear, I uploaded the regiond named.log file.

1 Like
34

@cmills, what version of MAAS are you using? the poster before you mentioned 3.3…

35

@billwear 3.1.0-10901-g.f1f8f1505

1 Like
36

okay, we really need help from someone who isn’t here this week, and we’ll ask them when they get back, but one option would be to stop maas, remove the bind dir and restart. maybe it’s a stale config in some way (it looks incongruous)? that should recreate it. “stop maas” might not be possible, i know.

37

okay, will try that but what about the original problem of not “Unable to find configuration file”

1 Like
38

dunno yet. still looking.

39

What is also weird is sometimes we are seing this error

2023/02/02 14:53:36 [error] 193048#193048: *2104 connect() to [::1]:5249 failed (101: Network is unreachable) while connecting to upstream, client: 10.166.105.100, server: , request: “GET /images/ubuntu/amd64/ga-22.04/jammy/stable/boot-initrd HTTP/1.0”, subrequest: “/log”, upstream: “http://[::1]:5249/log”, host: “10.166.96.60:5248” and we think it’s related to image-1.png located within the google drive. within the http error.log cc @billwear

40

google drive? okay, now i’m confused.