You need to look at the root file system. It is only about 2GB. If you
ssh into the device you can to a df -h command. This will tell you
how much space is available on each partition.
2018-09-23T06:14:43.455799-07:00 di=UzI4dUjxpu notice restsdk[9394]: watch.go:109: Stat(), error: stat /tmp/dynamicconfig.ini: no such file or directory
2018-09-23T06:14:53.456852-07:00 di=UzI4dUjxpu notice restsdk[9394]: watch.go:109: Stat(), error: stat /tmp/dynamicconfig.ini: no such file or directory
2018-09-23T06:15:03.457731-07:00 di=UzI4dUjxpu notice restsdk[9394]: watch.go:109: Stat(), error: stat /tmp/dynamicconfig.ini: no such file or directory
2018-09-23T06:15:13.458873-07:00 di=UzI4dUjxpu notice restsdk[9394]: watch.go:109: Stat(), error: stat /tmp/dynamicconfig.ini: no such file or directory
2018-09-23T06:15:23.459877-07:00 di=UzI4dUjxpu notice restsdk[9394]: watch.go:109: Stat(), error: stat /tmp/dynamicconfig.ini: no such file or directory
2018-09-23T06:15:33.461057-07:00 di=UzI4dUjxpu notice restsdk[9394]: watch.go:109: Stat(), error: stat /tmp/dynamicconfig.ini: no such file or directory
2018-09-23T06:15:43.462145-07:00 di=UzI4dUjxpu notice restsdk[9394]: watch.go:109: Stat(), error: stat /tmp/dynamicconfig.ini: no such file or directory
The dynamicconfig.ini error is a known issue. It is caused by the resdsdk process.
I think your problem is with the tmp filesystems not having enought room. First try a
reboot and check the diskspace again. If that does not fix it. check into the tmp filesystems
to see if you can determine what is taking up the space.