search

sensu / uchiwa-chef

Other
33 stars 40 forks source link

Uchiwa is restarted every chef run #22

Closed nickm4062 closed 6 years ago

nickm4062 commented 9 years ago

Currently uchiwa is restarted every chef run

portertech commented 9 years ago

Probably because the JSON isn't sorted https://github.com/sensu/uchiwa-chef/blob/master/recipes/default.rb#L33 Should use the sensu_json_file LWRP https://github.com/sensu/sensu-chef/blob/master/resources/json_file.rb

drpebcak commented 9 years ago

What platform are you seeing this on? This doesn't seem to happen for me in test-kitchen on the repo-centos-56 box.

nickm4062 commented 9 years ago

RHEL65 when using multiple api sources

portertech commented 9 years ago

@amdprophet ping.

amdprophet commented 9 years ago

@nickm4062 I'll have the JSON sorting fix done soon; can you compare last modified dates of the uchiwa config between converges and see if it changes?

drpebcak commented 9 years ago

@nickm4062 ah, I've only got one api source currently.

nickm4062 commented 9 years ago

@amdprophet will let you know shortly

nickm4062 commented 9 years ago

One converge to the next

[root@n7-z01-0a2a0b6b sensu]# stat uchiwa.json File: `uchiwa.json' Size: 563 Blocks: 8 IO Block: 4096 regular file Device: fd00h/64768d Inode: 17758 Links: 1 Access: (0640/-rw-r-----) Uid: ( 497/ uchiwa) Gid: ( 497/ uchiwa) Access: 2015-01-08 11:53:16.434547644 -0800 Modify: 2015-01-08 11:52:03.563547644 -0800 Change: 2015-01-08 11:53:06.477547644 -0800

[root@n7-z01-0a2a0b6b sensu]# stat uchiwa.json File: `uchiwa.json' Size: 563 Blocks: 8 IO Block: 4096 regular file Device: fd00h/64768d Inode: 17758 Links: 1 Access: (0640/-rw-r-----) Uid: ( 497/ uchiwa) Gid: ( 497/ uchiwa) Access: 2015-01-08 11:54:46.715547644 -0800 Modify: 2015-01-08 11:52:03.563547644 -0800 Change: 2015-01-08 11:54:35.654547644 -0800

amdprophet commented 9 years ago

@nickm4062 sorry for the delay - it looks like uchiwa.json is getting changed each run. I've already done some work to fix this and should have it pushed sometime next week.

majormoses commented 6 years ago

Pretty sure this is no longer an issue. Not sure where it got fixed or if there is something we are doing in our wrapper to account for this. Due to the age and lack of reproducibility I think we should close this and let someone open with a new issue (please link it) if we are seeing it.