Skip to main content
Question

FMEServer jobs not running after restart and small change to config

  • January 29, 2020
  • 10 replies
  • 27 views
paalped
Contributor
Forum|alt.badge.img+5

Hi,

 

Im experiencing jobs with tag "satskred" stuck in Queue after a small modification to the fmeServerConfig.txt

these are my changes:

#--------------------------------------------------------------------------

 

# Job Routing

 

#--------------------------------------------------------------------------

 

TM_QUEUE_TYPE=DEFAULT

 

TM_ENGINE_1=Engine1:fast default

 

TM_ENGINE_2=Engine2:fast satskred

 

#--------------------------------------------------------------------------

 

# System Notifications

 

I've set the job tag as "satskred" on my Subscription Notification.

 

Before (job runs on 2 engines):

#--------------------------------------------------------------------------

 

# Job Routing

 

#--------------------------------------------------------------------------

 

TM_QUEUE_TYPE=DEFAULT

 

#--------------------------------------------------------------------------

 

# System Notifications

 

 

 

I need the job to run on 1 single engine.

 

Engines:

Subscriptinon Advanced:

Job status:

Restarting:

Making new changes:

# Job Routing

 

# Legger inn denne endringen for å kjøre satskred på én engine (Enigne2)

 

#--------------------------------------------------------------------------

 

TM_QUEUE_TYPE=DEFAULT

 

TM_DEFAULT_TAG=default

 

TM_ENGINE_1=Engine1:fast default

 

TM_ENGINE_2=Engine2:fast satskred default

 

#--------------------------------------------------------------------------

 

# System Notifications

 

Every job without satskred tag runs...

 

 

Help appreciated!

 

Paal

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.

10 replies

sigtill
Supporter
Forum|alt.badge.img+25
  • sigtillSupporter
  • Supporter
  • 956 replies
  • January 29, 2020

Hi @paalped Which version of FME Server do you use? I would suggest not to use the fmeconfig but rather create the queue from the FME Server GUI

The real SigTill
paalped
Contributor
Forum|alt.badge.img+5
  • paalpedContributor
  • Author
  • Contributor
  • 130 replies
  • January 29, 2020

Hi @paalped Which version of FME Server do you use? I would suggest not to use the fmeconfig but rather create the queue from the FME Server GUI

Hei Sigbjørn, The Customer is using FME Server 2016.

sigtill
Supporter
Forum|alt.badge.img+25
  • sigtillSupporter
  • Supporter
  • 956 replies
  • January 29, 2020

Did you restart the FME Server so it could properly load the fmeconfig and pick up the changes? @paalped

The real SigTill
sigtill
Supporter
Forum|alt.badge.img+25
  • sigtillSupporter
  • Supporter
  • 956 replies
  • January 29, 2020

Have you tried:

#--------------------------------------------------------------------------
# Job Routing
#--------------------------------------------------------------------------
TM_QUEUE_TYPE=DEFAULT
TM_ENGINE_1=Engine1:default
TM_ENGINE_2=Engine2:satskred
#--------------------------------------------------------------------------
# System Notifications
The real SigTill
paalped
Contributor
Forum|alt.badge.img+5
  • paalpedContributor
  • Author
  • Contributor
  • 130 replies
  • January 29, 2020

Did you restart the FME Server so it could properly load the fmeconfig and pick up the changes? @paalped

Yes I have restared FME Server Core (service) mutliple times. I believe there is something wrong with my tag name setup.

sigtill
Supporter
Forum|alt.badge.img+25
  • sigtillSupporter
  • Supporter
  • 956 replies
  • January 29, 2020

Is the engine actually called Engine1 and not COMPUTERNAME_Engine1 or LOCALHOST_Engine1 ?

The real SigTill
paalped
Contributor
Forum|alt.badge.img+5
  • paalpedContributor
  • Author
  • Contributor
  • 130 replies
  • January 29, 2020

Is the engine actually called Engine1 and not COMPUTERNAME_Engine1 or LOCALHOST_Engine1 ?

Ah, where can I find the engine name?

sigtill
Supporter
Forum|alt.badge.img+25
  • sigtillSupporter
  • Supporter
  • 956 replies
  • January 29, 2020

Seems to be wrong name of engine?

#--------------------------------------------------------------------------
# Job Routing
#--------------------------------------------------------------------------
TM_QUEUE_TYPE=DEFAULT
TM_ENGINE_1=FMESERV02_Engine1:default
TM_ENGINE_2=FMESERV02_Engine2:satskred default
#--------------------------------------------------------------------------
# System Notifications
The real SigTill
paalped
Contributor
Forum|alt.badge.img+5
  • paalpedContributor
  • Author
  • Contributor
  • 130 replies
  • January 29, 2020

Is the engine actually called Engine1 and not COMPUTERNAME_Engine1 or LOCALHOST_Engine1 ?

Thanks! I just followed the example, but sure the Engine name was different than the example :) Thank you!

sigtill
Supporter
Forum|alt.badge.img+25
  • sigtillSupporter
  • Supporter
  • 956 replies
  • January 29, 2020

Thanks! I just followed the example, but sure the Engine name was different than the example :) Thank you!

So now it works as expected @paalped ?

The real SigTill

Community Stats

32,102
Posts
121,896
Replies
39,749
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.