It appears to be that the regiond db listener only noticed that the connection was lost at 19:02:30 (almost an hour after failover which happened at ~~18:12:50):
Traceback (most recent call last):
# ... listener.register("sys_stop_import", stop_import)
File "/usr/lib/python3/dist-packages/maasserver/listener.py", line 223, in register
"System channel '%s' has already been registered." % channel) maasserver.listener.PostgresListenerRegistrationError: System channel 'sys_stop_import' has already been registered.
This behavior started at 2019-02-25 19:02:27 when the listener first reported that it has lost the connection to the DB and continues now:
File "/usr/lib/python3/dist-packages/maasserver/listener.py", line 223, in register
"System channel '%s' has already been registered." % channel) maasserver.listener.PostgresListenerRegistrationError: System channel 'sys_stop_import' has already been registered.
Also to #15, #16 and #17:
It appears to be that the regiond db listener only noticed that the connection was lost at 19:02:30 (almost an hour after failover which happened at ~~18:12:50):
https:/ /pastebin. canonical. com/p/g8FDBCtst 5/
2019-02-25 18:02:24 maasserver. listener: [info] Listening for database notifications. listener: [debug] Connection lost. listener: [info] Listening for database notifications. listener: [debug] Connection lost. listener: [debug] Connection lost. listener: [debug] Connection lost. listener: [info] Listening for database notifications. listener: [info] Listening for database notifications. listener: [info] Listening for database notifications. listener: [debug] Connection lost. listener: [info] Listening for database notifications.
2019-02-25 19:02:27 maasserver.
2019-02-25 19:02:30 maasserver.
2019-02-25 20:03:54 maasserver.
2019-02-25 20:03:54 maasserver.
2019-02-25 20:03:54 maasserver.
2019-02-25 20:03:57 maasserver.
2019-02-25 20:03:57 maasserver.
2019-02-25 20:03:57 maasserver.
2019-02-25 20:10:19 maasserver.
2019-02-25 20:10:22 maasserver.
There were some 500 errors returned to client requests (because of the patched code): /pastebin. canonical. com/p/Q47fpgTfk f/
https:/
Then listener reported that it started listening for notifications a couple of times: /pastebin. canonical. com/p/Q47fpgTfk f/
https:/
And also the log gets messages like this periodically:
2019-02-25 21:02:26 maasserver. bootresources: [critical] Importing boot resources failed.
Traceback (most recent call last):
listener. register( "sys_stop_ import" , stop_import) python3/ dist-packages/ maasserver/ listener. py", line 223, in register
maasserver. listener. PostgresListene rRegistrationEr ror: System channel 'sys_stop_import' has already been registered.
# ...
File "/usr/lib/
"System channel '%s' has already been registered." % channel)
This behavior started at 2019-02-25 19:02:27 when the listener first reported that it has lost the connection to the DB and continues now:
https:/ /pastebin. canonical. com/p/KTHVjYGXH g/
The registration error comes from here: https:/ /github. com/maas/ maas/blob/ 2.5.0/src/ maasserver/ listener. py#L209- L223
File "/usr/lib/ python3/ dist-packages/ maasserver/ listener. py", line 223, in register
maasserver. listener. PostgresListene rRegistrationEr ror: System channel 'sys_stop_import' has already been registered.
"System channel '%s' has already been registered." % channel)