Welcome to the new design! Please report any bugs or issues, thanks :)
Web Dev + WordPress + Security

Fixing Mint after Switching Servers

[ Mint Icon ] After switching Perishable Press to its current home at A Small Orange, I began noticing an unusual problem with referrer data displayed in Mint. Specifically, the first item recorded in the XXX Strong Mint data panel — for both “Most Recent” and “Repeat” views — displayed several thousand hits for various site resources, all reporting the following IP address:

127.255.255.255 
zxw59eit.emirates.net.ae

Apparently, this particular location represents an invalid “loopback address.” The requested resources appear valid, indicating typical traffic patterns, but the loopback address is not the actual referrer. This issue was preventing Mint from accurately recording mountains of vital referral data.

Researching this issue reveals that the underlying problem involves the switching of a Mint installation between a 32-bit server and a 64-bit server. Installing Mint on either type of server without switching to the other should not trigger this problem. It is the switch from one to another that results in the generation of the loopback address.

Quick Fix

Fortunately, there is a straightforward fix for this issue. Open your Mint database via phpMyAdmin (or whatever you prefer) and execute the following commands (don’t forget to backup your data before you begin!).

Step 1

Within the mint_visit table, make any changes needed to ensure that all of the following fields display a value of UNSIGNED for the “Attributes” column (check out this screenshot).

  • mint_visit » id
  • mint_visit » dt
  • mint_visit » ip_long
  • mint_visit » referer_checksum
  • mint_visit » domain_checksum
  • mint_visit » resource_checksum
  • mint_visit » local_search_found

Step 2

Next, EMPTY the mint_visit table. In phpMyAdmin, open the mint_visit table and click the “Empty” tab (located in the upper row along with other SQL commands). Theoretically, Mint’s default settings will eventually flush out the invalid referrer data, however it may take several weeks or longer.

All Done

That’s all there is to it. After implementing this fix, I saw immediate resolution of the issue. The 127.255.255.255 address disappeared from the referrer data, as did the thousands of associated entries of requested resources.

Moreover, I implemented this fix several months ago and have not experienced any ill effects or repeat issues whatsoever. Indeed, the referrer data has been repopulated with accurate data, and Mint is once again a virtually flawless piece of statistical software.

Jeff Starr
About the Author
Jeff Starr = Web Developer. Book Author. Secretly Important.
.htaccess made easy: Improve site performance and security.

2 responses to “Fixing Mint after Switching Servers”

  1. Thanks,

    I recently moved servers and this has happened to me, your article gives the clearest instructions on how to fix this that i have come across, My stats are now all working correctly again.

    Thank you!!

  2. Jeff Starr
    Jeff Starr 2010/04/10 9:56 pm

    My pleasure, Graham — thanks for the feedback :)

Comments are closed for this post. Something to add? Let me know.
Welcome
Perishable Press is operated by Jeff Starr, a professional web developer and book author with two decades of experience. Here you will find posts about web development, WordPress, security, and more »
Banhammer: Protect your WordPress site against threats.
Thoughts
This new Admin Page Framework looks very good. Bookmarked for future use.
Two great places to find awesome plugins: pluginsearch.com and WP's browse new.
2 things I hate to see in stylesheets: _ and #
Love VLC media player but it fails miserably when it comes to randomizing large collections of mp3 and other files.
Dashlane redesigned, stating proudly they "removed all filigree". Should have kept it; the app now looks generic and boring. Killed your identity.
Working on integration for setaPDF + EDD on the new books subdomain. Good times.
Toggle visibility of hidden files on Mac: Cmd + Shift + .