So the past few months I’ve been enjoying my one channel in High-def in St. George. CBS.
I found this site a while back that displays the over-the-air channels. It shows the HD channels (CBS and PBS) we get here.. plus everything else.
When are we getting Fox, ABC, NBC, and WB in HD here in St. George? Who knows. I sure wish we’d get Fox in HD before “24″ stars in January. Doubt it’ll happen though. But here’s hoping.
So my take on the whole Yahoo vs Google ads is this.
1. Yahoo ads pay more per click than Google’s.
2. Yahoo ads get way less clicks than Google’s.
3. Yahoo ads let you target which ‘type’ of ads get displayed on different sites/pages.. Google just displays ads by the content on the page.
4. I make more $ on Google ads than Yahoo even though they pay more.
5. I may switch back to Google on all my stuff on December 1st instead of Yahoo.
6. If Yahoo had automatic ads based on content I might keep it.
7. Yahoo DOES have RSS ads. Not really sure about that though.
Situation #1:
Driving to work today around lunch time I was approaching the intersection at Washington and I15. The coolest thing was that there is this super pimped out Hummer-limo-vehicle. You know the type. Tinted windows. The rear passengers side window was down and two little kids were sticking their heads out. It was awesome.
Situation #2:
Down the street from where I live is this boy. He is ALWAYS dressed in a superboy outfit. You know the type, with a big “S” on his chest. Oh and he has a cape and is always bearfoot. It’s freaking cool.
5.0.17 snapshot is working just fine with no crashes or errors.. yet.
I dumped my databases from my 4.1.x server, scp’d them over to the new box, and restored. All looks good. Had I done this originally (tuesday night), I would have saved myself a bit of heartache and not had to deal with the InnoDB problem nor the INSERT DELAYED. But, oh well, at least now it works.
I think I have it figured out. It was a problem with the InnoDB from my 4.1.x installation when I copied it over to my 5.0.15 install. I dumped my InnoDB data files, logs, and recreated them on startup (on the new box), then did a restore from a dump of the RT (ticketing system) database. This seemed to fix the problem.
Weird thing was, before I dumped my InnoDB data files, I tried dumping the database and restoring it from dump. No go. I couldn’t get it to insert the first row in the first table.. So I did the above. Oh and then I tweaked some settings on my InnoDB part of my.cnf. Here’s some of them for future reference. Oh and I was able to recreate my InnoDB files correctly (i had forgot about the auto-extend file so one of my innodb data files before got up to 1102MB before I created a new one.. so now I have 3×1024MBs and a 512MB that can autoextend to 1024MB max.. much cleaner)
innodb_log_files_in_group = 3
innodb_log_file_size = 256M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_log_archive = 0
innodb_buffer_pool_size = 1G
innodb_additional_mem_pool_size = 32M
innodb_file_io_threads = 4
innodb_thread_concurrency = 16
innodb_lock_wait_timeout = 60
Anyway, tonight will be the test. Shall it work? Shall everything work? I sure hope so. I’m still running 5.0.17 (CVS snapshot from last night).. I think I’ll keep it around for the time being.
Stay tuned.. More later..
More issues with MySQL 5.0.15 crashing… not the same as before.. but a different type of crashing.
Time to try the daily snapshot and enable debugging. 
Found out the bug is reproducable on tables that I copied over from 4.1.x days. It only seems to crash on ‘INSERT DELAYED’ queries. A quick look of the Bugs DB on MySQL’s site reveals this bug:
http://bugs.mysql.com/bug.php?id=13707 – Server crash with INSERT DELAYED on MyISAM table
I applied the patch and things work beautifully now on my FreeBSD 6 box and MySQL5.0.15.
Now to apply this patch to my other MySQL 5.0.15 boxes… easier than waiting for 5.0.16 and hoping I dont get a crash.
Last night (or was it this morning?), I had the same issues as the night preceeding. MySQL 5.0.15 kept crashing over and over and over again. However, this only happened when I allowed network connections in. When I kept a ‘deny tcp from any to me 3306′ in the firewall table, mysql worked just happy as can be.
Todays project. Recompile with debug enabled, figure out what in the heck is causing it to crash on network connectivity to the daemon.
At least last night I knew enough not to screw up replication when I moved back to 4.1.15 on the old box.
