I thought I have reported this already but can not find it now so I realized it was not reported... cumin-0.1.4195-1.el5 sesame-0.7.3918-6.el5 When I restart sesame* while running cumin, a new instance** is created while the old gets deleted seconds after the original sesame process was shut down by init script. * service sesame restart ** in Administrator -> Inventory -> <hostname> The graph is started over while I would expect to see a gap but then continued graph. This issue is probably connected to unstable IDs, bug 622522
The data continuity problem described above is a current issue, and it's related to but distinct from the problem described in 622522. Note, however, that it's expected that the "sesame record" is deleted. The unexpected part is the loss of the old sesame's historical stats.
This is addressed in change 4255. The issue described in 622522 will mean that sesame's still exhibit the problem. It should work to test instead against a queue or exchange.
Created attachment 443411 [details] Deepest queue listing broken Is this fix connected with the issue on the picture? (All the queues listed there result in APPLICATION ERROR when their links are followed.)
No, those two issues are not connected.
FYI: the deepest queue listing APP ERROR is bug 623162
Verified with cumin-0.1.4297-1.el5 sesame-0.7.4297-1.el5