Amazon Alexa App / Echo Dot "Failed to authorize link code. Please try again."

This is just consumer gear, but Googling didn't turn up anything at all for the error, so here you go.

Symptoms:
Try to set up a freshly reset Echo device. When joining WiFi, you receive an error in a red banner at the top of the screen that says "Failed to authorize link code. Please try again."

Resolution:
Try from another device running the Alexa app. I tried from my wife's phone (where the Echo Dot order was originally placed) and it worked straight away.

ESXi 6.7u2 update to 6.7u3 failed

Error on my host: Update manager fails to patch the host. When running the manual patch, the host profile update fails.

Error in esxupdate.log:

2019-08-25T00:45:24Z esxupdate: 2099348: root: ERROR: esximage.Errors.InstallationError: ('VMware_locker_tools-light_10.3.10.12406962-14141615', '[Errno 28] No space left on device')

Resolution:
cd /tmp
wget http://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/tools-light/VMware_locker_tools-light_6.5.0-0.23.5969300.vib
esxcli software vib install -f -v /tmp/VMware_locker_tools-light_10.3.10.12406962-14141615.vib

Resume manual patching:
esxcli software profile update -p ESXi-6.7.0-20190802001-standard \ -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml 

esxcli network firewall ruleset set -e false -r httpClient

reboot

Done.

DPM agent push to 2008 Fails 0x80990a1c

Install protection agent on node.node.com failed:


Error 347: An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on node.node.com.


Error details: Unknown error (0x80990a1c)


Recommended action: Verify that the Agent Coordinator service on node.node.com is responding, if it is present. Review the error details, take the appropriate action, and then retry the agent operation.






Googling the error indicates that KB975759 may be missing.


This KB is not installed on the trouble server.






Manually installing the update MSU package says "update does not apply to your system".






Expand the update into a folder.


Expand –F:* c:\kb975579\Windows6.1-KB975579-x64.msu c:\temp\expandkb975579\






Run the installer (this takes a while!)


Start /w pkgmgr /ip /m:”c:\temp\expandkb975579\Windows6.0-KB975579-x64.cab






Reboot






Re-push the DPM protection agent.

ESXI 6.7 - Clone vmdk fails on change tracker error code 5948

vmkfstools -i /vmfs/volumes/ssd-ds1/filer/filer.vmdk /vmfs/volumes/ssd-ds2/filer/filer.vmdk
Destination disk format: VMFS zeroedthick
Cloning disk '/vmfs/volumes/ssd-ds1/filer/filer.vmdk'...
Clone: 100% done.Failed to clone disk: Invalid change tracker error code (5948).

Resolution:

1. rm the change tracker file (filer-ctk.vmdk)
2. vi /vmfs/volumes/ssd-ds1/filer/filer.vmdk , comment out the change tracker line. 
3. Repeat clone (vmkfstools -i) 

App Service Backup Fails when Including Azure MySQL DB

The application itself is running just fine on this DB string, but when including the Azure MySQL database in the App Service backup configuration, the backup fails.

Log Details:

MySql backup exited with code 2 for db:1cdda146. Output: mysqldump: Got error: 9002: The server name you tried cannot be found. Please use the correct name and retry. Please check your server name bdef0f98dd83a7ff16432ffc1c54394. when trying to connect

App Service Connect string:
Database=1cdda146;Data Source=bdef0f98dd83a7ff16432ffc1c54394.mysql.database.azure.com;User Id=c35e433d7a@bdef0f98dd83a7ff16432ffc1c54394;Password=<pw>

The DB name here is made up to match the example - the DB resource name is 31 chars. 

I can add another connection string with a different database - 29 chars, and that works. 

There also appears to be a lag in the App Service backup pulling the changes in the connection strings. If you change the settings for connection string N and immediately go run a backup, the old settings appear to be used. 

I've not found anywhere to point a finger at on this, yet. The log entry has a truncated server name. 

Next up I'll try making two new Azure MySQL DBs with 31 and 20 chars, to test my theory.

Update 1:
The new 31 char and 20 char DBs both back up fine. I guess I'll just make a new Azure MySQL DB and migrate schemas it.

Azure Application cannot enable SSL

I was testing out some stuff and ran across this error when trying to add an SSL cert to an application:

"Cannot enable SNI SSL for a hostname foo.bar.com because current site mode does not allow it."

This unhelpful error is just because you have selected a Free version of the Application Service plan. It has nothing to do with the web app you're in right now, other than the meager fact that you want to add SSL to it.

Upgrade the plan to a Standard or Premium plan to get past this error.

Unauthenticated SSH port forwarding in Cisco CSS 11500

References:
CISCO:   http://tools.cisco.com/security/center/viewAlert.x?alertId=37889
MITRE:  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0667

Timeline:
Feb 27 2015: Reported to Cisco PSIRT. Assigned to Incident Manager.
Mar 13 2015: Status check with Incident Manager.
[ Mar 18 2015: Cisco releases IntelliShield ID 37889 ] -- Not copied on this.
Apr 10 2015: Status check with Incident Manager
Apr 13 2015: Incident Manager supplies IntelliShield ID; Finding closed from my end.