Jump to content

This topic is 735 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Hi, 

I host my FMS17 server now on a EC2 T3-Medium AWS instance, which for cost reasons I stop at night and start during business hours. 

It seems that Zulu does not like that, it does not auto-restart.

Every day I have to access the instance and manually restart Zulu with the 360work Java app. 

I might say, that this was not always so.. Only once I upgrade the machine from a t2 to a t3. Is there a way to circumvent this?

What can I do? 

Link to post
Share on other sites
  • 2 weeks later...

Hello,

Sorry for the late reply. Next time you boot the instance, can you send us the logs? You can find them in the following directory:

Mac: Library/360Works/Applications/Logs
Win: Program Files\360Works\Applications\Logs

The logs I'd like you to find will be called "Zulu.[date].log", "catalina.[date].log", "manager.[date].log", where the date is the day you produced the issue in the format YYYY-MM-DD.

When you find the logs, e-mail them to us at support@360works.com. Once we receive them, we'll take a look at what's going on and get back to you.

Link to post
Share on other sites

This topic is 735 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.