Skip to main content

In one of our development environment, the MainServer1 service seems to restart at the top of every hour.  This makes the environment inaccessible until the service finishes restarting and returns to a status of running.

 

Any ideas what would cause this or how to fix it?

 

NOTE: We have a second development environment on this same server and do not have this issue with the services on this environment.

 

Thanks!

Hello,

 

did you have more information? 

it’s a cluster? a loadbalancing cluster? 

hours of restart is the same? did you have a patern? 

 

do you do a dump? it’s more easy to read logs with a dump. 


Did you tried recreating the IFS home instance?


@todscotta 

Server restarting basically means it is crashing due to some reason and the nodemanager is recovering it each time. If you need to find the root cause, you would have to go through the log files and see if you can find anything.

Logs can be found under “\\<IFS_HOME>\wls_domain\<InstanceID>\servers\” folder. Here you would find folders for each server and inside them you can find a folder name logs. In your case, you should focus on MainServer1 and Admin Server logs. 

Hope this helps.


Do you have any antivirus software scanning the IFS related directories at the top of the hour?

 


@todscotta,

Without looking at the logs it is difficult to pinpoint the issue. As mentioned by Charith visit the log files and see if you can find anything.


Furthermore Check event viewer entries in the server if you can identify anything outward, check if IFS java processes crashed or any system-level errors in OS. If any OS-related issue/third-party software causing errors there could be hits on the event viewer as well.


@todscotta  Could you please share the event logs? Were there any recent windows patch updates?