When I run

roslaunch kobuki_node minimal.launch

I get the following output

... logging to /home/ubuntu/.ros/log/8e8d5c0c-d4b3-11e7-836c-902e1cfcc74f/roslaunch-tegra-ubuntu-2175.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://localhost:58965/

SUMMARY

PARAMETERS * /diagnosticaggregator/analyzers/inputports/contains: ['Digital Input',... * /diagnosticaggregator/analyzers/inputports/path: Input Ports * /diagnosticaggregator/analyzers/inputports/removeprefix: mobilebasenodel... * /diagnosticaggregator/analyzers/inputports/timeout: 5.0 * /diagnosticaggregator/analyzers/inputports/type: diagnosticaggreg... * /diagnosticaggregator/analyzers/kobuki/contains: ['Watchdog', 'Mot... * /diagnosticaggregator/analyzers/kobuki/path: Kobuki * /diagnosticaggregator/analyzers/kobuki/removeprefix: mobilebasenodel... * /diagnosticaggregator/analyzers/kobuki/timeout: 5.0 * /diagnosticaggregator/analyzers/kobuki/type: diagnosticaggreg... * /diagnosticaggregator/analyzers/power/contains: ['Battery'] * /diagnosticaggregator/analyzers/power/path: Power System * /diagnosticaggregator/analyzers/power/removeprefix: mobilebasenodel... * /diagnosticaggregator/analyzers/power/timeout: 5.0 * /diagnosticaggregator/analyzers/power/type: diagnosticaggreg... * /diagnosticaggregator/analyzers/sensors/contains: ['Cliff Sensor', ... * /diagnosticaggregator/analyzers/sensors/path: Sensors * /diagnosticaggregator/analyzers/sensors/removeprefix: mobilebasenodel... * /diagnosticaggregator/analyzers/sensors/timeout: 5.0 * /diagnosticaggregator/analyzers/sensors/type: diagnosticaggreg... * /diagnosticaggregator/basepath: * /diagnosticaggregator/pubrate: 1.0 * /mobilebase/baseframe: basefootprint * /mobilebase/batterycapacity: 16.5 * /mobilebase/batterydangerous: 13.2 * /mobilebase/batterylow: 14.0 * /mobilebase/cmdveltimeout: 0.6 * /mobilebase/deviceport: /dev/kobuki * /mobilebase/odomframe: odom * /mobilebase/publishtf: True * /mobilebase/useimuheading: True * /mobilebase/wheelleftjointname: wheelleftjoint * /mobilebase/wheelrightjointname: wheelrightjoint * /rosdistro: indigo * /rosversion: 1.11.19

NODES / diagnosticaggregator (diagnosticaggregator/aggregatornode) mobilebase (nodelet/nodelet) mobilebasenodelet_manager (nodelet/nodelet)

auto-starting new master process[master]: started with pid [2186] ERROR: could not contact master [http://192.168.0.107:11311/] The traceback for the exception was written to the log file [master] killing on exit

and when I look at the logs it appears that it does connect to the master for a short time but then for some reason looses the connection. What's weird is that I tried this a few days ago and it worked successfully. I really hope this isn't a hardware failure. Any suggestions?