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)
Case 2 : When the Master set up goes down , Slave FOS service will automatically start the Slave MSP service and it will serve the user. If any of the Master MSP Service or Master FOS Service goes down , the other will automatically goes down. Here you will be notified as mentioned below to the configured email address.
Case 3 : When the Slave FOS Service goes down, then the Master Service will trigger an email stating the slave FOS is down.
Please note , When Server A is started as Master and Server B is started as Slave , then even during crash of Master , the Slave will serve the user but it will act only as Slave.
Users needs to fix the Master Issue and needs to run the Master again and have to Manually Stop the Slave services as mentioned in Case : 1 to restore the FOS set up.
Table format :
| S.No | Master FOS Service | Master MSP Service | Slave FOS Service | Slave MSP Service | Operation | Notification | Result |
| Case : 1 | Up | Up | Up | Down | Nothing | No | This is default configuration. |
| Case : 2 | Down | Down | Up | Up (Automatically UP) | Master MSP Service or Master FOS Service crashed | Yes , Mail will be sent Refer Mail format for Case : 2 (above) | |
| Case : 3 | Up | Up | Down (when this goes down) | Down (default) | Slave FoS Service crash | Yes , Mail will be sent refer Mail format for Case : 3 | After secondary FOS crash. |
| Case 4 : | Down | Down | Down(Acting master goes down alos) | Down | Both crashed | No mails will be sent |
Points to consider:
Example for Crash: Only for these cases , mails will be sent.
1. Removing from the network connection.
2. End process tree from the task managers.
Example for no Crash: for these cases , NO mails will be sent.
1. Manual shut down of the system.
2. Manual shut down of FOS and MSP services.
3. Kill the PID.
Startup Type of the both MSP FOS and MSP services (Refer screenshot)
1. Primary MSP FOS Service - Startup Type should be Automatic.
2. Primary MSP Service - Startup Type should be Manual.
3. Secondary MSP FOS Service - Startup Type should be Automatic.
4. Secondary MSP Service - Startup Type should be Manual.
New to ADSelfService Plus?
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 ...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 ...Script to send notification to users on upcoming contracts
Please follow the below link to setup python on the server https://pitstop.manageengine.com/portal/en/kb/articles/how-to-setup-python-on-the-server-11-11-2019 Steps to configure 1. Extract the attached zip file in <Home>/integration/custom_scripts ...Mail fetching - deleted flag issue
This message will be thrown, when you have provided a shared mailbox. The concept here is, SDP MSP reads the mail from the configured mailbox and adds it as a request. During the time, if some other application fetches the mail from the same mailbox ...Notification script using Custom function in custom trigger
This is applicable from 10600 builds. From 10600 , Business rules dont have Email notification feature. The same use case be achieved through Custom triggers feature as mentioned below. Script to enable notification of request creation using custom ...