-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MySQL database password-changing failure during fresh install of IIAB [using "sudo iiab"] on Ubuntu 19.04 [and now 18.04 too...whereas 19.10 & Debian 10.x work!] -- Ansible Python 3 needs python3-distutils #1714
Comments
@jvonau recommended Step 5 of https://vitux.com/how-to-install-and-configure-mysql-in-ubuntu-18-04-lts/ to try to diagnose this...
As compared to Ubuntu 18.04 where the output looks more promising...
@jvonau suggests:
@holta asked:
|
@m-anish appears to be having much the same issue on Ubuntu 18.04.2 Two possible solutions are outlined herein: Summary:
|
or simply sudo mysql -u root works for me on 18.04.2 as iiab-admin |
in general I prefer the approach we are taking for apps such as nextcloud, wp where we create a user in ansible, create an empty db in ansible, and give that user all rights on the db. |
@jvonau suggests @tim-moody's above suggestions might be insufficient with Ansible: perhaps instead user iiab-admin (or user pi?) might need to be added to a db group to solve this? @georgejhunt: should we use Ansible's |
Back-ref: Outstanding IIAB issues (network & Node-RED) on Ubuntu Server 19.04 [released 2019-04-18] |
Does this have anything to do with? #1833 Lost connection to MySQL server at 'sending authentication information', system error: 32 "Broken pipe" |
Surprisingly http://download.iiab.io installed Stages 0-to-5 onto Ubuntu Server 19.10 Final Freeze (BIG-sized IIAB) without problems! So I'm closing this tkt, as Ubuntu 19.04 support is not required or even desired. (But do re-open if/as nec.) |
Fresh install of IIAB 7.1/master (http://download.iiab.io) on Ubuntu 19.10 failed as follows:
FYI the rrror went away when I re-ran 'sudo iiab' -- whereas last week it succeeded on the very 1st pass. |
@jvonau believes Ansible's Python 3 warnings on Ubuntu 19.10 may be related...pasting in from https://paste.ubuntu.com/p/TTRh4xQvJK/ :
Ref: |
@jvonau helped me confirm that "apt install python3-distutils" (on a clean Ubuntu 19.10 system) make the above ~10 warnings go away. |
Likewise running
|
@jvonau suggests the following might be the underlying cause? ansible/ansible#47736 "mysql_user broken in [Ansible] 2.7.1 when using /root/.my.cnf" |
@jvonau should we close this now? (Or better to leave it open as a reference until upstream/all associated issues are more fully resolved?) |
I am getting a similar error: TASK [mysql : Update MySQL root password for localhost root accounts, if mysql_enabled] *** Environment: Have tried sudio iiab a few times Other points:
I thought I would pause at this point in case it is helpful to provide debugging - before I start trying to find a workaround myself. Is this an open issue? Any suggestions? |
The work around noted is it run 'iiab' as root and not to use sudo: hope it helps. |
Thank you @jvonau that solved the problem easily. Any idea how long before that work-around is addressed in the main ansible install script? |
on 18.04 vm, newly upgraded I hit (running iiab-install as root) using #2042 TASK [mysql : Update MySQL root password for localhost root accounts, if mysql_enabled] ****************************************************************************************************** I have never seen this before. |
Previous run I did not upgrade. |
|
reran scripts/ansible |
TK Kang is also suffering thru this regression, when trying to install IIAB 7.1 pre-release (master) on Ubuntu 18.04 Desktop. (If we do not find a solution, this will be documented as a "Known Issue" with the upcoming IIAB 7.1) |
This is appearing more likely, towards releasing IIAB 7.1 on/around 2020-01-30. |
Now that IIAB 7.1 pre-releases are installing very cleanly onto Ubuntu 20.04 LTS pre-releases, this has become less of an issue — and it should become even less of an issue on 2020-04-23 when Ubuntu 20.04 LTS is officially released — whereupon we can de-support legacy OS Ubuntu 18.04. |
I'm declaring this "wontfix" as (1) we transition from Ubuntu 18.04 LTS to 20.04 LTS (2) those who insist on using 18.04 have been warned @ https://github.com/iiab/iiab/wiki/IIAB-7.1-Release-Notes#known-issues |
Just fyi IIAB no longer supports Ubuntu 18.04 as a mainline OS, now that Ubuntu 20.04 has been released. Apologies! For more details, please see: https://github.com/iiab/iiab/wiki/IIAB-Platforms |
@tim-moody @georgejhunt this is the error I got the 1st time running a fresh install of "sudo iiab" on Ubuntu Server 19.04 VM @ 10.8.0.38:
This is the error I got the 2nd time I ran "sudo iiab" :
FWIW the above-mentioned file /home/iiab-admin/.my.cnf does not exist (certainly at this point).
During the 3rd run of "sudo iiab" the error seems to have gone away, presumably as a result of me running
sudo su -
to change from user iiab-admin to root?Is installing IIAB when logged in as a non-root user something we can hopefully fix? (Reason: instructions tell implementers to install IIAB using
curl <script> | sudo bash
which has worked extremely well over the past ~2 years, opening doors for less-technical and more security-conscious implementers.)The text was updated successfully, but these errors were encountered: