So I had been successfully running Perforce on a dedicated Ubuntu 20.04 LTS cloud server for many months. I recently however moved to a different house and now I cannot connect to the server anymore through P4Admin and P4V, and neither can the other users. I've been getting this error in P4Admin:
Connect to server failed; check $P4PORT.
TCP connect to 81.169.151.191:1666 failed.
connect: 81.169.151.191:1666: WSAECONNREFUSED
And get this error when connected to the server in Putty as root user:
p4 info
Perforce client error:
Connect to server failed; check $P4PORT.
TCP connect to 81.169.151.191:1666 failed.
connect: 81.169.151.191:1666: Connection refused
Has something gone wrong with the server? Anything I can do to restore the connection? My apologies in advance, I'm not an advanced user and have just been trying whatever the tutorials suggest.
Related
Whenever I try to add a connection profile using msconnect, I run into the issue shown below.
I've followed these instructions to no avail. It's worth noting that I have no issue querying the database with other IDEs like Pycharm or Datagrip.
For more information,
OS is macOS Monterey
it's a locally running Postgres container on port 5434 so I specify localhost,5434 as the server name when creating the connection
username & password were double-checked
mssql: Error 203: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - 17735680)
Wildfly application server is installed and started on windows. I am trying to use the CLI to do a connect which throws the below error. I am able to connect via URL. The jboss-cli.xml is pointing to the 8083 port which I am using. Windows Defender Firewall is off. My question is - Can I connect using CLI when the server is running as a service (It's not launched as standalone). if yes, can someone help me with the error, please?
C:\wildfly\bin> jboss-cli.bat --connect --controller=remote+http://localhost:8083
Failed to connect to the controller:
The controller is not available at localhost:8082:
java.net.ConnectException: WFLYPRT0053: Could not connect to
remote+http://localhost:8082. The connection failed: WFLYPRT0053:
Could not connect to remote+http://localhost:8082. The connection
failed: Connection refused: no further information Press any key to
continue . . .
I also tried the flags --user and --password.
I have Followed the below path http://clearwater.readthedocs.org/en/stable/Manual_Install/ for installation of Clearwater IMS node-specific modules. But when i was trying to install Homer & Homestead getting as connection refused.
TCP poll failed to 127.0.0.1 9160
nc: connect to 127.0.0.1 port 9160 (tcp) failed: Connection refused
Failed to connect to '127.0.0.1:7199': Connection refused
Due to which i am not able to proceed further.
Can anyone help me here.
the error comes sometimes when your port is not feee or port is using by some other services check once port is free or not
I'm running Ubuntu 14.04 on an AWS EC2 instance with Apache2. This morning I upgraded my Apache2 settings to allow multiple virtual servers following these instructions: https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-ubuntu-14-04-lts
Just now I tried to access my MongoDB instance, but I cannot do it either through the PHP MongoDB driver or through the shell. I get this error when attempting to connect with a PHP MongoClient():
Failed to connect to: localhost:27017: Connection refused'
and I get this error when trying to run the mongo shell:
2015-06-03T19:23:57.307+0000 W NETWORK Failed to connect to 127.0.0.1:27017, reason: errno:111 Connection refused
2015-06-03T19:23:57.308+0000 E QUERY Error: couldn't connect to server 127.0.0.1:27017 (127.0.0.1), connection attempt failed
at connect (src/mongo/shell/mongo.js:179:14)
at (connect):1:6 at src/mongo/shell/mongo.js:179
exception: connect failed
Everything was running fine just last night, and I haven't directly modified MongoDB settings. What can I do to fix this? How do Apache2 settings relate to MongoDB? I've been trying to look through the MongoDB docs, but I don't see anything that looks relevant.
You need to setup Security Group for your EC2 instance. And allow Inbound connection for the mongodb port, in your case 27017.
When I went through the logs, I saw a message that there was insufficient room for "journal file." I rebooted my AMI on an EC2 instance with more storage and reinstalled Mongo. That did the trick. I had uploaded a few files to the instance after updating my Apache2 settings, so those few more files must have pushed the instance past what Mongo could tolerate. Too bad the error message wasn't more helpful, but I should have checked the logs sooner. It would also be nice if the logs had a more explicit message.
trying to upload file using apache file upload, but getting this error:
java.net.ConnectException: Connection refused: connect
it was working yesterday, but today it is not working
Either the firewall configuration (by which I mean port forwarding, not access rules) has changed or the server process isn't running.
If this is a locally hosted server. make sure the correct port is forwarded for the correct IPV4, they change often and without much reason.