Login to download the latest version of Mint and your favorite Pepper, purchase additional licenses, or post in the Forum. Don't have an account? Create one!

In Partnership with Media Temple

Mint Forum

Server change altered stats?

fork
Minted
Posted on Sep 04, '07 at 05:30 pm

My server came to a screeching halt last week and after trying a few things, including restarting all services and even rebooting the server, I finally asked my ISP’s support staff to take a look and a few hours later they had it running again.

I updated Mint afterward from 2.15 to 2.16.

Looking at Mint and comparing the numbers to the averages each day for the past few weeks, I thought traffic on our server had dropped off for the Labor Day holiday weekend but I looked at my Google Analytics stats and they had actually increased slightly from the norm. Usually GA and Mint are quite close. Google is about 20% higher in every category.

The discrepancy between the two continues today and I can’t figure out if it’s the Mint update or the server tweaks.

Here are the server tweaks as described by support staff:

A.

“I corrected the issue by moving MySQL to the end of the startup sequence as follows:

mv /etc/rc3.d/S64mysql /etc/rc3.d/S99mysql”

B.

“1. I opened up /etc/resolv.conf with an text editor (nano) 2. I added “nameserver 127.0.0.1” so that when trying to include links via PHP, they went to the local resolver first rather than something externally.”

Would either of these affect the way Mint records visits?

I have also noticed occasionally hiccups with Mint since upgrading to 2.16. I keep a Safari window open on an extra monitor with updates refreshing every ten minutes on a relatively busy server. The window sometimes hangs when it refreshes the panes. Alll I get are the headings. Quitting and restarting Safari is the only thing that appears to work. I just moved the refresh up to 15 minutes and (so far) the hangup hasn’t happened in the last hour but the behavior had been erratic the past few days anyway.

Shaun Inman
Mint/Pepper Developer
Posted on Sep 04, '07 at 05:58 pm

Neither of those changes sound like they would affect Mint or any official Pepper, I can’t speak to third-party Pepper though. Also, the latest version of Mint is 2.12 so I can’t speak to any changes that may have been made between 2.15 and 2.16 (since they haven’t been written or released yet!).

fork
Minted
Posted on Sep 04, '07 at 10:06 pm

Oops—I wrote the Mint version numbers off the top of my head instead of moving my eyes 20 degrees to the right and looking at the info at the bottom of the actual Mint page.

Right now the only third party pepper that’s installed and active is Trends and it appears to be working normally with the data it has.

The ISP support people may have done other things to my server or MySQL they forgot to mention.

[Wondering aloud] Maybe I should try uninstalling and reinstalling Mint to see if that might fix it…

fork
Minted
Posted on Sep 06, '07 at 10:06 am

I installed the Debug pepper and it immediately revealed rows of red-backgrounded entries. None of the entries with red backgrounds were being counted in the running totals and the uncounted entries are approximately 20% less than usual — the same discrepancy seen when comparing to Google Analytics numbers. The entries with red background are missing cookie info.

I sent Shaun the debug URL via email.

Shaun Inman
Mint/Pepper Developer
Posted on Sep 06, '07 at 11:56 am

Don’t uninstall/reinstall. That’s never a solution to a visits inconsistency problem. What version of Mint did you update from (so I can determine what changes were made between the two versions that might result in this problem)?

fork
Minted
Posted on Sep 06, '07 at 12:07 pm

I updated from the previous version, 2.11.

Since 2.0, I have been doing the incremental upgrades within a few days of release.

Shaun Inman
Mint/Pepper Developer
Posted on Sep 06, '07 at 12:46 pm

There have been no changes between 2.11 and 2.12 that would account for this discrepancy. Are the two changes made by host the only two changes they made? Did they change PHP in anyway? Or add mod_security or new rules to mod_security.

The problem that you’re seeing in your Debugger is that when pages are requested the Mint JavaScript include is also requested but then it never makes the second request to record the data collected by the Mint JavaScript include.

This could be caused by a number of things. The server could “hang up” on the request. Another JavaScript error on the page could prevent the request from being made (I’m not seeing any evidence of this though). JavaScript could be disabled altogether.

Let me know about any other server changes.

fork
Minted
Posted on Sep 06, '07 at 01:03 pm

JavaScript could be disabled altogether.

Of course, that can’t be since Mint is recording most of the visits and Google, which also uses Javascript, continues to give the more typical stats at the higher figures.

You suggested a few months ago that I could allow Google to share the Mint prepend script and it’s been working fine. Only Mint isn’t recording all the visits now.

I wrote to the ISP support staff about any other changes they may have made to the server and they are adamantly silent.

I went back through my logs and the only other thing they did around that time was upgrade Perl, which apparently started the server problems in the first place. After upgrading from 5.87 to 5.88, MySQL failed but they didn’t recheck the server. I noticed the problem because Mint had stopped and WatchMouse bombarded me with email warnings, so I restarted MySQL and later rebooted the server, both to no avail. When I contacted tech support at the ISP they reported that they did the items (tagged A and B) mentioned at the beginning of this thread.

You must be logged in to reply. Login above or create an account