I am running FreeBSD 10.2. I spun the Droplet, accessed it via ssh, and did the following:
1) cd /usr/ports/ports-mgmt/portmaster/ ; sudo make install clean
2) sudo portmaster -a
3) cd /usr/ports/net/svnup ; sudo make install clean
4) sudo svnup release
5) sudo freebsd-update fetch install
6) sudo reboot
Then, it was not responding to pings, and I could not access it via ssh (additionally, it had no ip address.)
Next, support said I needed to run the following due to a DigitalOcean FreeBSD Provisioning Bug (in Single User Mode):
ln -s /etc/rc.digitalocean.d/[dropletNumber].conf /etc/rc.digitalocean.d/droplet.conf
Now vtnet0 has an ip address, but I have no Internet access, as shown by:
ping 8.8.8.8
no route to host
At this point support said to ask the community.
Any help would be much appreciated.
Regards, Brandon
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $100 of credit to try our products over 60 days!
my droplet is Ubuntu
Not sure what went wrong with you. This is what I did to set-up my FreeBSD droplet. Please notice it was done for a 10.1:
Reboot in single user to disable journaling due to a bug in FreeBSD 10.1 with SSD (I suggest you to check if this still apply to 10.2, in fact I’m going to check myself):
In single mode:
Now we are back in normal mode and we can finish the installation process:
Maybe at this point is better to start over with a fresh new droplet.
Anyway, I suggest to use pkg to manage your packages. Building everything may take a very long down time if this is a production machine.
Regards,
Nicholas