Hi,
ive got some login issues on my zimbra installation. I didnt changed anyhthing since a few weeks but after a reboot the server wont connect to localhost 389 anymore. it just refuses to connect and throws some IO errors.
Its a single server installation and worked for about an year...
When i try to start the instance it only shows:i have no firewall in front of this device and nothing locally installed.
my /etc/hosts file looks likeMy telnet also block without any reason.When i try to do something it only shows this IO error:ive installed another server and moved the whole /opt/zimbra dir to that one. After that it wont start again and fails with the same error.
Maybe i have a database failure but i cant find the real issue. And a move to a new server did nothing Does anyone ever saw this issue? Can anyone say me how to restore the database or move it to another server without this issues happening again?
ive got some login issues on my zimbra installation. I didnt changed anyhthing since a few weeks but after a reboot the server wont connect to localhost 389 anymore. it just refuses to connect and throws some IO errors.
Its a single server installation and worked for about an year...
When i try to start the instance it only shows:
Code:
zimbra@zmmail01:/root$ zmcontrol startHost zmmail01.domainConnect: Unable to determine enabled services from ldap.Unable to determine enabled services. Cache is out of date or doesn't exist.
my /etc/hosts file looks like
Code:
127.0.0.1 localhostOutside-IP zmmail01.domain zmmail01
Code:
root@zmmail01:~# telnet 127.0.0.1 389Trying 127.0.0.1...telnet: Unable to connect to remote host: Connection refusedroot@zmmail01:~# telnet localhost 389Trying 127.0.0.1...telnet: Unable to connect to remote host: Connection refusedroot@zmmail01:~# telnet zmmail01.domain 389Trying Outside-IP...telnet: Unable to connect to remote host: Connection refused
Code:
zimbra@zmmail01:/tmp$ zmprov getServer `zmhostname` | grep DNSMasterIP[] INFO: master is down, falling back to replica...[] FATAL: failed to initialize LDAP clientcom.zimbra.cs.ldap.LdapException: LDAP error: : An error occurred while attempting to connect to server zmmail01.domain:389: java.io.IOException: An error occurred while attempting to establish a connection to server zmmail01.domain:389: java.net.ConnectException: Connection refusedExceptionId:main:1625080364950:db0166bd84ec84adCode:ldap.LDAP_ERRORat com.zimbra.cs.ldap.LdapException.LDAP_ERROR(LdapException.java:90)at com.zimbra.cs.ldap.unboundid.UBIDLdapException.mapToLdapException(UBIDLdapException.java:74)at com.zimbra.cs.ldap.unboundid.UBIDLdapException.mapToLdapException(UBIDLdapException.java:40)at com.zimbra.cs.ldap.unboundid.LdapConnectionPool.createConnPool(LdapConnectionPool.java:117)at com.zimbra.cs.ldap.unboundid.LdapConnectionPool.createConnectionPool(LdapConnectionPool.java:63)at com.zimbra.cs.ldap.unboundid.UBIDLdapContext.init(UBIDLdapContext.java:111)at com.zimbra.cs.ldap.unboundid.UBIDLdapClient.init(UBIDLdapClient.java:39)at com.zimbra.cs.ldap.LdapClient.getInstanceIfLDAPavailable(LdapClient.java:62)at com.zimbra.cs.ldap.LdapClient.getInstance(LdapClient.java:69)at com.zimbra.cs.ldap.LdapClient.initialize(LdapClient.java:94)at com.zimbra.cs.account.ldap.LdapProv.<init>(LdapProv.java:47)at com.zimbra.cs.account.ldap.LdapProvisioning.<init>(LdapProvisioning.java:292)at com.zimbra.cs.account.ldap.LdapProvisioning.<init>(LdapProvisioning.java:289)at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)at java.base/java.lang.reflect.ReflectAccess.newInstance(ReflectAccess.java:166)at java.base/jdk.internal.reflect.ReflectionFactory.newInstance(ReflectionFactory.java:404)at java.base/java.lang.Class.newInstance(Class.java:591)at com.zimbra.cs.account.Provisioning.getInstance(Provisioning.java:354)at com.zimbra.cs.account.Provisioning.getInstance(Provisioning.java:310)at com.zimbra.cs.ephemeral.EphemeralStore.getFactory(EphemeralStore.java:303)at com.zimbra.cs.account.Entry.getEphemeralAttrs(Entry.java:393)at com.zimbra.cs.account.Entry.getAttrs(Entry.java:379)at com.zimbra.cs.account.Entry.getAttrs(Entry.java:352)at com.zimbra.cs.account.ProvUtil.dumpServer(ProvUtil.java:3144)at com.zimbra.cs.account.ProvUtil.doGetServer(ProvUtil.java:4941)at com.zimbra.cs.account.ProvUtil.execute(ProvUtil.java:1264)at com.zimbra.cs.account.ProvUtil.main(ProvUtil.java:4160)Caused by: LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to connect to server zmmail01.domain:389: java.io.IOException: An error occurred while attempting to establish a connection to server zmmail01.domain:389: java.net.ConnectException: Connection refused')at com.unboundid.ldap.sdk.LDAPConnection.connect(LDAPConnection.java:754)at com.unboundid.ldap.sdk.LDAPConnection.connect(LDAPConnection.java:686)at com.unboundid.ldap.sdk.LDAPConnection.<init>(LDAPConnection.java:518)at com.unboundid.ldap.sdk.SingleServerSet.getConnection(SingleServerSet.java:229)at com.unboundid.ldap.sdk.ServerSet.getConnection(ServerSet.java:98)at com.unboundid.ldap.sdk.LDAPConnectionPool.createConnection(LDAPConnectionPool.java:938)at com.unboundid.ldap.sdk.LDAPConnectionPool.<init>(LDAPConnectionPool.java:876)at com.unboundid.ldap.sdk.LDAPConnectionPool.<init>(LDAPConnectionPool.java:779)at com.unboundid.ldap.sdk.LDAPConnectionPool.<init>(LDAPConnectionPool.java:726)at com.zimbra.cs.ldap.unboundid.LdapConnectionPool.createConnPool(LdapConnectionPool.java:114)... 26 moreCaused by: java.io.IOException: An error occurred while attempting to establish a connection to server zmmail01.domain:389: java.net.ConnectException: Connection refusedat com.unboundid.ldap.sdk.LDAPConnectionInternals.<init>(LDAPConnectionInternals.java:137)at com.unboundid.ldap.sdk.LDAPConnection.connect(LDAPConnection.java:744)... 35 more
Maybe i have a database failure but i cant find the real issue. And a move to a new server did nothing Does anyone ever saw this issue? Can anyone say me how to restore the database or move it to another server without this issues happening again?
Statistics: Posted by ashoka232 — Fri Mar 22, 2024 4:50 am