O exception java net connectexception caught when

Fix Zimbra ERROR zclient IO ERROR

As part of our Server Management Services, we help our customers with similar errors regularly.

Today, let’s see how our Support Engineers tackle this.

Zimbra ERROR zclient IO ERROR

When we get the following error:

[] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused [] INFO: Retrying request ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)

we cannot execute any Zimbra zmprov commands. This is devastating since Zimbra Admin users use Zimbra CLI a lot.

In this article, let us see how our Support Engineers fix the error.

What is Zimbra zmprov?

The zmprov tool performs all provisioning tasks in Zimbra LDAP. It includes, creating accounts, aliases, domains, COS, distribution lists, and calendar resources.

Generally, each operation is invoked through the command-line options, each of which has a long name and a short name.

What causes the error

The major cause of this error is when Zimbra zmprov is not configured to get results from LDAP. To fix this, we need to set zimbra_zmprov_default_to_ldap to TRUE.

This will make sure all the zmprov commands get replies from LDAP server.

How to fix Zimbra ERROR zclient IO ERROR

$ zmlocalconfig |grep zmprov zimbra_zmprov_default_soap_server = localhost zimbra_zmprov_default_to_ldap = false zmprov_safeguarded_attrs = zimbraServiceEnabled,zimbraServiceInstalled zmprov_tmp_directory = $/zmprov

$ zmlocalconfig -e zimbra_zmprov_default_to_ldap=true

$ zmlocalconfig |grep zmprov zimbra_zmprov_default_soap_server = localhost zimbra_zmprov_default_to_ldap = true zmprov_safeguarded_attrs = zimbraServiceEnabled,zimbraServiceInstalled zmprov_tmp_directory = $/zmprov

$ zmprov gs `zmhostname` | grep zimbraServiceEnabled zimbraServiceEnabled: amavis zimbraServiceEnabled: antivirus zimbraServiceEnabled: antispam zimbraServiceEnabled: opendkim zimbraServiceEnabled: stats zimbraServiceEnabled: logger zimbraServiceEnabled: proxy zimbraServiceEnabled: service zimbraServiceEnabled: zimbra zimbraServiceEnabled: zimbraAdmin zimbraServiceEnabled: zimlet zimbraServiceEnabled: mailbox zimbraServiceEnabled: spell zimbraServiceEnabled: ldap zimbraServiceEnabled: memcached zimbraServiceEnabled: mta zimbraServiceEnabled: snmp zimbraServiceEnabled: dnscache

If this does not solve the problem, we try changing the zimbra_zmprov_default_soap_server to the IP address of our Mailbox server.

The setting will look like this.

$ zmlocalconfig -e zimbra_zmprov_default_soap_server=ip-address

• We have to execute the command using ‘zmprov -l’ instead of just ‘zmprov’ until mailboxd is running again. This will directly query the ldap server.

[Still stuck with the error? We are happy to assist.]

Conclusion

To conclude, the error can prevent us from executing any Zimbra zmprov commands. Today, we saw how our Support Engineers go about to fix this error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

Источник

Zimbra ERROR zclient IO ERROR Tips to fix it

Are you experiencing Zimbra ERROR zclient IO ERROR?

Here at Ibmi Media, as part of our Server Management Services , we regularly help our Customers to fix Email related issues.

In this context, we shall look into the major causes of this error and how to get rid of it.

Nature of Zimbra ERROR zclient IO ERROR?

When this error occurs, you will get the following error message;

[] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused

ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)

In this cases, you cannot execute any Zimbra zmprov commands. This is frustrating since Zimbra Admin users use Zimbra CLI a lot.

More information about Zimbra zmprov?

The zmprov tool performs all provisioning tasks in Zimbra LDAP. It includes, creating accounts, aliases, domains, COS, distribution lists, and calendar resources.

Generally, each operation is invoked through the command-line options, each of which has a long name and a short name.

Cause of Zimbra ERROR zclient IO ERROR

The major cause of this error is when Zimbra zmprov is not configured to get results from LDAP. To fix this, we need to set zimbra_zmprov_default_to_ldap to TRUE.

This will make sure all the zmprov commands get replies from LDAP server.

How to fix Zimbra ERROR zclient IO ERROR?

To fix this error, follow the steps below;
1. Start by checking for the setting of zimbra_zmprov_default_to_ldap to be sure. To do this, execute;

zmlocalconfig |grep zmprov

zimbra_zmprov_default_soap_server = localhost

zimbra_zmprov_default_to_ldap = false

zmprov_safeguarded_attrs = zimbraServiceEnabled,zimbraServiceInstalled

zmprov_tmp_directory = $/zmprov

2. If set to false, we reconfigure it to have the true flag. This will enable the setting by executing;

zmlocalconfig -e zimbra_zmprov_default_to_ldap=true

3, Then, recheck the settings by running;

zmlocalconfig |grep zmprov

zimbra_zmprov_default_soap_server = localhost

zimbra_zmprov_default_to_ldap = true

zmprov_safeguarded_attrs = zimbraServiceEnabled,zimbraServiceInstalled

zmprov_tmp_directory = $/zmprov

4. Now we try to execute any zmprov commands and see if it is working fine. To do this, execute;

zmprov gs `zmhostname` | grep zimbraServiceEnabled

zimbraServiceEnabled: amavis

zimbraServiceEnabled: antivirus

zimbraServiceEnabled: antispam

zimbraServiceEnabled: opendkim

zimbraServiceEnabled: stats

zimbraServiceEnabled: logger

zimbraServiceEnabled: proxy

zimbraServiceEnabled: service

zimbraServiceEnabled: zimbra

zimbraServiceEnabled: zimbraAdmin

zimbraServiceEnabled: zimlet

zimbraServiceEnabled: mailbox

zimbraServiceEnabled: spell

zimbraServiceEnabled: ldap

zimbraServiceEnabled: memcached

zimbraServiceEnabled: snmp

zimbraServiceEnabled: dnscache

5. If this does not solve the problem, we try changing the zimbra_zmprov_default_soap_server to the IP address of our Mailbox server.
The setting will look like this;

zmlocalconfig -e zimbra_zmprov_default_soap_server=ip-address

We have to execute the command using ‘ zmprov -l ’ instead of just ‘ zmprov ’ until mailboxd is running again. This will directly query the ldap server.

[Still having troubles with Zimbra ERROR zclient IO ERROR? We are ready to assist you today .]

Conclusion

This article will help to fix ERROR: zclient.IO_ERROR which can prevent us from executing any Zimbra zmprov commands.

Источник

(java.net.ConnectException) caught when processing request: Connection refused

posted 15 years ago

when I am trying to access a webservice using axis2 I am getting the following error request you to help me out in this regard.

(org.apache.commons.httpclient.HttpMethodDirector) — I/O exception (java.net.ConnectException) caught when processing request: Connection refused
(org.apache.commons.httpclient.HttpMethodDirector) — Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:139)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:124)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:100)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:284)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:204)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:449)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:317)
at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:267)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:393)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:326)
at com.ab.Client.invoke(Client.java:46)

Источник