Networking issues with VirtualBox 6.1.30
Herrick, Rick
The previous update of VirtualBox–6.1.28–was completely broken, so don’t try to use that. The latest version is 6.1.30, so I tried that to see if it fixed the issues that made 6.1.28 non-operational.
The good news is that it does.
The bad news is that the default IP addresses configured in XNAT Vagrant no longer work, due to a change in the range of IP addresses that VirtualBox allows for host-only network adapters. This “(intentionally) breaking change” restricts IP addresses to the range:
This means the first two numbers must be 192.68, while the third number has to be between 56 and 63 (inclusive), and the last can be 1 to 255, except:
- With 192.68.63.x, where 255 is reserved for broadcast
- You can use 1, but Vagrant or VirtualBox (not sure which, I think it’s the latter) will issue a warning
I’m reasonably certain these numbers are correct, but, if anyone knows differently, please correct me!
We’ll work on changing the XNAT Vagrant configurations to use IP addresses in line with these changes for the next XNAT release. In the meantime, if you need to upgrade to 6.1.30 for whatever reason, you can work around this by adding something like this to your local.yaml configuration:
vm_ip: 192.168.56.100
--
Rick Herrick
XNAT Architect/Developer
Computational Imaging Laboratory
Washington University School of Medicine
The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.
David Maffitt
Tue 11 Jan 2022 04:07:49 PM UTC
vagrant@xnat-system:~$ timedatectl
Local time: Tue 2022-01-11 16:10:18 UTC
Universal time: Tue 2022-01-11 16:10:18 UTC
RTC time: Tue 2022-01-11 16:09:20
Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: no
NTP service: active
RTC in local TZ: no
vagrant@xnat-system:~$ timedatectl set-time 16:32:30
Herrick, Rick
Try running this:
systemctl stop chrony.service
chronyd -q
systemctl start chrony.service
I ran into issues similar to what you’re seeing (probably the same as what you’re seeing) that broke the ability to log into the XNAT UI because of time differences between the server and client. The only way I could figure out how to work around it was installing chrony over ntp sync.
I actually have the command sequence above set to an alias in my default shell configuration:
alias td='systemctl stop chrony.service; chronyd -q; systemctl start chrony.service'
The ironic thing is that, once I added that alias, I almost never needed to use it 😊
--
Rick Herrick
XNAT Architect/Developer
Computational Imaging Laboratory
Washington University School of Medicine
From:
xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of David Maffitt <davidm...@gmail.com>
Date: Tuesday, January 11, 2022 at 10:43 AM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] Re: Networking issues with VirtualBox 6.1.30
|
* External Email - Caution * |
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
xnat_discussi...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/xnat_discussion/81d00c6f-3d84-4d0e-a12b-59c399cb99a0n%40googlegroups.com.