Problem

-- getting this error in Integrator trace file : "FORCED STOP: Reason Shared file system is not available. Timer has expired, no response within 30 seconds"

-- it triggers the restart of B2Bi

Resolution

* the monitoring of the shared file system performed by Integrator works as follow :

1. Integrator run constantly the command "stat" on $B2BI_SHARED_ROOT, $B2BI_SHARED_LOCAL and $B2BI_SHARED_DATA and waits for the status

2. if the status is not returns in B2BI_SHARED_FILE_SYSTEM_TIMEOUT/2 seconds, it first send a warning "Shared file system is not responding"

3. if the status is not returns in B2BI_SHARED_FILE_SYSTEM_TIMEOUT seconds, it returns the error "FORCED STOP: Reason Shared file system is not available. Timer has expired, no response within <B2BI_SHARED_FILE_SYSTEM_TIMEOUT> seconds"

* possible ways to investigate :

1- make sure the installation respects all pre-requisits listed here B2Bi Prerequisites and in particular the redHat version and the NFS requirements.

note that Some important NFS bugs that could cause this issue were fixed by RedHat in version 7.8, see https://bugzilla.redhat.com/show_bug.cgi?id=155220....

2- collect all Integrator/data/log, Integrator/data/trace ad Interchange/logs as soon as the problem occurs (some files like Interchange stat files are rotating rapidly and we may loose important info)

3- cross-check the error reported in Integrator trace file with Interchange stat files : <host>_cn_stats.log and <host>_te_stats.log :

-> Filesystemhealth checks the presence and permissions of the <shared>/common/data/backup/<host>_te folder, open a file stream for the test file, write few lines, and close the file stream

-> search file the string "FileSystemHealth" and check if the "Max" value has increased within the same period of time

4- analyze the OS monitoring tool (like nmon) to find potential issues occurring at the same time

5- monitor the access to the shared disk

-> refer to https://support.axway.com/kb/182513/language/en

-> possibly, add some other commands like ping, dd command, or Interchange dirtester tool to monitor the access to the shared

* possible workaround :

until the root cause of the slowness has been identified, increase the B2BI_SHARED_FILE_SYSTEM_TIMEOUT in $CORE_LOCAL/config/environment.dat (default is 30sec) or in Integration Engine System Manager -> System Profile -> Environment -> Miscellaneous -> "Shared file system timeout". Don't increase it to an excessive value, otherwise, B2Bi might remain frozen during such time and will not trigger the restart in an appropriate time