Archives for: January 2014

01/20/14

  03:25:00 pm, by The Dreamer   , 1420 words  
Categories: Digital Photography, Travel, TV, Doctor Who

Chicago TARDIS 2013

Link: http://tardisi.com/chicago-tardis-2013/

Chicago TARDIS 2013

I went to Chicago TARDIS 2013 this year, after having missed going to Chicago TARDIS 2012. This being the weekend after the 50th Anniversary, I was determined to make this convention.

This year things were interesting, in that I flew out of Manhattan at 7:05am, arriving in Chicago around 9am. Fortunately, I didn't have any trouble being able to check in right away when I arrived at the hotel. It was kind of strange being picked up and riding alone in a stretched limo. But, I guess its what was available when I showed up, and nobody else was making a similar trip around that time. I had booked shared ride service from Windy City Limos, like I had the previous two Chicago TARDISes. Return trip was in black sedan. I had also booked Black Car in Manhattan for the ride to and from the airport.

While getting settled in the hotel room, before heading down to see about lunch....I discovered to my horror that I the charger for my Panasonic Lumix DMC-FZ200 was not among my luggage. I did have a couple of what should be fully charged battery packs, but they would not last the weekend.

I later spent some time researching local options on what to do....I settled on the possibility of experiencing Target on Black Friday, where they were featuring the Nikon Coolpix L320 for $99.99 or the Nikon Coolpix L820 for $199.99. I was leaning towards the L320, since this wasn't likely to become one of my regular cameras, so price was a big factor. Alternatively was to see if they carried extra chargers for my camera, since they carried the Panasonic FZ70K....though I later found out that it wasn't the same battery. They had this camera on sale for $299.99, IIRC. Also the Coolpix L320 or L820 had the advantage to me that they took AA batteries (4).

I knew Target was going to be one of the stores opening Thursday night for Black Friday....though I wasn't sure when I would make the dash to try to salvage my trip.

Later on Thursday night, after getting my badge and then checking out the reception (when I saw other people heading the same way, but continue out across to Target.) After getting some food and drink, making a loop around the space, I decided that I would make a dash over to Target and see what's what.

It was chaos in Target, the electronics/cameras counter was pretty much inaccessible since everybody there was after iPad's of various models and sizes. I wandered around a bit to see if things might settle down as they started reporting certain iPads were now out of stock. Occurred to me that I should see about some cheaper water for use in the hotel room, but they didn't have any small packs of still purified or spring water available, so I got a 6 pack of flavored water. Guess I could do that instead of mixing Crystal Light to go with my medication.... As I walked back, I noticed that one of the end of aisle displays was full over Nikon Coolpix L320's. Since that was the most likely candidate if I was going to buy a camera for salvage the trip....its what I got.

It then took forever to snake out from one opposite corner of store to the other to check out. I had intentionally brought my Target Red card this trip, which I otherwise usually leave at home when I travel. Plus I hadn't shopped at Target for a while, in anticipation of this possibility I would later make another trip, to get refill pages for the album that I keep the purchased photos and such I get at Chicago TARDIS, and a bottle of shampoo as the hotel shampoo was bothering my scalp.....

I knew I had an 8 pack of Lithium Photo AA's in my luggage. I went back to my hotel room and unpacked the new camera and spent sometime getting familiar with it (using the included AA batteries.) Since I had owned Nikon Coolpix cameras before...namely the Coolpix S80 (Much earlier on there was a Coolpix 5500, but I don't recall what it was like anymore), I found the menus and such largely familiar, so I tweaked up some settings to fit the kind of shooting I was going to do this weekend. And, set up to give it a test.

The reception was still going on, so I went back in and shot some pictures around the room to get a feel for its controls and behavior. And, downed some more snackage before calling it a night.

Full story »

Pages: 1· 2

01/19/14

  04:22:00 pm, by The Dreamer   , 2307 words  
Categories: Networking, FreeBSD, Printers

HP Officejet Pro 8600 Plus e-All-in-One Printer - N911g

So, near the end of July, I started investigating (once again) on replacing my HP Photosmart 8450xi (which was now over 8 years old....bought it on June 30th, 2005 - Back from Vacation Tech Buying Spree?...setup on July 9th, 2005 - link

I had started looking some time before this, but was put off for a bit due to my experiences with the Brother DCP-7065DN -- link, since it seemed most of the choices out there were GDI and I'm moving to more and more heavily FreeBSD as my primary operating system.

Especially since it appears that 'box' finally called it quits on December 2nd, before I had started my journey home from Chicago TARDIS that day....and orac is inching close to its end, as the pair of ST2000DL003's which evidently only had 1 year warranties from June/September 2012 started going shortly into the new year. I was trying to use ddrescue to force sector remapping on the first drive, when the other drive has decided to vanish permanently. I had thought it was was DM's that had 1 year and DL's that had 5 years, perhaps I had it backwards....or its a question of when I purchased them, or how they were packaged.

Checking my order history, I purchased one drive on June as a bare drive and later in September as a retail kit. I haven't yet pulled the drives, so I can't look up the serial number for the vanished one, but Seagate's website says the one that is responding is out of warranty. Even if the other drive is still under warranty, not sure I want to deal with getting it exchanged for a refurb to create a solo 2TB drive. Can't think of not wanting raid given what I'll likely use it for. And, not sure I'd buy a different 2TB drive to be its mate (and it won't work with my other 2TB arrays, since its an advanced format 2TB drive...while the lraidz2 pool on zen used legacy format 2TB drives (which limits options of growing it non-destructively.)

Fortunately, I had copied one of the big volumes from it over to zen (along they way it got corrupted, so had been trying to copy it back from zen when the other drive died). And, files of the other volume (my pyTiVo store) should all be in backup, where I don't have space on zen to restore them yet.... I have pyTiVo on zen, but the content under it is different...and larger, so much that it is currently not being backed up. I haven't gotten made much progress on building the second backup server....guess I'll need to look at this sooner than later.

And, now it seems the other 2TB RAID-1 array on orac is dying. I just went ahead and failed the drive that was giving it issues. Not sure what to do with it...suppose I could try ddrescue on it and see what happens. The big volume on it had also been copied over to zen, so guess I'll update my HSTi's to point to zen instead of orac for their content. Another used to be for Time Machine backups, but I had moved that over to zen when I set up the new work laptop to do Time Machine backups on my home network. I was using that space as overflow from pyTiVo. And, another was for backups of various things, which I had stopped adding to as new backups are going to zen now. Its things like regular backups of my websites at dreamhost and 1and1, my router configs, serial console servers, and some other backups. I was also replicating some directories on zen to orac as backup (left over from when zen was a Windows 7 PC....which saved me from losing everything when it scrambled itself.)

But, back to my printer quest.

Full story »

01/08/14

  06:55:00 pm, by The Dreamer   , 1223 words  
Categories: FreeBSD

sonewconn: pcb 0xfffffe006acd9310: Listen queue overflow: 8 already in queue awaiting acceptance

Today this message appeared, and I knew that I needed to find a socket with a QLIM smaller than QLEN=8, but couldn't remember what the formula was.

But, the topic had come up on the bind-users list back on November 14th, 2013, where the messages was about '16 already in queue'.

Where for months before this I had been getting messages for '10 already in queue', and the only tcp socket I found that might be a problem The only thing with a QLIM of 10 was the submission port on sendmail, which didn't make sense...and bumping it up didn't help.

And, searching my system for the pcb was a bust (using lsof ‑i ‑Tfs | grep LISTEN or netstat ‑LAan)

Reducing end digits until I got matches, resulted in matches that didn't seem to fit.

So, I tried to ignore it....

When it popped up on the bind-users list. The discussion went to that the tcp-listen-queue default is 10. But, it didn't seem to apply in my case, until later when I did see some messages for "5 already in queue", because the base bind in FreeBSD 9.2 is 9.8.4-P2 where the default tcp-listen-queue is 3. It was changed to 10 in bind-9.9.

Anyways, when the thread came up on bind-users list, I decided that I needed to really dig for the answer. Searching through the kernel source, I eventually found my answer.

The message is reporting when QLEN > 3 * (QLIM / 2)

Aha...QLEN = 10 => QLIM = 6....which was my Socks5 proxy server (net/ss5)

Couldn't figure out how to change the listen queue in it through its configuration file, so I stopped using it. And, the messages stopped. I had filled out the proxy settings in chromium with squid for http & https and ss5 for Socks5....and evidently some update around the same time as when I upgraded to FreeBSD 9.2 (or perhaps FreeBSD 9.2 made the message show up for dmesg?). Switching to using squid for all protocols fixed it.

Meanwhile...while I was looking for that old message, which I had posted back on November 20th, 2013. I stumbled upon some older threads on freebsd-stable.

I was searching on home computer, where I'm subscribed to the list, while my work email isn't subscribed to the list... and all my old freebsd list emails have since been purged. Still trying to get my email back under control after switching providers...both personally and at work. Plan to let an old personal domain expire once the migration is fully done, but its going so slowly that I let it auto-renew last year...and perhaps forgetting to change to the default 2 year auto renew to 1 year was intentional? New expiration date is November 20th, 2015. It was an early domain that I had registered, before I knew that '-'s in domains are considered bad. There were a number of different blogs that I would try to leave comments at, and the comments would claim to go to moderation but actually get discarded. The owner of one site eventually responded saying the system automatically does that to domains with '-'s in them, since most of them are spam. But, he'll whitelist my domain for the future. (IIRC, it was about a different antispam patch he had written for our blogging platform, functionality that never made it into newer releases and hadn't gotten updated. Wishing something like it was back again.)

That made me wonder if another site, running under my employer's domain...with a '-' in it, was rejecting my comments under my work email account, because it has a '-' in it. Switching to the form without the '-', and the comments would appear. :)) I suggested to the site owner that he should remove that filter or at least whitelist our employer's domain.

The threads were older, and associated with upgrading to FreeBSD 9.2....first thread was started on August 1st, 2013. Was for "8 already in queue", and later indicated that the system was for backups and did outgoing rsync's and also did NFS and Samba. The discussion talked of strangeness of only having a queue limit that small, and that the default limit (128) is like 20 times that. The last reply to the thread was October 7th, 2013. Another thread started on September 30th, 2013 for "193 already in queue", with the last reply on November 12th, 2013.

The main hanging point again was that the pcb couldn't be found...and the suspicion is that its how daemons fork processes to listen to sockets and/or to handle requests, plus that they might create all these things and then use fork to detach to run in the background. The last thread was about using dtrace to maybe see if the process could be found that way.

I've been meaning to play around with that, but when I had last tried...found that its a module, and kldload dtrace wasn't the right way to load it.... its kldload dtraceall Guess I've rebooted since then, so it should be right (and done automatically in /boot/loader.conf.) Guess when I have time....

So, I wonder if I should reply to one or both of the threads....but first, its been a while since I blogged....so here I am.

As for today's message?

QLEN = 8 => QLIM = 5

At first I looked for the full address:

Shell

# netstat -LaAn | grep fffffe006acd9310

nothing

trimming, I eventually got:

Shell

# netstat -LaAn | grep fffffe006acd
fffffe006acdb7a0 tcp4  0/0/5          *.5666             
fffffe006acdb3d0 tcp4  0/0/128        *.587              
fffffe006acdcb70 tcp4  0/0/50         *.445              
fffffe006acdc3d0 tcp4  0/0/128        *.621

nrpe? Hmmm, did that one new disk check push me over?

What else is 5?

Shell

# netstat -LaAn | grep '/5 '
fffffe012b909b70 tcp4  0/0/5          *.10143            
fffffe006acdb7a0 tcp4  0/0/5          *.5666             
fffffe006aab2b70 tcp6  0/0/5          *.5666             
fffffe006abd17a0 tcp4  0/0/5          *.9032             
fffffe019a1503d0 tcp4  0/0/5          *.873              
fffffe012b9093d0 tcp6  0/0/5          *.873              
fffffe006abd0000 tcp6  0/0/5          *.2049             
fffffe006abd03d0 tcp4  0/0/5          *.2049             
....

10143, imapproxyd - wasn't accessing roundcube

9032, there shouldn't be anything accessing pyTiVo

2049, NFS hmmm....well, my MacBook Air might be doing a PowerNap and doing its TimeMachine backup to the NFS share on my FreeBSD server.

873, rsyncd - BackupPC is constrained against running more than 3 jobs at once, and at most 3 against this server (I break up my [bigger] systems so its not all backed up at once, using lockfile in DumpPreUserCmd, though I have exceptions on this server so that certain rsync shares aren't blocked if a really long backup is running (recently had an incremental take 1 day and 11 hours - at least on my FreeBSD/ZFS system I have a comamnd in DumpPreShareCmd to take a snapshot.... a couple of weeks earlier, I had an incremental take 1 day and 15.5 hours.

Tweaked some sysctl's, and deleted some old snapshots seems to have sped things back up.

Probably NRPE

So some of the messages convert to:

QLEN  =>  QLIM
====      ====
 193      128
  16       10
  10        6
   8        5
   5        3

OTOH, "8 already in queue" is what the first thread in August had, and he had added about being a backup server that does output rsync and had also mentioned NFS (and Samba).

Additionally, in the output looking for QLIM == 5, were these lines

Shell

unix  0/0/5          /tmp/.org.chromium.Chromium.wpVy4H/SingletonSocket
unix  0/0/5          /tmp/ksocket-beastie/klaunchere40501.slave-socket
unix  0/0/5          /home/beastie/.pulse/zen.lhaven.net-runtime/native
unix  0/0/5          /tmp/.esd-1000/socket
unix  0/0/5          /tmp/seahorse-QY4SIO/S.gpg-agent
unix  0/0/5          /var/run/samba/nmbd/unexpected

When I was previously looking for QLIM == 6, there were only the two tcp sockets, so it was only 50-50 on picking the culprit, and since the other was minidlna which I haven't done more than build/install it so far. It was really only the one socket to explain it, and it did clear up immediately once I stopped using it.

As for NRPE, there doesn't seem to be a way to change it easily....so I'll just see if the problem continues to happen, before investigating other solutions.

Full story »

Now instead of subjecting some poor random forum to a long rambling thought, I will try to consolidate those things into this blog where they can be more easily ignored profess to be collected thoughts from my mind.

Latest Poopli Updaters -- http://lkc.me/poop

bloglovin

There are 20 years 1 month 28 days 15 hours 37 minutes and 20 seconds until the end of time.
And, it has been 4 years 10 months 29 days 22 hours 25 minutes and 36 seconds since The Doctor saved us all from the end of the World!

Search

January 2014
Mon Tue Wed Thu Fri Sat Sun
 << < Current> >>
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    
Google

Linkblog

  XML Feeds

Who's Online?

  • Guest Users: 1
This seal is issued to lawrencechen.net by StopTheHacker Inc.
multiblog platform

hosted by
Green Web Hosting! This site hosted by DreamHost.

monitored by
Monitored by eXternalTest
SiteUptime Web Site Monitoring Service
website uptime