Skip to main content
Solved

FME Server fails without errors in log

  • November 14, 2023
  • 3 replies
  • 118 views

mathiku
Supporter
Forum|alt.badge.img+7

This is an FME Server that has recently begun to cause problems. One of the scheduled jobs fails but there is no information in the log.

Any leads on how to proceed and solve this problem?

 

FME Server 2022.2

Build 22765 - win64FME Server failure without log

Best answer by virtualcitymatt

It could be that this job is crashing - often a crash wont be reported in the log. If a job crashes then FME Server will try and resubmit it a few times before giving up.

 

To confirm this you can look in the fmeprocessmonitorengine.log (logs>engine>current>fmeprocessmonitorengine.log) you should see something about an engine ending unexpectedly.

 

and also you might be able to see multiple versions of the same log in the logs>engine>current>jobs folder. Multiple job logs will be saved in a folder. Here's an example where a job crashed (in this case from memory/space issues) and was resubmitted twice.

 

image

View original
Did this help you find an answer to your question?

3 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+39
  • Celebrity
  • Best Answer
  • November 15, 2023

It could be that this job is crashing - often a crash wont be reported in the log. If a job crashes then FME Server will try and resubmit it a few times before giving up.

 

To confirm this you can look in the fmeprocessmonitorengine.log (logs>engine>current>fmeprocessmonitorengine.log) you should see something about an engine ending unexpectedly.

 

and also you might be able to see multiple versions of the same log in the logs>engine>current>jobs folder. Multiple job logs will be saved in a folder. Here's an example where a job crashed (in this case from memory/space issues) and was resubmitted twice.

 

image


mathiku
Supporter
Forum|alt.badge.img+7
  • Author
  • Supporter
  • November 15, 2023
virtualcitymatt wrote:

It could be that this job is crashing - often a crash wont be reported in the log. If a job crashes then FME Server will try and resubmit it a few times before giving up.

 

To confirm this you can look in the fmeprocessmonitorengine.log (logs>engine>current>fmeprocessmonitorengine.log) you should see something about an engine ending unexpectedly.

 

and also you might be able to see multiple versions of the same log in the logs>engine>current>jobs folder. Multiple job logs will be saved in a folder. Here's an example where a job crashed (in this case from memory/space issues) and was resubmitted twice.

 

image

Thanks a lot, in this case this would make sense.

Edit: That seems to be the case. The logs look just like your picture.

What could be the cause? Lack of memory?

Event viewer doesn't add much information.


timatsafe
Safer
Forum|alt.badge.img+4
  • Safer
  • November 16, 2023
mathiku wrote:

Thanks a lot, in this case this would make sense.

Edit: That seems to be the case. The logs look just like your picture.

What could be the cause? Lack of memory?

Event viewer doesn't add much information.

Hi @mathiku​,

 

If you could submit a support case with your logs attached here we'd be happy to help you out!

Here's some info on How to Create a Great FME Flow Support Case

Cheers,

 

Tim


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings