I am tired for the new version since ver 21? so many problem!!

What is mean like this ?

2019-10-12T07:42:01.556Z        INFO    piecestore      deleted {"Piece ID": "NFBZHR7RZCFHK3JPBADYLH5CUSXC4UTYZY2NUD4DVJTY5ZITSLJQ"}
2019-10-12T07:42:51.089Z        INFO    piecestore      deleted {"Piece ID": "SZTBRWDPSCMATXBYM6VSYLAHOTDBZIOKWC36N3VWNPGBEKREBDMQ"}
2019-10-12T07:43:04.230Z        INFO    piecestore      deleted {"Piece ID": "BCJUH6IA7FMBK6SWXKMSJYKXVRZAYP6FU5XH5HSEQW4LNNNIPL7Q"}
2019-10-12T07:45:52.664Z        INFO    piecestore      deleted {"Piece ID": "AGR3OOWVDJKFBH6ZGQY6YFOLS4PEZWWTKK3RZAR3Q2G55GE6HQWQ"}
2019-10-12T07:47:25.855Z        INFO    piecestore      deleted {"Piece ID": "VHGKLSKW32NJFU5VFTJUUYBUJTZSDWO2YV7WKPUCPW3W7KD2GE4A"}
2019-10-12T07:48:55.795Z        ERROR   version Failed to do periodic version check: Get https://version.storj.io: dial tcp: lookup version.storj.io on 8.8.8.8:53: read udp 172.17.0.3:33469->8.8.8.8:53: i/o timeout

ming@ming-ubuntu:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=2 ttl=53 time=17.7 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=53 time=19.9 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=53 time=20.0 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=53 time=20.1 ms

Try to see if syncing the clock helps

Can u tell me more detail?

i don‘t understand

Om other hand it didnt say anything about time.
But you could install netTime and check if that does anything. Fast install and setup

Instead of using built in clock of your OS. More accurate and storj likes that

I check my storj server time ,It’s right.

ming@ming-ubuntu:~$ date
Sat Oct 12 16:22:09 CST 2019

Show us your dashboard.

I see this in my log when my internet is down. Check your internet connection. It might go down temporarily when your ISP assigns you a new IP if you have dynamic IP.

The DNS resolution from within the docker container seamed to be failing. 8.8.8.8:53 is a google dns server and i/o timeout meant it can’t be reached/connected. Your ping is from os not from inside of the container. Next you should test the ping or name resolution from inside the container.