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.

Network Configuration
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 45.55.xx.xxx netmask 255.255.224.0 broadcast 45.55.63.255 inet6 fe80::601:94ff:fe94:9301 prefixlen 64 scopeid 0x20<link> ether 04:01:94:94:93:01 txqueuelen 1000 (Ethernet) RX packets 377928 bytes 38584549 (36.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 298834 bytes 1061519721 (1012.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::601:94ff:fe94:9302 prefixlen 64 scopeid 0x20<link> ether 04:01:94:94:93:02 txqueuelen 1000 (Ethernet) RX packets 6 bytes 480 (480.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 10269 bytes 1825094 (1.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 40058 bytes 8361409 (7.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 40058 bytes 8361409 (7.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Problem (this never stop, using CPU and disk)
Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> Auto-activating connection ‘Wired connection 1’. Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: starting connection ‘Wired connection 1’ Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) scheduled… Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) started… Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): device state change: disconnected -> prepare (reason ‘none’) [30 40 0] Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) scheduled… Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) complete. Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) starting… Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): device state change: prepare -> config (reason ‘none’) [40 50 0] Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) successful. Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) complete. Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) scheduled. Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) started… Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): device state change: config -> ip-config (reason ‘none’) [50 70 0] Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> Activation (eth1) Beginning DHCPv4 transaction (timeout in 45 seconds) Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> dhclient started with pid 4666 Mar 6 13:18:21 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) complete. Mar 6 13:18:21 noctuamjuris dhclient[4666]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4 (xid=0x5f3e977b) Mar 6 13:18:23 noctuamjuris avahi-daemon[423]: Registering new address record for fe80::601:94ff:fe94:9302 on eth1.*. Mar 6 13:18:24 noctuamjuris ntpd[448]: Listen normally on 307 eth1 fe80::601:94ff:fe94:9302 UDP 123 Mar 6 13:18:25 noctuamjuris dhclient[4666]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 (xid=0x5f3e977b) Mar 6 13:18:25 noctuamjuris kernel: iptables: CN-Country-Drop: IN=eth0 OUT= MAC=04:01:94:94:93:01:f8:c0:01:27:e4:f0:08:00 SRC=222.186.56.42 DST=45.55.46.168 LEN=40 TOS=0x00 PREC=0x00 TTL=103 ID=256 PROTO=TCP SPT=6000 DPT=22 WINDOW=16384 RES=0x00 SYN URGP=0 Mar 6 13:18:30 noctuamjuris dhclient[4666]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 (xid=0x5f3e977b) Mar 6 13:18:37 noctuamjuris dhclient[4666]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15 (xid=0x5f3e977b)
ar 6 13:18:25 noctuamjuris kernel: iptables: CN-Country-Drop: IN=eth0 OUT= MAC=04:01:94:94:93:01:f8:c0:01:27:e4:f0:08:00 SRC=222.186.56.42 DST=45.55.46.168 LEN=40 TOS=0x00 PREC=0x00 TTL=103 ID=256 PROTO=TCP SPT=6000 DPT=22 WINDOW=16384 RES=0x00 SYN URGP=0 Mar 6 13:18:30 noctuamjuris dhclient[4666]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 (xid=0x5f3e977b) Mar 6 13:18:37 noctuamjuris dhclient[4666]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15 (xid=0x5f3e977b) Mar 6 13:18:52 noctuamjuris dhclient[4666]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15 (xid=0x5f3e977b) Mar 6 13:18:53 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 4 of 5 (IPv6 Configure Timeout) scheduled… Mar 6 13:18:53 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 4 of 5 (IPv6 Configure Timeout) started… Mar 6 13:18:53 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 4 of 5 (IPv6 Configure Timeout) complete. Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <warn> (eth1): DHCPv4 request timed out. Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): DHCPv4 state changed unknown -> timeout Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): canceled DHCP transaction, DHCP client pid 4666 Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): DHCPv4 state changed timeout -> done Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 4 of 5 (IPv4 Configure Timeout) scheduled… Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 4 of 5 (IPv4 Configure Timeout) started… Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): device state change: ip-config -> failed (reason ‘ip-config-unavailable’) [70 120 5] Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <warn> (eth1): Activation: failed for connection ‘Wired connection 1’ Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 4 of 5 (IPv4 Configure Timeout) complete. Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): device state change: failed -> disconnected (reason ‘none’) [120 30 0] Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): deactivating device (reason ‘none’) [0] Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> Auto-activating connection ‘Wired connection 1’. Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: starting connection ‘Wired connection 1’ Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) scheduled… Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) started… Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): device state change: disconnected -> prepare (reason ‘none’) [30 40 0] Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) scheduled… Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) complete. Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) starting… Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): device state change: prepare -> config (reason ‘none’) [40 50 0] Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) successful. Mar 6 13:19:06 noctuamjuris NetworkManager[563]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) complete.
and start over again …
Ken Loomis
lanbo
Azeem Cv
KFSys
doughboy
cos+digitalocean
Josep Esposito
Vivek V
Tony Rhoades
Wingrammer
gittyhubhubhub
Reaz NM