This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Fresh Large Filr install, Service Unavailable, try again later

Fresh install, 3 Filr Appliances, 2 search, and 1 MS SQL DB.   No errors during the deploy or initial configuration.  However unable to login with admin/admin on 8443 to configure.    In Appserver.log seems to start throwing errors when starting memcachedclient with registering "sessionFactory".  Over in Catalina.out it is throwing errors when trying to register means with log4j2.      Ideas?

HOME=/var/lib/wwwrun
_=/usr/lib64/jvm/java/bin/java}
2023-05-23T10:18:47,418 INFO [Catalina-utility-3] [org.kablink.util.dao.hibernate.DynamicDialect] - Database product name: Microsoft SQL Server, Database product version: 15.00.2000
2023-05-23T10:18:47,421 INFO [Catalina-utility-3] [org.kablink.util.dao.hibernate.DynamicDialect] - Database dialect class: org.hibernate.dialect.SQLServerDialect
2023-05-23T10:18:47,445 INFO [Catalina-utility-3] [com.googlecode.hibernate.memcached.MemcachedCacheProvider] - Starting MemcachedClient...
2023-05-23T10:18:47,458 WARN [Catalina-utility-3] [org.kablink.teaming.spring.web.context.support.XmlWebApplicationContext] - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.cache.CacheException: Unable to initialize MemcachedClient
2023-05-23T10:18:47,459 ERROR [Catalina-utility-3] [org.springframework.web.context.ContextLoader] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.cache.CacheException: Unable to initialize MemcachedClient

22-May-2023 23:15:57.813 INFO [Catalina-utility-2] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
22-May-2023 23:15:57.908 INFO [Catalina-utility-4] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
22-May-2023 23:15:58.465 WARNING [Catalina-utility-3] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [/ssf] at path [/logs] was not loaded as the canonical path [null] did not match. Use of symlinks is one possible cause.
2023-05-22 23:15:58,492 Catalina-utility-4 ERROR Could not register mbeans javax.management.InstanceAlreadyExistsException: org.apache.logging.log4j2:type=3f28054d,component=Loggers,name=org.springframework
at java.management/com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:436)
at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1855)
at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:955)
at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:890)
at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:320)
at java.management/com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
at org.apache.logging.log4j.core.jmx.Server.register(Server.java:400)
at org.apache.logging.log4j.core.jmx.Server.registerLoggerConfigs(Server.java:362)
at org.apache.logging.log4j.core.jmx.Server.reregisterMBeansAfterReconfigure(Server.java:186)
at org.apache.logging.log4j.core.jmx.Server.reregisterMBeansAfterReconfigure(Server.java:141)
at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:637)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:699)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:716)
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:270)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
at org.kablink.teaming.rest.servlet.listener.SessionListener.<clinit>(SessionListener.java:47)
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.newInstance(Constructor.java:490)
at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:142)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4420)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4939)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:683)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:658)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:662)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:689)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1888)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:829)

Parents Reply Children
  • 0 in reply to   

    No resolution yet.    I had our VMWare admin redeploy the Filr and Search VMs, and I snapshot them before I even powered them on.  And when I ran thru the basic appliance vm setup, the problem is there right away.  Very odd.   I just spent some time in our FW management console, watching while I restarted it to see if I could see any blocks, and only thing I saw was successfully connections being built to the NAS share.  No blocks.  So doesn't appear to be Firewall related.   Planning on bugging supervisor to approve a ticket.