@girish said in Regular short getaddrinfo EAI_AGAIN outages:
@jrl-abstract27 this is to do with the local DNS server (unbound) not resolving . In Cloudron 8 (the next release), we are removing unbound altogether and it will use your network's resolver via systemd-resolved. Maybe this issues gets sorted out with that.
Hi, i just upgraded to Cloudron 8.0.3, rebooted server and i see Unbound still appears in the services pages, is that normal? does that mean uptime kuma still uses it?
@girish ouch, i still have the EAI_AGAIN error, i suppose i have to check with uptime kuma then. Any suggestion? maybe our datacenter dns is overloaded and we should use google dns or something like that?
@james it doesnt work for me, here is the output
root@b2a9826b-7631-435b-91a0-d0a505476ee9:/app/code# bash /app/data/fix_db.sh
/app/data/fix_db.sh: line 2: $'\r': command not found
=> Checking if DEFAULT_CHARACTER_SET_NAME and DEFAULT_COLLATION_NAME are set to utf8mb4 and utf8mb4_unicode_ci
/app/data/fix_db.sh: line 4: $'\r': command not found
/app/data/fix_db.sh: line 8: $'\r': command not found
/app/data/fix_db.sh: line 22: syntax error near unexpected token `$'in\r''
'app/data/fix_db.sh: line 22: ` case $yn in
root@b2a9826b-7631-435b-91a0-d0a505476ee9:/app/code# /app/pkg/start.sh
=> Exporting env vars expected by Vaultwarden
=> Starting Bitwarden
/--------------------------------------------------------------------\
| Starting Vaultwarden |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the |
| official channels to report bugs/features, regardless of client. |
| Send usage/configuration questions or feature requests to: |
| https://github.com/dani-garcia/vaultwarden/discussions or |
| https://vaultwarden.discourse.group/ |
| Report suspected bugs/issues in the software itself at: |
| https://github.com/dani-garcia/vaultwarden/issues/new |
\--------------------------------------------------------------------/
[INFO] Using saved config from `/app/data/config.json` for configuration.
[2026-01-03 17:24:33.038][panic][ERROR] thread 'main' panicked at 'Error running migrations: QueryError(DieselMigrationName { name: "2024-03-06-170000_add_sso_users", version: MigrationVersion("20240306170000") }, DatabaseError(Unknown, "Referencing column 'user_uuid' and referenced column 'uuid' in foreign key constraint 'sso_users_ibfk_1' are incompatible."))': src/db/mod.rs:505
0: vaultwarden::init_logging::{{closure}}
1: std::panicking::panic_with_hook
2: std::panicking::panic_handler::{{closure}}
3: std::sys::backtrace::__rust_end_short_backtrace
4: __rustc::rust_begin_unwind
5: core::panicking::panic_fmt
6: core::result::unwrap_failed
7: vaultwarden::db::DbPool::from_config
8: vaultwarden::main::{{closure}}
9: vaultwarden::main
10: std::sys::backtrace::__rust_begin_short_backtrace
11: main
12: <unknown>
13: __libc_start_main
14: _start
root@b2a9826b-7631-435b-91a0-d0a505476ee9:/app/code#
PS: i restored to 1.22.2 to get it working for now.
@james hi James, same than @christophermag , copy/paste in Windows 11, applying his sed fix did the trick for me too.
PS: i didn't receive any email notification of the mentions.