Enabling Basic Authentication in solr 4.3 - java

I am following the link for Enabling Basic Authentication in solr 4.3.
https://lucidworks.com/blog/2015/08/17/securing-solr-basic-auth-permission-rules/
and when o am uploading security.json to ZooKeeper by
scripts/cloud-scripts/zkcli.sh -zkhost localhost:8983 -cmd putfile /security.json security.json
but getting the following Error:
WARN - 2016-06-16 23:19:28.798; org.apache.zookeeper.ClientCnxn$SendThread; Session 0x0 for server localhost/127.0.0.1:8983, unexpected error, closing socket connection and attempting reconnect
java.io.IOException: Packet len1213486160 is out of range!
at org.apache.zookeeper.ClientCnxnSocket.readLength(ClientCnxnSocket.java:112)
at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:79)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:366)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
Can anyone please help to resolve this issue.

I think issue is port number you are using port 8983 which is your host port. Solr run Zookeeper on hostPort+1000, so in your case port number would be localhost:9983

Related

HTTP/1.1 503 Service Unavailable upstream connect error or disconnect/reset before headers. reset reason: connection failure

We have Spring Boot applications which use Kubernetes and Istio. The application connects to AWS OpenSearch for CRUD functionality. Recently, the requests to OpenSearch started failing and we encountered this error repeatedly in the application logs:
method [POST], host [http://vpc-application-name.us-east-1.es.amazonaws.com], URI [/dummy/uri?param1=dummy1&param2=dummy2], status line [HTTP/1.1 503 Service Unavailable] upstream connect error or disconnect/reset before headers. reset reason: connection failure
When we tried to hit this URL through Postman, it was working. We also tried to bash into the Kubernetes pods of this service and tried to curl this URL from there, but we were getting proper response. So it looks like an issue from the Java side. When we restarted the pods, the error was gone.
What could have caused this error?
How to identify or narrow down the root cause of this issue?
I am fairly new to Istio, Kubernetes and AWS, and I do not know what to expect. Any help is appreciated.

Connect SQL developer with MYSQL server running on Docker container in EC2

Could you please guide me How can I connect my local SQL developer to MY SQL Server running on Docker container in EC2. But I havent installed mysql in my ec2 host.
I have tried with public dns and port 3306 but getting below error
An error occurred while establishing the connection:
`Long Message:
Communications link failure
The last packet successfully received from the server was 353 milliseconds ago. The last packet sent successfully to the server was 339 milliseconds ago.
Details:
   Type: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException
   SQL State: 08S01`
follow the guide in this official AWS documentation
https://aws.amazon.com/premiumsupport/knowledge-center/connect-http-https-ec2/
Use port 3306 however, this is a guide for webservers

Tried all: '1' addresses, but could not connect over HTTP

Can some one help me understand why I'm getting this error while running my managed server locally. My admin server is also running (locally as well) on port 7001.
Why it is trying to connect 172.30.XXX.XXX ip ? I am but confused what's happening here. When I startup my managed server I get this exception.
INFO: The Wsee Service is starting
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '172.30.XXX.XXX', port: '7001'
at weblogic.net.http.HttpClient.openServer(HttpClient.java:401)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:506)
at weblogic.net.http.HttpClient.New(HttpClient.java:313)
at weblogic.net.http.HttpClient.New(HttpClient.java:289)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:267)
at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:76)
Thanks for your help.

connecting to postgreSQL server failed

I am trying to install "Kwok information server" and I am new to postgreSQL. I just followed the installation guide of Kwok information server.
when I am trying to install kwok-schema-setup.jar file using java through postgreSQL server in Command Prompt, I am getting the following error..."Connecting to PostgreSQL Server ...failed. Connection refused. Check that the ho
stname and port are correct and that the postmaster is accepting TCP/IP connecti
ons. Cause: java.net.ConnectException: Connection refused: connect
Schema setup encountered errors" .
And when I am trying to connect to the server using pgAdmin III, I am getting the following error "Server doesn't listen
The server doesn't accept connections: the connection library reports
could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 5432? ".
Please anyone help me regarding, Thanks in advance!!
Looks like your Postgresql daemon is not running. Check if the server has started and is running. I dont know which OS you are using but try ps -ax on linux/mac or the task manager in windows.
Maybe a firewall that is blocking the connection, you have to provide more information about your environment to be sure.

Netbeans can't start derby server

I've been trying to start the server but I get this error message:
2013-01-23 19:24:18.133 GMT : Security manager installed using the
Basic server security policy. 2013-01-23 19:24:18.430 GMT : Could not
listen on port 1527 on host localhost: java.net.BindException: Cannot
assign requested address: JVM_Bind
On top of that I get a prompt saying:
Unable to connect. Cannot establish a connection to
jdbc:derby://localhost:1527/sample using
org.apache.derby.jdbc.ClientDriver (java.net.SocketException : Error
connecting to server localhost on port 1527 with message Network is
unreachable: connect.).
How is one suppose to fix such an issue?
I had the same issue but my problem was I had my loopback (lo) network interface disabled... took me quite long to discover... (But most common would be another instance of derby already running I think)

Categories