I upgraded from 3.3 to 3.5 without checking here first, now I find myself with no GUI.
One of three airgapped copies of 3.3, working prior to the upgrade. I loaded https://dl.nabox.org/nabox/NAbox-3.5.update via the Maintenance page and the dialog timed in the second to last step.
The behavior seems related to a few recent threads here but I cannot find the same errors in dc logs etc. I've updated /etc/hosts with the SAN and nabox host names and IPs, added a server entry to /etc/resolv.conf and ensured that that DNS server is answering both names, to no avail.
dc down and dc up -d return with no apparent errors. The only instance of "misbehaving" in dc logs is the update check going to github, expected because airgapped.
Thoughts on how to begin correcting this? This is my test/devel instance, I'm (obviously) goint to hold off in production until I understand this.
#Upgraded from 3.3 to 3.5, no GUI?
wicked void
surreal oak
What about dc logs traefik ?
wicked void
One line:
traefik | wget: can't connect to remote host (172.18.0.5): Connection refused
On the nabox ssh interface, there is no 172.18.0.5 interface. There IS a .1:
br-a1271198cee3 Link encap:Ethernet HWaddr 02:42:15:C2:1B:66
inet addr:172.18.0.1 Bcast:172.18.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7356930 errors:0 dropped:0 overruns:0 frame:0
TX packets:8173953 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1233626142 (1.1 GiB) TX bytes:16254558366 (15.1 GiB)
wicked void
Looking at a working 3.3, I see a number of traefik logs for "can't connecto to remote host" on a handful of 172.18.0.xx IP addresses... Not sure if this is expected behavior therefor not diagnostic for my purposes on this failed 3.5 upgrade.
wicked void
traefik | wget: can't connect to remote host (172.21.0.12): Connection refused
traefik | wget: can't connect to remote host (172.21.0.11): Host is unreachable
traefik | wget: bad address 'nabox-api:5000'
traefik | wget: bad address 'nabox-api:5000'
traefik | wget: bad address 'nabox-admin'
traefik exited with code 0
traefik has been recreated
traefik exited with code 137
traefik has been recreated
traefik | wget: can't connect to remote host (172.21.0.12): Connection refused
traefik | wget: can't connect to remote host (172.21.0.10): Connection refused
traefik | wget: can't connect to remote host (172.21.0.10): Connection refused
Looks like traefik is looping?
nabox03:~# dc logs -f --tail 10 traefik
traefik exited with code 0
Error response from daemon: can not get logs from container which is dead or marked for removal
nabox03:~# dc logs -f --tail 10 traefik
traefik | wget: can't connect to remote host (172.22.0.12): Connection refused
Yep it can’t connect to nabox-api probably because it’s not running. « dc ps » and « dc logs nabox-api » ?
wicked void
nabox-api | Traceback (most recent call last):
nabox-api | File "/app/api.py", line 48, in <module>
nabox-api | nabox.ovf.apply_ovf_configuration()
nabox-api | File "/app/nabox/ovf.py", line 62, in apply_ovf_configuration
nabox-api | 'dns':dns, }
nabox-api | UnboundLocalError: local variable 'dns' referenced before assignment
nabox-api | Traceback (most recent call last):
nabox-api | File "/app/api.py", line 48, in <module>
nabox-api | nabox.ovf.apply_ovf_configuration()
nabox-api | File "/app/nabox/ovf.py", line 62, in apply_ovf_configuration
nabox-api | 'dns':dns, }
nabox-api | UnboundLocalError: local variable 'dns' referenced before assignment```"dc ps" outputs too much for Discord. The lines for nabox-admin and -api:
nabox-api registry.lab/nabox-api:latest "python api.py" nabox-api 28 seconds ago Restarting (1) Less than a second ago```Looks like -api is looping, each time I check it's "Restarting (1) less than a second ago"
surreal oak
Ok, that's the same issue than another user.
You have to stop NAbox, and edit the OVF properties in vApp options in vCenter.
Make sure there is a correct value in "dns". A fix is ongoing
wicked void
<Property oe:key="address" oe:value="redacted"/>
<Property oe:key="dns" oe:value=""/>
<Property oe:key="gateway" oe:value="redacted"/>
<Property oe:key="hostname" oe:value="NAbox03"/>
<Property oe:key="netmask" oe:value="255.255.255.0"/>
</PropertySection>```Testing now.
nabox web gui is back!
For any else struggling... Power off the VM, navigate to the VM in vCenter, Configure tab, Settings, vApp Options, Properties at the bottom of the screen, select "dns" and "SET VALUE" and give it a viable DNS server.
wicked void
On-topic question... is working DNS required for 3.5?