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 - win64
Solved
FME Server fails without errors in log
+8- Supporter
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.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+47- Celebrity
- Best Answer
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.
+8- Supporter
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.
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.
+4- Safer
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