I am using dropwizard metrics meter to count the total number of requests my application receives. And i am pushing this meter data to influxdb which i want to show in grafana dashboard.
my influx db data looks like :-
time client cluster count fifteen-minute five-minute mean-minute one-minute server
---- ------ ------- ----- -------------- ----------- ----------- ---------- ------
1507235148003000000 OurImportantClient CL01 56992 50.678040360101775 99.52398667263071 172.70072682021265 80.00874252631192 localhost
1507235148033000000 OurImportantClient CL01 2177 60.95977917444668 31.29599463894603 6.596861684474326 0.717010283038515 localhost
1507235157999000000 OurImportantClient CL01 57604 50.7944205524674 98.26861507721358 169.42222449289022 77.14554982009743 localhost
1507235158033000000 OurImportantClient CL01 2177 60.28619734584058 30.269989895387145 6.40284451016588 0.6069361011507497 localhost
1507235168000000000 OurImportantClient CL01 58189 50.8795672749558 96.9648721158363 166.25254478413774 74.28375646281316 localhost
1507235168034000000 OurImportantClient CL01 2177 59.62005833421925 29.277621588246074 6.219878501675276 0.5137603178004709 localhost
1507235178001000000 OurImportantClient CL01 58764 50.95269899397442 95.67086847891309 163.2315524063629 71.7026680938437 localhost
1507235178032000000 OurImportantClient CL01 2177 58.96127989935249 28.317786983971164 6.047145479629095 0.43488871999209266 localhost .
When i am trying to display this in grafana i am seeing a weird graph. What is wrong in my query .
Related
On a Windows 10 system, I am trying to run a Docker containiner running geth which listens to port 8545. This docker-compose.yml has been tested to run perfectly on both Ubuntu and Mac OS X.
docker-compose version 1.21.1, build 7641a569 is being used on the Windows 10 system.
Problem: Docker throws an error after executing docker-compose up.
Fatal: Error starting protocol stack: listen unix /root/.ethereum/geth.ipc: bind: operation not permitted
What might be causing this error, and how can we solve it?
docker-compose.yml
version: '3'
services:
geth:
image: ethereum/client-go:latest
volumes:
- ./nodedata:/root/.ethereum
- ./files/genesis.json:/root/genesis.json:ro
ports:
- 30303:30303
- "30303:30303/udp"
- 8545:8545
- 8546:8546
command: --networkid 1337 --cache 512 --port 30303 --maxpeers 50 --rpc --rpcaddr "0.0.0.0" --rpcapi "eth,personal,web3,net" --bootnodes enode://0b37f58139bef9fef04ff50c1d2d95acade0b6989433ed2148683f294a12e8ca7eb17915864a0dd61d5533e898b7040b75df1a17cca27e90d106f95dea255b45#167.99.55.99:30303
container_name: geth-nosw
Output after running docker-compose up
Starting geth-node ... done
Attaching to geth-node
geth-node | INFO [07-22|20:43:11.482] Maximum peer count ETH=50 LES=0 total=50
geth-node | INFO [07-22|20:43:11.488] Starting peer-to-peer node instance=Geth/v1.8.13-unstable-526abe27/linux-amd64/go1.10.3
geth-node | INFO [07-22|20:43:11.488] Allocated cache and file handles database=/root/.ethereum/geth/chaindata cache=384 handles=1024
geth-node | INFO [07-22|20:43:11.521] Initialised chain configuration config="{ChainID: 1337 Homestead: 1 DAO: <nil> DAOSupport: false EIP150: 2 EIP155: 3 EIP158: 3 Byzantium: 4 Constantinople: <nil> Engine: clique}"
geth-node | INFO [07-22|20:43:11.521] Initialising Ethereum protocol versions="[63 62]" network=1366
geth-node | INFO [07-22|20:43:11.524] Loaded most recent local header number=0 hash=b85de5…3971b4 td=1
geth-node | INFO [07-22|20:43:11.524] Loaded most recent local full block number=0 hash=b85de5…3971b4 td=1
geth-node | INFO [07-22|20:43:11.524] Loaded most recent local fast block number=0 hash=b85de5…3971b4 td=1
geth-node | INFO [07-22|20:43:11.525] Loaded local transaction journal transactions=0 dropped=0
geth-node | INFO [07-22|20:43:11.530] Regenerated local transaction journal transactions=0 accounts=0
geth-node | INFO [07-22|20:43:11.530] Starting P2P networking
geth-node | INFO [07-22|20:43:13.670] UDP listener up self=enode://3e0e8e9a886a347fffb0150e670b45c8ae19f0f87ebb6d3fa0f7f312f17220b426913ac96df9527ae0ca00138c9e50ffe646255d5655e6023c47ef10aabf0224#[::]:30303
geth-node | INFO [07-22|20:43:13.672] Stats daemon started
geth-node | INFO [07-22|20:43:13.674] RLPx listener up self=enode://3e0e8e9a886a347fffb0150e670b45c8ae19f0f87ebb6d3fa0f7f312f17220b426913ac96df9527ae0ca00138c9e50ffe646255d5655e6023c47ef10aabf0224#[::]:30303
geth-node | INFO [07-22|20:43:13.676] Blockchain manager stopped
geth-node | INFO [07-22|20:43:13.677] Stopping Ethereum protocol
geth-node | INFO [07-22|20:43:13.677] Ethereum protocol stopped
geth-node | INFO [07-22|20:43:13.677] Transaction pool stopped
geth-node | INFO [07-22|20:43:13.681] Database closed database=/root/.ethereum/geth/chaindata
geth-node | INFO [07-22|20:43:13.681] Stats daemon stopped
geth-node | Fatal: Error starting protocol stack: listen unix /root/.ethereum/geth.ipc: bind: operation not permitted
geth-node | Fatal: Error starting protocol stack: listen unix /root/.ethereum/geth.ipc: bind: operation not permitted
geth-node exited with code 1
The problem is that you cannot create a unix socket on a volume that is linked to a windows file system.
Here's a link on how to work around that.
I am trying to configure hyperledger fabric network.
I run three zookeepers, three kafkas, three orderers and a couchdb.
They are docker containers and work well. All containers are in the same docker network called ibknet.
After that, I run peer container but it has a problem to detect couchdb container while its starting. Here is my command to run peer container.
docker run -d --name main.stock.ibk.com --hostname main.stock.ibk.com \
-p 7051:7051 \
-p 7053:7053 \
-e CORE_LEDGER_STATE_STATEDATABASE=CouchDB \
-e CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0:5984 \
--network ibknet hyperledger/fabric-peer:x86_64-1.0.4
Here is the list of running docker containers before executing the command above.
0b49e1d9e135 hyperledger/fabric-couchdb:x86_64-1.0.4 "tini -- /docker-e..." 28 minutes ago Up 28 minutes 4369/tcp, 5984/tcp, 9100/tcp couchdb0
592e81a721f1 hyperledger/fabric-orderer:x86_64-1.0.4 "orderer" 28 minutes ago Up 28 minutes 0.0.0.0:9050->7050/tcp orderer2
5a0d0f05770d hyperledger/fabric-orderer:x86_64-1.0.4 "orderer" 28 minutes ago Up 28 minutes 0.0.0.0:8050->7050/tcp orderer1
681894ae835a hyperledger/fabric-orderer:x86_64-1.0.4 "orderer" 28 minutes ago Up 28 minutes 0.0.0.0:7050->7050/tcp orderer0
2c1910c3e293 hyperledger/fabric-kafka:x86_64-1.0.4 "/docker-entrypoin..." 28 minutes ago Up 28 minutes 9092-9093/tcp kafka2
b27ff82abd3d hyperledger/fabric-kafka:x86_64-1.0.4 "/docker-entrypoin..." 29 minutes ago Up 28 minutes 9092-9093/tcp kafka1
2f84d000c2d6 hyperledger/fabric-kafka:x86_64-1.0.4 "/docker-entrypoin..." 29 minutes ago Up 28 minutes 9092-9093/tcp kafka0
25438ef57579 hyperledger/fabric-zookeeper:x86_64-1.0.4 "/docker-entrypoin..." 29 minutes ago Up 29 minutes 2181/tcp, 2888/tcp, 3888/tcp zookeeper2
c01262ae099e hyperledger/fabric-zookeeper:x86_64-1.0.4 "/docker-entrypoin..." 29 minutes ago Up 29 minutes 2181/tcp, 2888/tcp, 3888/tcp zookeeper1
f95e92b10b25 hyperledger/fabric-zookeeper:x86_64-1.0.4 "/docker-entrypoin..." 29 minutes ago Up 29 minutes 2181/tcp, 2888/tcp, 3888/tcp zookeeper0
And I got this error messages in docker logs when I run the peer container.
2017-12-01 07:26:34.238 UTC [ledgermgmt] initialize -> INFO 002 Initializing ledger mgmt
2017-12-01 07:26:34.238 UTC [kvledger] NewProvider -> INFO 003 Initializing ledger provider
2017-12-01 07:26:34.624 UTC [couchdb] handleRequest -> WARN 004 Retrying couchdb request in 125ms. Attempt:1 Error:Get http://couchdb0:5984/: dial tcp 75.126.101.240:5984: getsockopt: connection refused
2017-12-01 07:26:34.987 UTC [couchdb] handleRequest -> WARN 005 Retrying couchdb request in 250ms. Attempt:2 Error:Get http://couchdb0:5984/: dial tcp 75.126.101.240:5984: getsockopt: connection refused
2017-12-01 07:26:35.533 UTC [couchdb] handleRequest -> WARN 006 Retrying couchdb request in 500ms. Attempt:3 Error:Get http://couchdb0:5984/: dial tcp 75.126.101.240:5984: getsockopt: connection refused
2017-12-01 07:26:36.279 UTC [couchdb] handleRequest -> WARN 007 Retrying couchdb request in 1s. Attempt:4 Error:Get http://couchdb0:5984/: dial tcp 75.126.101.240:5984: getsockopt: connection refused
2017-12-01 07:26:37.617 UTC [couchdb] handleRequest -> WARN 008 Retrying couchdb request in 2s. Attempt:5 Error:Get http://couchdb0:5984/: dial tcp 75.126.101.240:5984: getsockopt: connection refused
2017-12-01 07:26:39.819 UTC [couchdb] handleRequest -> WARN 009 Retrying couchdb request in 4s. Attempt:6 Error:Get http://couchdb0:5984/: dial tcp 75.126.101.240:5984: getsockopt: connection refused
2017-12-01 07:26:44.019 UTC [couchdb] handleRequest -> WARN 00a Retrying couchdb request in 8s. Attempt:7 Error:Get http://couchdb0:5984/: dial tcp 75.126.101.240:5984: getsockopt: connection refused
2017-12-01 07:26:52.279 UTC [couchdb] handleRequest -> WARN 00b Retrying couchdb request in 16s. Attempt:8 Error:Get http://couchdb0:5984/: dial tcp 75.126.101.240:5984: getsockopt: connection refused
2017-12-01 07:27:08.515 UTC [couchdb] handleRequest -> WARN 00c Retrying couchdb request in 32s. Attempt:9 Error:Get http://couchdb0:5984/: dial tcp 75.126.101.240:5984: getsockopt: connection refused
2017-12-01 07:27:40.730 UTC [couchdb] handleRequest -> WARN 00d Retrying couchdb request in 1m4s. Attempt:10 Error:Get http://couchdb0:5984/: dial tcp 75.126.101.240:5984: getsockopt: connection refused
panic: Error in instantiating ledger provider: Unable to connect to CouchDB, check the hostname and port: Get http://couchdb0:5984/: dial tcp 75.126.101.240:5984: getsockopt: connection refused
What do I miss? And I have no idea that where 75.126.101.240 address is from.
Actually, I could succeed in running it with --add-host option by mentioning exactly ip. But I don't think that is a proper way because ip is changing whenever I start docker servers.
Please help this issue. Thanks.
Try adding : "--dns-search ." to the docker run command. The resolver on your host system is likely configured to append / search a domain for unknown hosts. "--dns-search ." should force resolution only via the embedded Docker DNS
I've installed a neo4j database on a Google Cloud Compute instance and am wanting to connect to the database from my laptop.
[1] I have neo4j running on Google Cloud
● neo4j.service - Neo4j Graph Database
Loaded: loaded (/lib/systemd/system/neo4j.service; disabled; vendor preset: enabled)
Active: active (running) since Sat 2017-09-30 09:33:39 UTC; 1h 3min ago
Main PID: 2099 (java)
Tasks: 41
Memory: 504.5M
CPU: 18.652s
CGroup: /system.slice/neo4j.service
└─2099 /usr/bin/java -cp /var/lib/neo4j/plugins:/etc/neo4j:/usr/share/neo4j/lib/*:/var/lib/neo4j/plugins/* -server -XX:+UseG1GC -XX:-OmitStackTraceInFastThrow -XX:+AlwaysPreTouch -XX:+U
nlockExperimentalVMOptions -XX:+TrustFinalNonStaticFields -XX:+DisableExplicitGC -Djdk.tls.ephemeralDHKeySize=2048 -Dunsupported.dbms.udc.source=debian -Dfile.encoding=UTF-8 org.neo4j.server.Commu
nityEntryPoint --home-dir=/var/lib/neo4j --config-dir=/etc/neo4j
Sep 30 09:33:40 neo4j-graphdb-server neo4j[2099]: certificates: /var/lib/neo4j/certificates
Sep 30 09:33:40 neo4j-graphdb-server neo4j[2099]: run: /var/run/neo4j
Sep 30 09:33:40 neo4j-graphdb-server neo4j[2099]: Starting Neo4j.
Sep 30 09:33:42 neo4j-graphdb-server neo4j[2099]: 2017-09-30 09:33:42.948+0000 INFO ======== Neo4j 3.2.5 ========
Sep 30 09:33:42 neo4j-graphdb-server neo4j[2099]: 2017-09-30 09:33:42.988+0000 INFO Starting...
Sep 30 09:33:44 neo4j-graphdb-server neo4j[2099]: 2017-09-30 09:33:44.308+0000 INFO Bolt enabled on 127.0.0.1:7687.
Sep 30 09:33:47 neo4j-graphdb-server neo4j[2099]: 2017-09-30 09:33:47.043+0000 INFO Started.
Sep 30 09:33:48 neo4j-graphdb-server neo4j[2099]: 2017-09-30 09:33:48.160+0000 INFO Remote interface available at http://localhost:7474/
Sep 30 09:39:17 neo4j-graphdb-server neo4j[2099]: 2017-09-30 09:39:17.918+0000 WARN badMessage: 400 No URI for HttpChannelOverHttp#27d4a9b{r=0,c=false,a=IDLE,uri=-}
Sep 30 09:46:18 neo4j-graphdb-server neo4j[2099]: 2017-09-30 09:46:18.374+0000 WARN badMessage: 400 for HttpChannelOverHttp#6cbed0ca{r=0,c=false,a=IDLE,uri=-}
[2] I've created a firewall rule on Google Cloud to allow external access to the DB server
The network tag of "google-db-server" has been added to the Google Cloud Compute server.
My expectation is that the rule below will allow any external machine to connect to port 7474 on the Google Cloud Compute instance
user#machine:~/home$ gcloud compute firewall-rules create custom-allow-neo4j --action ALLOW --rules tcp:7474 --description "Enable access to the neo4j database" --direction IN --target-tags google-db-server
user#machine:~/home$ gcloud compute firewall-rules list --format json
[
{
"allowed": [
{
"IPProtocol": "tcp",
"ports": [
"7474"
]
}
],
"creationTimestamp": "2017-09-30T00:25:51.220-07:00",
"description": "Enable access to the neo4j database",
"direction": "INGRESS",
"id": "5767618134171383824",
"kind": "compute#firewall",
"name": "custom-allow-neo4j",
"network": "https://www.googleapis.com/compute/v1/projects/graphdb-experiment/global/networks/default",
"priority": 1000,
"selfLink": "https://www.googleapis.com/compute/v1/projects/graphdb-experiment/global/firewalls/custom-allow-neo4j",
"sourceRanges": [
"0.0.0.0/0"
],
"targetTags": [
"google-db-server"
]
},
[3] Running nmap from the Google Cloud server instance shows that port 7474 is available locally, and I can telnet to that port locally
google_user#google-db-server:~$ nmap -p 22,80,443,7474 localhost
Starting Nmap 7.01 ( https://nmap.org ) at 2017-09-30 10:46 UTC
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000081s latency).
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
443/tcp closed https
7474/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds
google-user#google-db-server:~$ telnet localhost 7474
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
[4] However I am unable to connect from my laptop and nmap shows port 7474 as unavailable
user#machine:~/home$ nmap -p 22,80,443,7474 35.201.26.52
Starting Nmap 7.01 ( https://nmap.org ) at 2017-09-30 20:50 AEST
Nmap scan report for 52.26.201.35.bc.googleusercontent.com (35.201.26.52)
Host is up (0.28s latency).
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
443/tcp closed https
7474/tcp closed unknown
Nmap done: 1 IP address (1 host up) scanned in 0.75 seconds
So despite the firewall rule being created to allow any IP address to connect to the Google Cloud Compute instance on tcp:7474, I'm still unable to access this port from my laptop.
Am I missing some additional steps?
It looks like neo4j is only listening on the loopback interface. This means it only accepts connections from the same machine. You can verify this by running sudo netstat -lntp. If you see 127.0.0.1:7474, it's only listening on loopback. It should be 0.0.0.0:7474.
you can fix this in the neo4j config by setting dbms.connector.bolt.listen_address to 0.0.0.0:7474. Your Linux distribution may also have a different place to set this configuration.
Following the documentation for telegraph v0.13, we try to launch the telegraph instance in terminal:
telegraf -config telegraf.conf
Note the Database creation failed:
Get http://localhost:8086/query?db=&q=CREATE+DATABASE+IF+NOT+EXISTS+%22telegraf%22: dial tcp 127.0.0.1:8086: getsockopt: connection refused
How to fix? Is it a firewall problem?
The error is visible in the log in the terminal output:
2016/07/27 22:15:11 Starting Telegraf (version 0.13.1)
2016/07/27 22:15:11 Loaded outputs: influxdb
2016/07/27 22:15:11 Loaded inputs: cpu mem
2016/07/27 22:15:11 Tags enabled: host=johns-MacBook-Pro-2.local
2016/07/27 22:15:11 Agent Config: Interval:10s, Debug:false, Quiet:false, Hostname:"johns-MacBook-Pro-2.local", Flush Interval:10s
2016/07/27 22:15:30 Output [influxdb] buffer fullness: 11 / 10000 metrics. Total gathered metrics: 11. Total dropped metrics: 0.
2016/07/27 22:15:30 Database creation failed: Get http://localhost:8086/query?db=&q=CREATE+DATABASE+IF+NOT+EXISTS+%22telegraf%22: dial tcp 127.0.0.1:8086: getsockopt: connection refused
2016/07/27 22:15:30 Error writing to output [influxdb]: Could not write to any InfluxDB server in cluster
2016/07/27 22:15:40 Output [influxdb] buffer fullness: 21 / 10000 metrics. Total gathered metrics: 21. Total dropped metrics: 0.
2016/07/27 22:15:40 Database creation failed: Get http://localhost:8086/query?db=&q=CREATE+DATABASE+IF+NOT+EXISTS+%22telegraf%22: dial tcp 127.0.0.1:8086: getsockopt: connection refused
Okay, wasn't a port issue. influxdb wasn't running properly
I have a CentOS 6 server.
Now to install Gigablast search engine on it.
I follow this guide case for ReadHat. http://www.gigablast.com/faq.html#src
After run make -j 4. I run './gb 0' to start your a single gigablast node.
Then I access to my server via IP address: x.x.x.x:8000, but I get message "This webpage is not available"
Could someone tell me why I get this error.
I can't see the error in my log file.
And this is my log content.
db: Logging to file /dev/stderr.
db: Use 'gb -d' to run as daemon. Example: gb -d
1447962510128 000 conf: Gigablast Version: Nov 19 2015 19:37:46
1447962510128 000 conf: Gigablast Architecture: 64-bit
1447962510128 000 host: Working directory is /root/open-source-search-engine-master/
1447962510128 000 host: Using /root/open-source-search-engine-master/hosts.conf
1447962510128 000 host: Process ID is 9751
1447962510128 000 host: Detected local ip 127.0.0.1
1447962510128 000 host: Detected local ip x.x.x.x
1447962510128 000 host: Running as host id #0
1447962510374 000 wikt: Loading /root/open-source-search-engine-master/wiktionary-syns.dat
1447962510499 000 wikt: Loading /root/open-source-search-engine-master/wiktionary-buf.txt
1447962510552 000 wikt: test "love" -> "en|love,loved,loving,loves"
1447962510552 000 wiki: Loading /root/open-source-search-engine-master/wikititles2.dat
1447962510635 000 mem: addMem(100663296): tbl-wiki. ptr=0x7fcbfa33e014 used=127113172
1447962510727 000 db: Loading conf for collection main (0)
1447962510997 000 mem: addMem(349869920): buckets-posdb. ptr=0x7fcbe4b1d014 used=238787108
1447962511145 000 mem: addMem(193164080): mem-titledb. ptr=0x7fcbd8bce014 used=596421652
1447962511629 000 mem: addMem(100000022): mem-spiderdb. ptr=0x7fcbc4273014 used=1035055046
1447962511950 000 db: Verifying shard parity for posdb of 64000 bytes for coll main (collnum=0)...
1447962511950 000 db: Verifying shard parity for titledb of 640000 bytes for coll main (collnum=0)...
1447962511950 000 db: Verifying shard parity for tagdb of 64000 bytes for coll main (collnum=0)...
1447962511950 000 db: Verifying shard parity for clusterdb of 64000 bytes for coll main (collnum=0)...
1447962511950 000 db: Verifying shard parity for linkdb of 64000 bytes for coll main (collnum=0)...
1447962511950 000 db: Verifying shard parity for spiderdb of 64000 bytes for coll main (collnum=0)...
1447962511950 000 db: Verifying shard parity for doledb of 64000 bytes for coll main (collnum=0)...
1447962512158 000 mem: addMem(109051904): udictht. ptr=0x7fcbac23c014 used=1429646307
1447962512161 000 table: grewtable udictht from 2097152 to 8388608 slots in 78 ms (this=0x1be9ba0) (used=0)
1447962512530 000 gb: unifiedDict-buf.txt or unifiedDict-map.dat checksum is not approved for live service (1974148069587949864 != -14450509118443930)
1447962512530 000 speller: turning off spell checking for now
1447962512593 000 mem: addMem(109051904): tbl-lang. ptr=0x7fcba5a3b014 used=1511435235
1447962512594 000 lang: Successfully Loaded 0 Language Lists and 0 duplicate word hashes.
1447962512594 000 cat: Error opening structure file: /root/open-source-search-engine-master/catdb/gbdmoz.structure.dat
1447962512594 000 cat: Loading Categories From /root/open-source-search-engine-master/catdb/gbdmoz.structure.dat Failed.
1447962512594 000 cat: Loaded Categories From /root/open-source-search-engine-master/catdb/gbdmoz.structure.dat.
1447962512595 000 admin: Loading hashtable from /root/open-source-search-engine-master/catcountry.dat
1447962512614 000 autoban: read 0 entries
1447962512649 000 udp: Listening on UDP port 9000 with niceness=2 and fd=3.
1447962512649 000 db: Loading cache from /root/open-source-search-engine-master//dns.cache
1447962512653 000 udp: Listening on UDP port 5998 with niceness=1 and fd=4.
1447962512653 000 dns: Sending requests on client port 5998 using socket descriptor 4.
1447962512653 000 dns: Using nameserver 8.8.8.8:53.
1447962512653 000 dns: Using nameserver 8.8.4.4:53.
1447962512658 000 https: Reading SSL certificate from: /root/open-source-search-engine-master/gb.pem
1447962512659 000 http: Listening on TCP port 8000 with sd=5
1447962512659 000 https: Listening on TCP port 7000 with sd=6
1447962512670 000 build: Loading 8 bytes from /root/open-source-search-engine-master/addsinprogress.dat
1447962512686 000 db: gb is now ready
1447962512737 000 spider: made spidercoll=7925150 for cr=2501800
1447962512738 000 spider: hit spider queue rebuild timeout for main (0)
1447962512738 000 spider: rebuild complete for main. Added 0 recs to waiting tree, scanned 0 bytes of spiderdb.
1447962512778 000 gb: clock is now synced with host #0.
1447962519926 000 thread: Using 36708352 bytes for 20 thread stacks.
gigablast starts on server on port 8000 by default, try changing your port to 8000
http://x.x.x.x:8000