Question

Apps10 Middleware fails with leftover files on every stop-start

  • 25 January 2024
  • 1 reply
  • 52 views
R
Rank
Badge +3

The customer is able to start their server following the file deletions described in 

https://community.ifs.com/framework-experience-infrastructure-cloud-integration-dev-tools-50/common-reason-why-you-get-server-failed-not-restartable-after-a-vm-restart-8315

but they have to do this at every start. It seems like something in the shutdown fails, every time and leads to :

Line 1675: <Dec 1, 2023 7:21:01 PM CST> <INFO> <IFSPROD> <AdminServer> <Adjusted state of server 'AdminServer ' from RUNNING to FAILED_NOT_RESTARTABLE>
    Line 1677: <Dec 1, 2023 7:21:01 PM CST> <INFO> <IFSPROD> <IntServer1> <Adjusted state of server 'IntServer1 ' from FORCE_SHUTTING_DOWN to FAILED_NOT_RESTARTABLE>
    Line 1679: <Dec 1, 2023 7:21:01 PM CST> <INFO> <IFSPROD> <MainServer1> <Adjusted state of server 'MainServer1 ' from FORCE_SHUTTING_DOWN to FAILED_NOT_RESTARTABLE>
    Line 1719: <Dec 1, 2023 7:40:20 PM CST> <INFO> <IFSPROD> <AdminServer> <Adjusted state of server 'AdminServer ' from STARTING to FAILED_NOT_RESTARTABLE>

They are looking for a solution. We looked at the user and they seem to be local admins.

Other ideas?

Thanks.

Robert Heard

1 reply

U
Rank
Userlevel 4
Badge +7

Check the managed server and node manager logs for any more details of errors. It looks like the instance had face a runtime issue and recorded the details in the diagnostic files. Servers will not be started until the issues is fixed and diagnostic data is cleared. The other response mentioned simply clears the diagnostic data by deleting those files, so the issue may reoccur once again. I also noticed that it mentions changing the IP to VM name (address). According to the docs servers must be installed in VMs having static IPs.

Reply


Terms & ConditionsCookie settings