I'm trying to set up the Google HTML 5 "Grits" on Mac OS X.
http://code.google.com/p/gritsgame/wiki/DeveloperSetUp
When I get to Actually run locally I'm getting this error:
$ sudo node games-server/main.js $*
info - socket.io started
SERVERID: nKmXj1MfcULEx31vTlBtmz+u
checkConnection: POST http://localhost:9100/register-controller -> FAILED due to Error: connect ECONNREFUSED
Will call checkConnection again in 3.2 seconds
I'm new to node, is there something I need to do to start the server first before I run this command?
I solved it:
You need to start app engine first:
dev_appserver.py --skip_sdk_update_check --backends . $*
Then you can run the node command
node games-server/main.js $*
(I'm not sure why the wiki has them in the opposite order.)
Related
Recently installed Neo4J on a Raspberry Pi on a docker container (portainer). Everything seems to working fine. I can open a terminal in Portainer and run commands. I can see there are two DB and I can even run Cypher commands (cut and pasted the Movie entries). But I'm not able to run any commands using the browser. I seem to be able to connect the browser (http://localhost:7474/browser/) and see the ":play movie-graph" run. But when I try to run the query to enter movie data, I get the following error: "ERROR: Neo.DatabaseError.General.UnknownError" Running :sysinfo doesn't return any results. Also the cursor is $ as opposed to a DB name. And don't see any databases in the Database menu on the left.
Again, I'm able to run queries using Cypher Shell through a Portainer terminal.
Here are the container details:
IMAGE neo4j:latest#sha256:b91a4a85afb0cec9892522436bbbcb20f1d6d026c8c24cafcbcc4e27b5c8b68d
CMD neo4j
ENTRYPOINT tini -g -- /startup/docker-entrypoint.sh
ENV
JAVA_HOME /usr/local/openjdk-11
JAVA_VERSION 11.0.15
LANG C.UTF-8
NEO4J_AUTH none
NEO4J_dbms_connector_bolt_advertised__address localhost:7687
NEO4J_dbms_connector_http_advertised__address localhost:7474
NEO4J_dbms_connector_https_advertised__address localhost:7473
NEO4J_EDITION community
NEO4J_HOME /var/lib/neo4j
NEO4J_SHA256 34c8ce7edc2ab9f63a204f74f37621cac3427f12b0aef4c6ef47eaf4c2b90d66
NEO4J_TARBALL neo4j-community-4.4.8-unix.tar.gz
PATH /var/lib/neo4j/bin:/usr/local/openjdk-11/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
I'm sure it is something silly I'm missing, but reading multiple forum comments haven't help. Any help would be appreciated.
Thank you.
SJ
When you load the neo4jbrowser from your internet browser at:
http://localhost:7474/browser
, you need to connect to the bolt advertised address of your neo4j server at:
bolt://localhost:7687
I am currently trying to run through the example first application for Hyperledger Fabric here -> http://hyperledger-fabric.readthedocs.io/en/release-1.1/write_first_app.html
I am unable to get past calling node invoke.js
Originally I was getting the same error as this question Error invoking chaincode using Node.js SDK [TypeError: Cannot read property 'getConnectivityState' of undefined]
But after reverting to grpc#1.9.1 I get the following result:
I am able to do everything up to the node query.js method and that returns successfully but can't quite get past this.
Node version: 8.11.1
Docker Version:
fabric client section of package-lock.json
FYI: I am trying to run on Windows 10 mostly using the docker toolbox bash, or a separate git bash CLI.
Last piece of info!
Even though the invoke js command fails with the above error, I can see that the PUT command to couch db does go through and car10 has been successfully added.
If I check the docker logs for peer0.org1.example.com I see the following:
So did it actually work?
I have an alpine machine on my virtual machine and I want to install mongodb. I added the package for mongodb using "apk add mongodb". I started mongo daemon using command mongod in one terminal. Then opened another terminal with mongo shell using mongo --disableJavaScriptJIT. I tried adding files and reading them from the database and that worked fine. But when I do sudo service mongodb restart I got the following output.
* Caching service dependencies ... [ ok ]
* Starting mongodb ...
* start-stop-daemon: failed to start `/usr/bin/mongod' [ !! ]
* ERROR: mongodb failed to start
The first thing you should do is to read the log file. I think that you’ll read here that mongodb doesn’t have rights to access some files. When you started it manually, you haven’t run it as user mongodb, have you…?
If this hypothesis is right, then the solution is to fix owner (and group) of the /var/lib/mongodb (recursively).
I am in the midst of "Getting Started with Node.js on Heroku", where I want to "Run the app locally" by:
$ foreman start web
(cf. https://devcenter.heroku.com/articles/getting-started-with-nodejs#run-the-app-locally)
It says:
/usr/local/foreman/lib/foreman/process.rb:54:in run': undefined methodspawn' for Process:Module (NoMethodError)
from /usr/local/foreman/lib/foreman/process.rb:53:in chdir'
from /usr/local/foreman/lib/foreman/process.rb:53:inrun'
from /usr/local/foreman/lib/foreman/engine.rb:356:in spawn_processes'
from /usr/local/foreman/lib/foreman/engine.rb:353:inupto'
from /usr/local/foreman/lib/foreman/engine.rb:353:in spawn_processes'
from /usr/local/foreman/lib/foreman/engine.rb:352:ineach'
from /usr/local/foreman/lib/foreman/engine.rb:352:in spawn_processes'
from /usr/local/foreman/lib/foreman/engine.rb:57:instart'
from /usr/local/foreman/lib/foreman/cli.rb:41:in start'
from /usr/local/foreman/vendor/gems/thor-0.19.1/lib/thor/command.rb:27:insend'
from /usr/local/foreman/vendor/gems/thor-0.19.1/lib/thor/command.rb:27:in run'
from /usr/local/foreman/vendor/gems/thor-0.19.1/lib/thor/invocation.rb:126:ininvoke_command'
from /usr/local/foreman/vendor/gems/thor-0.19.1/lib/thor.rb:359:in dispatch'
from /usr/local/foreman/vendor/gems/thor-0.19.1/lib/thor/base.rb:440:instart'
from /usr/bin/foreman:15
(Running on Mac OS 10.7.5)
Any ideas what may help? Thanks!
Check out https://github.com/ddollar/foreman/issues/473.
Seems to be related to an old version of foreman or ruby.
I intended to implement a chat feature in my rails application. After a brief backup work I found JUGGERNAUT is the best option. By going to through http://juggernaut.rubyforge.org/
I have successfully implemented the juggernaut in my application.
Presently I'm all set to implement chat feature and after a vigorous surfing over web I couldn't get good tutorial to implement it but I found the some part of implementation at http://www.golygon.com/2010/12/private-chat-room-in-ruby-on-rails-3-0/. I decided to follow it but initially to implement the tutorial we need to have redis server and node.js in our system. I installed both in my environment.
But I'm facing the following problem as follows:
If I try
redis-server, I'm getting the following error
[11440] 08 Aug 10:08:16 # Warning: no config file specified, using the default config. In order to specify a config file use 'redis-server /path/to/redis.conf'
[11440] 08 Aug 10:08:16 # Opening port: bind: Address already in use
and as per the tutorial
if I try
sudo node server.js, I'm getting the following error
[sudo] password for re5:
node.js:63
throw e;
^
Error: ENOENT, No such file or directory '/home/re5/Documents/task17/server.js'
at Object.openSync (fs:153:18)
at Object.readFileSync (fs:94:15)
at Module._loadScriptSync (node.js:468:39)
at Module.loadSync (node.js:338:12)
at Object.runMain (node.js:522:24)
at Array.<anonymous> (node.js:756:12)
at EventEmitter._tickCallback (node.js:55:22)
at node.js:773:9
As I don't know much about the redis and node I'm unable to figure out what was the problem regarding to this errors.
I'm stuck and couldn't go further as I'm not sure whether this two are configured perfectly or not.
currently I'm using rails 3.0.7 and ruby 1.8.7
Can any one help me out.
Well your first error is quite simple to understand.
[11440] 08 Aug 10:08:16 # Opening port: bind: Address already in use
This means that there is aready a server bound to that port and using it as a server, this can happen if you have other applications/servers running or if you try to have mutiple instances of the server run at one time. To fix this you need to stop the process and then start it back up again. You can usually do this by closing all of your terminal windows or using your operating systems process manager to terminate the process, if those methods dont work for you try shutting your computer down and starting it back up. If you are still unable to start the Redis server after this then there are some more steps we can take.
The next error is due to node.js not being able to find a file that it needs. Reinstalling node.js should fix this problem for you.
Let me know if this fixes your problem or if you need more help.