Connection unsuccessful showing


#1

When I try to click on refresh on web console it showing me connection unsuccessful. Can someone please help me for this.

Command output as below.

sudo supervisorctl
supervisor> restart din ingestor
din: ERROR (no such process)
ingestor: ERROR (no such process)
din: ERROR (no such process)
ingestor: ERROR (no such process)

============


#2

sudo docker-compose logs
Attaching to comp-dnif-a10
comp-dnif-a10 | * Stopping enhanced syslogd rsyslogd
comp-dnif-a10 | …done.
comp-dnif-a10 | * Starting enhanced syslogd rsyslogd
comp-dnif-a10 | …done.
comp-dnif-a10 | Starting redis-server: redis-server.
comp-dnif-a10 | ====================================
comp-dnif-a10 | UNET CONNECTION ERROR…
comp-dnif-a10 | Please check your network setting…
comp-dnif-a10 | ====================================
comp-dnif-a10 | * Stopping enhanced syslogd rsyslogd
comp-dnif-a10 | …done.
comp-dnif-a10 | * Starting enhanced syslogd rsyslogd
comp-dnif-a10 | …done.
comp-dnif-a10 | Starting redis-server: redis-server.
comp-dnif-a10 | Traceback (most recent call last):
comp-dnif-a10 | File “/usr/src/nm/scripts/startup-config.py”, line 111, in
comp-dnif-a10 | with open(a10conf_path) as json_data:
comp-dnif-a10 | IOError: [Errno 2] No such file or directory: ‘/dnif/EnSNvvcH2v9MWSjn/a10conf.json’
comp-dnif-a10 | Generating a 2048 bit RSA private key
comp-dnif-a10 | …+++
comp-dnif-a10 | …+++
comp-dnif-a10 | writing new private key to ‘/dnif/EnSNvvcH2v9MWSjn/ssl/dnif_https_API.key’
comp-dnif-a10 | -----
comp-dnif-a10 | Generating a 2048 bit RSA private key
comp-dnif-a10 | …+++
comp-dnif-a10 | …+++
comp-dnif-a10 | writing new private key to ‘/dnif/EnSNvvcH2v9MWSjn/ssl2/dnif_https_listener.key’
comp-dnif-a10 | -----
comp-dnif-a10 | * Starting Elasticsearch Server
comp-dnif-a10 | sysctl: setting key “vm.max_map_count”: Read-only file system
comp-dnif-a10 | …done.
comp-dnif-a10 | * Restarting periodic command scheduler cron
comp-dnif-a10 | * Stopping periodic command scheduler cron
comp-dnif-a10 | …done.
comp-dnif-a10 | * Starting periodic command scheduler cron
comp-dnif-a10 | …done.
comp-dnif-a10 | Traceback (most recent call last):
comp-dnif-a10 | File “/usr/src/nm/scripts/escheck.py”, line 9, in
comp-dnif-a10 | libmg.check(wdir)
comp-dnif-a10 | File “libmg.py”, line 232, in libmg.check
comp-dnif-a10 | KeyError: ‘dsat1’
comp-dnif-a10 | Traceback (most recent call last):
comp-dnif-a10 | File “/usr/src/nm/rtdp-datastore-v6/ecurator/ecurator.py”, line 1, in
comp-dnif-a10 | from bin.ecurator import execute
comp-dnif-a10 | File “ecurator/ecurator.py”, line 58, in init ecurator
comp-dnif-a10 |
comp-dnif-a10 | TypeError: ‘NoneType’ object has no attribute ‘getitem
comp-dnif-a10 | Traceback (most recent call last):
comp-dnif-a10 | File “/usr/src/nm/rtdp-datastore-v6/iliteralDS/create_field_list.py”, line 1, in
comp-dnif-a10 | from bin.create_field_list import execute
comp-dnif-a10 | File “iliteralDS/create_field_list.py”, line 58, in init iliteralDS.create_field_list
comp-dnif-a10 |
comp-dnif-a10 | TypeError: ‘NoneType’ object has no attribute ‘getitem
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | tput: No value for $TERM and no -T specified
comp-dnif-a10 |
comp-dnif-a10 | ____ _ _ ___ _____ __ __
comp-dnif-a10 | | _ | \ | |_ | | \ \ \ \
comp-dnif-a10 | | | | | | || || |
\ \ \
comp-dnif-a10 | | |
| | |\ || || | / / / /
comp-dnif-a10 | |
/|| _||| // //
comp-dnif-a10 |
comp-dnif-a10 | Server is now running…
comp-dnif-a10 | Please visit DNIF console at : http://go.dnif.it/
comp-dnif-a10 | tput: No value for $TERM and no -T specified
comp-dnif-a10 |
comp-dnif-a10 | /usr/lib/python2.7/dist-packages/supervisor/options.py:297: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a “-c” argument specifying an absolute path to a configuration file for improved security.
comp-dnif-a10 | 'Supervisord is running as root and it is searching ’
comp-dnif-a10 | 2019-06-07 12:22:14,055 CRIT Set uid to user 0
comp-dnif-a10 | 2019-06-07 12:22:14,133 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
comp-dnif-a10 | * Stopping enhanced syslogd rsyslogd
comp-dnif-a10 | …done.
comp-dnif-a10 | * Starting enhanced syslogd rsyslogd
comp-dnif-a10 | …done.
comp-dnif-a10 | Starting redis-server: redis-server.
comp-dnif-a10 | Traceback (most recent call last):
comp-dnif-a10 | File “/usr/src/nm/scripts/startup-config.py”, line 121, in
comp-dnif-a10 | with open("/etc/elasticsearch/elasticsearch.yml", ‘r’) as rfile :
comp-dnif-a10 | IOError: [Errno 2] No such file or directory: ‘/etc/elasticsearch/elasticsearch.yml’
comp-dnif-a10 | * Starting Elasticsearch Server
comp-dnif-a10 | sysctl: setting key “vm.max_map_count”: Read-only file system
comp-dnif-a10 | …done.
comp-dnif-a10 | * Restarting periodic command scheduler cron
comp-dnif-a10 | * Stopping periodic command scheduler cron
comp-dnif-a10 | /sbin/start-stop-daemon: warning: failed to kill 124: No such process
comp-dnif-a10 | …done.
comp-dnif-a10 | * Starting periodic command scheduler cron
comp-dnif-a10 | …done.
comp-dnif-a10 | Traceback (most recent call last):
comp-dnif-a10 | File “/usr/src/nm/scripts/escheck.py”, line 9, in
comp-dnif-a10 | libmg.check(wdir)
comp-dnif-a10 | File “libmg.py”, line 232, in libmg.check
comp-dnif-a10 | KeyError: ‘dsat1’
comp-dnif-a10 | Traceback (most recent call last):
comp-dnif-a10 | File “/usr/src/nm/rtdp-datastore-v6/ecurator/ecurator.py”, line 1, in
comp-dnif-a10 | from bin.ecurator import execute
comp-dnif-a10 | File “ecurator/ecurator.py”, line 58, in init ecurator
comp-dnif-a10 |
comp-dnif-a10 | TypeError: ‘NoneType’ object has no attribute ‘getitem
comp-dnif-a10 | Traceback (most recent call last):
comp-dnif-a10 | File “/usr/src/nm/rtdp-datastore-v6/iliteralDS/create_field_list.py”, line 1, in
comp-dnif-a10 | from bin.create_field_list import execute
comp-dnif-a10 | File “iliteralDS/create_field_list.py”, line 58, in init iliteralDS.create_field_list
comp-dnif-a10 |
comp-dnif-a10 | TypeError: ‘NoneType’ object has no attribute ‘getitem
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | --> [+] exists…!!
comp-dnif-a10 | tput: No value for $TERM and no -T specified
comp-dnif-a10 |
comp-dnif-a10 | ____ _ _ ___ _____ __ __
comp-dnif-a10 | | _ | \ | |_ | | \ \ \ \
comp-dnif-a10 | | | | | | || || |
\ \ \
comp-dnif-a10 | | |
| | |\ || || | / / / /
comp-dnif-a10 | |
/|| _||| // //
comp-dnif-a10 |
comp-dnif-a10 | Server is now running…
comp-dnif-a10 | Please visit DNIF console at : http://go.dnif.it/
comp-dnif-a10 | tput: No value for $TERM and no -T specified
comp-dnif-a10 |
comp-dnif-a10 | /usr/lib/python2.7/dist-packages/supervisor/options.py:297: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a “-c” argument specifying an absolute path to a configuration file for improved security.
comp-dnif-a10 | 'Supervisord is running as root and it is searching ’
comp-dnif-a10 | 2019-06-07 12:31:32,880 CRIT Set uid to user 0
comp-dnif-a10 | Unlinking stale socket /var/run/supervisor.sock
comp-dnif-a10 | 2019-06-07 12:31:33,238 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking


#3

Hi @smit

comp-dnif-a10 | ====================================
comp-dnif-a10 | UNET CONNECTION ERROR…
comp-dnif-a10 | Please check your network setting…
comp-dnif-a10 | ====================================

From the logs it seems you are not able to connect to the UNET.

Could you check the connectivity to UNET by executing the following command (let me know the output of the same):

 $ telnet 52.72.25.136 443

Press ‘Ctrl + ]’ and then type ‘quit’ to close the telnet terminal.

You can also try:

wget https://api2.netmonastery.com/hello