After putting the solution in
my previous post through its paces for a few
weeks, I realized the less intrusive approach is to patch Homestead v2's scripts/create-mysql.sh
with the following
snippet:
#!/usr/bin/env bash
cat > /etc/mysql/conf.d/password_expiration.cnf << EOF
[mysqld]
default_password_lifetime = 0
EOF
service mysql restart
DB=$1;
mysql -e "CREATE DATABASE IF NOT EXISTS \`$DB\` DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_unicode_ci";
This change pipes the default_password_lifetime
setting into the file /etc/mysql/conf.d/password_expiration.cnf
and
restarts the mysql
service. The provisioning process then can proceed as normal.
This approach requires no updated
vagrant virtualbox image or
other similar adjustments and allows us to
keep using version 0.3.3
indefinitely.
I'm likely going to abandon my settler and homestead forks as I couldn't adequately maintain them moving forward. I'll work to push this upstream as I feel it should be implemented there.
On November 7th 2016, I was hit with a peculiar issue I've never seen before working in a provisioned Homestead box. The exception:
PDOException in Connector.php line 55:
SQLSTATE[HY000] [1862] Your password has expired. To log in you must change it using a client that supports expired passwords.
Firing up a different vagrant machine, I was greeted with the same problem. This seemed to affect all of the vagrant
boxes using version laravel/homestead (virtualbox, 0.3.3)
.
On the machine, the MySQL version displayed by mysql --version
is
mysql Ver 14.14 Distrib 5.7.9, for Linux (x86_64) using EditLine wrapper
MySQL 5.7's password expiration policy seemed to point to the culprit.
From MySQL 5.7.4 to 5.7.10, the default default_password_lifetime value is 360 (passwords must be changed approximately once per year). For those versions, be aware that, if you make no changes to the default_password_lifetime variable or to individual user accounts, all user passwords will expire after 360 days, and all user accounts will start running in restricted mode when this happens.
Looking at the list of users with relevant columns shown that the password for the user homestead
was set on 2015-11-13 03:50:18
.
mysql> select host, user, authentication_string, password_expired, password_last_changed, password_lifetime from mysql.user;
+-----------+-----------+-------------------------------------------+------------------+-----------------------+-------------------+
| host | user | authentication_string | password_expired | password_last_changed | password_lifetime |
+-----------+-----------+-------------------------------------------+------------------+-----------------------+-------------------+
| localhost | root | *14E65567ABDB5135D0CFD9A70B3032C179A49EE7 | N | 2016-11-08 22:28:11 | NULL |
| localhost | mysql.sys | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | N | 2015-11-13 03:50:10 | NULL |
| 0.0.0.0 | root | *14E65567ABDB5135D0CFD9A70B3032C179A49EE7 | N | 2015-11-13 03:50:15 | NULL |
| 0.0.0.0 | homestead | *14E65567ABDB5135D0CFD9A70B3032C179A49EE7 | N | 2015-11-13 03:50:18 | NULL |
| % | homestead | *14E65567ABDB5135D0CFD9A70B3032C179A49EE7 | N | 2015-11-13 03:50:18 | NULL |
+-----------+-----------+-------------------------------------------+------------------+-----------------------+-------------------+
5 rows in set (0.00 sec)
Date manipulation in PHP showed
that 360 days from 2015-11-13 03:50:18
is 2016-11-07 03:50:18
, about the time this started occurring.
It was later that I discovered this pull request didn't make it into
branch revert-56-master
used to build the 0.3.3
box. It succinctly described the problem at hand.
I saw 4 possible choices for a permanent solution:
default_password_lifetime=0
explicitly in /etc/mysql/my.cnf
.PASSWORD EXPIRE NEVER
to disable password expiration for that user.In looking to correct upstream, the pull request was denied with very good reason. It was a ton of work to seemingly get the 5.6 branch up to master and I have absolutely no guarantee that something wasn't broken in the process.
Not being content with abandoning that work, I pushed a vagrant virtualbox image that should continue the 5.6 branch forward for the foreseeable future. There is one major caveat, it requires a patch to Homestead v2 to accommodate the changes introduced.
Steps required to use the image:
vagrant box add w0rd-driven/homestead
.box: "w0rd-driven/homestead"
in Homestead.yaml
to specify a different vagrant box than the default
of laravel/homestead
."laravel/homestead": "2.0.x-dev"
to the require-dev
section of composer.json
.repositories
section of composer.json
:"repositories": [
{
"type": "git",
"url": "https://github.com/w0rd-driven/homestead.git"
}
],
composer update
to change to the new composer package.vagrant destroy -f
then vagrant up
.I've enabled issues on both forks of settler and homestead. Unfortunately, I don't have VMWare Fusion to build the vmware provider image. If anyone has the capabilities, I would gladly grant the access to push the image.
In the event this causes grief in the future I wanted to point out the steps to downgrade Windows 10 Mobile build 14295 back to 8.1. The Windows Device Recovery Tool fails to detect the phone without the steps outlined in BrunoTrivellato's response on page 2.
To make this easier, I thought I would repurpose the steps as I can't seem to find an independent or direct link:
Reboot your phone (pressing volume down + home button for some seconds until it vibrates) and immediately plug it back in the PC.
I wanted to mark what feels like an oasis in the desert of a long journey. During my last job search over 2 years ago, I tired of what had become a disjointed resume update routine. Accomplish a task, go to the Word-document-as-one-true-source, update, print to PDF, go to LinkedIn, update, go to careers.stackoverflow.com, update, rinse & repeat.
I yearned for one interchangeable format that allowed me to generate HTML, Word and PDF at the very least. JSON Resume combined with resume-linkedin seemed like a great fit. Unfortunately, due to recent LinkedIn API changes resume-linkedin was all but useless. My first contribution was born out of the realization that if you could get the LinkedIn data through the API console, the process still worked, albeit extremely cumbersome.
As I worked on migrating this site to my personal fork of a theme in Hexo, I thought a custom JSON Resume theme would also be a good fit. These changes to my resume can be found here or here.
I said in my previous post that a lot can happen in 2 years.
In that time span I've:
Moved to using a MacBook and OSX.
Transitioned away from .NET and don't really miss it. I do randomly play around with .NET core when possible but I haven't actually built anything with it.
Drank the vagrant koolaid via PuPHPet.
I jumped in the deep end with tools like gulp, bower and yeoman.
That's really only scratching the surface. It would've been helpful to have blog posts as I moved along but as with most things, life got in the way.
My main goal for the early part of 2016 is to revamp this site and make it the playground I was looking for in 2013. Octopress is really nice but if I upgrade to v3 it's not much more work to migrating away to something like Hexo, Metalsmith, or DocPad.