Solved

issue with component "Trigger". Publisher dirwatch does not exist

4 months ago
December 14, 2024
4 replies
48 views

+2

mbaumgartner
Contributor
1 reply

I am trying to create an automation using a trigger that watches a directory. If a file in the directory is added/created it launches an FME Workspace. However I keep getting the following error:

2024-12-14T20:10:08Z | 410109 : (Automations) Creating link from trigger...
3	2024-12-14T20:10:08Z | 410108 : (Automations) Creating dirwatch trigger...
4	2024-12-14T20:10:08Z | 410112 : (Automations) Unable to assemble automation. There was an issue with component "Trigger". Publisher dirwatch does not exist.

The same thing happens when I try add a trigger that watches an FTP? and I get the same error when trying to add a Publication under the Notification.

What am I missing? Do I need to add something special for a trigger to work? is it possible that I am missing some part of FME?

I am working with a FME FLOW 2024.1that is in a Azure Kubernetes cluster.

Any help or hint that could explain the error is highly appreciated.

Best answer by virtualcitymatt

mbaumgartner wrote:

I am working with a FME FLOW 2024.1that is in a Azure Kubernetes cluster.

This most likely is somehow related I would guess.

Are you able to set up a directory watch or FTP watch in the old fashioned way (e.g., Notifications(classic), Publications)? If you set up the publications you might see some more information in the specific publication logs (logs>core>current>publishers>dirwatch.log).

It’s also possible some ports are closed. You can see more info on ports here: https://docs.safe.com/fme/html/FME-Flow/ReferenceManual/FME-Flow-Ports.htm

View original

Did this help you find an answer to your question?

+35

virtualcitymatt
Celebrity
1844 replies
Best Answer
4 months ago
December 18, 2024

mbaumgartner wrote:

I am working with a FME FLOW 2024.1that is in a Azure Kubernetes cluster.

This most likely is somehow related I would guess.

Are you able to set up a directory watch or FTP watch in the old fashioned way (e.g., Notifications(classic), Publications)? If you set up the publications you might see some more information in the specific publication logs (logs>core>current>publishers>dirwatch.log).

It’s also possible some ports are closed. You can see more info on ports here: https://docs.safe.com/fme/html/FME-Flow/ReferenceManual/FME-Flow-Ports.htm

+13

evoteck
Enthusiast
58 replies
4 months ago
December 18, 2024

Setting up a directory watch or FTP watch in the old pattern that will give you solution.

Evoteck Geospatial Consult

+2

mbaumgartner
Author
Contributor
1 reply
3 months ago
January 7, 2025

Thanks a lot for all your answers. I think indeed the issue is most likely due to the Architektur and how things are set up.

In the end I was able to configure a Trigger watching an sFTP but after that it was not possible to lunche a workbench.

On the setup I am working with the number of parallel running workbenches is limited to 1. Not understanding what really happens behind the scene in a Automation but I think that this is one of the factors that makes thins not working.

The solution in the end was to avoid Automation and run different workbenches that are launched with a schedule. Not too elegant but it works.

+35

virtualcitymatt
Celebrity
1844 replies
3 months ago
January 7, 2025

mbaumgartner wrote:

The solution in the end was to avoid Automation and run different workbenches that are launched with a schedule. Not too elegant but it works.

Where there’s a will, there’s a way.

I’ll be honest, my experience of FTP and directory watch has always been a bit hit and miss. Sometimes things fail to trigger and on the flip side I’d had the case where ALL files in an FTP have caused simultaneous triggers - that was a real mess.