I am trying to explore my transaction and I am using Quorum transaction explorer.
I run the network via vagrant and I executed:
NODE_ENDPOINT=http://localhost:2222 docker-compose up
I get an error telling me "Connection refused" and I don't know why.
Does anyone have an idea about this problem?
Related
I have encountered a problem. I recently rebooted my instance, it turned out that after the reboot I lost access to the SSH command. After typing the command, I get a Connection timed out error. The next day going to the Cloud site I got this message (image). Is there anything I can do about it?
image
to work normally so I can connect using SSH
I have a Laravel app on digital ocean and it runned fine for about 4 days now.
But today when I woke up it suddenly couldn't connect to the DB.
Also when I try to login in phpmyadmin it says
2002 - Connection refused — The server is not responding (or the local server's socket is not correctly configured).
I tried changing localhost to 127.0.0.1 in the config-db.php file and restarting apache, because some guy in their forums had the same problem and said that it fixed it for him, but for me it had no effect.
Other errors I see are
mysqli_real_connect(): (HY000/2002): Connection refused
Connection for controluser as defined in your configuration failed.
mysqli_real_connect(): (HY000/2002): Connection refused
I am certain that no configuration files have been changed, it just stopped working, why that might be, and how to prevent it in the future ?
The OS is Ubutnu 18.04.13 (if it matters)
It would appear as if your MySQL daemon is no longer running.
The hints here are that the Laravel app is not able to reach the MySQL server, and that phpMyAdmin is also unable to reach the MySQL server.
You should look in the MySQL error log for hints. You may also find hints in your syslog, depending on how your system is configured. This could give you information about why the service has stopped. You might also find information in the systemd log, which can probably best be viewed with journalctl -u mysql -b.
You could verify that it's actually stopped with systemctl status mysql, even though it's difficult for me to think of a reason why it would be running correctly but not responding to any connection attempts.
Next, you should probably start the service again with sudo systemctl start mysql. If it fails to start, you'll see some information about why not with information about viewing the log file, which you can copy and paste in to your question to help us further with troubleshooting.
I have a need to run mysql queries within gulp to check certain fields in a table. I currently connect to a development server via ssh tunnel, which is opened via terminal so that my host is set to 'localhost'.
When I execute a connection attempt, the tunnel crashes with:
channel 4: open failed: connect failed: Connection refused
Then the server process crashes with an out of memory error.
We use node-mysql2 and a ssh tunnel to run GraphQL locally for testing, so I can't think of anything in particular in gulp that would cause what is essentially a race condition almost instantaneously from the time that the gulp command is sent.
Gulp Code:
If anyone has any insights I'd be much obliged.
Fix can be found here, thanks to the mysql2 developer for pointing me in the right direction!
More info on fix here:
https://stackoverflow.com/a/30669454/705115
I deployed my sails app in ec2 and I have mysql database in rds.
when I use mysql in rds from my local, it worked absolutely fine. But when I connect myswl in rds from the ec2 it is giving me this error:
error: A hook (`orm`) failed to load!
error: Error (E_UNKNOWN) :: Encountered an unexpected error
: Could not connect to MySQL:
Error: Handshake inactivity timeout
Please help me solve this issue. Should I configure my ec2 instance to connect to rds?
When adding inbound connection in the security options, don't use anywhere. As you can imagine, this is not secure at all. Instead use the security group associated with your instance. Of course, if you want to connect to your database remotely, add only your external IP address to the rules. "Anywhere" is like an invitation to the whole world saying: "Try to hack me!"
I figured it out. Added a inbound connection in security options with anywhere option.
I have my database hosted somewhere else and I have this in my /conf file:
db.default.driver= com.mysql.jdbc.Driver
db.default.url="jdbc:mysql://myserver.com:3306/mydb"
db.default.user=myusername
db.default.password=mypassword
When I test it locally then it connects to the database just fine. I'm able to create/delete from the tables, etc. I changed the heroku config:
heroku config:add DATABASE_URL=mysql://myusername:mypassword#<myserver>:3306/mydb
and procfile
web: target/start -Dhttp.port=${PORT} ${JAVA_OPTS}
When I deploy it to heroku, I get errors:
2014-06-08T08:21:35.308207+00:00 heroku[web.1]: State changed from starting to crashed
2014-06-08T08:21:35.309586+00:00 heroku[web.1]: State changed from crashed to starting
2014-06-08T08:21:33.996174+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2014-06-08T08:21:33.996382+00:00 heroku[web.1]: Stopping process with SIGKILL
2014-06-08T08:21:35.293114+00:00 heroku[web.1]: Process exited with status 137
The error log is pretty long. Please let me know if you need further information. Any help is appreciated!
This is a shot in the dark, as there isn't any indication of issue in the logs, but I've faced similar "ghost" failures with Heroku.
It seems that there is a very large latency trying to leave their network, for whatever reason. While using an Apache Thrift RPC system on Heroku, nothing was working until I bumped the connection timeout to about 30 seconds. I saw intermittent failures with RabbitMQ (the Heroku add-on version), and their support told me to bump the connection timeout in this case as well.
Based on that, I would add this to your config file:
db.default.connectionTimeout=30 seconds