Monday, September 9, 2019

Tammy

Joy needs to remember to post her thoughts every day, not once a week at most...  *sigh*

Anyway, late for work, but...  Tammy, my ...  well it's not defined as of yet, person, I finally met her.  It's wonderful.  The connection is basically the same as it's been in chat, but now with real bodies.  Touching even.  Some anyway.

I hope it's going to continue like it is.  We seem to really like each other's company. 

Monday, September 2, 2019

Deep Thought Disaster

Boom....

So, I was cheap, I left the house to get too warm during the day.  I ended up frying one of my main drives on my media server.  And then the main drive on my internet server.  Fuck.

Everything is dead.  Now to recover.

Evaluating the damage

The plex server's main drive or rather the lvm volume that had most of the storage is failing rapidly.  It won't even boot anymore now.

Dent's main drive is in a similar state so.

No:
  • Internet
  • Dhcp
  • smtp
  • mail
  • mailing lists
  • web server
  • usenet
  • media
The main problem of course is the internet.  Hell my house is automated, nothing works without the internet.

I have no memory of where my freeipa server was and I couldn't browse to it or anything.  I'm screwed.

What I do have

I've got an 8tb drive.   I also ended up buying a synology diskstation SAN, better one than the one I had.  This one has BTRFS.  I don't want this happening again.  'ya know?

Freeipa doesn't work.  I couldn't figure out what was up with it.  However I did have a snapshot with dhcp and dns working great on the services vm on the esx server.  So I got that working.

I let a pvmove run for a few days trying to move the logical volumes elsewhere.  This is not working at all.

Currently, I have what seems to be a totally dead dent and the main server drive is down in bucket.  I have a router that is working fine to connect us to the internet.  I have dhcp/dns running on a VM in the esx server.  So I've got internet.    I have a new VM with centos 7 1810 and freeipa on it.  That is where I am.

Detailed steps as I take them.

My current plan was to delete srv and debianroot which were on the dead drive.  It seems to hang when I do this.

What I'm going to do instead is:
  1. Figure out exactly what drive is dead on bucket
  2. Remove that drive and the 8tb drive from lvm
  3. turn off bucket
  4. ditto physically on the machine
  5. put the 8tb drive into the new server
  6. remove the old server configuration from the esx server
  7. shut down old h2gt2g
That will leave it in a state where everything is gone and I'm ready to get going.

I started playing with ipa.  I added ipa.deepthot.aa to the /etc/hosts file of my laptop.  Then I went onto the ipa server and started looking around.  Looks good.  I am going to muck with it a bit, just 'cause I'm here
I'm setting the mail domain to deepthot.org and the shell to bash

OK... now... to bucket
using 'lshw -C disk' I can see that the disk is a Seagate 4TB model ST4000DM000-1F21

I'm going to remove that one and the 8TB from the bucket lvm array
Tried to remove them several different ways.  Finally, just pulled both drives and used the 'vgreduce --removemissing --force'  That destroyed my partitions, however the server was backed up on my USB drives fairy recently.

Bucket boots fine.  Both remaining drives are healthy.  It still sounds really loud.

Monday 9/2/19 Day 2

Dent seems totally dead.  I've powered down Bucket to make it quiet.  I'm going to have to bring it back up eventually.  I don't know if the Torrent VM is there still.  I'll have to track down the VPN at least.

First Project New h2gt2g

  1. Remove h2gt2g from heartogold
  2. Power down h2gt2g 
  3. Unpack new h2gt2g
  4. Install drives
  5. Switch out SANs
  6. Play around a bit with the new SAN
When mucking about with heartogold I found a corrupted VM on it.  Not sure how it got in that state, however I ended up turning on ssh, sshing into heartogold and editing a configuration file as outlined in: https://communities.vmware.com/thread/582673

You should be able to permanently remove any inventory reference to this VM by removing the five lines that refer to this entry in /etc/inventory/hostd/vmInventory.xml e.g.:
  <ConfigEntry id="0002">
    <objID>3</objID>
    <secDomain/>
    <vmxCfgPath>/vmfs/volumes/590cca43-c78bd3ac-1234-000c2908a466/VMware vCenter Server Appliance/VMware vCenter Server Appliance.vmx</vmxCfgPath>
  </ConfigEntry>

Copy a back-up before doing this and use vi to edit the file.
Stop vpxa and hostd before edit:
#/etc/init.d/vpxa stop
#/etc/init.d/hostd stop
restart these after edit:
#/etc/init.d/vpxa start
#/etc/init.d/hostd start


Bob
The only thing configured properly on the esx server was the nfs share I set up yesterday to serve up iso files.  I went and deleted it from both vms and then deleted the nfs partition itself from here:


So, new SAN, regular RAID which sucks.  Yeah it's btrfs, but it's not using it right.  So boooo...  Sent it back, I'm going to buy two more drives for the old raid instead.  Put the 8TB into the old raid, it's now scanning and stuff.  Time for bed.

Sunday, September 1, 2019

More on becoming Joy

Joy's Journey with a Destination in Sight

I still haven't been keeping a blog as often as I should.  It should be daily and there's just not enough to do.  So when the important days happen I miss them.

First Stop Orchie

In November I think of 2018 there was a blood test that seemed to indicate the Spironolactone was damaging my kidneys.  The easiest way to take care of that is with an orchiectomy.  Now what they normally do for like prostate cancer or whatever they're looking for smooth tight skin, so they really do a number on the scrotum.  I haven't looked that closely into it.  However if you're trans you want to save that skin.  This requires one incision along the center of the testes to minimize scarring and so on.  Anyway, I decided to talk to one of the best MTF surgeons that happens to be located here in Scottsdale.

Dr. Ley told me about the type of incisions they'd have to make and so on.  I was thinking of going to a urologist that was in network to have it done rather than Dr. Ley who's not and require payment up front.  I wasn't really thinking of it being imminent, but I asked he what she thought about me for a vaginoplasty.

She told me I have plenty of tissue and it would be something that's doable.  However I needed to be 215 lbs to get it done.  My heart sank, I was at 307 lbs that day.  100lbs just seems totally unreachable.  Heck, that's lighter than I've been since I got married in 1982.  I was 225 back in those days.  When I had my heart attack I was about 260, thinking I was 250.  Impossible.

It's Impossible, Right?

I thought about it for a long while and I decided that I really should get a vagina.  At this point my body really wants to have one.  My bits think they're girl bits.  Anyway, after a couple of months I thought this weight goal is impossible, but let's try.  If I can get to 250 I can make it the rest of the way.

At the first of the year I started trying on my own to get there.  I did, well, meh.  It's hard to do this.  I made it to 290 with nutrition drinks and frankly lots of cheating.  My girlfriend Cheryl has diabetes.  Her endocrinologist has someone running a medifast thing out of her office.  Cheryl said why don't you try that.  So I did.

Turns out if you want something more than eating you can lose weight.

Wrong.  You can do this girl

This was April.  I hit my 250 goal about July.  As of this writing I'm at 237 which is 22 lbs away.  I saw Dr Ley, gave her a bunch of money and now I have a surgery date April 2 2020.  I should be healthy in time for the elections.  I'm doing this, it's happening and it's real.

Final musings

I've been thinking about going all the way about as long as I've been thinking about transitioning.  So close to 40 years now.  It seemed like something impossibly difficult for me to achieve.  The money, the time, hell in those days you had to transition for a year before you could even get hormones.  Impossible.

Every step I take puts the next step in reach.  The first was the hardest because I didn't deserve it.  Having the audacity to do HRT when I was just a total loser and not worth anything took quite a bit.  Since then though it's been fairly easy.  Each step has been easier because each one before wasn't as hard as I thought it would be.

I'm here.  I'm Joy Aliza Denebeim: trans woman, and I couldn't be happier.

Deepthot Project Status

Things that need doing

So I left for awhile.  I've had 2 hard drive failures taking out my media server and my main internet box.  Everything is dead.  None of the stuff I have listed as working is in fact working anymore.  I've decided to throw up my hands and start over from scratch.  I'm going to publish this blog and start another.
  1. freeipa - winner although it has been a pain to get working
  2. ldap
  3. dns
  4. home directories
  5. establish network
    1. dhcp
    2. upnp
  6. services
    1. email
      1. exim
      2. imap
      3. mailing lists
      4. spamassassin
    2. media
      1. torrent
      2. plex
    3. web
    4. ssh
      • yubikey
      • external
    1. news
    2. social
      1. mastodon
      2. freenet
      3. diaspora
Do not install heimdal-clients it uninstalls freeipa fucking you up royally

Router

The NAT stuff is kinda a pain on my mikrotik.  But setting up NAT is from ip->firewall->nat  Remember src-nat is outgoing dst-nat is incoming.   Also annoyingly you have to know the IP, so you'll need to set up the dhcp with the IP hard wired.

DNS

*finally* I've been trying for days to get dhcp and dns to play nicely.  The breakthrough was a couple of things.
  • Make sure your permissions are correct on the key file.
    include "/etc/bind/rndc.key"; needs to be readable by both dhcp and dns.  And that belongs in the named.conf file.  freeipa isn't enough.
  • The update permission is in the zone configuration of the dns zones.  This is the magic config that makes it work:
    grant rndc-key zonesub;
  • Don't be afraid to dump the leases on dhcp.  To do that you:
    1. systemctl stop isc-dhcp-server
    2. rm  /var/lib/dhcp/dhcpd.leases
    3. touch /var/lib/dhcp/dhcpd.leases
    4. chown dhcpd /var/lib/dhcp/dhcpd.leases
I hope this is right and sufficient.  I really need to be better about taking notes.  Of course that's why I'm doing the blog.

Adding a client to freeipa

  • apt install -y freeipa-client sssd-tools autofs nfs-kernel-server
  • ipa-client-install
  • ipa service-add nfs/<client>.deepthot.int
  • ipa-getkeytab -s services.deepthot.int -p nfs/<client>.deepthot.int -k /etc/krb5.keytab
  • ipa-client-automount
  • echo automount:  files sss >>/etc/nsswitch.conf
  • edit /etc/nsswitch.conf and put the sss first (there should be a better way)

Snapshots

  1. mount /dev/sda2 /mnt # mount root of btrfs on /mnt
  2. mkdir /mnt/snapshots
  3. btrfs subvolume snapshot -r @ snapshots/whatever
    @ is the root file system's subvolume.  This makes a read-only subvolume that is the state of the filesystem when the snapshot is taken.  You could snapshot anything actually like @/etc to save just the etc before you do something unwise
Easy peasy.  Rollback is a bit tougher
  1. mount /dev/sda2 /mnt
  2. cd /mnt
  3. mv @ to @.bak
  4. btrfs subvolume snapshot snapshots/whatever @
Notice this is missing the -r that makes a read/write snapshot.  If you'd made the original read-write you could have just moved the snapshot to @
I haven't tried this yet, but you probably would have to do a mount -o remount,rw / or something similar.  Maybe a reboot to be safe.

DHCP

Since I set up a second IPA server I thought it would be good to make the dhcp redundant as well.  https://kb.isc.org/docs/aa-00502 is what I'm going to follow.
After a bunch of grief due to me not paying close attention to the configuration (the peer ports change as well as the peer names) I got it working.  Seems to work okayish.

TODO

Okay, the next thing I'm going to do is bite the bullet and set up the home directories.  They're almost there.  One thing though, I want my laptop to be on the network when it's there, but still allow me to log in with a *different* home directory when I'm not on deepthot.  That is I think my next thing.
Derp, no the first thing I need to do is to figure out what the deal is with the keysync on services.  It crashes every minute and fiik why. (actually I just cloned the original and made a redundant server.  I'm planning on reinstalling the old one)
There's still an issue with dhcp, it's requesting x.deepthot.int.deepthot.int be put in, actually it seems to only be fs.  I'm thinking maybe remove it from the kerberos group and re-add it. the issue is dhcp asks for the hostname not the short hostname, if you do what the docs say and set the hostname to include the domain that screws up the dhcp/dns.  So, just use the short one, but make sure the domainname is set right preferably with dhcp working right.

Sunday, June 9, 2019

deepthot configuration router

So, I got tired of writing in my notebook about the new configuring I'm doing on deepthot.  I thought hey make a new blog, but no deepthot is not available.  There was a blog 15 years ago with one entry.  *sigh* ah well, so I guess I'll post stuff here.

Today I thought I'd move the laptop and the server onto the router and set it up 'for real', sadly this kinda blew up.  The router is supposed to be answering on 192.168.42.1, but it's not.  What it is doing is dhcping on a bridged network.  I believe that port 1 is supposed to be the uplink and 2-10 are the local lan.  I think that's what I set up.

So, what I need to do is to set the bridge to .1 instead of dhcp.  I think that's all that's required.

I did this first, doesn't seem to help.
Oh, for testing I set the wired lan to 42.42, the wifi is still on 12.* this seems to work nicely.

I switched the wires around.  Before I put the main network in port 3 and looped port 1 and 2.  I removed the loop and the plugged the main network into 1.  This didn't help.  I think it's worse I seem to have lost the local machines from the web browser I think.  Yeah, it just needed the network on the bridge.  Well foo...  Nat?

So, I'm not sure what I did, but the thing totally locked up, I rebooted it and now it seems to be working.  At least to the .1 address.  Natting doesn't seem to work.

I ended up resetting the router to factory default, then turning off dhcp and setting the address to 192.168.42.1 on the router.  That seems to have worked.



Wednesday, June 5, 2019

OK, so over a year since my last blog entry.  I guess I must be making this post for the same reason I made my last one.  Namely it's something Mischa said in my session today.  She strongly suggested I start keeping a journal.  She says that writing is a good way to integrate your left and right hemispheres of the brain.  I hadn't thought about that.  It makes sense though, at least with touch typing that invokes both sides of the brain, but also there's the whole visual processing of what you've written.  So, cool I guess.

Wow, it's been a year.  Lots of stuff happened.  Izzie and I started talking with each other and hanging out for several months, then she ghosted me in October.  I haven't heard from her since.  Her birthday is tomorrow.

The court went over fine.  I'm now legally female and my name is Joy Aliza Denebeim.  I'm out everywhere.  For over a year in fact.

Last blog post I hadn't told my mother yet, I came out to her the day before her 98th birthday.  It went really well.  I think she likes Joy way more than she liked Jay.  We can relate quite a bit better than we did before.  I originally was going to come out to her when I went to visit in Dec 2018, but when full time came looming up at me I realized that I'd be so female by next christmas it would just be a shock for her.  So I came out.

The visit by the way went great.  I had a good time visiting with her.  This of course was half a year ago now. 

That's me at pride a month or so ago.  My smiles keep getting bigger and more genuine.  I like myself. 
This is me after my friend Gia had he way with me