Home > Other Systems (CPVLab, iMobiTrax, P202, Track Revenue, Click, Google Analytics, etc.) > The STM Mobile Tracker

---

New WURFL DB Available - Update Your STM Tracker (12)

---

Hey guys , just a heads up that a new version of the WURFL DB (2.3.4) got released recently.

For anyone that uses the STM mobile tracker , by updating you will have a more accurate OS / Handset / Model detection.

You can download the file from here :

http://sourceforge.net/projects/wurf...s/WURFL/2.3.4/

To update your DB just follow these 3 steps :

A. copy the latest wurfl.zip to: 3rd-parties/wurfl/resources ( on your server where the tool is installed )
B. delete the 'old' wurfl data by removing a db table ( type this sql query on phpmyadmin ):
DROP TABLE wurfl_object_cache;
C. any tracking request will trigger the wurfl update automatically.

That's it , now enjoy your improved device detection

---

I know it's retarded, but every time I see "WURFL" all I can think of is this:



Maybe someone should make a database called "WHARGBL" and it can have sprinkler dog as it's logo.

---

Hi Besmir, I found that the latest version is now 2.3.5
The update process is still the same ?

---

I cant get the system to accept version 2.3.5. After replacing the .zip file and droping the cache table, the tracker fails with an error saying "mysql server has gone away clearing wurfl_object_cache". If I rollback to wurfl 2.3.4, then the system starts behaving as expected.

Has anyone been able to update wurfl to 2.3.5 successfully on STM Mobile Tracker?

---

Hmm - we'll look into this. Thanks!

---

Yep I updates just fine.

Looks more like a timeout issue with mysql since it needs to import it all in the db the first time.

I would submit a ticket to your host so they can increase the timeout.

---

No luck. This is the error I get when navigating to a campaign page after updating to 2.3.5 and dropping the wurfl table:

Warning: Error while sending QUERY packet. PID=1452 in /var/www/html/3rd-parties/wurfl/WURFL/Storage/Mysql.php on line 132

Fatal error: Uncaught exception 'WURFL_Storage_Exception' with message 'MySql error MySQL server has gone away clearing prosperdb.wurfl_object_cache' in /var/www/html/3rd-parties/wurfl/WURFL/Storage/Mysql.php:134 Stack trace: #0 /var/www/html/3rd-parties/wurfl/WURFL/DeviceRepositoryBuilder.php(162): WURFL_Storage_Mysql->clear() #1 /var/www/html/3rd-parties/wurfl/WURFL/DeviceRepositoryBuilder.php(109): WURFL_DeviceRepositoryBuilder->clean() #2 /var/www/html/3rd-parties/wurfl/WURFL/DeviceRepositoryBuilder.php(86): WURFL_DeviceRepositoryBuilder->buildRepository(Object(WURFL_Xml_VersionIterator) , Object(WURFL_Xml_DeviceIterator), Array) #3 /var/www/html/3rd-parties/wurfl/WURFL/WURFLManagerFactory.php(164): WURFL_DeviceRepositoryBuilder->build('/var/www/html/3...', Array) #4 /var/www/html/3rd-parties/wurfl/WURFL/WURFLManagerFactory.php(127): WURFL_WURFLManagerFactory->deviceRepository(Object(WURFL_Storage_Mysql), Object(WURFL_UserAgentHandlerChain)) #5 /var/www/html/3rd-parties/wurfl/WURFL/WURFLManagerFactory.php(66): WURFL_WU in /var/www/html/3rd-parties/wurfl/WURFL/Storage/Mysql.php on line 134

---

@affilia320 - Did you increase the mySQL timeout as bbrock32 suggested?

---

Yep man, it's definitively a MySQL issue.

I would hit up your host and they should be able to fix it.

It's quite a big import so that's why it needs a big timeout.

---

I am the host myself :-) how long should the import take then? I put the timeouts at 1 minute and the issue persists...

---

On my 16 core box it took about 1-2 minutes from what I recall.

The time is proportional to how fast your server is.

---

Try to adjust max_allowed_packet in /etc/my.cnf if it is set too low.

I had some errors with the new versions and when I increased that value it started working fine.

---

Home > Other Systems (CPVLab, iMobiTrax, P202, Track Revenue, Click, Google Analytics, etc.) > The STM Mobile Tracker