Reply
Highlighted
New Member
Posts: 2
Registered: ‎10-18-2016

ToughSwitch Failure (mod_ping_stats_on_io: command failed (1))

Hello Guys,

 

I noticed my ToughSwitch Pro timing out along with two connected devices - NSM5 but the 3rd device (RocketM5) wasn't timing out. Rocket M5 is the last mile (backhaul) to the location, whilst the NSM5 are used as the access points, all connected to thesame TS Pro, which has been upgraded to V1.4.1, been EdgeSwitch now.

 

Checking the log of the TS after it came back, below error message displayed thrice.

 

mod_ping_stats_on_io: command failed (1)

 

What could have caused the TS to time out with the backhaul stable and responding fine?

 

Feedbacks will be appreciated.

 

Thanks

Regular Member
Posts: 544
Registered: ‎01-14-2015
Kudos: 414
Solutions: 54

Re: ToughSwitch Failure (mod_ping_stats_on_io: command failed (1))

[ Edited ]

Hello @nikpefan

 

Welcome to the UBNT community.

Do you have your devices connected to UNMS?
This logs appears to be related to UNMS.

https://community.ubnt.com/t5/UNMS-Beta/mod-ping-stats-on-io-command-failed/td-p/2151924

Majo

New Member
Posts: 2
Registered: ‎10-18-2016

Re: ToughSwitch Failure (mod_ping_stats_on_io: command failed (1))

Hello @MajoV

 

Thanks for the feedback. Yes, indeed, the device was affed to the UNMS.

 

Regards,

Newton

Reply