Skip to content

what does this mean? ERROR pinging Field Server field.carriota.com:- LOCAL Client error message: ECONNRESET #39

@xzcccc

Description

@xzcccc

I have installed the iri full-node and field in my OS, and the iri and field run successfully. However, the field debug information as follow:

10:40:15.440    FIELD        Field Client      v.0.1.6
10:40:15.444    FIELD        Field ID:         02d6*************************************** (do NOT share online!)
10:40:15.445    FIELD        Public ID:        02d6936f97640741
10:40:15.445    FIELD        Field Server(s):  field.carriota.com
10:40:15.445    FIELD        Donations:        ENABLED
10:40:15.445    FIELD        Donations:        Seed for dynamic IOTA address generation: ERJ*****
10:40:15.445    FIELD        IRI:              Public access through the Field is ENABLED
10:40:15.445    FIELD        IRI:              PoW (attachToTangle) jobs are ENABLED
10:40:15.495    FIELD        IRI online!
10:40:17.052    FIELD        ERROR pinging Field Server field.carriota.com:
10:40:36.919    FIELD        ERROR pinging Field Server field.carriota.com:
10:41:18.450    FIELD        ERROR pinging Field Server field.carriota.com:
10:41:18.450    FIELD        - LOCAL Client error message: ECONNRESET
10:42:02.816    FIELD        ERROR pinging Field Server field.carriota.com:
10:42:21.109    FIELD        ERROR pinging Field Server field.carriota.com:
10:42:21.110    FIELD        - LOCAL Client error message: ECONNRESET
10:42:41.659    FIELD        ERROR pinging Field Server field.carriota.com:
10:42:41.660    FIELD        - LOCAL Client error message: ECONNRESET

and the IRI debug information:

Logging - property 'logging-level' set to: [INFO]
06/19 10:39:30.228 [main] WARN  com.iota.iri.IRI$IRILauncher - No neighbor has been specified. Server starting nodeless.
06/19 10:39:30.231 [main] INFO  com.iota.iri.IRI$IRILauncher - Welcome to IRI Testnet 1.4.2.4
06/19 10:39:31.960 [main] INFO  com.iota.iri.IRI$IRILauncher - You have set the debug flag. To enable debug output, you need to uncomment the DEBUG appender in the source tree at iri/src/main/resources/logback.xml and re-package iri.jar
06/19 10:39:32.072 [main] INFO  c.i.i.s.r.RocksDBPersistenceProvider - Initializing Database Backend... 
06/19 10:39:32.125 [main] INFO  c.i.i.s.r.RocksDBPersistenceProvider - RocksDB persistence provider initialized.
06/19 10:39:32.127 [Latest Milestone Tracker] INFO  com.iota.iri.Milestone - Waiting for Ledger Validator initialization...
06/19 10:39:32.128 [Solid Milestone Tracker] INFO  com.iota.iri.Milestone - Initializing Ledger Validator...
06/19 10:39:32.129 [Solid Milestone Tracker] INFO  com.iota.iri.Milestone - Tracker started.
06/19 10:39:32.138 [main] INFO  com.iota.iri.network.UDPReceiver - UDP replicator is accepting connections on udp port 14600
06/19 10:39:32.139 [UDP receiving thread] INFO  com.iota.iri.network.UDPReceiver - Spawning Receiver Thread
06/19 10:39:32.140 [UDP receiving thread] INFO  com.iota.iri.network.UDPReceiver - Receiver thread processed/dropped ratio: 0/0
06/19 10:39:32.143 [main] INFO  c.i.i.network.replicator.Replicator - Started ReplicatorSourcePool
06/19 10:39:32.149 [Thread-2] INFO  c.i.i.n.r.ReplicatorSourcePool - TCP replicator is accepting connections on tcp port 15600
06/19 10:39:32.150 [pool-3-thread-1] INFO  com.iota.iri.network.Node - Spawning Broadcaster Thread
06/19 10:39:32.151 [pool-3-thread-2] INFO  com.iota.iri.network.Node - Spawning Tips Requester Thread
06/19 10:39:32.152 [pool-3-thread-2] INFO  com.iota.iri.network.Node - toProcess = 0 , toBroadcast = 0 , toRequest = 0 , toReply = 0 / totalTransactions = 0
06/19 10:39:32.155 [pool-3-thread-3] INFO  com.iota.iri.network.Node - Spawning Neighbor DNS Refresher Thread
06/19 10:39:32.155 [pool-3-thread-3] INFO  com.iota.iri.network.Node - Checking Neighbors' Ip...
06/19 10:39:32.156 [pool-3-thread-4] INFO  com.iota.iri.network.Node - Spawning Process Received Data Thread
06/19 10:39:32.160 [pool-3-thread-5] INFO  com.iota.iri.network.Node - Spawning Reply To Request Thread
06/19 10:39:32.187 [main] INFO  org.xnio - XNIO version 3.3.6.Final
06/19 10:39:32.204 [main] INFO  org.xnio.nio - XNIO NIO Implementation Version 3.3.6.Final
06/19 10:39:32.416 [main] INFO  com.iota.iri.IRI$IRILauncher - IOTA Node initialised correctly.
06/19 10:39:33.127 [Latest Milestone Tracker] INFO  com.iota.iri.Milestone - Tracker started.
06/19 10:39:47.153 [pool-3-thread-2] INFO  com.iota.iri.network.Node - toProcess = 0 , toBroadcast = 0 , toRequest = 0 , toReply = 0 / totalTransactions = 0
06/19 10:39:57.154 [pool-3-thread-2] INFO  com.iota.iri.network.Node - toProcess = 0 , toBroadcast = 0 , toRequest = 0 , toReply = 0 / totalTransactions = 0
06/19 10:40:12.155 [pool-3-thread-2] INFO  com.iota.iri.network.Node - toProcess = 0 , toBroadcast = 0 , toRequest = 0 , toReply = 0 / totalTransactions = 0
06/19 10:40:22.158 [pool-3-thread-2] INFO  com.iota.iri.network.Node - toProcess = 0 , toBroadcast = 0 , toRequest = 0 , toReply = 0 / totalTransactions = 0

I can find my node in field.carriota.com and in my os I can ping the field.carriota.com successfully:

~# ping field.carriota.com
PING field.carriota.com (195.201.104.164) 56(84) bytes of data.
64 bytes from static.164.104.201.195.clients.your-server.de (195.201.104.164): icmp_seq=1 ttl=49 time=265 ms
64 bytes from static.164.104.201.195.clients.your-server.de (195.201.104.164): icmp_seq=2 ttl=49 time=264 ms
64 bytes from static.164.104.201.195.clients.your-server.de (195.201.104.164): icmp_seq=3 ttl=49 time=269 ms
64 bytes from static.164.104.201.195.clients.your-server.de (195.201.104.164): icmp_seq=4 ttl=49 time=280 ms
^C
--- field.carriota.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 264.406/270.027/280.284/6.212 ms

So what’s the problem about
"10:40:17.052 FIELD ERROR pinging Field Server field.carriota.com:"
and how to solve this problem?
Or can I ignore the error?

OS : Ubuntu 16.04 x86_64
IRI:1.4.2.4

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions