How to find out which version of Redis is running in PCF DEV? I'm using the latest PCF DEV 1.2.0 for PAS 2.4.4 and created the service as per the docs, like this:
cf cs p.redis cache-small redis
It is running, and I have some app talking to it. Now I just want to know which version it is.
I found a way with the help of a colleague: First, find out the hostname, port and password by querying the environment of the application which is successfully connected to Redis with cf env [APP-NAME]. The relevant chunk looks like this:
"VCAP_SERVICES": {
"p.redis": [
{
"binding_name": null,
"credentials": {
"host": "q-s0.redis-instance.default.service-instance-deadbeef-8008.bosh",
"password": "THXQCcElifUCCbJD2RlU7tgjZegmkn",
"port": 6379
},
(...)
Now, SSH into the apps container with cf ssh [APP-NAME] and use Netcat to connect to Redis:
vcap#...:~$ nc q-s0.redis-instance.default.service-instance-deadbeef-8008.bosh 6379
Then use AUTH and the password to "login"...
AUTH THXQCcElifUCCbJD2RlU7tgjZegmkn
+OK
...and issue the INFO command - the Redis version is displayed right at the top:
INFO
$3365
# Server
redis_version:5.0.2
(...)
Anyway, this is likely very much work for a tiny bit of information - are there other ways?
Related
I am trying out okd but it fails for me during the oc cluster up port check step. The debug output is not very verbose to be polite. Do you have an idea what to look for.
$ oc cluster up
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Checking type of volume mount ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
Checking if required ports are available ...
error: a port needed by OpenShift is not available
But the required ports 53 and 8443 are not taken
sudo netstat -tulpn | grep '\(:8443\|:53\)'
At least netstat returns nothing
Versions:
$ oc version
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
and
CentOS Linux release 7.6.1810 (Core)
I have not been able to find out how to turn debugging on so that it is possible to see what it really checks for.
Has the user you are running the command as enough priveledges to open privileged ports (ports <1024) on your host machine?
try running cluster up as root or with sudo
yes I starting whole okd as root user
I created the Ubuntu virtual machine on that I created the Go environment after that I successfully imported and installed the skx/dns-api-go
I followed this doc: https://github.com/skx/dns-api-go for to set up the environment also I installed the required dependencies like
Dancer,Plack::Middle ware::Throttle::Lite,Net::DNS::Resolver,twiggy,
libdancer-perl ,libnet-cidr-lite-perl ,
libplack-middleware-reverseproxy-perl.
after that, at last, I run the following command:
dns-api-go -redis-server localhost:6379
then am getting the following result :
Launching the server on http://127.0.0.1:9999 redis: 2018/09/25
11:18:56 ring.go:263: ring shard state changed: Redis is down.
when I changed the port number in web preview in cloud shell it is showing as your server is not listing to 6379 port number, but in the instance level when I run the netstat -an command it is showing as the server is listing for 6379 port
please help me in resolving these issue.
6379 is redis server port which is there for rate limiting feature. If you go through the main.go file, you'll see go server port is 9999. Just run "dns-api-go" command and hit http://localhost:9999/
I have installed aerospike on my mac my following this installation steps
All the validations are working fine. I am able to connect to the cluster using browser chrome. Below is the screen shot.
I have also installed the AQL tools following the instructions here.
But I'm unable to connect to local node from aql.
$ aql
2017-11-21 16:06:09 WARN Failed to connect to seed 127.0.0.1 3000.
AEROSPIKE_ERR_CONNECTION Bad file descriptor, 127.0.0.1:3000
Error -1: Failed to connect
$ asadm
Aerospike Interactive Shell, version 0.1.11
ERROR: Not able to connect any cluster.
Also, I have noticed the Java client is giving error.
AerospikeClient client = new AerospikeClient("localhost", 3000);
when I changed the localhost to actual Ip returned by vagrant ssh -c "ip addr"|grep 'global eth1' it is working fine.
How to connect with aql using customer parameters? I want to pass ip address and port as parameters to aql. Any suggestions.
$ aql --help
https://www.aerospike.com/docs/tools/aql/index.html - discusses all various command line options.
$ aql -h a.b.c.d -p 1234
There is another possibility, you have your owned port instead of the default 3000, so when you try to connect to aerospike, you can try to run command like : aql -p4000
Hope this may help you
Seems like the port is not getting freed even after exiting the vagrant console.
Tried closing all the terminal windows and then starting again. But no luck.
Finally, restarting the system resolved the issue.
I am trying to install Parse-Server and Parse-Dashboard in Google Cloud (Debian/Jesse). I have already installed on both Windows (locally) and on Heroku and everything worked fine.
My configuration is the following:
Linux Debian 3.16.43-2
Node JS 7.10
Mlab
Firewall Ports are open
Installed both Parse-Server and Dashboard via npm.
I think Parse-Server is running fine since I was able to check that MLab database was written with Parse-Server tables (_SCHEMA, etc).
My Parse Dashboard config file is the following:
{
"apps": [
{
"serverURL": "http://localhost:1337/parse",
"appId": "1",
"masterKey": "654321",
"appName": "AppName",
"production": "true"
}
],
"users": [
{
"user":"username",
"pass":"password"
}
]
}
I run parse-server with this command and it shows the following status:
parse-server --appId 1 --masterKey 654321 --databaseURI mongodb://dbAdmin:db123456#Omitted.mlab.com:Omitted/Omitted --serverURL http://127.0.0.0.1/ --port 1337 --appName AppName
appId: 1
masterKey: ***REDACTED***
port: 1337
host: 0.0.0.0
databaseURI: mongodb://dbAdmin:db123456#Omitted.mlab.com:Omitted/Omitted
serverURL: http://127.0.0.0.1/
mountPath: /parse
appName: AppName
maxUploadSize: 20mb
userSensitiveFields: ["email"]
I run parse-dashboard with this command and it shows the following status:
parse-dashboard --config /usr/local/lib/node_modules/parse-dashboard/Parse-Dashboard/parse-dashboard-config.mine.json --allowInsecureHTTP
The dashboard is now available at http://0.0.0.0:4040/
I am able to log into Dashboard but it keeps saying:
server not reachable unable to connect to server.
I have tried the following list of fixes:
Changed serverURL to localhost or to 127.0.0.1
Added /parse at the end of the address
Changed serverURL port to 1333
Checked APP ID, APP Masterkey and APP Name
Opened firewall ports
Stopped using configuration file
Nothing solves this problem. If anyone has any suggestion, I would very be pleased to try.
Thanks in Advance.
Regards,
James P
Problem solved. Probably this is not the correct solution, but at least it worked.
The serverURL: http://127.0.0.0.1/ or serverURL: http://localhost/ did not work for me. I have changed both parse-server and parse-dashboard to an external IP for (35.x.x.x, in my case).
I faced the same problem.
Configuration:
Installed mongodb, parse-server & parse-dashboard, all 3 on separate docker instances.
Used a 4th docker instance with apache2 to make it work as a reverse proxy.
Mistake:
Pointed subdomain parse-dashboard.ABC.com to the parse-dashboard, but did not point parse-server to any subdomain. The most important part here is that parse-dashboard uses JavaScript to access app on parse-server, so this resulted in a CORS error.
Solution:
I pointed parse.ABC.com to parse-server.
Hope this helps someone.
Have you started mongodb?
sudo service
Did you start parse-server before Parse-Dashboard?
In your project folder
npm start
On another terminal in your project folder start Parse-Dashboard
Parse-dashboard --config parse-dashboard-config.json
I'm trying to follow beginner tutorial on Docker's website and I suffer with an error on login.
OS is Ubuntu 14.04, I'm not using VirtualBox and I'm not behind any proxy and want to push to the "regular" docker repository (not private one).
All threads I've found mention proxies and private repositories but that isn't my case, I'm just trying to do simple beginner tutorial.
Here is my attempt:
$ sudo docker login
[sudo] password for myuname:
Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.
Username: myDHuname
Password:
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
My docker info:
Containers: 5
Running: 0
Paused: 0
Stopped: 5
Images: 5
Server Version: 1.11.0
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 28
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 3.19.0-58-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.686 GiB
Name: myuname-ThinkPad-T420
ID: 6RW3:X3FC:T62N:CWKI:JQW5:YIPY:RAHO:ZHF4:DFZ6:ZL7X:JPOD:V7EC
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Epilogue
Now docker login is passing. I have not touched anything since yesterday when it was broken...
I can't reproduce the behavior anymore.
I encounter this issue when my first use docker. I've shadowsocks proxy on, and configed as pac mode. When I try to run docker run hello-world, I get this timeout error. When I set the proxy mode to global, the error is aslo there.
But when I disable the proxy, docker runs well. It pull remote image successfully.
docker for windows
Note: Some users reported problems connecting to Docker Hub on Docker
for Windows stable version. This would manifest as an error when
trying to run docker commands that pull images from Docker Hub that
are not already downloaded, such as a first time run of docker run
hello-world. If you encounter this, reset the DNS server to use the
Google DNS fixed address: 8.8.8.8. For more information, see
Networking issues in Troubleshooting.
The error Client.Timeout exceeded while awaiting headers indicates:
GET request to the registry https://registry-1.docker.io/v2/ timedout
The library responsible (most likely libcurl) timed out before a response was heard
The connection never formed (proxy/firewall gobbled it up)
If you see the below result you can rule out timed out and network connectivity
$ curl https://registry-1.docker.io/v2/
{"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":null}]}
If you get the above response next would be to check if your user environment has some proxy configuration.
env | grep "proxy"
Note: The docker runs as root. Maybe you have http_proxy in your env. Most likely I am wrong. Anywho see what happens with the curl GET request
change the proxy settings in the firefox. May be you are in access restricted mode. Just add the server address in the firefox settings -> preferences -> advanced -> network -> configuration (settings). Add the server ip in the no proxy for the issue can be resolved