Solved

IFS 8 Prod crashes every 30 mins to 2 hours

  • 16 March 2022
  • 2 replies
  • 173 views

Userlevel 2
Badge +5

Hello,

 

Since March 10, 2022 our IFS 8 Prod environment has been crashing about every hour.

We have not been able to identify any changes to our database, firewalls, servers, scheduled tasks, integrations, IFS front end configurations, hosting

To get it back up, we log onto middleware server > instance > bin > stop all services then start all services. It stays online for a bit, then crashes again.

Best guess is that it seems to be connected to the # of users that login. 

 

Relevant details:

  • The Database does not go down during the crash
  • During/after a crash before we start all servers again, the ‘check server status’ script shows severs are up even though no one can access
  • It stays up over the weekend or during night shifts
    • significantly fewer users doing less types of tasks during these times
    • only confirming production, moving inventory, and quality control plans
  • Integrations & major functionality
    • Radley EDI, Radley data collection, TrueCommerce EDI
    • CBS, demand planner

 

What we’ve done so far:

  • Disabled all scheduled database tasks
  • disabled all event actions
  • disabled integration with Radley and TrueCommerce
  • increased “connection pool max size”
  • disabled CBS
  • disabled batch service and connect service

 

Has anyone experienced a similar issue where IFS won’t stay up?

 

Happy to provide any additional information. Thank you for your help.

icon

Best answer by ACIJGARRIEPY 29 March 2022, 20:44

View original

This topic has been closed for comments

2 replies

Userlevel 7
Badge +18

Hey Jesse - Do you have a case open with support about this? It’s good to see if anyone else has had this issue, but I’d make sure our support team knows what’s going on!

Userlevel 2
Badge +5

Hi @KristenGastaldo  thank you for your reply.

 

We were already working with IFS support at the time of this post.

 

We were unable to find a root cause and ended up redeploying our IFS Application from the IFS Build on a brand new server. The issue has not returned.

 

Thank you!