Ganache (from Truffle) hangs when started - ethereum

When I run the file "ganache-1.0.1-x86_64.AppImage" that I downloaded from GitHub, Ganache just hangs showing the following screen with no more actions.
Is something missed?
I tried Ganache version 1.0.0 and and version 1.0.1.
My system contains:
Ubuntu 17.10 64bit
node v6.11.4
npm 3.5.2
Truffle v4.0.1 (core: 4.0.1)
Solidity v0.4.18 (solc-js)
Thanks,

After investigation, I found that there was an application that uses the same default port of Ganache 7545.
Ganache should show error message clarifying that there is another application that uses the default running port. And better to suggest another port to start running with OR open Ganache settings page and notify to change the running port
I opened an issue at GitHub regarding this:
https://github.com/trufflesuite/ganache/issues/126
However, the solution is to close or change the port of the other application that uses the port 7545. Then you can run Ganache. After that, from Ganache settings, you can change the port that Ganache uses for any other free port you want.
Note: if Ganache crash for any reason and you hit the close button, it could be that it is still running in the background and still listening on (use) the port that it was running on. Therefore, you may need to kill (end) its process that is still running in the background.

Related

Trying to launch json server in my localhost but states that the local host never sent date

i'm new to coding and right now i'm learning to launch json server through VSC in my bootcamp (flatiron). I'm having trouble with opening it in my localhost file in my google browser. I'm running Ubuntu on my PC. when I installed npm install -g json-server it stated that I have 4 moderate severity vulnerabilities.
I have tried to turn off my firewalls and antivirus, cleared the chrome history, tried to change my DNS and had no luck.
I've been stuck with this issue for 2 days now, please help !
[this is what local host is stating in the web browser1
This is the vulnerabilities being shown

Proxy server for Gatling

Recently I installed Gatling for performance testing on Ubuntu 14.04. And to run the recorder I needed to configure a proxy server in my browser. I tried to change proxy settings in Google chrome, but I don`t have rights. So I tried to do it using network settings in Ubuntu (Network -> Network proxy). But when I open a website which I need to test, nothing happens in the recorder.
So I do not really know is there a problem with the proxy server or Gatling itself? And how to check if the proxy server is configured correctly?
I would appreciate any help!
It's a bit too late, but I had a similar problem today. Was able to solve only by setting global IP address like xxx.xxx.xxx.xxx. Nor localhost nor 127.0.0.1 worked for me Chrome. After that I was able to notice http requests in Recorder inside Executed Events
Hopefully it could help somebody else
Edit : this is how setting looks like in Chrome, taking into account you have specified in Recorder Listening port to be 8000 also:

Chrome service-worker process running on port 3000?

The following error shows up in my Rails app logs and in my Chrome JavaScript console, but only on Chrome, and only when the app is running on localhost on port 3000:
Started GET "/service-worker.js" for 127.0.0.1 at 2015-12-15 09:31:04 -0800
ActionController::RoutingError (No route matches [GET] "/service-worker.js"):
Apparently someone else has had this same problem, but solved it by reinstalling the OS (!). This isn't an option for me.
According to lsof, there is some other some other process running on port 3000:
COMMAND PID FD TYPE NODE NAME
Google 49368 174u IPv4 TCP localhost:55612->localhost:hbci (CLOSE_WAIT)
ruby 57985 17u IPv4 TCP *:hbci (LISTEN)
Other things of note:
NodeJS is installed
Chrome Version 47.0.2526.80 (64-bit) on OS X 10.10.5
The stuff in chrome://flags/ has been reset to default
I've disabled all Chrome extensions
If I kill that Google process, it just reappears
What is this uninvited process?
Visit chrome://serviceworker-internals/ to view a list of service workers.
Click the "Unregister" button to remove the registration of the offender.
The Google Web Starter Kit installs a service worker that may continue running after using its local development server.
ALL CREDIT for this answer goes to Jeff Posnick. Just thought this question should have a formal answer that's easy to find since it was driving me to madness before I came across this page :)

VisualSVN messed up my localhost in Chrome

EDIT:
The localhost seem to be working fine in my firefox, IE and even Chrome's incognito mode. These is a problem specific to chrome. Any ideas?
PREVIOUS:
I just uninstalled VisualSVN Server from my Windows 7. But now when I try to hit localhost, I get redirected to localhost/svn. I am using WAMP and developing something that requires the root access. I can not put the project in a sub directory. I have also tried netstat -ao but no process is using ports 80 or 443.
You may have solved the problem....but for future, those who came here like me looking for a solution to this, this seems to be a prob for browser cache....clearing browser cache history solves the problem.....did for me...
If you uninstalled VisualSVN Server, then it's some other application which runs on 80 / 443 port that redirects you to /svn. Some steps that may help you to determine the root cause:
Verify that VisualSVN Server has been successfully uninstalled.
Start appwiz.cpl and see whether VisualSVN Server is listed as the installed application,
Start services.msc and see whether "VisualSVN Server" service is listed.
Run netstat -anbv and see which app runs on HTTP(S) port.

tasseo authentication fails

I was wondering if anyone uses Tasseo for their Graphite dashboards. I'm having some problems I dont quite get. Basically, Tasseo polls Graphite server for stats - if you have authentication enabled (http base auth) on your Graphite server then you must export GRAPHITE_URL and GRAPHITE_AUTH environment variables to the environment in which tasseo is running ie. if you run tasseo as runit service then your run script should look like this:
#!/bin/sh
exec 2>&1
export GRAPHITE_URL="https://graphite-url"
export GRAPHITE_AUTH="user:password"
cd /app
exec chpst -u tasseo bundle exec rackup -o 127.0.0.1 -p 5000 -s thin
What I noticed though is that IF I DONT authenticate to the Graphite in the SAME browser in which I'm running Tasseo in another tab (by running I literally mean running as Tasseo is just a sinatra app fully built in javascript ie it's running in your browser), then I'm NOT able to display ANY graphs. As soon as I authenticate against Graphite in the same browser all works fine.
Tasseo is using CORS ie. it's polling Graphite from within JavaScript so it might do something with it.
The most annoying thing is that I have to do this every time I restart tasseo app server :-( So when I restart tasseo I have to reload Graphite page - I assume so that is re-authenticates ?
Also I noticed that even though when I reload the Graphite tab, Tasseo works for a while and then after some time (dont have exact measures) it stops working - in Chrome's development console I can see that the OPTIONS requests to Graphite are failing - so the GET requests must too.
Anyone ideas ?
Just If anyone comes across this problem when setting up Tasseo then make sure if you're using Self Signed Certificate on Graphite server, then they MUST BE trusted by the browser which is running Tasseo's CORS java script. Otherwise you'll be noticing what is described above - once you set those self signed certificates as TRUSTED, everything wil work like a charm!