1.8beta3: clusterd.log starts off with about 34MB of 0's

[Jason Hobbs]

My clusterd.log starts off with about 34MB of 0's:

jason@inire:~/logs_for_open_files$ hexdump clusterd.log | head -n 10
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
20855f0 0000 0000 0000 0000 0000 0000 3200 3130
2085600 2d35 3430 322d 2030 3630 323a 3a39 3932
2085610 302b 3030 2030 545b 5446 2050 5528 5044
2085620 5d29 4420 7461 6761 6172 206d 6572 6563
2085630 7669 6465 6620 6f72 206d 2728 3031 322e
2085640 3534 302e 312e 3635 2c27 3220 3730 2930
2085650 203a 523c 5152 6144 6174 7267 6d61 6628
2085660 6c69 6e65 6d61 3d65 7870 6c65 6e69 7875

[Larry Michel (lmic)]

Still seeing this with 1.8.0~beta6+bzr3899-0ubuntu1~trusty1

$ hexdump clusterd.log | head -n 10
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0a7f8f0 0000 0000 0000 3032 3531 302d 2d35 3731
0a7f900 3020 3a36 3832 353a 2b38 3030 3030 5b20
0a7f910 5d2d 5420 6d69 6465 6420 7275 6e69 2067
0a7f920 706f 6974 6e6f 6e20 6765 746f 6169 6974
0a7f930 6e6f 7020 6f72 6563 7373 320a 3130 2d35
0a7f940 3530 312d 2037 3630 323a 3a38 3835 302b
0a7f950 3030 2030 2d5b 205d 5528 5044 5020 726f
0a7f960 2074 3034 3338 2033 6c43 736f 6465 0a29

[Andres Rodriguez (andreserl)]

Larry, has the log been rotated and created *after* the upgrade to beta6?

[Ricardo Bánffy (rbanffy)]

Couldn't reproduce it here from a fresh install from trunk.

ricardo@maas-test:~/build-area$ hexdump -C /var/log/maas/clusterd.log | head -n 10
00000000 32 30 31 35 2d 30 35 2d 31 39 20 31 33 3a 35 31 |2015-05-19 13:51|
00000010 3a 31 36 2d 30 34 30 30 20 5b 2d 5d 20 4c 6f 67 |:16-0400 [-] Log|
00000020 20 6f 70 65 6e 65 64 2e 0a 32 30 31 35 2d 30 35 | opened..2015-05|
00000030 2d 31 39 20 31 33 3a 35 31 3a 31 36 2d 30 34 30 |-19 13:51:16-040|
00000040 30 20 5b 2d 5d 20 74 77 69 73 74 64 20 31 33 2e |0 [-] twistd 13.|
00000050 32 2e 30 20 28 2f 75 73 72 2f 62 69 6e 2f 70 79 |2.0 (/usr/bin/py|
00000060 74 68 6f 6e 20 32 2e 37 2e 36 29 20 73 74 61 72 |thon 2.7.6) star|
00000070 74 69 6e 67 20 75 70 2e 0a 32 30 31 35 2d 30 35 |ting up..2015-05|
00000080 2d 31 39 20 31 33 3a 35 31 3a 31 36 2d 30 34 30 |-19 13:51:16-040|
00000090 30 20 5b 2d 5d 20 72 65 61 63 74 6f 72 20 63 6c |0 [-] reactor cl|

after stopping, deleting the file and restarting,

00000000 32 30 31 35 2d 30 35 2d 31 39 20 31 34 3a 31 32 |2015-05-19 14:12|
00000010 3a 33 36 2d 30 34 30 30 20 5b 2d 5d 20 4c 6f 67 |:36-0400 [-] Log|
00000020 20 6f 70 65 6e 65 64 2e 0a 32 30 31 35 2d 30 35 | opened..2015-05|
00000030 2d 31 39 20 31 34 3a 31 32 3a 33 36 2d 30 34 30 |-19 14:12:36-040|
00000040 30 20 5b 2d 5d 20 74 77 69 73 74 64 20 31 33 2e |0 [-] twistd 13.|
00000050 32 2e 30 20 28 2f 75 73 72 2f 62 69 6e 2f 70 79 |2.0 (/usr/bin/py|
00000060 74 68 6f 6e 20 32 2e 37 2e 36 29 20 73 74 61 72 |thon 2.7.6) star|
00000070 74 69 6e 67 20 75 70 2e 0a 32 30 31 35 2d 30 35 |ting up..2015-05|
00000080 2d 31 39 20 31 34 3a 31 32 3a 33 36 2d 30 34 30 |-19 14:12:36-040|
00000090 30 20 5b 2d 5d 20 72 65 61 63 74 6f 72 20 63 6c |0 [-] reactor cl|

Forcing logrotate failed with a permission error, but that'll be another bug. I'll try to fix it and see if the NULs appear after a rotation.

[Ricardo Bánffy (rbanffy)]

I was unable to reproduce the issue from either a fresh install from source or from ppa:maas-maintainers/experimental.

[Ricardo Bánffy (rbanffy)]

Clarifying: installing on a fresh install of Trusty, from latest sources and the packages listed on http://paste.ubuntu.com/11249525/

[Raphaël Badin (rvb)]

The logs attached to bug 1449402 and bug 1466979, are proof that this is bug is still present.

[Blake Rouse (blake-rouse)]

This has not shown up in a while so I am going to mark it as incomplete. Please mark it as new if it occurs again.

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]