-
Posts
-
Not really worried, but thought I would post it in case it helps Leo figure out a fix with his new upgrade….
in my Bluehost cPanel error log I have got a pretty big stack of these errors:
PHP Warning: Illegal string offset ‘address’ in /home2/thpstock/public_html/wp-content/themes/symbiostock/inc/classes/network-manager/network-manager.php on line 515
All on that same line, 515.
EDIT: Everything seems to be working by the way, but still, its an error.
View my portfolio at THPStock Direct via Microstock Man. I also do Web Design & Graphic Design.
I had this error too. Network sites data were stored in database as serialized variables. All of them looked ok, but some were recognized as corrupted. Maybe they were stored by different php version(?). This error was visible on site after Symbiostock->Network->Update Symbiocards.
In my case helped removing all network partners and adding them again.@ajt wrote:
I had this error too. Network sites data were stored in database as serialized variables. All of them looked ok, but some were recognized as corrupted. Maybe they were stored by different php version(?). This error was visible on site after Symbiostock->Network->Update Symbiocards.
In my case helped removing all network partners and adding them again.Thanks ajt.
Here are some more errors in my cPanel error log in case it means anything to Leo or other developers…
[01-Apr-2014 18:57:11 America/Denver] PHP Warning: (null)(): 659 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:57:11 America/Denver] PHP Warning: (null)(): 661 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:57:11 America/Denver] PHP Warning: (null)(): 659 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:57:11 America/Denver] PHP Warning: (null)(): 661 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:09 America/Denver] PHP Warning: (null)(): 650 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:11 America/Denver] PHP Warning: (null)(): 650 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:22 America/Denver] PHP Warning: (null)(): 643 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:22 America/Denver] PHP Warning: (null)(): 649 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:22 America/Denver] PHP Warning: (null)(): 654 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:22 America/Denver] PHP Warning: (null)(): 656 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:22 America/Denver] PHP Warning: (null)(): 658 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:22 America/Denver] PHP Warning: (null)(): 643 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:22 America/Denver] PHP Warning: (null)(): 649 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:22 America/Denver] PHP Warning: (null)(): 654 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:22 America/Denver] PHP Warning: (null)(): 656 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 18:59:22 America/Denver] PHP Warning: (null)(): 658 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 19:01:06 America/Denver] PHP Warning: (null)(): 628 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 19:01:08 America/Denver] PHP Warning: (null)(): 650 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 19:01:12 America/Denver] PHP Warning: (null)(): 638 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 19:03:15 America/Denver] PHP Warning: (null)(): 638 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 19:05:11 America/Denver] PHP Warning: (null)(): 647 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 19:05:41 America/Denver] PHP Warning: (null)(): 644 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 19:05:47 America/Denver] PHP Warning: (null)(): 650 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 19:07:17 America/Denver] PHP Warning: (null)(): 649 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 19:07:48 America/Denver] PHP Warning: (null)(): 645 is not a valid cURL handle resource in Unknown on line 0
[02-Apr-2014 01:08:09 UTC] PHP Warning: Illegal string offset ‘width’ in /home2/thpstock/public_html/wp-content/themes/symbiostock/image.php on line 24
[02-Apr-2014 01:08:09 UTC] PHP Warning: Illegal string offset ‘height’ in /home2/thpstock/public_html/wp-content/themes/symbiostock/image.php on line 25
[01-Apr-2014 19:08:51 America/Denver] PHP Warning: (null)(): 649 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 19:09:38 America/Denver] PHP Warning: (null)(): 647 is not a valid cURL handle resource in Unknown on line 0
[01-Apr-2014 19:10:41 America/Denver] PHP Warning: (null)(): 646 is not a valid cURL handle resource in Unknown on line 0View my portfolio at THPStock Direct via Microstock Man. I also do Web Design & Graphic Design.
ok recently my site has been slowed down and I am getting throttled like crazy. Looking at the my_sql_slow_queries logs it is full of logs like this:
# Wed Apr 2 08:01:31 2014
# Query_time: 17.546484 Lock_time: 14.704007 Rows_sent: 0 Rows_examined: 1230440
SET timestamp=1396447291;
DELETE FROM cef_ss_analytics_history
WHERE time < UNIX_TIMESTAMP(DATE_SUB(NOW(),
INTERVAL 60 DAY))# Wed Apr 2 08:01:34 2014
# Query_time: 2.610174 Lock_time: 0.000125 Rows_sent: 0 Rows_examined: 965850
SET timestamp=1396447294;
DELETE FROM cef_ss_analytics_keyword_performance
WHERE time < UNIX_TIMESTAMP(DATE_SUB(NOW(),
INTERVAL 60 DAY))# Wed Apr 2 08:01:34 2014
# Query_time: 17.823088 Lock_time: 15.130240 Rows_sent: 0 Rows_examined: 1230440
SET timestamp=1396447294;
DELETE FROM cef_ss_analytics_history
WHERE time < UNIX_TIMESTAMP(DATE_SUB(NOW(),
INTERVAL 60 DAY))# Wed Apr 2 08:01:36 2014
# Query_time: 1.996870 Lock_time: 0.000136 Rows_sent: 0 Rows_examined: 965851
SET timestamp=1396447296;
DELETE FROM cef_ss_analytics_keyword_performance
WHERE time < UNIX_TIMESTAMP(DATE_SUB(NOW(),
INTERVAL 60 DAY))# Wed Apr 2 08:01:37 2014
# Query_time: 18.605820 Lock_time: 15.740977 Rows_sent: 0 Rows_examined: 1230442
SET timestamp=1396447297;
DELETE FROM cef_ss_analytics_history
WHERE time < UNIX_TIMESTAMP(DATE_SUB(NOW(),
INTERVAL 60 DAY))As you can see, some of these take 18 seconds to complete! No wonder I am getting throttled. There are thousands of these going on.
I am on with Bluehost chat at the moment trying to figure something out, but does anyone here have any suggestions?
View my portfolio at THPStock Direct via Microstock Man. I also do Web Design & Graphic Design.
Leo – I just had another developer friend of mine look at my site, which has been getting throttled for 60 seconds every minute (yep, the whole time) for a while now, and is barely functioning.
He found that this code is getting run every second or so…
DELETE FROM cef_ss_analytics_keyword_performance
WHERE time < UNIX_TIMESTAMP(DATE_SUB(NOW(),
INTERVAL 60 DAY));
DELETE FROM cef_ss_analytics_history
WHERE time < UNIX_TIMESTAMP(DATE_SUB(NOW(),
INTERVAL 60 DAY));Coming from /home2/thpstock/public_html/wp-content/themes/symbiostock/inc/classes/analytics.php
line 337
It seems that every time a page gets hit it runs that code, creating long queries. My site had up to 7 or 8 of those queries running at any given time, some taking up to 30+ seconds to complete!
He has commented out this code for now, and my site is speedy once again. It seems there is a serious bug here that needs addressing asap. Basically any long process that is causing errors to be logged is associated with SS’s analytics. I really hope you can give an option to turn it off completely, or fix the way it handles these requests.
I hope that makes sense. Cheers.
View my portfolio at THPStock Direct via Microstock Man. I also do Web Design & Graphic Design.
Edited to add a big THANK YOU to Tim for find this!
So I looked at my site and see masses of throttling
I’m off to comment out the code your friend suggested to see if that helps.
I’m assuming that just turning off public access to analytics wouldn’t do it – that it’s still generating the stuff, just not sharing it?
So that made a huge difference. Right before I made the change
And 50 minutes later
I don’t know why the numbers for earlier 15 minute segments don’t match up, but the bottom line is that the graph is now quiet (and I did do some searches and accessed images on the site during that time).
I guess this has been going on since analytics were introduced? When the fixes are made to this, I’d really like to see an on-off switch – not just for public access but for the whole process of gathering data. Even when the current bug is fixed, there may be future changes to server or usage of the sites that cause analytics to impact performance. The ability to quickly turn the whole thing on and off will allow us to simply see whether or not that’s the performance problem without tinkering with the code.
Many thanks for digging up this one. Great job! 😀
Throttling of my site stopped instantly after commenting out that line. I wonder, though, what side effect(s) this might have. As I understand this the change doesn’t turn off analytics completely but just one step of it.
For whatever it’s worth, I’m not seeing a throttling problem on my site. 3.91 seconds over the last 24 hours is all I show when I checked. Two incidents, each less than 2 seconds in duration.
I’m not sure why I might be escaping the problem. Analytics are turned on in my site.
Symbiostock 3.3.3
Child theme 0.1.0
Symbiostock Site Map 1.1.3
Symbiostock Professional 1.5.2
Along with several of the standard plugins@klsbear wrote:
For whatever it’s worth, I’m not seeing a throttling problem on my site. 3.91 seconds over the last 24 hours is all I show when I checked. Two incidents, each less than 2 seconds in duration.
If I recall from the slow search with network turned on, your site was one of the speedy ones. No idea if the two things are connected and I haven’t gone back to turn on the network and see if that has reasonable speed searches now the throttling is done
@Imago Borealis wrote:
Many thanks for digging up this one. Great job! 😀
Throttling of my site stopped instantly after commenting out that line. I wonder, though, what side effect(s) this might have. As I understand this the change doesn’t turn off analytics completely but just one step of it.
I have the same results. Throttling stopped as soon as I commented out the code. Although my site did not have much compared to others, I am sure every bit helps.
@joannsnover wrote:
@klsbear wrote:
For whatever it’s worth, I’m not seeing a throttling problem on my site. 3.91 seconds over the last 24 hours is all I show when I checked. Two incidents, each less than 2 seconds in duration.
If I recall from the slow search with network turned on, your site was one of the speedy ones. No idea if the two things are connected and I haven’t gone back to turn on the network and see if that has reasonable speed searches now the throttling is done
I was thinking the same. Since I never turned off networking it was easy to test: search time dropped from 30+ seconds to 10+ seconds. Still not really good but definitely better.
@joannsnover wrote:
So that made a huge difference. Right before I made the change
And 50 minutes later
I don’t know why the numbers for earlier 15 minute segments don’t match up, but the bottom line is that the graph is now quiet (and I did do some searches and accessed images on the site during that time).
I guess this has been going on since analytics were introduced? When the fixes are made to this, I’d really like to see an on-off switch – not just for public access but for the whole process of gathering data. Even when the current bug is fixed, there may be future changes to server or usage of the sites that cause analytics to impact performance. The ability to quickly turn the whole thing on and off will allow us to simply see whether or not that’s the performance problem without tinkering with the code.
Thanks guys, I am REALLY glad the fix worked and that it has helped you all too. My throttling now is 29 seconds in the last 24 hours – compared to over 23 hours out of 24 hours!!! HUGE HUGE HUGE difference in site performance.
I totally agree with the bolded part above – an OFF switch is essential. This analytics stuff is way too resource intensive for some servers at the moment.
As for the question of what repercussions turning this part of the code off will have the answer is yes, there will be a downside. What the code effectively does is delete any analytics data older than 60 days. So with it commented out, it won’t do that. Thus the database keeps growing. So what my dev friend suggested (which is pretty easy) is to run the SQL commands (i.e.: That code I pasted in) once a week or two to clean out the old records. To do this, go to PHPMyAdmin under the Bluehost control panel. In the left hand column select your database (make sure its the right one, you may have to expand the tree to look at it). Then with that database selected, click the tab across the top that says SQL. Paste in ONE of the two commands commented out at a time and hit go. If you get an error (as I did), delete the “;” from the end of the command, and type it in again – don’t know why but that fixes it. Then run the second command you commented out. This will then clean up your old analytics data, as Leo intended it.
Its so nice to have a fast, functioning site again 🙂
View my portfolio at THPStock Direct via Microstock Man. I also do Web Design & Graphic Design.
By the way, this fix doesn’t in any way (as far as I am aware at least!) fix those PHP errors that I reported at the start of this thread. They still need to be looked into, especially all those cURL references.
View my portfolio at THPStock Direct via Microstock Man. I also do Web Design & Graphic Design.
My site is so slow it is painful .
Can someone explain exactly which bit has to be commented out – and do you do it with /* */ ?
}
$this->delete_expired();
}}
I tried it white screened my pages.
If you don’t know how to work with MySql would it have the same effect if you put the original analytics.php back for a while as well?
http://kerioakimaging.com - trying to reopen
http://nail-art-at.kerioak.com - Art and Nail Art
You must be logged in to reply to this topic.