upgrade to 8.8.15 and now - Firefox can’t establish a connection

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
snowymoountain
Advanced member
Advanced member
Posts: 111
Joined: Thu Aug 02, 2018 4:24 pm

upgrade to 8.8.15 and now - Firefox can’t establish a connection

Post by snowymoountain »

Hi All seems OK...

However when you go to login the connection is refused.

I've upgraded and all seemed OK.

Has anyone any suggestions to resolve this ?

Release 8.8.15_GA_3953.RHEL8_64_20200629025823 RHEL8_64 FOSS edition.

[zimbra@newmail ~]$ zmcontrol start
Host our server.com
Starting ldap...Done.
Starting zmconfigd...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting memcached...Done.
Starting proxy...Done.
Starting amavis...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Done.
Starting stats...Done.
Starting service webapp...Done.
Starting zimbra webapp...Done.
Starting zimbraAdmin webapp...Done.
Starting zimlet webapp...Done.


when using a browser...
Unable to connect

Firefox can’t establish a connection to the server at 192.168.100.78:7071.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
phoenix
Ambassador
Ambassador
Posts: 27278
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

Re: upgrade to 8.8.15 and now - Firefox can’t establish a connection

Post by phoenix »

Is the Zimbra server listening to that port and can you telnet to it from another machine?
Regards

Bill

Rspamd: A high performance spamassassin replacement

Per ardua ad astra
snowymoountain
Advanced member
Advanced member
Posts: 111
Joined: Thu Aug 02, 2018 4:24 pm

Re: upgrade to 8.8.15 and now - Firefox can’t establish a connection

Post by snowymoountain »

Thanks Bill,

it appears to be but this is what I have
java 4071834 zimbra 151u IPv4 62395778 0t0 TCP 127.0.0.1:7171 (LISTEN)
mysqld 4073348 zimbra 19u IPv4 62390126 0t0 TCP 127.0.0.1:7306 (LISTEN)
zmlogger: 4073354 zimbra 3u IPv4 62380068 0t0 TCP 127.0.0.1:10663 (LISTEN)
memcached 4073876 zimbra 26u IPv4 62385761 0t0 TCP *:11211 (LISTEN)
memcached 4073876 zimbra 27u IPv6 62385762 0t0 TCP *:11211 (LISTEN)
nginx 4073902 zimbra 8u IPv4 62391713 0t0 TCP *:143 (LISTEN)
nginx 4073902 zimbra 9u IPv4 62391714 0t0 TCP *:993 (LISTEN)
nginx 4073902 zimbra 10u IPv4 62391715 0t0 TCP *:110 (LISTEN)
nginx 4073902 zimbra 11u IPv4 62391716 0t0 TCP *:995 (LISTEN)
nginx 4073902 zimbra 12u IPv4 62391717 0t0 TCP *:80 (LISTEN)
nginx 4073902 zimbra 13u IPv4 62391718 0t0 TCP *:443 (LISTEN)
nginx 4073902 zimbra 14u IPv4 62391719 0t0 TCP *:9071 (LISTEN)
nginx 4073903 zimbra 8u IPv4 62391713 0t0 TCP *:143 (LISTEN)
nginx 4073903 zimbra 9u IPv4 62391714 0t0 TCP *:993 (LISTEN)
nginx 4073903 zimbra 10u IPv4 62391715 0t0 TCP *:110 (LISTEN)
nginx 4073903 zimbra 11u IPv4 62391716 0t0 TCP *:995 (LISTEN)
nginx 4073903 zimbra 12u IPv4 62391717 0t0 TCP *:80 (LISTEN)
nginx 4073903 zimbra 13u IPv4 62391718 0t0 TCP *:443 (LISTEN)
nginx 4073903 zimbra 14u IPv4 62391719 0t0 TCP *:9071 (LISTEN)
nginx 4073904 zimbra 8u IPv4 62391713 0t0 TCP *:143 (LISTEN)
nginx 4073904 zimbra 9u IPv4 62391714 0t0 TCP *:993 (LISTEN)
nginx 4073904 zimbra 10u IPv4 62391715 0t0 TCP *:110 (LISTEN)
nginx 4073904 zimbra 11u IPv4 62391716 0t0 TCP *:995 (LISTEN)
nginx 4073904 zimbra 12u IPv4 62391717 0t0 TCP *:80 (LISTEN)
nginx 4073904 zimbra 13u IPv4 62391718 0t0 TCP *:443 (LISTEN)
nginx 4073904 zimbra 14u IPv4 62391719 0t0 TCP *:9071 (LISTEN)
nginx 4073905 zimbra 8u IPv4 62391713 0t0 TCP *:143 (LISTEN)
nginx 4073905 zimbra 9u IPv4 62391714 0t0 TCP *:993 (LISTEN)
nginx 4073905 zimbra 10u IPv4 62391715 0t0 TCP *:110 (LISTEN)
nginx 4073905 zimbra 11u IPv4 62391716 0t0 TCP *:995 (LISTEN)
nginx 4073905 zimbra 12u IPv4 62391717 0t0 TCP *:80 (LISTEN)
nginx 4073905 zimbra 13u IPv4 62391718 0t0 TCP *:443 (LISTEN)
nginx 4073905 zimbra 14u IPv4 62391719 0t0 TCP *:9071 (LISTEN)
amavis-se 4073926 zimbra 12u IPv4 62388655 0t0 TCP 127.0.0.1:23232 (LISTEN)
amavis-se 4073929 zimbra 11u IPv4 62391725 0t0 TCP 127.0.0.1:23233 (LISTEN)
/opt/zimb 4073989 zimbra 5u IPv4 62382762 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4073989 zimbra 7u IPv4 62382763 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4073989 zimbra 8u IPv4 62382764 0t0 TCP 127.0.0.1:10032 (LISTEN)
/opt/zimb 4073990 zimbra 5u IPv4 62382762 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4073990 zimbra 7u IPv4 62382763 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4073990 zimbra 8u IPv4 62382764 0t0 TCP 127.0.0.1:10032 (LISTEN)
/opt/zimb 4073991 zimbra 5u IPv4 62382762 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4073991 zimbra 7u IPv4 62382763 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4073991 zimbra 8u IPv4 62382764 0t0 TCP 127.0.0.1:10032 (LISTEN)
/opt/zimb 4073994 zimbra 5u IPv4 62382762 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4073994 zimbra 7u IPv4 62382763 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4073994 zimbra 8u IPv4 62382764 0t0 TCP 127.0.0.1:10032 (LISTEN)
/opt/zimb 4073997 zimbra 5u IPv4 62382762 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4073997 zimbra 7u IPv4 62382763 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4073997 zimbra 8u IPv4 62382764 0t0 TCP 127.0.0.1:10032 (LISTEN)
/opt/zimb 4074000 zimbra 5u IPv4 62382762 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4074000 zimbra 7u IPv4 62382763 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4074000 zimbra 8u IPv4 62382764 0t0 TCP 127.0.0.1:10032 (LISTEN)
/opt/zimb 4074003 zimbra 5u IPv4 62382762 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4074003 zimbra 7u IPv4 62382763 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4074003 zimbra 8u IPv4 62382764 0t0 TCP 127.0.0.1:10032 (LISTEN)
/opt/zimb 4074006 zimbra 5u IPv4 62382762 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4074006 zimbra 7u IPv4 62382763 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4074006 zimbra 8u IPv4 62382764 0t0 TCP 127.0.0.1:10032 (LISTEN)
/opt/zimb 4074009 zimbra 5u IPv4 62382762 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4074009 zimbra 7u IPv4 62382763 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4074009 zimbra 8u IPv4 62382764 0t0 TCP 127.0.0.1:10032 (LISTEN)
/opt/zimb 4074012 zimbra 5u IPv4 62382762 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4074012 zimbra 7u IPv4 62382763 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4074012 zimbra 8u IPv4 62382764 0t0 TCP 127.0.0.1:10032 (LISTEN)
/opt/zimb 4074015 zimbra 5u IPv4 62382762 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4074015 zimbra 7u IPv4 62382763 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4074015 zimbra 8u IPv4 62382764 0t0 TCP 127.0.0.1:10032 (LISTEN)
httpd 4074049 zimbra 3u IPv4 62401714 0t0 TCP *:7780 (LISTEN)
httpd 4074055 zimbra 3u IPv4 62401714 0t0 TCP *:7780 (LISTEN)
httpd 4074056 zimbra 3u IPv4 62401714 0t0 TCP *:7780 (LISTEN)
httpd 4074057 zimbra 3u IPv4 62401714 0t0 TCP *:7780 (LISTEN)
snowymoountain
Advanced member
Advanced member
Posts: 111
Joined: Thu Aug 02, 2018 4:24 pm

Re: upgrade to 8.8.15 and now - Firefox can’t establish a connection

Post by snowymoountain »

phoenix wrote:Is the Zimbra server listening to that port and can you telnet to it from another machine?
Yes, I SSH'd to it to get this information.
snowymoountain
Advanced member
Advanced member
Posts: 111
Joined: Thu Aug 02, 2018 4:24 pm

Re: upgrade to 8.8.15 and now - Firefox can’t establish a connection

Post by snowymoountain »

it starts OK with

zmcontrol start but quickly falls over

snippet
2021-07-20 09:44:59,370 INFO [main] [] extensions - attachment scan is disabled
2021-07-20 09:44:59,370 INFO [main] [] extensions - Initialized extension clamscanner: com.zimbra.clam.ClamScannerExt@com.zimbra.cs.extension.ZimbraExtensionClassLoader@6c8dbf56
2021-07-20 09:44:59,378 INFO [main] [] extensions - registered handler at /nginx-lookup
2021-07-20 09:44:59,379 INFO [main] [] extensions - Initialized extension nginx-lookup: com.zimbra.cs.nginx.NginxLookupExtension@com.zimbra.cs.extension.ZimbraExtensionClassLoader@54089484
2021-07-20 09:44:59,382 INFO [main] [] extensions - Initialized extension versioncheck: com.zimbra.cs.versioncheck.VersionCheckExtension@com.zimbra.cs.extension.ZimbraExtensionClassLoader@5b5dce5c
2021-07-20 09:44:59,386 INFO [main] [] extensions - Initialized extension zimbrasamba: com.zimbra.ldaputils.ZimbraLDAPUtilsExtension@com.zimbra.cs.extension.ZimbraExtensionClassLoader@fb49fdf
2021-07-20 09:44:59,388 INFO [main] [] extensions - Registering zm-gql
2021-07-20 09:44:59,517 INFO [main] [] extensions - Loading standard graphql schema builder.
2021-07-20 09:44:59,519 INFO [main] [] extensions - Loading com.zimbra.graphql.repositories.impl.ZXMLAccountRepository . . .
2021-07-20 09:44:59,521 INFO [main] [] extensions - Loading com.zimbra.graphql.repositories.impl.ZXMLAuthRepository . . .
2021-07-20 09:44:59,521 INFO [main] [] extensions - Loading com.zimbra.graphql.repositories.impl.ZNativeAuthRepository . . .
2021-07-20 09:44:59,523 INFO [main] [] extensions - Loading com.zimbra.graphql.repositories.impl.ZXMLCalendarRepository . . .
2021-07-20 09:44:59,525 INFO [main] [] extensions - Loading com.zimbra.graphql.repositories.impl.ZXMLContactRepository . . .
2021-07-20 09:44:59,526 INFO [main] [] extensions - Loading com.zimbra.graphql.repositories.impl.ZXMLFolderRepository . . .
2021-07-20 09:44:59,527 INFO [main] [] extensions - Loading com.zimbra.graphql.repositories.impl.ZXMLMessageRepository . . .
2021-07-20 09:44:59,528 INFO [main] [] extensions - Loading com.zimbra.graphql.repositories.impl.ZXMLSearchRepository . . .
2021-07-20 09:44:59,530 INFO [main] [] extensions - Loading com.zimbra.graphql.repositories.impl.ZXMLTaskRepository . . .
2021-07-20 09:44:59,530 INFO [main] [] extensions - Generating schema with loaded resolvers . . .
2021-07-20 09:45:00,259 WARN [main] [] AnnotatedArgumentBuilder - No explicit argument name given and the parameter name lost in compilation: public abstract boolean org.w3c.dom.TypeInfo.isDerivedFrom(java.lang.String,java.lang.String,int)#java.lang.String arg0. For details and possible solutions see https://github.com/leangen/graphql-spqr ... ument-name
2021-07-20 09:45:00,259 WARN [main] [] AnnotatedArgumentBuilder - No explicit argument name given and the parameter name lost in compilation: public abstract boolean org.w3c.dom.TypeInfo.isDerivedFrom(java.lang.String,java.lang.String,int)#java.lang.String arg1. For details and possible solutions see https://github.com/leangen/graphql-spqr ... ument-name
2021-07-20 09:45:00,259 WARN [main] [] AnnotatedArgumentBuilder - No explicit argument name given and the parameter name lost in compilation: public abstract boolean org.w3c.dom.TypeInfo.isDerivedFrom(java.lang.String,java.lang.String,int)#int arg2. For details and possible solutions see https://github.com/leangen/graphql-spqr ... ument-name
2021-07-20 09:45:00,785 INFO [main] [] extensions - registered handler at /graphql
2021-07-20 09:45:00,785 INFO [main] [] extensions - Initialized extension zm-gql: com.zimbra.graphql.resources.GQLExtension@com.zimbra.cs.extension.ZimbraExtensionClassLoader@10c47c79
2021-07-20 09:45:00,788 INFO [main] [] extensions - registered handler at /oauth2
2021-07-20 09:45:00,788 INFO [main] [] extensions - Initialized extension zm-oauth-social: com.zimbra.oauth.resources.OAuth2Extension@com.zimbra.cs.extension.ZimbraExtensionClassLoader@12a2585b
2021-07-20 09:45:00,794 INFO [main] [] mailbox - Starting ZAL version 2.10.0 commit 833a7ac872e01d24a48ca2183d698c6304e6af5c
2021-07-20 09:45:00,799 INFO [main] [] mailbox - File /opt/zimbra/lib/ext/zimbradrive/extension-path not present, using standard boot
2021-07-20 09:45:00,800 INFO [main] [] extensions - Searching ZAL extension in directory /opt/zimbra/lib/ext/zimbradrive
2021-07-20 09:45:00,800 WARN [main] [] extensions - Ignoring file non zip-file /opt/zimbra/lib/ext/zimbradrive/zimbradrive-extension.conf.example
2021-07-20 09:45:00,889 INFO [main] [] extensions - Initialized extension Zimbra Abstraction Layer for: zimbradrive: org.openzal.zal.extension.ZalEntrypointImpl@com.zimbra.cs.extension.ZimbraExtensionClassLoader@2c9a6717
2021-07-20 09:45:00,889 INFO [IncomingDirectorySweeper] [] store - IncomingDirectorySweeper thread starting
2021-07-20 09:45:00,896 INFO [main] [] store - Starting up FileCache at /opt/zimbra/data/tmp/uncompressed. maxFiles=2147483647, maxBytes=9223372036854775807.
2021-07-20 09:45:00,897 INFO [main] [] FileDescriptorCache - Loading settings: zimbraMailFileDescriptorCacheSize=1000.
2021-07-20 09:45:01,074 INFO [main] [] EhcacheManager - Cache 'imap-active-session-cache' created in EhcacheManager.
2021-07-20 09:45:01,153 INFO [main] [] OffHeapDiskStore - The index for data file ehcache-disk-store.data is more recent than the data file itself by 4ms : this is harmless.
2021-07-20 09:45:01,183 INFO [main] [] EhcacheManager - Cache 'imap-inactive-session-cache' created in EhcacheManager.
2021-07-20 09:45:01,187 INFO [main] [] AnnotationSizeOfFilter - Using regular expression provided through VM argument org.ehcache.sizeof.filters.AnnotationSizeOfFilter.pattern for IgnoreSizeOf annotation : ^.*cache\..*IgnoreSizeOf$
2021-07-20 09:45:01,198 INFO [main] [] JvmInformation - Detected JVM data model settings of: 64-Bit OpenJDK JVM with Compressed OOPs
2021-07-20 09:45:01,256 INFO [main] [] AgentLoader - Failed to attach to VM and load the agent: class java.io.IOException: Can not attach to current VM
2021-07-20 09:45:01,269 INFO [main] [] OffHeapDiskStore - The index for data file ehcache-disk-store.data is more recent than the data file itself by 18529499601ms : this is harmless.
2021-07-20 09:45:01,270 INFO [main] [] EhcacheManager - Cache 'sync-state-item-cache' created in EhcacheManager.
2021-07-20 09:45:01,284 INFO [main] [] redolog - Starting pre-startup crash recovery
2021-07-20 09:45:01,303 INFO [FileLogWriter.FsyncThread-1626770701302] [] redolog - Starting fsync thread with interval 10
2021-07-20 09:45:01,305 INFO [main] [] redolog - waiting for FileLogWriter.FsyncThread-1626770701302 to finish.
2021-07-20 09:45:01,313 INFO [FileLogWriter.FsyncThread-1626770701302] [] redolog - fsync thread exiting
2021-07-20 09:45:01,314 INFO [main] [] redolog - FileLogWriter.FsyncThread-1626770701302 finished
2021-07-20 09:45:01,318 INFO [main] [] redolog - No uncommitted transactions to redo
2021-07-20 09:45:01,318 INFO [main] [] redolog - waiting for FileLogWriter.FsyncThread-1626770701318 to finish.
2021-07-20 09:45:01,318 INFO [FileLogWriter.FsyncThread-1626770701318] [] redolog - Starting fsync thread with interval 10
2021-07-20 09:45:01,328 INFO [FileLogWriter.FsyncThread-1626770701318] [] redolog - fsync thread exiting
2021-07-20 09:45:01,329 INFO [main] [] redolog - FileLogWriter.FsyncThread-1626770701318 finished
2021-07-20 09:45:01,329 INFO [main] [] redolog - Finished pre-startup crash recovery
2021-07-20 09:45:01,330 INFO [FileLogWriter.FsyncThread-1626770701330] [] redolog - Starting fsync thread with interval 10
2021-07-20 09:45:01,339 INFO [main] [] misc - MINA setUseDirectBuffers(false)
2021-07-20 09:45:01,348 INFO [main] [] lmtp - Adding LMTP callback: com.zimbra.cs.mailbox.Notification
2021-07-20 09:45:01,348 INFO [main] [] lmtp - Adding LMTP callback: com.zimbra.cs.mailbox.QuotaWarning
2021-07-20 09:45:01,356 INFO [LmtpServer] [] TcpServer/7025 - Starting accept loop: 1 core threads, 20 max threads.
2021-07-20 09:45:01,439 INFO [main] [] pop - Starting Pop3Server on /0.0.0.0:7110
2021-07-20 09:45:01,447 FATAL [main] [] system - Exception during startup, aborting server, please check your config
com.zimbra.common.service.ServiceException: system failure: unable to list all servers


another

at org.eclipse.jetty.start.Main.start(Main.java:490)
at org.eclipse.jetty.start.Main.main(Main.java:77)
Caused by: LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to connect to server newmail.mydomain.com:389: java.io.IOException: An error occurred while attempting to establish a connection to server newmail.mydomain.com: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)
... 72 more
Caused by: java.io.IOException: An error occurred while attempting to establish a connection to server newmail.mydomain.com:389: java.net.ConnectException: Connection refused
at com.unboundid.ldap.sdk.LDAPConnectionInternals.<init>(LDAPConnectionInternals.java:137)
at com.unboundid.ldap.sdk.LDAPConnection.connect(LDAPConnection.java:744)
... 81 more
2021-07-20 09:47:04,161 INFO [main] [] ldap - master is down, falling back to replica...
2021-07-20 09:47:04,165 FATAL [main] [] system - failed to initialize LDAP client
com.zimbra.cs.ldap.LdapException: LDAP error: : An error occurred while attempting to connect to server newmail.mydomain.com:389: java.io.IOException: An error occurred while attempting to establish a connection to server newmail.mydomain.com:389: java.net.ConnectException: Connection refused
ExceptionId:main:1626770824163:16e9ee915d3fd3fa
Code:ldap.LDAP_ERROR
at 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)
another


42,213 INFO [LmtpServer-3] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,214 INFO [LmtpServer-9] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,214 INFO [LmtpServer-8] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,215 INFO [LmtpServer-7] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,215 INFO [LmtpServer-5] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,217 INFO [LmtpServer-12] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,222 INFO [LmtpServer-16] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,229 INFO [LmtpServer-17] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,236 INFO [LmtpServer-13] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,242 INFO [LmtpServer-18] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,242 INFO [LmtpServer-14] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,249 INFO [LmtpServer-19] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:22:42,260 INFO [LmtpServer-20] [name=admin@mydomain.com;mid=2;ip=192.168.100.78;] lmtp - try again for message from=admin@mydomain.com,to=admin@mydomain.com: another mail delivery in progress.
2021-07-20 10:23:40,964 WARN [LmtpServer] [] TcpServer/7025 - Thread pool is 105% utilized. 21 out of 20 threads in use.
2021-07-20 10:23:40,965 ERROR [LmtpServer] [] TcpServer/7025 - cannot handle connection; thread pool exhausted
java.util.concurrent.RejectedExecutionException: Task com.zimbra.cs.lmtpserver.TcpLmtpHandler@78bdc8b7 rejected from java.util.concurrent.ThreadPoolExecutor@6a315679[Running, pool size = 20, active threads = 20, queued tasks = 0, completed tasks = 39]
at java.base/java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2055)
at java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:825)
at java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1355)
at com.zimbra.cs.server.TcpServer.run(TcpServer.java:206)
at java.base/java.lang.Thread.run(Thread.java:830)
2021-07-20 10:23:41,039 WARN [LmtpServer] [] TcpServer/7025 - Thread pool is 105% utilized. 21 out of 20 threads in use.
2021-07-20 10:23:41,039 ERROR [LmtpServer] [] TcpServer/7025 - cannot handle connection; thread pool exhausted
java.util.concurrent.RejectedExecutionException: Task com.zimbra.cs.lmtpserver.TcpLmtpHandler@77fd19a6 rejected from java.util.concurrent.ThreadPoolExecutor@6a315679[Running, pool size = 20, active threads = 20, queued tasks = 0, completed tasks = 39]
at java.base/java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2055)
at java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:825)
at java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1355)
at com.zimbra.cs.server.TcpServer.run(TcpServer.java:206)
at java.base/java.lang.Thread.run(Thread.java:830)
User avatar
JDunphy
Outstanding Member
Outstanding Member
Posts: 899
Joined: Fri Sep 12, 2014 11:18 pm
Location: Victoria, BC
ZCS/ZD Version: 9.0.0_P39 NETWORK Edition

Re: upgrade to 8.8.15 and now - Firefox can’t establish a connection

Post by JDunphy »

Another set of eyes... perhaps this:

Code: Select all

... 81 more
2021-07-20 09:47:04,161 INFO [main] [] ldap - master is down, falling back to replica...
2021-07-20 09:47:04,165 FATAL [main] [] system - failed to initialize LDAP client
com.zimbra.cs.ldap.LdapException: LDAP error: : An error occurred while attempting to connect to server newmail.mydomain.com:389: java.io.IOException: An error occurred while attempting to establish a connection to server newmail.mydomain.com:389: java.net.ConnectException: Connection refused
Do you have an ldap running? Do a netstat to see if newmail.mydomain.com has a socket in a listen state for port 389. If it is, double check any FW settings that could be blocking the connection if this is on a different box.

Jim
snowymoountain
Advanced member
Advanced member
Posts: 111
Joined: Thu Aug 02, 2018 4:24 pm

Re: upgrade to 8.8.15 and now - Firefox can’t establish a connection

Post by snowymoountain »

JDunphy wrote:Another set of eyes... perhaps this:

Code: Select all

... 81 more
2021-07-20 09:47:04,161 INFO [main] [] ldap - master is down, falling back to replica...
2021-07-20 09:47:04,165 FATAL [main] [] system - failed to initialize LDAP client
com.zimbra.cs.ldap.LdapException: LDAP error: : An error occurred while attempting to connect to server newmail.mydomain.com:389: java.io.IOException: An error occurred while attempting to establish a connection to server newmail.mydomain.com:389: java.net.ConnectException: Connection refused
Do you have an ldap running? Do a netstat to see if newmail.mydomain.com has a socket in a listen state for port 389. If it is, double check any FW settings that could be blocking the connection if this is on a different box.

Jim
I do,
amavis Running
ldap Running
logger Running
mailbox Running
memcached Running
mta Stopped
postfix is not running
proxy Running
service webapp Running
snmp Running
spell Running
stats Running
zimbra webapp Running
zimbraAdmin webapp Running
zimlet webapp Running
zmconfigd Running
[zimbra@newmail ~]$


I have stopped postfix so I can get a backup off....
No idea what is blocking it


Tasks: 559 total, 1 running, 558 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 0.1 sy, 0.0 ni, 99.5 id, 0.0 wa, 0.3 hi, 0.1 si, 0.0 st
MiB Mem : 128554.7 total, 1386.8 free, 14326.9 used, 112841.0 buff/cache
MiB Swap: 4096.0 total, 3399.2 free, 696.8 used. 110286.4 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1816 root 20 0 0 0 0 S 1.3 0.0 86:29.12 kvdo0:indexW
1823 root 20 0 0 0 0 S 1.0 0.0 30:43.03 kvdo0:indexW
1826 root 20 0 0 0 0 S 1.0 0.0 40:07.92 kvdo0:indexW
1822 root 20 0 0 0 0 S 0.7 0.0 126:18.79 kvdo0:indexW
1566 root 20 0 0 0 0 S 0.3 0.0 31:02.29 callbackW
1588 root 20 0 0 0 0 S 0.3 0.0 6:28.37 kvdo0:hashQ0
1592 root 20 0 0 0 0 S 0.3 0.0 7:22.89 kvdo0:bioQ3
1593 root 20 0 0 0 0 S 0.3 0.0 8:33.92 kvdo0:ackQ
1814 root 20 0 0 0 0 S 0.3 0.0 62:25.78 kvdo0:indexW
1815 root 20 0 0 0 0 S 0.3 0.0 66:19.55 kvdo0:indexW
1817 root 20 0 0 0 0 S 0.3 0.0 67:35.92 kvdo0:indexW
1818 root 20 0 0 0 0 S 0.3 0.0 75:47.83 kvdo0:indexW
1819 root 20 0 0 0 0 S 0.3 0.0 9:32.92 kvdo0:indexW
1821 root 20 0 0 0 0 S 0.3 0.0 67:16.23 kvdo0:indexW
1824 root 20 0 0 0 0 S 0.3 0.0 62:40.84 kvdo0:indexW
1825 root 20 0 0 0 0 S 0.3 0.0 47:03.64 kvdo0:indexW
1828 root 20 0 0 0 0 S 0.3 0.0 52:38.02 kvdo0:indexW
1829 root 20 0 0 0 0 S 0.3 0.0 186:57.73 kvdo0:indexW
4134424 root 20 0 274888 5444 4272 R 0.3 0.0 0:00.14 top
1 root 20 0 245576 12020 8292 S 0.0 0.0 2:15.49 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.99 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H-kblockd
9 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
10 root 20 0 0 0 0 S 0.0 0.0 0:16.98 ksoftirqd/0
11 root 20 0 0 0 0 I 0.0 0.0 2:52.33 rcu_sched
12 root rt 0 0 0 0 S 0.0 0.0 0:00.02 migration/0
13 root rt 0 0 0 0 S 0.0 0.0 0:00.50 watchdog/0
14 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/0
15 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/1
16 root rt 0 0 0 0 S 0.0 0.0 0:00.34 watchdog/1
17 root rt 0 0 0 0 S 0.0 0.0 0:00.03 migration/1
18 root 20 0 0 0 0 S 0.0 0.0 0:07.67 ksoftirqd/1
20 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/1:0H-kblockd
21 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/2
22 root rt 0 0 0 0 S 0.0 0.0 0:00.35 watchdog/2
23 root rt 0 0 0 0 S 0.0 0.0 0:00.03 migration/2
24 root 20 0 0 0 0 S 0.0 0.0 0:04.72 ksoftirqd/2
26 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/2:0H-kblockd
27 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/3
28 root rt 0 0 0 0 S 0.0 0.0 0:00.32 watchdog/3
29 root rt 0 0 0 0 S 0.0 0.0 0:00.03 migration/3
30 root 20 0 0 0 0 S 0.0 0.0 0:03.47 ksoftirqd/3
32 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/3:0H-kblockd
33 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/4
snowymoountain
Advanced member
Advanced member
Posts: 111
Joined: Thu Aug 02, 2018 4:24 pm

Re: upgrade to 8.8.15 and now - Firefox can’t establish a connection

Post by snowymoountain »

JDunphy wrote:Another set of eyes... perhaps this:

Code: Select all

... 81 more
2021-07-20 09:47:04,161 INFO [main] [] ldap - master is down, falling back to replica...
2021-07-20 09:47:04,165 FATAL [main] [] system - failed to initialize LDAP client
com.zimbra.cs.ldap.LdapException: LDAP error: : An error occurred while attempting to connect to server newmail.mydomain.com:389: java.io.IOException: An error occurred while attempting to establish a connection to server newmail.mydomain.com:389: java.net.ConnectException: Connection refused
Do you have an ldap running? Do a netstat to see if newmail.mydomain.com has a socket in a listen state for port 389. If it is, double check any FW settings that could be blocking the connection if this is on a different box.

Jim

Thanks Jim,

The firewall is off and this is a stand alone server with no replica. This is what I get...

[root@newmail ~]# netstat --listen --program|grep -E "zimbra|java"
tcp 1 0 localhost.loca:webcache 0.0.0.0:* LISTEN 134753/java
tcp 0 0 0.0.0.0:vmsvc-2 0.0.0.0:* LISTEN 134753/java
tcp 0 0 0.0.0.0:7993 0.0.0.0:* LISTEN 134753/java
tcp 0 0 0.0.0.0:7995 0.0.0.0:* LISTEN 134753/java
tcp 0 0 0.0.0.0:pcsync-https 0.0.0.0:* LISTEN 134753/java
tcp 9 0 0.0.0.0:iwg1 0.0.0.0:* LISTEN 134753/java
tcp 0 0 0.0.0.0:7072 0.0.0.0:* LISTEN 134753/java
tcp 0 0 0.0.0.0:martalk 0.0.0.0:* LISTEN 134753/java
tcp 0 0 localhos:drm-production 0.0.0.0:* LISTEN 266147/java
tcp 0 0 0.0.0.0:7110 0.0.0.0:* LISTEN 134753/java
tcp 0 0 0.0.0.0:7143 0.0.0.0:* LISTEN 134753/java
udp 0 0 0.0.0.0:46694 0.0.0.0:* 266147/java
udp 0 0 0.0.0.0:52443 0.0.0.0:* 134753/java
unix 2 [ ACC ] STREAM LISTENING 63949048 86669/perl /opt/zimbra/data/tmp/amavisd-zmq.sock
unix 2 [ ACC ] STREAM LISTENING 63864777 86714/amavisd (mast /opt/zimbra/data/amavisd/amavisd.sock
unix 2 [ ACC ] STREAM LISTENING 63916206 86874/saslauthd /opt/zimbra/data/sasl2/state/mux
unix 2 [ ACC ] STREAM LISTENING 63867555 86064/mysqld /opt/zimbra/data/tmp/mysql/mysql.sock
unix 2 [ ACC ] STREAM LISTENING 63913086 84052/slapd /opt/zimbra/data/ldap/state/run/ldapi
[root@newmail ~]#


[root@newmail ~]# ps aux|grep java|awk '{print "owner:" $1 " PID:" $2 " path:"$11}'
owner:root PID:134752 path:/opt/zimbra/libexec/zmmailboxdmgr
owner:zimbra PID:134753 path:/opt/zimbra/common/bin/java
owner:zimbra PID:178584 path:/opt/zimbra/common/lib/jvm/java/bin/java
owner:zimbra PID:234907 path:/opt/zimbra/common/lib/jvm/java/bin/java
owner:zimbra PID:266147 path:/opt/zimbra/common/lib/jvm/java/bin/java
owner:zimbra PID:293701 path:/opt/zimbra/common/lib/jvm/java/bin/java
owner:zimbra PID:349912 path:/opt/zimbra/common/lib/jvm/java/bin/java
owner:root PID:368852 path:grep
[root@newmail ~]# ps aux|grep java|awk '{print "owner:" $1 " PID:" $2 " path:"$11}'|grep -v "path:grep"
owner:root PID:134752 path:/opt/zimbra/libexec/zmmailboxdmgr
owner:zimbra PID:134753 path:/opt/zimbra/common/bin/java
owner:zimbra PID:178584 path:/opt/zimbra/common/lib/jvm/java/bin/java
owner:zimbra PID:234907 path:/opt/zimbra/common/lib/jvm/java/bin/java
owner:zimbra PID:266147 path:/opt/zimbra/common/lib/jvm/java/bin/java
owner:zimbra PID:293701 path:/opt/zimbra/common/lib/jvm/java/bin/java
owner:zimbra PID:349912 path:/opt/zimbra/common/lib/jvm/java/bin/java

[zimbra@newmail ~]$ ps -alef | grep zimbra | grep slapd
1 S zimbra 389743 1 0 80 0 - 21035676 - 07:25 ? 00:00:00 /opt/zimbra/common/libexec/slapd -l LOCAL0 -u zimbra -h ldap://newmail.mydomain.com:389 ldapi:/// -F /opt/zimbra/data/ldap/config
0 S zimbra 396520 388946 0 80 0 - 2296 - 07:30 pts/0 00:00:00 grep --color=auto slapd
User avatar
JDunphy
Outstanding Member
Outstanding Member
Posts: 899
Joined: Fri Sep 12, 2014 11:18 pm
Location: Victoria, BC
ZCS/ZD Version: 9.0.0_P39 NETWORK Edition

Re: upgrade to 8.8.15 and now - Firefox can’t establish a connection

Post by JDunphy »

Try this given ldap didn't bind to the socket correctly or I am missing that on the output you have provided even though you are showing the process is running.

Code: Select all

# su - zimbra
% cd bin
% ./ldap status
slapd running pid: 1741585
% ./ldap stop
Killing slapd with pid 1741585. done.
% ./ldap start
Started slapd: pid 1814509
% netstat -na |grep 389 |grep LISTEN
tcp        0      0 192.168.1.15:389       0.0.0.0:*               LISTEN     
If that starts and you see port 389 in a LISTEN state, than issue a ldap stop and proceed to your normal zmcontrol start.

If this fails, you have a problem with your ldap DB or /etc/hosts doesn't have the ip address of newmail.mydomain.com ... This can happen if your zmhostname is different than your hostname. Just make sure you have an entry for the hostname also. install.sh seems to catch this anomaly during a new installation and warns you that your /etc/hosts is wrong but for an upgrade it can miss this. This is a wild guess on my part of course for you.

Jim
Post Reply