News:

Wondering if this will always be free?  See why free is better.

Main Menu

Converting data from serialize to JSON... stucked

Started by iso, February 14, 2019, 02:49:26 PM

Previous topic - Next topic

iso

Upgrading from 2.0.15 to 2.1 RC1

Upgrade process gets stucked during Converting data from serialize to JSON... Current Table: "log_spider_hits".
How long is it expected to operate? Time passed is also stucked.

I have no access to the sql log, only to the apache access log, so I can not say if anything happened in the background.

information of the log_spider_hits table attached

shawnb61

Do you have any data in the log_spider_hits table?   If so, could you share it?

Do you have any data in the log_subscribed table? 
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

iso

There is a lot of data in this table. It is the biggest table of my installation. (100,7 MiB)

I have attached some pictures and below are some examples of the url data

url varchar(1024)
a:4:{s:5:"topic";i:1383;s:9:"prev_next";s:4:"next";s:5:"board";i:22;s:10:"USER_AGENT";s:72:"Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)";}

a:3:{s:5:"topic";i:369;s:5:"board";i:11;s:10:"USER_AGENT";s:72:"Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)";}

a:1:{s:10:"USER_AGENT";s:100:"DoCoMo/2.0 N905i(c100;TB;W24H16) (compatible; Googlebot-Mobile/2.1; +http://www.google.com/bot.html)";}


Quote from: shawnb61 on February 14, 2019, 03:51:27 PM
Do you have any data in the log_subscribed table?

No.


shawnb61

Hmmm...  We have to find which one is a problem.   

First quick stab - what does the data look like if you get rid of items that start with a:, e.g., with a query like this:
SELECT * FROM `smf_log_spider_hits` WHERE SUBSTRING(url, 1, 2) != 'a:'

Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp


shawnb61

My first thought is, do you really need all that data?  That's tracking spider/crawler activity on your site.  Are you (or someone else) using that data for anything? 

If not, I'd suggest pruning it before attempting another upgrade.   My initial suspicion is that there is something funky in some old historical data. 

In 2.0.x, look under Admin | Members | Search Engines | Spider Log.   

Can you prune that data, or do you need to keep it around?
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp


albertlast

To finding the root cause,
it would be better to get all url instead of a selection.

Advertisement: