why some historian(like sql,mqtt,crate) Falling out????

[vishuPPatel]

Hello ....Volttron Team

Currently we phase this error give me suggestion how to Fix it??

2018-03-05 04:41:16,466 (listeneragent-3.2 12908) listener.agent INFO: Peer: 'pubsub', Sender: 'listeneragent-3.2_1':, Bus: u'', Topic: 'heartbeat/listeneragent-3.2_1', Headers: {'Date': '2018-03-05T04:41:16.463898+00:00', 'max_compatible_version': u'', 'min_compatible_version': '3.0'}, Message: {'status': 'GOOD', 'last_updated': '2018-01-12T19:23:31.485596+00:00', 'context': 'Listener Message'} 2018-03-05 04:41:19,005 (mqtt_historianagent-0.1 14245) volttron.platform.agent.base_historian DEBUG: Queue wait timed out. Falling out. 2018-03-05 04:41:19,005 (mqtt_historianagent-0.1 14245) volttron.platform.agent.base_historian DEBUG: Backing up unpublished values. 2018-03-05 04:41:19,005 (mqtt_historianagent-0.1 14245) volttron.platform.agent.base_historian DEBUG: Getting oldest outstanding to publish. 2018-03-05 04:41:19,005 (mqtt_historianagent-0.1 14245) volttron.platform.agent.base_historian DEBUG: Reading from/waiting for queue. 2018-03-05 04:41:19,171 (sqlhistorianagent-3.6.1 12905) volttron.platform.agent.base_historian DEBUG: Queue wait timed out. Falling out. 2018-03-05 04:41:19,172 (sqlhistorianagent-3.6.1 12905) volttron.platform.agent.base_historian DEBUG: Backing up unpublished values. 2018-03-05 04:41:19,172 (sqlhistorianagent-3.6.1 12905) volttron.platform.agent.base_historian DEBUG: Getting oldest outstanding to publish. 2018-03-05 04:41:19,172 (sqlhistorianagent-3.6.1 12905) volttron.platform.agent.base_historian DEBUG: Reading from/waiting for queue. 2018-03-05 04:41:19,350 (crate_historianagent-1.0.1 23627) volttron.platform.agent.base_historian DEBUG: Queue wait timed out. Falling out. 2018-03-05 04:41:19,351 (crate_historianagent-1.0.1 23627) volttron.platform.agent.base_historian DEBUG: Backing up unpublished values. 2018-03-05 04:41:19,351 (crate_historianagent-1.0.1 23627) volttron.platform.agent.base_historian DEBUG: Getting oldest outstanding to publish. 2018-03-05 04:41:19,351 (crate_historianagent-1.0.1 23627) volttron.platform.agent.base_historian DEBUG: Reading from/waiting for queue. 2018-03-05 04:41:21,463 (listeneragent-3.2 12908) listener.agent INFO: Peer: 'pubsub', Sender: 'listeneragent-3.2_1':, Bus: u'', Topic: 'heartbeat/listeneragent-3.2_1', Headers: {'Date': '2018-03-05T04:41:21.460746+00:00', 'max_compatible_version': u'', 'min_compatible_version': '3.0'}, Message: {'status': 'GOOD', 'last_updated': '2018-01-12T19:23:31.485596+00:00', 'context': 'Listener Message'} 2018-03-05 04:41:26,465 (listeneragent-3.2 12908) listener.agent INFO: Peer: 'pubsub', Sender: 'listeneragent-3.2_1':, Bus: u'', Topic: 'heartbeat/listeneragent-3.2_1', Headers: {'Date': '2018-03-05T04:41:26.463309+00:00', 'max_compatible_version': u'', 'min_compatible_version': '3.0'}, Message: {'status': 'GOOD', 'last_updated': '2018-01-12T19:23:31.485596+00:00', 'context': 'Listener Message'}

That's we are not capturing log into cratedb and mqtt historian & sql historian also not working why this type of error is accrue

Thanks In Advance....!!!!

[kmonson]

This is not an error condition. If no new data comes in for a period of time the historian framework (and thus all historians) will time out waiting on new data from the input queue to check if there is a backlog of data that needs to be caught up on. It isn't always needed (as you can see) and the timeout does not take into account if there was any backlogged data. It does it whether it needs to or not.

If your driver is not publishing very often or you are capturing only other types of messages that are sporadic you can reduce or eliminate the frequency of these messages by setting the retry_period value in your historian's configuration to a higher value. See http://volttron.readthedocs.io/en/develop/core_services/historians/index.html

[vishuPPatel]

Here my all drive stop get the data in log in to own storage, @kmonson this problem i face first time i don't how to fix it??

Can you Give me the simple and best trick to fix it!!!!......

Thanks In Advance.....!!!!1

[kmonson]

The problem is not the historian as far as I can tell. It looks like there isn't anything publishing data to topics that the historians are listening on. Are you sure the agents that should be publishing are running/working? Is the Master Driver agent running?

[vishuPPatel]

we are capture to other server(In installed master drive ) data in volttron centere server but our lot of data tracking without master drive in volttron centre dataloger data store in database but suddenly our data store in database is store what's problem of these historian problem ??

Can you guide me how to debug why these historian not working??

Thanks!!!

[jhaack]

Can you email us volttron@pnnl.gov? Let's try to get on a call to get more information.