Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Existing file mount point fails



The existing file mount point fails.

Error Messages


950 [tp-apr-8080-exec-105] [TABTHREAD0] [] [your_rsv] (nvoke.Rule_Connect_File.Action) ERROR your_server|your_ip|Rule-Connect-File.your_connect_file_rule your_operator_id - No such Directory or Folder: /usr/local/tomcat/work/sync-data/transfer/EDBR/quest-edbr-prod/sftp-transfer No such Directory or Folder: /usr/local/tomcat/work/sync-data/transfer/your_file_spec/your_node/sftp-transfer at com.pegarules.generated.activity.ra_action_invoke_952104d6cee3442ecad0c0e4bb0c37bd.step2_circum0( ~[?:?] at com.pegarules.generated.activity.ra_action_invoke_952104d6cee3442ecad0c0e4bb0c37bd.perform( ~[?:?]at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( ~[prprivate.jar:?]

Steps to Reproduce


Root Cause

A defect or configuration issue in the operating environment. The file was in the S3 bucket. The Goofys stopped and the mount point for the S3 bucket was unavailable to the Pega-web container.


Make the following change to the operating environment:
Perform a rolling restart.



Published January 30, 2019 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us