Skip to main content
Hi,

 

 

We are seeing some very strange behaviour from FME Server 2015.0 (windows) where:
  • all the job logs are being deleted instantely (or perhaps every second) even though the maintance job is set up to run every month.
  • If we disable the maintenance 'delete jobs' schedule the logs persist.
  • One of our regular scheduled jobs continues to appear in the job queue list, even though we have disabled it - we then cannot delete the entries in the queue either.
  • Other schedueled jobs, and jobs being triggered outside of the schedular, appear to run as normal.
It's like something has become disattached from FME server core, and submitting jobs on their own.

 

 

We have tried a restart of FME server, and i'm told the task manager process window was checked for rogue processes, however the issue still persists.

 

 

I think my IT service provider will be rasieing a support call, however can anyone suggest things to look at.

 

 

I've suggested a full server reboot to kill all processes - but i'm concerned that something may be 'stored' somewhere and reset it.

 

 

Has anyone else experienced this issue or can anyone offer any suggestions as to the cause of this error and what to look for?

 

 

The architecture is based on 2 windows servers, both running engines but with the core service in an active-passive configuration.  

 

 

We have an oracle database acting as the  repository DB (tweaking the backup regime on this potentially to instigated the issue - but we're not sure how/why)

 

 

The logs and file repository are running on a windows fileshare.

 

 

AD authentication is on.

 

 

Regards,

 

Nick
Hi

 

 

The disappearing logs might be due to low disk space.

 

 

Have a look in the file "<hostname>_fmecleanup.log", typically located under

 

C:\\ProgramData\\Safe Software\\FME Server\\Logs\\service\\current\\<hostname>_fmecleanup.log

 

 

You can configure the cleanup service in fmeServerConfig.txt under the heading "Cleanup Watch". You will have to restart the FME Server services if you modify the values.

 

 

If that doesn't help, the FME Server logs files must be analyzed further.

 

 

David

 

 

Reply