Update Failed

[ayorofrance]

Hi Eric,

I am getting Datafeedr Notification - Store Update Failed emails more frequently now...

I have mostly ignored them but given that they keep appearing I've decided to figure out what is going on.

So I got this email on shop 31858 this morning:

This is to inform you that the automatic update on your website (www.xxxxxxx.xxx) has failed. Please see the error message(s) below:

ERROR: 
-Update cannot complete, please try again, 
Technical details:
plugin/plugin:139 view=category
app/tracker:61 track: no referrer
app/update:90 BEGIN: status=read
app/update:139 UPDATE FAILED
app/update:139 UPDATE FAILED
ERROR: err_update_error hung at read (lock=16279)(122)

After which I went online to do a manual Product and Settings update.

This reported Success, however I received this email shortly afterwards:

This is to inform you that the automatic update on your website (www.xxxxxxx.xxx) has failed. Please see the error message(s) below:

ERROR: 
-Error (mysql: (0) [INSERT INTO sr_dfr_xopt(skey,sval) VALUES('update_lock', 6237)]), 
Technical details:
plugin/plugin:139 view=category
app/tracker:61 track: no referrer
app/update:90 BEGIN: status=download
app/update:139 UPDATE FAILED
ERROR: mysql: (0) [INSERT INTO sr_dfr_xopt(skey,sval) VALUES('update_lock', 6237)] (663)

Does this mean the manual update did not succeed?

And what could be the reason I get these emails frequently?

I believe I mainly (only?) get these emails on my larger stores (10,000 - 25.000 products).

It's mostly the err_update_error hung message but these are some of the other messages I have seen:

ERROR: 
-Error (mysql: (0) [INSERT IGNORE INTO sg_dfr_shop_products_tmp(id,net_id,net_code,network,merchant_id,merchant,name,slu]), 
Technical details:
plugin/plugin:139 view=category
app/tracker:61 track: no referrer
app/update:90 BEGIN: status=read
app/update:139 UPDATE FAILED
ERROR: mysql: (0) [INSERT IGNORE INTO sg_dfr_shop_products_tmp(id,net_id,net_code,network,merchant_id,merchant,name,slu] (663)

ERROR: 
-Error (mysql: (0) [INSERT INTO sg_dfr_xopt(skey,sval) VALUES('update_lock', 12192)]), 
Technical details:
plugin/plugin:139 view=category
app/tracker:61 track: no referrer
app/update:90 BEGIN: status=read
app/update:139 UPDATE FAILED
ERROR: mysql: (0) [INSERT INTO sg_dfr_xopt(skey,sval) VALUES('update_lock', 12192)] (663)

ERROR: 
-Store data cannot be read, 
Technical details:
plugin/plugin:139 view=category
app/tracker:68 track: internal referrer=(http://xxxxxx.xxx/s/c/xxxxxxxxxxxxxxx)
app/update:90 BEGIN: status=read
unlink /xxxx/xxxx/wordpress/xxxx/tmp/xxxx/_dfrtmp_6f9e234d4ceb2f9bcd92826709a89080
app/reader:68 header: expect: 3.4 found: %2F%2ADATAFEEDR%3A3.3%2A%2F%0A
app/update:139 UPDATE FAILED
ERROR: err_read bad_header_version(122)

[Eric]

Hi

We had some issues with the Factory yesterday. If you are still getting these error messages, can you PM me the following information:

BLOG LOGIN INFO with ADMINISTRATOR PERMISSIONS (Temporary login information preferred)
Admin URL:
Username:
Password:

FTP LOGIN INFORMATION (Temporary login information preferred)
Host:
Login:
Password:

Thanks,
Eric

[ayorofrance]

Hi Eric,

Unfortunately these errors have been happening sporadically over some time now.

I did another update of this shop this morning, which returned an 'Update Successful' message in the UI and shortly thereafter I got this email:

ERROR: 
-Error (mysql: (0) [INSERT IGNORE INTO sr_dfr_shop_p2c_tmp(id,cat_id) VALUES (1690900574017303,597427), (169090057491487]), 
Technical details:
plugin/plugin:139 view=category
app/tracker:61 track: no referrer
app/update:90 BEGIN: status=read
app/update:139 UPDATE FAILED
ERROR: mysql: (0) [INSERT IGNORE INTO sr_dfr_shop_p2c_tmp(id,cat_id) VALUES (1690900574017303,597427), (169090057491487] (663)

This afternoon I redid the shop update, and so far no email...

Does the email mean that the shop update was not successful after all?

Do you still need the login info?

Sorry I can't be more specific :-(

Cheers,

Anders

[Eric]

Hi

Yes, please send us information so that we can try to troubleshoot this.

Thanks,
Eric

[Eric]

Hi

"not_readable" is thrown when the downloaded feed becomes unreadable for some reason. The most probable reason is when the script that cleans up the shared /tmp directory at regular intervals cannot run. We had the issue in the past and the remedy was to use a private directory inside yours webspace for temporary files.

Here's how to add a tmp directory inside your webspace:
/show...4437#post24437

Eric

[ayorofrance]

Hi Eric,

Thanks for looking into this... I'll setup private dirs and take it from there...

Cheers,

Anders