SimpleXML warning in tmp feed in Product Feed Pro

  • Resolved broksonic

    (@broksonic)


    4 years, 4 months ago

    The plugin has been great – thanks!

    That said, we are seeing warnings in our logs recently – all with call stacks like this (the token changes occasionally for the feed at issue instead of where it says REDACTED, of course)

    E_WARNING:?simplexml_load_file(): I/O warning : failed to load external entity "/srv/wp-content/uploads/woo-product-feed-pro/xml/REDACTED_tmp.xml"
in simplexml_load_file called at /srv/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php (1080)
in WooSEA_Get_Products::woosea_create_xml_feed called at /srv/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php (3721)
in WooSEA_Get_Products::woosea_get_products called at /srv/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php (4503)
in woosea_continue_batch called at /srv/wp-includes/class-wp-hook.php (287)
in WP_Hook::apply_filters called at /srv/wp-includes/class-wp-hook.php (311)
in WP_Hook::do_action called at /srv/wp-includes/plugin.php (544)
in do_action_ref_array called at /srv/wp-cron.php (138)

    The feeds are created fine – but this shows up over and over again (and occasionally repeatedly in rapid succession).

    One thing I noticed – we had seen it for one feed id consistently (and only for it). I deleted that feed, but the warning continued, it just moved to a different feeds ID (which we had never seen the warning before before that)

Viewing 11 replies - 1 through 11 (of 11 total)

  • Hi,

    Thanks for using our plugin and reaching out to us. Sorry to hear you are seeing these warnings in your error logs.

    Those errors happen when the plugin cannot find the temporarily XML feed it uses to update the product feeds. This can be caused by you removing those temporarily XML feeds are by permission issues on those XML files. Did you do such thing? (the plugin only deletes temporarily feeds when it is done processing the feed).

    Thread Starter broksonic

    (@broksonic)

    Nope. Nothing we are touching.

    It runs fine for a few hours, then starts doing this, then stops a bit, then starts doing this again

    (The main ID is an hourly feed)

    Some other process, firewall, security, caching plugin that could be causing this? Doing some clean-up or creating permission restrictions maybe?

    Thread Starter broksonic

    (@broksonic)

    Not that we can tell. When I look when this is alerting a lot, the tmp file simply doesn’t exist on disk.

    Is there logging we can grab to help here?

    This is a related error we saw 254 times in last 24 hours, many in rapid succession:

    Thread Starter broksonic

    (@broksonic)

    copy(/srv/wp-content/uploads/woo-product-feed-pro/xml/REDACTED_tmp.xml): failed to open stream: No such file or directory
in copy called at /srv/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php (3812)
in WooSEA_Get_Products::woosea_project_update called at /srv/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php (3730)
in WooSEA_Get_Products::woosea_get_products called at /srv/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php (4503)
in woosea_continue_batch called at /srv/wp-includes/class-wp-hook.php (287)
in WP_Hook::apply_filters called at /srv/wp-includes/class-wp-hook.php (311)
in WP_Hook::do_action called at /srv/wp-includes/plugin.php (544)
in do_action_ref_array called at /srv/wp-cron.php (138)

    Across a couple of different feed IDs

    This is on WPEngine. Nothing that would impact on-disk caching installed.

    Thread Starter broksonic

    (@broksonic)

    I should state, when it’s in this state, the UI says it’s stuck in processing 100%

    Thread Starter broksonic

    (@broksonic)

    Just tried it by manually clicking refresh

    1st times, it just ran fine.
    The 2nd time, it got stuck (with same errors in logs)
    3rd time it ran fine
    4th time, it got stuck (with same errors in logs)
    and so on.

    I feel like there’s some state not being refreshed.

    When the tmp feed is done processing (100%) it copies the tmp feed to the final feed URL. All we could still think of is that our plugin, for some permission/security issue, is not allowed to copy over the tmp file to the final feed location.

    Thread Starter broksonic

    (@broksonic)

    It works other times, though. Nothing setup or permissions change.

    Seeing same behavior in both our production and staging environments, as well as local computer (occasional stuck at 100% with these errors).

    Thread Starter broksonic

    (@broksonic)

    Any logging or other info we can get for this?

    Thread Starter broksonic

    (@broksonic)

    I now have one permanently stuck in this state – warning like this and at 100%. Even cancelling it via the Ui won’t free it up.

    • This reply was modified 4 years, 4 months ago by broksonic.
Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘SimpleXML warning in tmp feed in Product Feed Pro’ is closed to new replies.