This article explains the route lookup failure issue due to "PFE_ERROR_FAIL_OPERATION"

Route lookup will fail for certain destinations on SRX even though the routes will be present in the RE routing table. Log messages will have below given errors:

May 16 11:57:18 SRX PFE_ERROR_FAIL_OPERATION: rt_halp_vectors->rt_iff_detach failed 
May 16 11:57:18 SRX PFE: RT iff detach failed (no such file or directory) for ifl 67 
May 16 11:57:18 SRX PFE_ERROR_FAIL_OPERATION: rt_halp_vectors->rt_iff_detach failed 
May 16 11:57:18 SRX PFE: RT iff detach failed (no such file or directory) for ifl 87 
May 16 11:57:18 SRX PFE_ERROR_FAIL_OPERATION: rt_halp_vectors->rt_iff_detach failed 
May 16 11:57:18 SRX PFE: RT iff detach failed (no such file or directory) for ifl 87

Packet will be dropped by the flow and the traceoptions will shows the below given logs:

Jul 30 03:12:21 03:12:21.436363:CID-1:THREAD_ID-04:LSYS_ID-00:RT:Route-lookup failed for 10.87.235.142
Jul 30 03:12:21 03:12:21.436365:CID-1:THREAD_ID-04:LSYS_ID-00:RT: route lookup failed: dest-ip 10.87.235.142 orig ifp reth2.301 output_ifp N/A fto 0x0 orig-zone 12 out-zone 65535 vsd 1 orig vrf-id 0 out vrf-id 0 orig vrf-grp-id 0 out vrf-grp-id 0
Jul 30 03:12:21 03:12:21.436367:CID-1:THREAD_ID-04:LSYS_ID-00:RT: readjust timeout to 12s
Jul 30 03:12:21 03:12:21.436369:CID-1:THREAD_ID-04:LSYS_ID-00:RT: packet dropped, pak dropped since re-route failed

This issue occurs due to route sync failure between routing table and the forwarding table. In order to fix this issue restart routing process using the below given command:

>restart routing gracefully

If the above command does not fix the issue, reboot the device once.