Bootstrapping Chef on windows
**ERROR: Network Error: Connection refused - connect(2)
Check your knife configuration and network settings**
I have installed knife windows pluggin and also configured the winrm but after doing this also .. i am facing this issue .
I could not resolve this. Has anyone come across this problem and found a solution?
Related
I recently switched to ubuntu and when I installed and tried to create a connection on Oracle SQL Developers 22.2.1 I get a error
Status : Failure -Test failed: IO Error: The Network Adapter could not establish the connection
Ive tried changing the ports and switching between JDK 19,17 and 11 non of them seem to fix the error, all the guides that i can find on this error seem to be specifically for windows.
any help is appreciated and apologies if I have couldnt explain my problem clearly.
Testing connection of server should produce successful but its giving Status : Failure -Test failed: IO Error: The Network Adapter could not establish the connection
I'm a beginner here,
I'm using a raspberry pi-4 running raspian OS. I'm trying to run sudo openvas-setup but it just fails to connect to dl.greenbone.net over and over again at least 20 times before finishing with errors. Can anyone tell me why this is? I'll paste code below:
--2021-05-20 19:00:56-- (try: 3) http://dl.greenbone.net/community-nvt-feed-current.tar.bz2
Connecting to dl.greenbone.net (dl.greenbone.net)|2a01:130:2000:127::d1|:80... failed: No route to host.
Connecting to dl.greenbone.net (dl.greenbone.net)|89.146.224.58|:80... failed: Connection timed out.
Retrying.
--2021-05-20 19:03:15-- (try: 4) http://dl.greenbone.net/community-nvt-feed-current.tar.bz2
Connecting to dl.greenbone.net (dl.greenbone.net)|2a01:130:2000:127::d1|:80... failed: No route to host.
Connecting to dl.greenbone.net (dl.greenbone.net)|89.146.224.58|:80... failed: Connection timed out.
Retrying.
the server has been shut down more then a year ago. The Greenbone OpenVAS version you are using a very very outdated and can't be used anymore. Maybe updating raspbian helps. Otherwise you can try building it from source with https://greenbone.github.io/docs/
I have virtuoso 6.1 in ubuntu. I was loading a dbpedia RDF but the server where virtuoso is setup disconnected while doing it, giving me this error:
Error 08S01: [Virtuoso Driver]CL065: Lost connection to server at line
2 of Top-Level: rdf_loader_run()
Since then I only get this error:
Error S2801: [Virtuoso Driver]CL033: Connect failed to localhost:1111
= localhost:1111.
I tried to kill virtuoso and restart it but nothing changes, I also tried changing the port but it still tries to connect to port 1111, and when I specify the new port it gives me the same message. Does anyone knows how to solve this issue?
I am fairly new to Linux (and brand new to chef) and I have ran into an issue when setting up my chef server. I am trying to create an admin user with the command
sudo chef-server-ctl user-create admin Admin Ladmin admin#example.com
examplepass -f admin.pem
but after I keep getting this error:
ERROR: Connection refused connecting...
ERROR: Connection refused connecting to https://127.0.0.1/users/, retry 5/5
ERROR: Network Error: Connection refused - Connection refused
connecting to https://..., giving up
Check your knife configuration and network settings
I also noticed that when I ran chef-server-ctl I got this output:
[2016-12-21T13:24:59-05:00] ERROR: Running exception handlers Running
handlers complete
[2016-12-21T13:24:59-05:00] ERROR: Exception
handlers complete Chef Client failed. 0 resources updated in 01 seconds
[2016-12-21T13:24:59-05:00] FATAL: Stacktrace dumped to
/var/opt/opscode/local-mode-cache/chef-stacktrace.out
[2016-12-21T13:24:59-05:00] FATAL: Please provide the contents of the
stacktrace.out file if you file a bug report
[2016-12-21T13:24:59-05:00] FATAL:
Chef::Exceptions::CannotDetermineNodeName: Unable to determine node
name: configure node_name or configure the system's hostname and fqdn
I read that this error is due to a prerequisite mistake but I'm uncertain as to what it means or how to fix it. So any input would be greatly appreciated.
Your server does not have a valid FQDN (aka full host name). You'll have to fix this before installing Chef server.
We untar spark-0.9.0-incubating.tgz and trying to build it for use with Yarn.
SPARK_HADOOP_VERSION=2.0.0-cdh4.6.0 SPARK_YARN=true sbt/sbt assembly
...
[info] Resolving io.netty#netty-all;4.0.13.Final ...
[error] Server access Error: Connection timed out url=https://oss.sonatype.org/content/repositories/snapshots/io/netty/netty-all/4.0.13.Final/netty-all-4.0.13.Final.pom
[error] Server access Error: Connection timed out url=https://oss.sonatype.org/service/local/staging/deploy/maven2/io/netty/netty-all/4.0.13.Final/netty-all-4.0.13.Final.pom
...
If I just cut-paste the url into a browser, I get:
404 - ItemNotFoundException
Retrieval of /io/netty/netty-all/4.0.13.Final/netty-all-4.0.13.Final.pom from M2Repository(id=snapshots) is forbidden by repository policy SNAPSHOT.
org.sonatype.nexus.proxy.ItemNotFoundException: Retrieval of /io/netty/netty-all/4.0.13.Final/netty-all-4.0.13.Final.pom from M2Repository(id=snapshots) is forbidden by repository policy SNAPSHOT.
at org.sonatype.nexus.proxy.maven.AbstractMavenRepository.doRetrieveItem(AbstractMavenRepository.java:380)
at org.sonatype.nexus.proxy.maven.maven2.M2Repository.doRetrieveItem(M2Repository.java:396)
at org.sonatype.nexus.proxy.repository.AbstractRepository.retrieveItem(AbstractRepository.java:765)
at org.sonatype.nexus.proxy.repository.AbstractRepository.retrieveItem(AbstractRepository.java:608)
at org.sonatype.nexus.proxy.router.DefaultRepositoryRouter.retrieveItem(DefaultRepositoryRouter.java:155)
at org.sonatype.nexus.web.content.NexusContentServlet.doGet(NexusContentServlet.java:359)
at org.sonatype.nexus.web.content.NexusContentServlet.service(NexusContentServlet.java:331)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
I have seen this reported in a number of places but no solution. Is this error because we are behind a corporate firewall, or is this due to something else? Please advise.
I had proxy set as environment variables, but it appears they are not being picked up. Adding them in sbt directly worked for me.
Edit $SPARK_HOME/sbt/sbt
For example,
EXTRA_ARGS="-Dhttp.proxySet=true -Dhttp.proxyHost=myproxy.mycompany.com -Dhttp.proxyPort=80 -Dhttps.proxySet=true -Dhttps.proxyHost=myproxy.mycompany.com -Dhttps.proxyPort=80 -Dftp.proxySet=true -Dftp.proxyHost=myproxy.mycompany.com -Dftp.proxyPort=80 -Dhttp.nonProxyHosts=mydomain -Dhttps.nonProxyHosts=mydomain -Dftp.nonProxyHosts=mydomain"