Server log



  • Just a thought for the future, but it would be useful if the server log included the node name as well as the EUI. When looking at the list in the log I often have to refer back to the resources->nodes page to see what EUI is what node. If the node name were included in the logs it would be more user friendly.



  • @skywatch Can you paste a log message here?



  • @jkandasa Sure! 😉

    2018-12-20 22:16:25,607 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=1, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1545344156804, properties=null)
    2018-12-20 22:16:53,898 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=18, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1545344185613, properties=null)
    2018-12-20 22:17:23,684 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=140, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1545344213903, properties=null)
    2018-12-20 22:18:04,216 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=61, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1545344255846, properties=null)
    2018-12-20 22:18:37,579 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=43, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1545344289352, properties=null)
    2018-12-20 22:35:56,829 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=6, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1545345328558, properties=null)
    2018-12-20 22:36:26,217 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=1, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1545345356837, properties=null)
    2018-12-20 22:36:54,457 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=18, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1545345386225, properties=null)
    2018-12-20 22:37:23,663 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=140, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1545345414463, properties=null)
    

    I do have a few nodes down for work and that is making the nack fail messages longer than usual. But as you can see, only node EUI is showing. No way to know the name of the node without looking it up - It would be more convenient to have it in this message to help track/diagnose an issue.

    Actually, thinking about it, could it be possible to have a toggle in the nodes page somewhere to 'turn off' ack requirement temporarily? That way controller knows not to check for ack from nodeX due to it being turned off. Does that make sense? Or is it a gateway only thing and either on for all or off for all?



  • @skywatch Thank you for the log. This log displayed from the raw message, this message does not contain node name, etc., If we want to display node name, we need to query the database, it may lead slight performance issue in the embedded board.

    Actually, thinking about it, could it be possible to have a toggle in the nodes page somewhere to 'turn off' ack requirement temporarily? That way controller knows not to check for ack from nodeX due to it being turned off. Does that make sense? Or is it a gateway only thing and either on for all or off for all?

    It is a good point. please create GitHub issue to track this feature request.


Log in to reply
 

Suggested Topics

3
Online

475
Users

407
Topics

2.5k
Posts