A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
We are looking to run a few droplets to server some video content using wowza streaming software. But the network performance seems low. We want to server about 300 people video at 3Mbps. We planed on creating 4 or 5 servers to do this but from the test so far we see upload sppeds as low at 20Mbs to 189Mbs. Is this normal for a droplet?
I’m using this SW. The AMI and it’s perfect. Work as should.
This AMI should be a HVM type(not paravirtualization) to perform 10Gbps on VPC with enhanced network on c3.8xlarge. 1 star less
Support is slow. I’m trying to reach them on support@wowza and still don’t have an answer about origin/edge with adaptive bitrate(SMIL) configurations for 2 days. One more star less.
I am sure that this program will be great to use if the people at Weiss will streamline access more efficiently. After paying for and spin up an instance with using the 1-Click feature in the marketplace, I couldn’t access to the streaming enginemanager http://[wowza-ip-address]:8088/enginemanager ( of course I replaced the wowza ip address). I read and performed every step and was not able to get into that page. The assistance of custom essay writing service helps students understand the basics of every custom written paper, as well as the elements of creative writing.
Hi, I created my first droplet couple of days back on Banglore DC. I am trying to access same from USA and it looks like it shows very high lag. Also using it via ssh with lags make it difficult to use. Following are snippet of ping command. Just to know if changing my DC to Asia or Europe would solve this problem? PING XXX.XX.XX.XX (XXX.XX.XX.XX): 56 data bytes Request timeout for icmp_seq 0 64 bytes from XXX.XX.XX.XX: icmp_seq=0 ttl=46 time=1009.562 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=1 ttl=46 time=1007.247 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=2 ttl=46 time=1006.057 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=3 ttl=46 time=1004.836 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=4 ttl=46 time=1004.675 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=5 ttl=46 time=1008.498 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=6 ttl=46 time=1009.231 ms Request timeout for icmp_seq 8 64 bytes from XXX.XX.XX.XX: icmp_seq=8 ttl=46 time=1009.095 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=9 ttl=46 time=1008.378 ms Request timeout for icmp_seq 11 64 bytes from XXX.XX.XX.XX: icmp_seq=11 ttl=46 time=1008.870 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=12 ttl=46 time=1006.362 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=13 ttl=46 time=1006.554 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=14 ttl=46 time=1007.753 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=15 ttl=46 time=1005.372 ms Request timeout for icmp_seq 17 64 bytes from XXX.XX.XX.XX: icmp_seq=17 ttl=46 time=1006.765 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=18 ttl=46 time=1006.453 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=19 ttl=46 time=1007.759 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=20 ttl=46 time=1005.189 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=21 ttl=46 time=1004.227 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=22 ttl=46 time=1006.418 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=23 ttl=46 time=278.888 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=24 ttl=46 time=1008.178 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=25 ttl=46 time=1004.993 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=26 ttl=46 time=281.633 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=27 ttl=46 time=1007.910 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=28 ttl=46 time=289.008 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=29 ttl=46 time=1006.386 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=30 ttl=46 time=1004.721 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=31 ttl=46 time=771.703 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=32 ttl=46 time=1006.595 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=33 ttl=46 time=1006.524 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=34 ttl=46 time=1008.401 ms 64 bytes from XXX.XX.XX.XX: icmp_seq=35 ttl=46 time=1004.929 ms ^C --- XXX.XX.XX.XX ping statistics --- 37 packets transmitted, 33 packets received, 10.8% packet loss round-trip min/avg/max/stddev = 278.888/933.914/1009.562/209.688 ms
Hello I am building out an infrastructure for an application that my team is building. I currently have 4 droplets (may end up being 5 droplets) each running Ubuntu 16.04. I have one droplet acting as a reverse proxy server (running NGINX), one droplet acting as my Application server, one application acting as my Database Server and one droplet is a Continuous Integration server (running jenkins). I want to make sure that all but the reverse proxy server are only accessible over the Private network that you guys provide. How ever, I obviously still want to be able to access these droplets even though they are only accessible on private Networking. How could I do this? Do I need to setup openVPN and have that connect to the your Private Networking or what? Thanks for your help!
Hello, I have four subdomains. First two subdomains are set with wildcard *.static.MYSITE.com and .*v2.MYSITE.COM Another two subdomains are set without wildcard test.z3lab.info, cms.z3lab.info Which subdomains are more correct, and why do we use wildcard? This is my zone file ``` $ORIGIN z3lab.info. $TTL 1800 z3lab.info. IN SOA ns1.digitalocean.com. hostmaster.z3lab.info. 1472229537 10800 3600 604800 1800 z3lab.info. 1800 IN NS ns1.digitalocean.com. z3lab.info. 1800 IN NS ns2.digitalocean.com. z3lab.info. 1800 IN NS ns3.digitalocean.com. z3lab.info. 1800 IN A 46.101.197.231 *.static.z3lab.info. 1800 IN CNAME z3lab.info. *.v2.z3lab.info. 1800 IN CNAME z3lab.info. test.z3lab.info. 1800 IN CNAME z3lab.info. cms.z3lab.info. 1800 IN CNAME z3lab.info. ```
How To Set Up an NFS Mount on Ubuntu 16.04 Posted Aug 4, 2016 9.7k views Networking Ubuntu Ubuntu 16.04 ============================================ Question for: https://www.digitalocean.com/community/questions What does nfs-server.service code=exited status=22 mean? [using M. Anderson's tutorial] =============================================== Log: SetUp NFS Mount Ubuntu 16.04 ============================================== This tutorial has gotten me further in getting one Ubuntu 16.04 to file share than the other 5 or so, good writing! Have searched and found no mention of status=22 here or at Ask.Ubuntu. [file folders /status/22/ for another program. ] other nfs-server.service questions do not seem to apply to this situation. # This is a home office LAN with 1 Ubuntu HP 220-110z tower and 1 Ubuntu HP Laptop and one Win 10 Laptop. [connecting with Win 10 is another matter.] # Remote superuser not wanted. I have been following M. Anderson's tutorial at: https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nfs-mount-on-ubuntu-16-04 I did not know what was needed so I included I hope not too much. I successfully completed up to Step 3 — Configuring the NFS Exports on the Host Server Brief list of commands completed: ``` Host:~$ sudo apt-get update Host:~$ sudo apt-get install nfs-kernel-server Client:~$ sudo apt-get update Client:~$ sudo apt-get install nfs-common Host:~$ sudo mkdir /var/nfs/general -p Host:~$ sudo chown nobody:nogroup /var/nfs/general Host:~$ ls -la /var/nfs/general total 8 drwxr-xr-x 2 nobody nogroup 4096 Sep 23 21:44 . drwxr-xr-x 3 root root 4096 Sep 23 21:44 .. # for Win10 Laptop Host:~$ ls -la /home total 12 drwxr-xr-x 4 root root 4096 Jul 20 19:48 . drwxr-xr-x 24 root root 4096 Sep 24 04:31 .. drwxr-xr-x 34 luigiwriter luigiwriter 4096 Sep 25 01:38 luigiwriter # for Ubuntu 16.04 Tower Host:~$ sudo sudo nano /etc/exports /var/nfs/general 192.168.200.255(rw, sync, no_subtree_check) /home 192.168.200.208(rw, sync, no_subtree_check) ^O ^X Host:~$ sudo ufw status Status: active To Action From -- ------ ---- 2049 ALLOW 192.168.200.255 ``` The Failure Error message occured here. ``` # ================================================================ Host:~$ sudo systemctl restart nfs-kernel-server Job for nfs-server.service failed because the control process exited with error code. See "systemctl status nfs-server.service" and "journalctl -xe" for details. ``` DETAILS ``` # ================================================================ Host:~$ sudo systemctl status nfs-server.service # ---------------------------------------------------------------- * nfs-server.service - NFS server and services Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor pre Active: FAILED (Result: exit-code) since Sun 2016-09-25 01:33:13 EDT; 57s a <<---* Process: 5531 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCC Process: 5525 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUC Process: 5522 ExecStop=/usr/sbin/rpc.nfsd 0 (code=exited, status=0/SUCCESS) Process: 1181 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status <<---*status=0 Process: 5825 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=22) <<---*status=22 Main PID: 1181 (code=exited, status=0/SUCCESS) Sep 25 01:33:13 Hostsystemd[1]: Starting NFS se Sep 25 01:33:13 Hostexportfs[5825]: exportfs: / Sep 25 01:33:13 Hostsystemd[1]: nfs-server.serv Sep 25 01:33:13 Hostsystemd[1]: FAILED TO START <<---* Sep 25 01:33:13 Hostsystemd[1]: nfs-server.serv Sep 25 01:33:13 Hostsystemd[1]: nfs-server.serv # EOF ---------- # ================================================================ Host:~$ sudo journalctl -xe # ---------------------------------------------------------------- # Sep 25 01:32:13 is when the failure started. Sep 25 01:32:13 Hostsudo[5796]: pam_unix(sudo:session): sessi Sep 25 01:33:13 Hostsudo[5816]: [Host:] TTY=pts/17 ; PW Sep 25 01:33:13 Hostsudo[5816]: pam_unix(sudo:session): sessi Sep 25 01:33:13 Hostsystemd[1]: Stopped NFS server and servic -- Unit nfs-server.service has finished shutting down. <<---* # In the following, Most repetative lines have been deleted, # For example when the -- Subject: and following line are the same message. # Also deleted the following two lines from each entry: # -- Defined-By: systemd # -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel Sep 25 01:33:13 Hostsystemd[1]: Starting NFS Mount Daemon... -- Unit nfs-mountd.service has begun starting up. Sep 25 01:33:13 Hostsystemd[1]: Starting NFSv4 ID-name mappin -- Unit nfs-idmapd.service has begun starting up. Sep 25 01:33:13 Hostsystemd[1]: Started NFSv4 ID-name mapping -- Unit nfs-idmapd.service has finished starting up. -- The start-up result is done. Sep 25 01:33:13 Hostrpc.mountd[5824]: Version 1.2.8 starting Sep 25 01:33:13 Hostsystemd[1]: Started NFS Mount Daemon. -- Unit nfs-mountd.service has finished starting up. -- The start-up result is done. Sep 25 01:33:13 Hostsystemd[1]: Starting NFS server and servi # NO FAILURE MESSAGES BEFORE THIS POINT in Journalctl. -- -- Unit nfs-server.service has begun starting up. Sep 25 01:33:13 Hostexportfs[5825]: exportfs: /etc/exports:1: Sep 25 01:33:13 Hostsystemd[1]: nfs-server.service: Control p Sep 25 01:33:13 Hostsystemd[1]: FAILED TO START NFS SERVER AN <<---* -- UNIT NFS-SERVER.SERVICE HAS FAILED. <<---*status=22 -- The result is failed. Sep 25 01:33:13 Hostsystemd[1]: nfs-server.service: Unit ente Sep 25 01:33:13 Hostsystemd[1]: nfs-server.service: Failed wi <<---* Sep 25 01:33:13 Hostrpc.mountd[5824]: Caught signal 15, un-re <<---* Sep 25 01:33:13 Hostsystemd[1]: Stopping NFS Mount Daemon... <<---* -- Subject: Unit nfs-mountd.service has begun shutting down -- -- Unit nfs-mountd.service has begun shutting down. Sep 25 01:33:13 Hostsystemd[1]: Stopping NFSv4 ID-name mappin -- -- Unit nfs-idmapd.service has begun shutting down. Sep 25 01:33:13 Hostsudo[5816]: pam_unix(sudo:session): sessi Sep 25 01:33:13 Hostsystemd[1]: Stopped NFS Mount Daemon. -- Unit nfs-mountd.service has finished shutting down. -- Sep 25 01:33:13 Hostsystemd[1]: Stopped NFSv4 ID-name mapping -- Unit nfs-idmapd.service has finished shutting down. ``` # This Section repeats 4 times with identical results ----------------------- ``` Sep 25 01:34:03 Hostkernel: [UFW BLOCK] IN=enp2s0 OUT= MAC=01:00:5e:00:00:01:a Sep 25 01:36:08 Hostkernel: [UFW BLOCK] IN=enp2s0 OUT= MAC=01:00:5e:00:00:01:a Sep 25 01:36:54 Hostsystemd[1]: Starting Automatically refresh installed snaps -- -- Unit snapd.refresh.service has begun starting up. Sep 25 01:36:55 Host/usr/lib/snapd/snapd[1019]: store.go:539: DEBUG: cannot se Sep 25 01:36:55 Host/usr/lib/snapd/snapd[1019]: daemon.go:170: DEBUG: uid=0;@ Sep 25 01:36:55 Hostsnap[5858]: [4B blob data] Sep 25 01:36:55 Hostsnap[5858]: All snaps up to date. Sep 25 01:36:55 Hostsystemd[1]: Started Automatically refresh installed snaps. -- Unit snapd.refresh.service has finished starting up. -- -- The start-up result is done. Sep 25 01:36:55 Hostsystemd[1]: snapd.refresh.timer: Adding 3h 59.727602s rand Sep 25 01:36:55 Hostsystemd[1]: snapd.refresh.timer: Adding 58.845634s random Sep 25 01:38:13 Hostkernel: [UFW BLOCK] IN=enp2s0 OUT= MAC=01:00:5e:00:00:01:a lines 2256-2284/2284 (END) Sep 25 01:33:13 Hostsystemd[1]: Stopped NFSv4 ID-name mapping service. -- Subject: Unit nfs-idmapd.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Unit nfs-idmapd.service has finished shutting down. # End of repeating section ---------------------------------------------------- Sep 25 01:36:55 Hostsystemd[1]: snapd.refresh.timer: Adding 3h 59.727602s random Sep 25 01:36:55 Hostsystemd[1]: snapd.refresh.timer: Adding 58.845634s random tim Sep 25 01:38:13 Hostkernel: [UFW BLOCK] IN=enp2s0 OUT= MAC=01:00:5e:00:00:01:a0:e lines 2256-2284/2284 (END) ``` ``` # =============================================== Tried again here: Host:~$ sudo systemctl restart nfs-kernel-server Job for nfs-server.service failed because the control process exited with error code. See "systemctl status nfs-server.service" and "journalctl -xe" for details. Host:~$ ```