FOXCOUNTER, Kiss my ass or get your shit together - GoFuckYourself.com

whee · 05-07-2004, 05:43 PM

Got a shitload of sites you ya, last 48 hours I checked my stats I got this:

2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)

Happens all the time, please fix it or we shall leave your otherwize extremly fine service.

Lace · 05-07-2004, 05:51 PM

BVF · 05-07-2004, 05:54 PM

Quote:

Originally posted by whee
please fix it or we shall leave your otherwize extremly fine service.

Fine and FREE I might add

uno · 05-07-2004, 05:55 PM

People still use them?

whee · 05-07-2004, 07:03 PM

Quote:

Originally posted by BVF
Fine and FREE I might add

Yes... FREE.. AND FINE... I love this counter.

EviLGuY · 05-07-2004, 07:05 PM

Counters are so 1999.

jimmyf · 05-07-2004, 07:08 PM

Quote:

Originally posted by whee
Yes... FREE.. AND FINE... I love this counter.

I like it better than any other counter and my server logs. But I must say there database has been screwed up off and on for at least the last month. wish they would get it fix.

webmaster x · 05-07-2004, 07:09 PM

Time to pull ourselves together.

jimmyf · 05-07-2004, 08:47 PM

Quote:

Originally posted by whee
Got a shitload of sites you ya, last 48 hours I checked my stats I got this:

2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)

Happens all the time, please fix it or we shall leave your otherwize extremly fine service.

here's another very good counter I've been trying it on one of my site's going put on other one

EroticStats
http://64.106.143.56/

fctech · 05-09-2004, 07:40 PM

The problems you have seen with foxcounter in recent days have been related to a disk error.

Initially the database process was halting due to what appeared to be some corrupt data. So, we dumped all the data out and reloaded it all (for the technically minded the database is in InnoDB files) which is the only way to 'clean' any corrupt database files. In the process, we also upgraded the db software to the latest version. This all happened during the 48hr downtime that was mentioned above. It seems that this reloading and upgrade haven't solved the problem. The db process is still exiting unexpectedly so we are now in the process of running some diagnostics to determine whether it is a problem with the scsi drive or something a little less sinister (like the drive needs to be scanned for bad sectors and have the bad sectors marked as such).

So .... please bear with us while we sort this out. As you can imagine, it is a large and fairly complex setup we have here. I am hoping that we can just find a few bad sectors on the disk.

pornstar2pac · 05-09-2004, 07:41 PM

Quote:

Originally posted by fctech
The problems you have seen with foxcounter in recent days have been related to a disk error.

Initially the database process was halting due to what appeared to be some corrupt data. So, we dumped all the data out and reloaded it all (for the technically minded the database is in InnoDB files) which is the only way to 'clean' any corrupt database files. In the process, we also upgraded the db software to the latest version. This all happened during the 48hr downtime that was mentioned above. It seems that this reloading and upgrade haven't solved the problem. The db process is still exiting unexpectedly so we are now in the process of running some diagnostics to determine whether it is a problem with the scsi drive or something a little less sinister (like the drive needs to be scanned for bad sectors and have the bad sectors marked as such).

So .... please bear with us while we sort this out. As you can imagine, it is a large and fairly complex setup we have here. I am hoping that we can just find a few bad sectors on the disk.

wow, do you own Foxcounter?

fctech · 05-09-2004, 09:28 PM

Quote:

Originally posted by pornstar2pac
wow, do you own Foxcounter?

Nope. I just look after the technical side of things.

05-07-2004, 05:43 PM	#1
whee Confirmed User Join Date: Sep 2002 Location: http://www.nightstation.com Posts: 1,375	FOXCOUNTER, Kiss my ass or get your shit together Got a shitload of sites you ya, last 48 hours I checked my stats I got this: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111) Happens all the time, please fix it or we shall leave your otherwize extremly fine service. __________________ http://www.nightstation.com

05-07-2004, 05:51 PM	#2
Lace Too lazy to set a custom title Industry Role: Join Date: Mar 2004 Posts: 16,116	__________________ Your Paysite Partner Strength In Numbers! StickyDollars \| RadicalCash \| KennysPennies \| HomegrownCash

05-07-2004, 05:55 PM	#4
uno RIP Dodger. BEST.CAT.EVER Industry Role: Join Date: Dec 2002 Location: NYC Area Posts: 18,450	People still use them? __________________ -uno icq: 111-914 CrazyBabe.com - porn art MojoHost - For all your hosting needs, present and future. Tell them I sent ya!

05-07-2004, 07:09 PM	#8
webmaster x Confirmed User Join Date: Mar 2004 Posts: 4,400	Time to pull ourselves together. __________________ Click 9500 FHG Text Descriptions--Only $89!

05-07-2004, 07:05 PM	#6
EviLGuY So Fucking Banned Join Date: Apr 2003 Location: malta Posts: 12,745	Counters are so 1999.

05-09-2004, 07:40 PM	#10
fctech Registered User Join Date: May 2004 Location: Geeksville, USA Posts: 2	The problems you have seen with foxcounter in recent days have been related to a disk error. Initially the database process was halting due to what appeared to be some corrupt data. So, we dumped all the data out and reloaded it all (for the technically minded the database is in InnoDB files) which is the only way to 'clean' any corrupt database files. In the process, we also upgraded the db software to the latest version. This all happened during the 48hr downtime that was mentioned above. It seems that this reloading and upgrade haven't solved the problem. The db process is still exiting unexpectedly so we are now in the process of running some diagnostics to determine whether it is a problem with the scsi drive or something a little less sinister (like the drive needs to be scanned for bad sectors and have the bad sectors marked as such). So .... please bear with us while we sort this out. As you can imagine, it is a large and fairly complex setup we have here. I am hoping that we can just find a few bad sectors on the disk.