Is this node running well? or is it not working as it should be?
fork@tech2:~/forknote-linux$ ./forknoted --config-file configs/technetium.conf
Success: Configuration file openned: "configs/technetium.conf"
2018-Jan-02 19:36:18.743872 INFO forknote v2.1.1.1245 ()
2018-Jan-02 19:36:18.744925 INFO Module folder: ./forknoted
2018-Jan-02 19:36:18.746964 INFO Opening DB in /home/fork/.technetium/DB
2018-Jan-02 19:36:18.763394 INFO DB opened in /home/fork/.technetium/DB
2018-Jan-02 19:36:18.766321 INFO Initializing core...
2018-Jan-02 19:36:18.777807 INFO Core initialized OK
2018-Jan-02 19:36:18.778304 INFO Initializing p2p server...
2018-Jan-02 19:36:18.778495 INFO Generated new peer ID: 7029398983946693145
2018-Jan-02 19:36:18.778632 INFO Binding on 0.0.0.0:34250
2018-Jan-02 19:36:18.778833 INFO Net service binded on 0.0.0.0:34250
2018-Jan-02 19:36:18.778966 INFO Attempting to add IGD port mapping.
2018-Jan-02 19:36:22.784096 INFO No IGD was found.
2018-Jan-02 19:36:22.784263 INFO P2p server initialized OK
2018-Jan-02 19:36:22.792004 INFO Starting core rpc server on address 127.0.0.1:34377
2018-Jan-02 19:36:22.792378 INFO Core rpc server started ok
2018-Jan-02 19:36:22.792522 INFO Starting p2p net loop...
2018-Jan-02 19:36:22.792608 INFO Starting node_server
2018-Jan-02 19:36:22.799842 INFO
2018-Jan-02 19:36:22.799842 INFO **********************************************************************
2018-Jan-02 19:36:22.799842 INFO You are now synchronized with the network. You may now start simplewallet.
2018-Jan-02 19:36:22.799842 INFO
2018-Jan-02 19:36:22.799842 INFO Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command.
2018-Jan-02 19:36:22.799842 INFO Otherwise, you will possibly need to synchronize the blockchain again.
2018-Jan-02 19:36:22.799842 INFO
2018-Jan-02 19:36:22.799842 INFO Use "help" command to see the list of available commands.
2018-Jan-02 19:36:22.799842 INFO **********************************************************************
2018-Jan-02 19:36:22.802332 WARNING [207.246.65.66:57677 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:24.809138 WARNING [207.246.65.66:46316 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:26.811479 WARNING [207.246.65.66:33803 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:28.814101 WARNING [207.246.65.66:46890 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:30.817393 WARNING [207.246.65.66:35115 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:32.819522 WARNING [207.246.65.66:38274 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:34.823345 WARNING [207.246.65.66:38731 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:36.825551 WARNING [207.246.65.66:54882 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:38.828191 WARNING [207.246.65.66:54645 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:40.832488 WARNING [207.246.65.66:51703 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:42.834446 WARNING [207.246.65.66:44667 INC] Exception in connectionHandler: TcpConnection::read