Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Hey
I upgraded to freeBSD 13.0 and it seem to have broken the DO network configurations, I am forced to go to the console and run /usr/local/rc.d/digitalocean restart and then I have network again…
When the server boots up I get the following:
DigitalOcean: expected hostID xxxx(edited out) DigitalOcean: resizing the disk… vtbd0 recovering is not needed vtbd0p3 resized DigitalOcean: expanding the ZFS pool DigitalOcean: mount configdrive could not determine starting sector, using very first session DigitalOcean: applying droplet configuration DigitalOcean: reading meta-data ld-elf.so.1: Shared object “libonig.so.5” not found, required by “jq” DigitalOcean: hostname is set in /etc/rc.conf, skipping setting hostname ld-elf.so.1: Shared object “libonig.so.5” not found, required by “jq” ld-elf.so.1: Shared object “libonig.so.5” not found, required by “jq” ld-elf.so.1: Shared object “libonig.so.5” not found, required by “jq” DigitalOcean: adding public IPv4 configuration ld-elf.so.1: Shared object “libonig.so.5” not found, required by “jq” ld-elf.so.1: Shared object “libonig.so.5” not found, required by “jq” DigitalOcean: adding anchor ipv4 configuration ld-elf.so.1: Shared object “libonig.so.5” not found, required by “jq” ld-elf.so.1: Shared object “libonig.so.5” not found, required by “jq” DigitalOcean: adding private IPv4 configration ld-elf.so.1: Shared object “libonig.so.5” not found, required by “jq” ld-elf.so.1: Shared object “libonig.so.5” not found, required by “jq” ld-elf.so.1: Shared object “libonig.so.5” not found, required by “jq” DigitalOcean: adding IPv6 configuration DigitalOcean: finished droplet configuration DigitalOcean: re-starting networking Created clone interfaces: lo1. lo0: link state changed to UP ifconfig: ‘netmask’ requires argument ifconfig: ‘prefixlen’ requires argument vtnet0: link state changed to UP ifconfig: alias: bad value ifconfig: ‘netmask’ requires argument vtnet1: link state changed to UP
anyone else had the same problem and now how to fix it?
Karl Denninger
Karl Denninger
Karl Denninger
GIORGIO MICHELI
SandyDarkBlueRay
Sam Whited
Albert Valbuena
3886dfb8910643e1a66d5fe5837be4
dirtycornflakes
sremick
MohammedAbuObaid
Eugene Selin