Open Thatoo opened 5 months ago
juil. 01 02:01:16 systemd[1]: Started Matrix Signal Bridge.
juil. 01 02:01:17 mautrix-signal[486]: 2024-07-01T02:01:17+02:00 INF Initializing bridge built_at="Jun 16 2024, 21:03:57" go_version=go1.22.4 name=mautrix-signal version=0.6.2
juil. 01 02:01:17 mautrix-signal[486]: 2024-07-01T02:01:17+02:00 INF Initializing libsignal version:0.51.0 component=libsignal file=rust/bridge/ffi/src/logging.rs line=106 target=signal_ffi::logging
juil. 01 02:01:17 mautrix-signal[486]: 2024-07-01T02:01:17+02:00 INF Bridge initialization complete, starting...
juil. 01 02:01:17 mautrix-signal[486]: panic: failed to check if table exists: dial tcp [::1]:5432: connect: connection refused
juil. 01 02:01:17 mautrix-signal[486]: goroutine 1 [running]:
juil. 01 02:01:17 mautrix-signal[486]: go.mau.fi/util/dbutil.(*Database).tableExistsNoError(0x10?, {0x1c2c118?, 0xc0003a8d20?}, {0x1a72599?, 0x539d0a?})
juil. 01 02:01:17 mautrix-signal[486]: /builds/mautrix/signal/.cache/pkg/mod/go.mau.fi/util@v0.5.0/dbutil/upgrades.go:108 +0x73
juil. 01 02:01:17 mautrix-signal[486]: go.mau.fi/util/dbutil.(*Database).checkDatabaseOwner(0xc0000de090, {0x1c2c118, 0xc0003a8d20})
juil. 01 02:01:17 mautrix-signal[486]: /builds/mautrix/signal/.cache/pkg/mod/go.mau.fi/util@v0.5.0/dbutil/upgrades.go:123 +0x8a
juil. 01 02:01:17 mautrix-signal[486]: go.mau.fi/util/dbutil.(*Database).Upgrade(0xc0000de090, {0x1c2c118, 0xc0003a8d20})
juil. 01 02:01:17 mautrix-signal[486]: /builds/mautrix/signal/.cache/pkg/mod/go.mau.fi/util@v0.5.0/dbutil/upgrades.go:157 +0x3a
juil. 01 02:01:17 mautrix-signal[486]: maunium.net/go/mautrix/bridge.(*Bridge).start(0xc0003a0508)
juil. 01 02:01:17 mautrix-signal[486]: /builds/mautrix/signal/.cache/pkg/mod/maunium.net/go/mautrix@v0.19.0-beta.1/bridge/bridge.go:718 +0x2a8
juil. 01 02:01:17 mautrix-signal[486]: maunium.net/go/mautrix/bridge.(*Bridge).Main(0xc0003a0508)
juil. 01 02:01:17 mautrix-signal[486]: /builds/mautrix/signal/.cache/pkg/mod/maunium.net/go/mautrix@v0.19.0-beta.1/bridge/bridge.go:908 +0x614
juil. 01 02:01:17 mautrix-signal[486]: main.main()
juil. 01 02:01:17 mautrix-signal[486]: /builds/mautrix/signal/main.go:351 +0x2a5
juil. 01 02:01:17 systemd[1]: mautrix_signal.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
juil. 01 02:01:17 systemd[1]: mautrix_signal.service: Failed with result 'exit-code'.
What could be this INVALIDARGUMENT
?
Here is what I have set in /opt/yunohost/mautrix_signal/config.yaml
permissions:
'*': relay
'domain.tld': user
'@administrator:domain.tld': admin
But it can't be a config.yaml error, otherwise it would not start at all, not even manually.
Any idea what it could be and how to solve this issue?
Well actually the issue seems more related to
juin 24 02:01:17 mautrix-signal[523]: panic: failed to check if table exists: dial tcp [::1]:5432: connect: connection refused
than INVALIDARGUMENT
.
Maybe setting a delay after boot, could solve this issue, couldn't it?
I wanted to make a PR but Im afraid I merged it or I don't get how to make the PR from my commit https://github.com/YunoHost-Apps/mautrix_signal_ynh/commit/193b702d2f4a3456f30871a58195830dd81de164
Describe the bug
When the server restart, mautrix-signal fails to start but afterwards, I can start it manually.
Context
Steps to reproduce
Expected behavior
Mautrix signal should start automatically after the server boot.
Logs