A Holt

icon indicating a website link https://internet-in-a-box.org

icon company Unleash Kids! icon location I work with contributors and educators of all kind to make Internet-in-a-Box (formerly http://schoolserver.org) happen around the globe!

Results 1003 comments of A Holt

http://box/radio or http://box/azuracast alongside http://box:12080 [or whatever new port is chosen, was 10080 !]

See @rickgurmet's screenshot and @jvonau's explanation — showing why port 10080 will need to be changed: - https://github.com/iiab/iiab/issues/2991#issuecomment-1215245383 If this hopefully works out in coming weeks, then a shorter URL...

http://box/radio or http://box/azuracast alongside http://box:12080 [or whatever new port is chosen, was 10080 !]

Progress 4 days ago: - #3374 (But this might be too much work, as details are likely buried within AzuraCast's Docker container!) Related: - PR #2946

DB warnings recently began appearing during IIAB install: "did not set no_log for no_password_changes" [caused by Ansible 2.9.6?]

Another example warning...that we never used to see: (until Ansible 2.9.6?) > TASK [mediawiki : Create MySQL database user iiab_mediawiki_user with password, and permissions to above db] *** [WARNING]: Module...

DB warnings recently began appearing during IIAB install: "did not set no_log for no_password_changes" [caused by Ansible 2.9.6?]

> OS and ansible version would be useful - Raspbian Lite 2020-02-13 (with all apt updates applied) - Ansible 2.9.6

DB warnings recently began appearing during IIAB install: "did not set no_log for no_password_changes" [caused by Ansible 2.9.6?]

Does anyone know...if these DB warnings went away...now that IIAB's install uses Ansible 2.9.7? Ref: #2340 Recommend Ansible 2.9.7+, Mandate Ansible 2.8.11+

DB warnings recently began appearing during IIAB install: "did not set no_log for no_password_changes" [caused by Ansible 2.9.6?]

> Does anyone know...if these DB warnings went away...now that IIAB's install uses Ansible 2.9.7? No such luck! FYI these pink warnings continue ("Module did not set no_log for no_password_changes")...

DB warnings recently began appearing during IIAB install: "did not set no_log for no_password_changes" [caused by Ansible 2.9.6?]

Not the same issue...but this is reminiscent of a "wontfix" tkt here: (originally from 2019-06-01) #1714 "MySQL database password-changing failure during fresh install of IIAB [using "sudo iiab"] on Ubuntu...

DB warnings recently began appearing during IIAB install: "did not set no_log for no_password_changes" [caused by Ansible 2.9.6?]

Is this still an issue? Or can it be closed?

DB warnings recently began appearing during IIAB install: "did not set no_log for no_password_changes" [caused by Ansible 2.9.6?]

@jvonau summarizes on our weekly IIAB call: a boolean flag could be passed to Ansible to suppress this warning.

Multipass can't delete LXD instances that go into Error state

> Hi @aatrcoutinho, until we get this fixed, you can delete instances in LXD directly: `lxc delete --project=multipass` Lifesaver !! This worked for me too: ``` lxc delete deb12 --project=multipass...