MAAS

[2.4] 2018-04-24 17:49:06 maasserver.dhcp: [critical] None (UNABLE TO OBTAIN TRACEBACK FROM EVENT)

Bug #1766671 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Critical
Unassigned
MAAS 2.4.0rc2

Bug Description

Quite a few seconds after a restart, I see the following:

This only shows the regiond.log even though I'm tailing both, rackd.log and regiond.log.

2018-04-24 17:48:57 regiond: [info] 192.168.1.73 POST /ping HTTP/1.1 --> 404 NOT_FOUND (referrer: -; agent: PycURL/7.43.0.1 libcurl/7.58.0 GnuTLS/3.5.18 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3)
2018-04-24 17:48:57 regiond: [info] 10.90.90.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2018-04-24 17:49:05 maasserver.dhcp: [critical] None
        (UNABLE TO OBTAIN TRACEBACK FROM EVENT)

2018-04-24 17:49:06 maasserver.dhcp: [critical] None
        (UNABLE TO OBTAIN TRACEBACK FROM EVENT)

2018-04-24 17:49:18 -: [info] b'/etc/resolv.conf' changed, reparsing
2018-04-24 17:49:18 -: [info] Resolver added ('127.0.0.53', 53) to server list
2018-04-24 17:49:27 regiond: [info] 192.168.1.73 POST /ping HTTP/1.1 --> 404 NOT_FOUND (referrer: -; agent: PycURL/7.43.0.1 libcurl/7.58.0 GnuTLS/3.5.18 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3)
2018-04-24 17:49:27 regiond: [info] 10.90.90.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2018-04-24 17:49:35 maasserver.dhcp: [critical] None
        (UNABLE TO OBTAIN TRACEBACK FROM EVENT)

2018-04-24 17:49:36 maasserver.dhcp: [critical] None
        (UNABLE TO OBTAIN TRACEBACK FROM EVENT)

2018-04-24 17:49:57 regiond: [info] 192.168.1.73 POST /ping HTTP/1.1 --> 404 NOT_FOUND (referrer: -; agent: PycURL/7.43.0.1 libcurl/7.58.0 GnuTLS/3.5.18 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3)
2018-04-24 17:49:57 regiond: [info] 10.90.90.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)

Revision history for this message
Andres Rodriguez (andreserl) wrote :

ubuntu@maas00:~$ tail -f /var/log/maas/regiond.log /var/log/maas/rackd.log
==> /var/log/maas/regiond.log <==

2018-04-24 17:49:36 maasserver.dhcp: [critical] None
        (UNABLE TO OBTAIN TRACEBACK FROM EVENT)

2018-04-24 17:49:57 regiond: [info] 192.168.1.73 POST /ping HTTP/1.1 --> 404 NOT_FOUND (referrer: -; agent: PycURL/7.43.0.1 libcurl/7.58.0 GnuTLS/3.5.18 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3)
2018-04-24 17:49:57 regiond: [info] 10.90.90.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2018-04-24 17:50:27 regiond: [info] 192.168.1.73 POST /ping HTTP/1.1 --> 404 NOT_FOUND (referrer: -; agent: PycURL/7.43.0.1 libcurl/7.58.0 GnuTLS/3.5.18 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3)
2018-04-24 17:50:27 regiond: [info] 10.90.90.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2018-04-24 17:50:57 regiond: [info] 192.168.1.73 POST /ping HTTP/1.1 --> 404 NOT_FOUND (referrer: -; agent: PycURL/7.43.0.1 libcurl/7.58.0 GnuTLS/3.5.18 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3)
2018-04-24 17:50:57 regiond: [info] 10.90.90.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)

==> /var/log/maas/rackd.log <==
2018-04-24 17:48:34 Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(TCP, '::ffff:192.168.100.1', 38100) PEER:IPv6Address(TCP, '::ffff:192.168.100.1', 5252))
2018-04-24 17:48:34 provisioningserver.rpc.clusterservice: [info] Event-loop 'maas00:pid=12057' authenticated.
2018-04-24 17:48:34 provisioningserver.rpc.clusterservice: [info] Event-loop 'maas00:pid=12052' authenticated.
2018-04-24 17:48:35 provisioningserver.rpc.clusterservice: [info] Event-loop 'maas00:pid=12053' authenticated.
2018-04-24 17:48:35 provisioningserver.rpc.clusterservice: [info] Event-loop 'maas00:pid=12056' authenticated.
2018-04-24 17:48:35 provisioningserver.rpc.clusterservice: [info] Rack controller 'w8epds' registered (via maas00:pid=12052) with MAAS version 2.4.0~beta3-6892-gd6fef78f1-0ubuntu1~18.04.1.
2018-04-24 17:48:35 provisioningserver.rpc.clusterservice: [info] Rack controller 'w8epds' registered (via maas00:pid=12057) with MAAS version 2.4.0~beta3-6892-gd6fef78f1-0ubuntu1~18.04.1.
2018-04-24 17:48:35 provisioningserver.rpc.clusterservice: [info] Fully connected to all 4 event-loops on all 1 region controllers (maas00).
2018-04-24 17:48:36 provisioningserver.rpc.clusterservice: [info] Rack controller 'w8epds' registered (via maas00:pid=12053) with MAAS version 2.4.0~beta3-6892-gd6fef78f1-0ubuntu1~18.04.1.
2018-04-24 17:48:36 provisioningserver.rpc.clusterservice: [info] Rack controller 'w8epds' registered (via maas00:pid=12056) with MAAS version 2.4.0~beta3-6892-gd6fef78f1-0ubuntu1~18.04.1.

Changed in maas:
milestone: none → 2.4.0rc1
importance: Undecided → High
status: New → Triaged
Andres Rodriguez (andreserl)
Changed in maas:
importance: High → Critical
assignee: nobody → Blake Rouse (blake-rouse)
Revision history for this message
Andres Rodriguez (andreserl) wrote :

After the recent fixes and such, I've not seen this issue anymore. I might as well be related to: LP: #1768575

Changed in maas:
status: Triaged → Incomplete
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 2.4.0rc1 → 2.4.0rc2
Andres Rodriguez (andreserl)
Changed in maas:
status: Incomplete → Invalid
assignee: Blake Rouse (blake-rouse) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.