Steps to be followed for FOS Crash Issue

Steps to be followed for FOS Crash Issue

Kindly enable the access logger of Tomcat of the product. This can be done by modifying the <MASTER_prod_home>/conf/server.xml file. Have a BACKUP of this file by creating a COPY of it before doing any modifications.
1) Search for "access log" string in that file
2) After the "-->" string occurring after "access log", insert the following:
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" pattern="%t %u %U %{JSESSIONIDSSO}c &quot;%{Referer}i&quot; %a %A %m %D %b %s %r &quot;%{User-Agent}i&quot;" prefix="localhost_access_log." resolveHosts="false" suffix=".log"/>
3) Save and close the file
4) Restart the server

Shut down the MASTER.
After this re-name the existing Slave setup's folder name and try to create a new mirror setup.

Have attached a web.xml file with this ticket. Replace it with the file in <MASTER_prod_home>fos/WEB-INF. Before replacing, kindly create a BACKUP COPY of that file.
Start the MASTER now.

A new mirror setup (Slave) will be created now and certain configuration changes have been made to test whether everything works fine.

Upon the FOS service failing next time, kindly ask the the whole log folder of the Master, the fos log of the Master and the fos log of the Slave.

      New to M365 Manager Plus?
      New to M365 Manager Plus?
        New to RecoveryManager Plus?
        New to RecoveryManager Plus?
          New to Exchange Reporter Plus?
          New to Exchange Reporter Plus?
            New to SharePoint Manager Plus?
            New to SharePoint Manager Plus?
                See all integrations
                New to ADManager Plus?
                See all integrations
                New to ADManager Plus?

                  New to ADSelfService Plus?

                  Start your free trial
                  Start your free trial

                    • Related Articles

                    • FAQs for FOS(Failover Service)

                      Q1: What is FOS? FOS stands for "Fail Over Service." It is a feature designed to address unexpected hardware or software failures that could potentially render a service desk application unavailable. In the context of SDPMSP , the Fail Over Service ...

                    • FOS Notification Mail Related Details

                      Case 1 : Master FOS service , Master MSP Service , Slave FOS service will alone gets started in services.msc (windows). Slave MSP service will always be in down status. (Refer Case 1 in below table which is default status when the FOS is enabled)  ...

                    • Application startup issue with Windows Services

                      Upon starting the application from Windows Services (from the windows server), if you receive an error like "Error2: The system cannot find the file specified", please follow the below steps to fix the issue: ** Right-click on the ManageEngine ...

                    • Pre-requisites for FOS - Adapter / NIC address

                      1. Whether it's two different Physical VM servers (with different hosts) - In this case, you will have a different NIC address / Adapter name. (Adapter name won't be the same) - This model we will support. 2. One VM server where 2 partitioned servers ...

                    • JIRA integration - Issue Types are not loaded

                      Post the JIRA is integrated with SDP MSP , the Projects data gets populated. However the other field - Issue Types will not show any values. To fix this follow the below steps The api call is used to fetch the issue types is ...

                      Related Products