Baycreek Kayak and SUP Cup 2013

[dciframe]http://connect.garmin.com:80/activity/embed/375634626,465,548,0,auto,border:1px solid blue;align:left;[/dciframe]Today was the first long race I’ve done since coming back from my surgery. BayCreek Paddling Center sponsored a race up and down Irondequoit Bay, starting and ending at their dock. Mostly I avoid the bay because its usually a horrendous mess of conflicting boat wakes, and the first kilometer and a half from BayCreek is shallow, which is very slow if you’re in a long boat, especially if you’re heavier than the average paddler like I am – we call it suck water because it feels like its sucking the boat down. Fortunately today the cold and the lateness of the season kept most of the power boaters away except the fishermen, so the wakes weren’t a problem. This allowed me to paddle my Thunderbolt, which is a tiny bit faster and lighter than my v10 Sport, which is what I’d use if waves were going to be an issue.

We lined up in front of the dock. I took the far left because almost as soon as you start you go under the Empire Blvd bridge which is low and dark and in the darkness under the bridge there is a hidden obstacle just below the water on the right side. Bill was to my immediate right. Bill always starts really fast and fades in a km or so. To his right were my coach, Dan, and then his son Tom, and a couple of others.

At the start, Jim M and Tom took off incredibly fast, as expected, followed by the Canadian guy (sorry, forgot his name, but he drove down from Toronto today) who was being tailed by Matt, then Dan with Bill and I tailing him. Half way through the suck water Bill starts to drop off, and Dan decides to leave the channel for a direct route. Gutsy move considering its even worse suck water out of the channel. I put in a huge effort to get onto his tail wake and latch on. It’s cost me – by pulse is up to 163, which is my max and not sustainable for very long. After I caught his wake I tried to recover a bit but he was pushing pretty hard and I think I got it barely under 160. By about the third kilometer or so I was feeling a bit better so I came up into his side wake. By the fourth kilometer I was actually able to take a turn in front. By that point Jim had put a big gap over Tom, and Matt had dropped behind so we really only had to think about trying to catch the Canadian guy if we could. The great thing about Dan and I is we didn’t really need to talk things over, but Dan said I should pull to the Bay Bridge, and then he’d pull to the marker. But I was fading again and he had to take over before we reached it. He led to the turn, and then at the turn he held off accelerating out of the turn until he knew I was with him, which was a really nice thing for him to do since he could have gapped me there.

At the turn you get a chance to assess where you are in relation to the people behind you. Matt was about the only person behind us we had to worry about, and he was pretty far back. We weren’t catching the Canadian guy either.

Soon after passing the Bay Bridge, the Canadian guy seemed to turn to parallel a moving fishing boat, and then cut in front of him. After the race he’d said he’d yelled at them to slack off their speed so he could go in front of them because they were trailing long lines so he couldn’t go behind them, but at first they’d just stared at him stupidly and not cut their speed but he managed to make himself understood after he turned alongside them. That problem made me think we had a chance of catching him, but he was just too strong and he continued going fast as we got more tired and slowed down.

Both us were slowing down a bit, but I felt like Dan was fading faster than me. For one thing, he seemed to have a slight problem with a couple of boat wakes, and then he dropped onto my stern wake and then went off to the leeward side into what he said was some faster water. He came back up to me after a few hundred meters and we resumed switching leads. He said to switch leads every thirty seconds or so, but it felt like when it was my turn to lead I accelerated to the front but when it was his turn to lead I’d have to slack off and let him come up. From about the 9 kilometer mark I decided not to bother letting him come through and just lead. That lasted up until the 10 kilometer mark where the suck water started. Both of us were totally in the bag, and trying to put down power in the suck was hurting my shoulder. Dan said to take it easy, we weren’t going to catch the Canadian and nobody behind was going to catch us, so we should just relax and get home. 500 meters from the finish, Jim, who is out warming down, says hi to us then yells just behind us saying “Come on Matt, only 500 meters to go”, and sure enough Matt comes by over my right shoulder. Where the hell did he come from? He powers by, Dan and I both try to hold on to him but he shakes us and finishes a couple of boat lengths ahead. Dan and I don’t sprint, but I make sure to finish a few centimeters ahead of him just so I can say I finally beat him. Back in 2009 Steve B challenged me to some day beat Dan, and today I did. He helped me on various spots on the course, and I helped him on a few spots, but overall I felt like we were incredibly evenly matched.

Still no closer to a decision on boats

I’ve got three boats:

  • Epic V10 Sport surf ski. Under-stern rudder, good on bigger waves, a bit slow.
  • West Side Boat Shop Thunderbolt. Regular (non-surf ski) kayak. Over-stern rudder, not so good in the waves, turns like a barge, faster than the V10 Sport.
  • Think Legend surf ski. Fast, but tippy as hell. Not sure I can handle any sort of waves, not even boat wakes with it. I still have problems getting it around 180 degree turns without slowing right down.

I’ve also got three races coming up:

  • Baycreek Kayak and SUP Cup, Sat Sept 14 on Irondequoit Bay
  • Long Lake Longboat Regatta, Sat Sept 21 on Long Lake in the Adirondacks
  • Erie Canal Regatta, Sunday Sept 29th at Fairport

I’ve pretty much decided that for the third race I’m going to paddle the Legend. There aren’t going to be any wind driven waves and probably not many boat wakes to deal with, plus it will be the third race in three weekends so if I DNF I won’t care that much. That leaves the other two.

Today I was paddling on the Bay in my V10 Sport, and nearly died after my rudder snagged some weeds and I was trying to keep up with Paul D. I ended up having to stop and back up to clear the rudder, and I eventually caught Paul but as soon as I did I got another weed. I had been leaning towards using the V10 Sport but if weeds are a problem, the Thunderbolt might be a better choice for the Baycreek race.

I had also been leaning towards the Thunderbolt for Long Lake. The only downside is that if the wind is really whipping up the lake, I might wish I’d brought the V10 Sport. Weeds aren’t likely to be a problem there, but waves might. I don’t have room on my roof rack to bring both and decide on the day. The other factor is that all during my recovery, my one shining goal on the horizon was to do Long Lake again. I’ve always enjoyed that race and I’ve had some good results. I don’t want to fuck it up by bringing the wrong boat. On the other hand, in 2010 I had a great result because I was better in the waves in my Thunderbolt than others were in their boats. So I’m still leaning towards the Thunderbolt.

No such thing as a smooth upgrade.

My colo box has started exhibiting this strange behaviour:

  1. My “guest” (aka domU) OS will stop talking to the network. I can still log into it by going to the “host” (dom0) OS and issuing the xm console xen1 command.
  2. The guest still thinks it’s connected to the network. ifdown eth0; ifup eth0 doesn’t accomplish anything.
  3. If I reboot the guest, using shutdown -r now "", reboot, or, from the host, xm shutdown xen1; xm create xen1.cfg doesn’t come back up. xm gives an error about being unable to reserve enough memory.
  4. If I reboot the host, it doesn’t come back, and I have to either go into the colo or put in a trouble ticket, wait a few hours and then phone them up to ask why they’re ignoring my trouble ticket. They always respond that they’re really swamped right now and they must have missed it in the rush. When I go in, they’re always bored out of their minds and playing games. Oh, and good fucking luck finding a phone number anywhere on their web site. I only found one because I had it in my phone from before they were taken over by Earthlink.

When it was happening every 4 or 5 months, I wasn’t worried. When it happened twice in one month, I got worried. When it happened again 3 days after that “twice in one month”, I’m really worried.

Thinking that this might be a Xen problem, I decided to upgrade the host OS from Debian 6 to Debian 7. Mostly, it worked just fine except for two “small” problems:

  1. I couldn’t figure out how to make it boot the Xen stuff automatically and
  2. When I manually booted the Xen stuff, the network wouldn’t come up

The first problem is due to the way they re-arranged the grub menu – all the Xen stuff is under a submenu. The recommendation I found was to use dpkg-divert --divert /etc/grub.d/08_linux_xen --rename /etc/grub.d/20_linux_xen to put the Xen stuff ahead of the non-Xen stuff in the Grub menu. That seems like a cheezy hack, but I’ll take it for now.

The second problem appears to be because of changes in the way Xen does bridging – evidently they bring up eth0 before /etc/network/interfaces brings it up, or something like that, and everybody gets all confused. The extremely dubious hack I found on-line to fix that is to add a pre-up ip addr del xx.xxx.xxx.xxx/255.255.244.0 dev eth0 || true to the definition of eth0 in /etc/network/interfaces. I suspect a better long term answer will be to figure out how to set up the proper bridging for the Xen stuff.

Now that’s all hacked together to work, fingers crossed that it actually reduces the freeze-up problem. Meanwhile, all the guest OSes are still running a 2.6.32-5-xen-amd64 kernel and I’d like to switch to a 3.2.0-4-amd64 kernel. Hopefully I can do that without another long night of standing in a hot colo facility.

Gear Review: Vaikobi V Cold Short Sleeve + V Cold Warm-Up Sleeves

I should preface this with a few things about me:

  • I’m a competitive paddler in Rochester NY, USA.
  • I’m a big guy for a paddler, although I recently lost a lot of weight, I’m still on the upper range for what you’d normally see in a surf ski.
  • Companies that sell gear for competitive paddling are few and far between in the USA, and most of what I have experience with is NRS.

Since it’s getting on for fall here in the north country, I have been wearing my Vaikobi V Cold Short Sleeve top a lot. In the cold early mornings, I add the V Cold Warm Up Sleeves for the warm up, and then strip them off for the actual work-out. The top gives a great combination of warmth, sweat evaporation and wind resistance that makes it great when you get in the boat and it’s 56°F and by the time you get out it’s 72°F. There are no rub points or irritations. It moves well with you.

I love the cut of this top, and I love the look. The zip is good for temperature regulation, and they’ve put a little flap over the top of the zip track so it doesn’t rub against your neck. It appears extremely well made with good attention to detail.

I’ve paddled two recent races in this top – the first one it was 52°F and I kept the sleeves on (and wore my Vaikobi V Cold Paddling Pant), and the second one was 66°F and I took the sleeves off after doing my warm up. In both cases, I was comfortable and wasn’t either too warm or too cold.

And keeping in mind that I’m not as athletic as most people you see on product reviews, here’s a picture of me paddling in the top:
Erie Canal Regatta 2013

If the top makes me look this good, imagine what it can do for you.

I should add a bit of a caveat here. I had a huge sticker shock three weeks after receiving my order. You can find the whole story in my review of the Vaikobi V Heat short down towards the bottom. If it wasn’t for this factor, I’d want at least one more of these tops, and maybe the long sleeve one as well. But now they have a US distributor so that’s no longer a factor. So I’m going to be ordering some more.

What a day so far

First off, our power went out. A quick survey of the neighborhood showed it was out all up and down the street, and a call to RG&E revealed that it was a tree down over a power line.

Then while I was taking a break in the back yard, unable to work because of the lack of power (although in retrospect I probably should have mowed the grass since I’m going to have to work tomorrow to make up lost time), I got an email from a member of the flying club asking why my email address (and a non-functioning email address at that) was listed as a technical contact for their domain, and can I help them transfer the domain over to their control. Doing what googling I could do on my phone showed that the current registrar are notorious domain hijackers. Oh oh.

Once the power came on, the main router was flashing a green “power light” and not connecting. Again, doing what limited web searching I can do on a tiny smartphone screen shows that this means the firmware is corrupt, and it can happen if the router loses power (which seems like a pretty shitty failure mode – you’d think the firmware could only be corrupted if it were in the process of updating the firmware, otherwise it’s not exactly what you’d call “firm”, now is it?) The solution is to download the latest firmware and reflash the ROMs, which is difficult if you don’t have an internet connection. Fortunately I have two of these routers, one at the other end of the house to act as a wireless repeater. So I grabbed that one and did a factory reset, and then reconfigured it as best I can. That was a bit of a hassle because at some time in the past I changed the name of our wifi from either Robinson_Tomblin to Tomblin_Robinson or vice versa, and I couldn’t recall which, and so when I got it wrong the iPad and iPhone happily connected to it, but the printer, the TiVos and the Nexus 7 wouldn’t.

With network connections re-established (sort of – every router configuration change seemed to involve losing it again for a time up to a minute or so), it was time to download the new firmware, enable tftp in the Windows laptop, and flash it. Amazingly enough, it actually worked. Then I reconfigured that router, and everything was back in business.

Except now my security camera isn’t working. Down to the basement to unplug the POE cable, plug it back in, and it’s working.

Now it’s time to look into the flying club business. Thank goodness for searchable mail archives – the club asked me to transfer the domain to them in February 2011, and I did. And they were using that infamous domain thief as their registrar. And at the time I pointed out that they’d need to reset all the various contact email addresses. I also gave them a list of email forwards I had set up for their domain, and they decided to turn them all off. So phew, it’s not my problem and not my fault and if they can’t remember how to log into their registrar account and change the email address, too bad for them. I feel sorry for them, and I don’t wish them ill will, but the relief of it not being something I have to help fix is overpowering all that.