Support Article
Existing file mount point fails
Summary
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 - com.pega.pegarules.pub.PRRuntimeException: No such Directory or Folder: /usr/local/tomcat/work/sync-data/transfer/EDBR/quest-edbr-prod/sftp-transfer com.pega.pegarules.pub.PRRuntimeException: 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(ra_action_invoke_952104d6cee3442ecad0c0e4bb0c37bd.java:636) ~[?:?] at com.pegarules.generated.activity.ra_action_invoke_952104d6cee3442ecad0c0e4bb0c37bd.perform(ra_action_invoke_952104d6cee3442ecad0c0e4bb0c37bd.java:87) ~[?:?]at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3587) ~[prprivate.jar:?]
Steps to Reproduce
Unknown
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.
Resolution
Make the following change to the operating environment:
Perform a rolling restart.
Published January 30, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.