tracking hell. i need a fix soon

i am going through module tracking hell. from ADS tracking to video tracking to new tracking fields in the mysql database.

I can get rid of them iff i over write all damaged files and then repair them. but this is happening like ever single days now.

and not always at midnight. i assume there is a tracking field problem and can not locate it at all.

Is there a way to turn tracking off completely so i can get rid of a crashed website everyday.

or is there a fix in some field that has to be done to get this tracking to work properly.

 users are getting extremely annoyed. this has been an ongoing problem for months now and is getting worse

and more frequent.. someone who has knowledge of this type of problem please help.

Query:

SELECT `id`, `user_id`, `data` FROM `sys_sessions` WHERE `id`='' LIMIT 1

Mysql error: Table '.\d714\sys_sessions' is marked as crashed and last (automatic?) repair failed

Found error in the file 'D:\WEBSITE\indigoampp\apache-2.2.11\htdocs\inc\classes\BxDolSessionQuery.php' at line 28.
Called 'getRow' function with erroneous argument #0.


Debug backtrace:

======================================================

and adds_track  videos_track and all other accessed modules have trackers fields crashed and unusable.

The error tells you what wrong.

Mysql error: Table '.\d714\sys_sessions' is marked as crashed and last (automatic?) repair failed

So from phpMyAdmin try and repair the sys_sessions table. If it cannot be repaired, that table can safely be truncated. So try to truncate the table if a repair fails.

ok done. checking out the other module tracking tables. i see for admin account it writing field =1 and field=0

i think it suppose to be only writing a 1 for user id but it it writing both 1s and 0s

That is normal.

The session that shows a 0 as a user_id is a guest session. It's when a person is not logged in yet.

hmmm... ok.. i deleted all the module track data from every field that has track in it. and the sys_sessions completely.

it crashed again last night. ergh.

doing the data deletion again to see if it finally fixes it.

will let you know if it crashes after midnight tommorrow with all empty tracking and session

yet again it crashed. everytrime someone looks at something it crashes.

I am going to get default 714 and build the database then overwrite all the sys_files with the new database.

hopefully copying bx etc etc saves my work on the site. and the sys_sessions problem is fixed.

seems to happen on cron job

There is definately a major problem with my site or the boonex code itself for module_TRACK fields in the database.

seems anytime someone views anything like a video/sound or other at midnight. i assume some sort of cron or other job gets done and crashes all the _TRACK fields and Sessions field. beyond repair. the only way i was able to recover from the crash event was to manually delete everything except for the _TRACKING and _SESSIONS fields from an old backup and then over write all the corrupted data files and do a mysql repair.. this is getting very very annoying every night at midnight. about the only time it does not crash is when no sounds/videos/ etc are viewed. I need help on this problem as soon as possible. I can't be up or around the computer every night at midnight to do a 15 minute repair of something that sound be working to begin with

Unfortunately this has nothing to do with dolphin.

Dolphin merely passes data to the database server for writing, requests from the database server when reading. The database server itself handles all of the actual work.

You have a obvious problem with your database server. Given that it's happening during the cron runs which is the time that dolphin does most of the cleanup work. It is at that time the database will be under it's highest load. It is quite apparent it is not handling that load very well.

There are a number of things that can cause database corruption. The most common are faulty memory, faulty hard drive, or low free space on the hard drive.

You need to talk to your host. This is a database or server hardware problem. It has nothing to do with dolphin.

I had this problem before and what it came down to was Memory for my site, I also switched Hosting services because the one I was with was not use to Dolphin and knew nothing as far as helping track down the crashing problem..... It took a certain person from Boonex to track it down for me, if you do need to switch Try out Zarconia.net 

all is solved. apparently when i emptied tables with mysql administrator it showed as being emptied. then a refresh with it show them as holding data. weird. i used navicat to anihilate the table to empty. no problem since