After power failure problem

[Saentist]

Problem/Motivation

(Why the issue was filed)

After latest OS (ova) update there is a problems after power failure,
it do not start correct

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: phpMyAdmin
 A web interface for the official MariaDB add-on
-----------------------------------------------------------
 Add-on version: 0.8.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 8.2  (amd64 / qemux86-64)
 Home Assistant Core: 2022.6.7
 Home Assistant Supervisor: 2022.05.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/phpmyadmin.sh
[11:20:21] ERROR: Got unexpected response from the API: Service not enabled
cont-init: info: /etc/cont-init.d/phpmyadmin.sh exited 139
cont-init: warning: some scripts exited nonzero
s6-rc: warning: unable to start service legacy-cont-init: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

[sinclairpaul]

Please check the MariaDB addon is running, the logs would suggest it isn't.

[Saentist]

It was running without any errors
but somehow inexpected shutdown of system make this
and need to return to old snapshot and loose statistics data.

Other interesting thing is that "recoreder" stay unacessable state when this happens.

[FritsOV]

MariaDb has to be installed and is running...

[Nikitian]

Have same problem. MariaDB is running and HA works with maria

-----------------------------------------------------------
 Add-on: phpMyAdmin
 A web interface for the official MariaDB add-on
-----------------------------------------------------------
 Add-on version: 0.8.1
 You are running the latest version of this add-on.
 System: Raspbian GNU/Linux 10 (buster)  (armv7 / raspberrypi4)
 Home Assistant Core: 2022.8.7
 Home Assistant Supervisor: 2022.08.6
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
Log level is set to DEBUG
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/phpmyadmin.sh
[10:46:40] DEBUG: Requested API resource: http://supervisor/services/mysql
[10:46:40] DEBUG: Request method: GET
[10:46:40] DEBUG: Request data: {}
[10:46:40] DEBUG: API HTTP Response code: 400
[10:46:40] DEBUG: API Response: {"result": "error", "message": "Service not enabled"}
[10:46:40] ERROR: Got unexpected response from the API: Service not enabled
cont-init: info: /etc/cont-init.d/phpmyadmin.sh exited 139
cont-init: warning: some scripts exited nonzero
s6-rc: warning: unable to start service legacy-cont-init: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
prog: fatal: stopping the container.

[RaphDaMan]

I do have the same issue. MariaDB is running, recorder is working...

phpMyAdmin protocol

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: phpMyAdmin
 A web interface for the official MariaDB add-on
-----------------------------------------------------------
 Add-on version: 0.8.1
 You are running the latest version of this add-on.
 System: Ubuntu 20.04.5 LTS  (amd64 / qemux86-64)
 Home Assistant Core: 2022.9.6
 Home Assistant Supervisor: 2022.09.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
Log level is set to INFO
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/phpmyadmin.sh
[15:27:14] ERROR: Got unexpected response from the API: Service not enabled
cont-init: info: /etc/cont-init.d/phpmyadmin.sh exited 139
cont-init: warning: some scripts exited nonzero
s6-rc: warning: unable to start service legacy-cont-init: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
prog: fatal: stopping the container.
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

MariaDB protocol

mysql.innodb_index_stats                           OK
mysql.innodb_table_stats                           OK
mysql.plugin                                       OK
mysql.proc                                         OK
mysql.procs_priv                                   OK
mysql.proxies_priv                                 OK
mysql.roles_mapping                                OK
mysql.servers                                      OK
mysql.table_stats                                  OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                               OK
mysql.time_zone_transition                         OK
mysql.time_zone_transition_type                    OK
mysql.transaction_registry                         OK
homeassistant.event_data                           OK
homeassistant.events                               OK
homeassistant.recorder_runs                        OK
homeassistant.schema_changes                       OK
homeassistant.state_attributes                     OK
homeassistant.states                               OK
homeassistant.statistics                           OK
homeassistant.statistics_meta                      OK
homeassistant.statistics_runs                      OK
homeassistant.statistics_short_term                OK
phpmyadmin.pma__bookmark                           OK
phpmyadmin.pma__central_columns                    OK
phpmyadmin.pma__column_info                        OK
phpmyadmin.pma__designer_settings                  OK
phpmyadmin.pma__export_templates                   OK
phpmyadmin.pma__favorite                           OK
phpmyadmin.pma__history                            OK
phpmyadmin.pma__navigationhiding                   OK
phpmyadmin.pma__pdf_pages                          OK
phpmyadmin.pma__recent                             OK
phpmyadmin.pma__relation                           OK
phpmyadmin.pma__savedsearches                      OK
phpmyadmin.pma__table_coords                       OK
phpmyadmin.pma__table_info                         OK
phpmyadmin.pma__table_uiprefs                      OK
phpmyadmin.pma__tracking                           OK
phpmyadmin.pma__userconfig                         OK
phpmyadmin.pma__usergroups                         OK
phpmyadmin.pma__users                              OK
sys.sys_config                                     OK
traccar.DATABASECHANGELOG                          OK
traccar.DATABASECHANGELOGLOCK                      OK
traccar.tc_attributes                              OK
traccar.tc_calendars                               OK
traccar.tc_commands                                OK
traccar.tc_device_attribute                        OK
traccar.tc_device_command                          OK
traccar.tc_device_driver                           OK
traccar.tc_device_geofence                         OK
traccar.tc_device_maintenance                      OK
traccar.tc_device_notification                     OK
traccar.tc_device_order                            OK
traccar.tc_devices                                 OK
traccar.tc_drivers                                 OK
traccar.tc_events                                  OK
traccar.tc_geofences                               OK
traccar.tc_group_attribute                         OK
traccar.tc_group_command                           OK
traccar.tc_group_driver                            OK
traccar.tc_group_geofence                          OK
traccar.tc_group_maintenance                       OK
traccar.tc_group_notification                      OK
traccar.tc_group_order                             OK
traccar.tc_groups                                  OK
traccar.tc_maintenances                            OK
traccar.tc_notifications                           OK
traccar.tc_orders                                  OK
traccar.tc_positions                               OK
traccar.tc_servers                                 OK
traccar.tc_statistics                              OK
traccar.tc_user_attribute                          OK
traccar.tc_user_calendar                           OK
traccar.tc_user_command                            OK
traccar.tc_user_device                             OK
traccar.tc_user_driver                             OK
traccar.tc_user_geofence                           OK
traccar.tc_user_group                              OK
traccar.tc_user_maintenance                        OK
traccar.tc_user_notification                       OK
traccar.tc_user_order                              OK
traccar.tc_user_user                               OK
traccar.tc_users                                   OK
[16:19:03] INFO: Ensuring internal database upgrades are performed
[16:19:03] INFO: Ensure databases exists
parse error: Expected string key before ':' at line 1, column 4
[16:19:03] ERROR: Unknown HTTP error occured
[16:19:03] INFO: Create database null
[16:19:03] INFO: Ensure users exists and are updated
jq: error (at <stdin>:1): null (null) has no keys
[16:19:04] INFO: Init/Update rights
jq: error (at <stdin>:1): null (null) has no keys
parse error: Expected string key before ':' at line 1, column 4
[16:19:04] ERROR: Unknown HTTP error occured
[16:19:04] INFO: Successfully send service information to Home Assistant.

[tjorim]

Do any of you happen to have the watchdog enabled on the mariadb add-on?

[RaphDaMan]

Do any of you happen to have the watchdog enabled on the mariadb add-on?

Yep, the watchdog for mariadb is enabled on my installation. Do you think it's a blocker?

[tjorim]

Yes, there are some known issues with that. For example the NPM add-on. Try to disable any watchdogs and try again.

[patman15]

Yes, there are some known issues with that. For example the NPM add-on. Try to disable any watchdogs and try again.

I had the same issue and after disabling the watchdog on the mariadb add-on and restarting (mariadb) the phpmyadmin finally works. Probably this should be added to the documentation?

[tjorim]

Should be fixed for some time already (in home-assistant/supervisor#3815). I am unable to reproduce this myself at the moment.
Unfortunately, both Nikitian and RaphDaMan are running unsupported systems (Raspbian GNU/Linux 10 (buster) and Ubuntu 20.04.5 LTS respectively).
@patman15 What setup are you using? If it is still an issue please report it here: https://github.com/home-assistant/supervisor. (you can reference to hassio-addons/addon-nginx-proxy-manager#344 as well)

[RaphDaMan]

I disabled the watchdog on all add-ons installed and used (Home Panel, MaridDB, Studio Coder Server, TasmoAdmin and Traccar), restarted complete HA environment, restarted MariaDB individually and phpMyAdmin is again exiting/stopping with error...

[RaphDaMan]

Got it solved!

After review my MariaDB settings and looking at the "hidden" network port I changed to 3307 (MariaDB usual as 3306 is for MySQL). Now phpMyAdmin is working fine again!

Many thanks to you all for your support and ideas!
Great community!

[patman15]

@patman15 What setup are you using? If it is still an issue please report it here: https://github.com/home-assistant/supervisor. (you can reference to hassio-addons/addon-nginx-proxy-manager#344 as well)

@tjorim it's an (almost) up-to-date HassOS installation in a virtual machine:
Home Assistant 2022.9.5 Supervisor 2022.09.1 Operating System 9.0 Frontend 20220907.2 - latest
MariaDB 2.5.1, phpMyAdmin 0.8.1

I just tried to get back to my original failure, but now I cannot reproduce anymore, even with watchdog enabled. I'm 100% sure that only watchdog disabling and rebooting helped. Strange.