pserv.log full of "Duplicate ACK for blocknum" errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Low
|
Unassigned | ||
python-tx-tftp |
New
|
Undecided
|
Unassigned |
Bug Description
This has been going on for almost an hour:
2014-12-12 22:51:08+0000 [RemoteOriginRe
2014-12-12 22:51:08+0000 [RemoteOriginRe
2014-12-12 22:51:08+0000 [RemoteOriginRe
2014-12-12 22:51:08+0000 [RemoteOriginRe
2014-12-12 22:51:08+0000 [RemoteOriginRe
2014-12-12 22:51:08+0000 [RemoteOriginRe
2014-12-12 22:51:08+0000 [RemoteOriginRe
2014-12-12 22:51:08+0000 [RemoteOriginRe
2014-12-12 22:51:08+0000 [RemoteOriginRe
...
2014-12-12 23:45:33+0000 [RemoteOriginRe
2014-12-12 23:45:33+0000 [RemoteOriginRe
2014-12-12 23:45:33+0000 [RemoteOriginRe
2014-12-12 23:45:33+0000 [RemoteOriginRe
I'm having nodes fail to commission, timing out, while this is happening.
maas 1.7.1~rc1+bzr3313-0
tags: | added: oil |
Changed in maas: | |
milestone: | none → next |
Changed in maas: | |
status: | New → Triaged |
Changed in maas: | |
status: | Triaged → New |
Changed in maas: | |
status: | Incomplete → Triaged |
importance: | Undecided → Low |
Changed in maas: | |
milestone: | next → none |
I noticed this system was a ppc64el system, based on the initrd/kernel file it retrieved, and that its MAC address (6c:ae:8b:6a:93:c3) didn't show up for any systems enlisted in MAAS.