Windows Server 2019 - SuperDoctor SD5 Monitoring App issues?

Support
1

Hello Anyone able to run chia on windows server?

I tried is not several times on 4 different servers it seems to fail with certificates for port 8444. Any tipp how to sort this out - installation in Win10 worked without issues.

2021-05-21T22:16:01.686 wallet wallet                     : INFO     Started wallet service on network_id: mainnet
2021-05-21T22:16:01.688 wallet wallet                     : INFO     Reconnecting to peer {'host': '127.0.0.1', 'port': 8444}
2021-05-21T22:16:01.701 wallet wallet_server              : INFO     Cannot connect to host 127.0.0.1:8444 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1091)')]
2021-05-21T22:16:01.703 daemon __main__                   : INFO     Register service {'service': 'chia_wallet'}
2021-05-21T22:16:01.708 daemon __main__                   : INFO     registered for service chia_wallet
2021-05-21T22:16:01.714 daemon __main__                   : INFO     {'success': True}
2021-05-21T22:16:03.670 farmer farmer                     : INFO     Reconnecting to peer {'host': '127.0.0.1', 'port': 8444}
2021-05-21T22:16:03.685 farmer farmer_server              : INFO     Cannot connect to host 127.0.0.1:8444 ssl:True [SSLCertVerificationError: (1, '[**SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1091)')]**
2021-05-21T22:16:04.698 wallet wallet                     : INFO     Reconnecting to peer {'host': '127.0.0.1', 'port': 8444}
2021-05-21T22:16:04.706 wallet wallet_server              : INFO     Cannot connect to host 127.0.0.1:8444 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1091)')]
2

You’ve run chia init?.. seems like a serious issue. Do you only have a single node?

3

Just used the GUI. Means install which works and then wait. After several minutes (maybe 10) private key is created and you can continue - but obviously the full node never comes up. It is 100% reproducable.

Setup will be with several nodes but this test was just with single nodes.

Did not try a CLI start yet.

Update if using CLI I get… if anyoen has an idea how to sort out this permission issue?

Daemon not started yet
Starting daemon
chia_harvester: started
chia_timelord_launcher: chia_timelord_launcher failed to start. Error: start failed
chia_timelord: started
chia_farmer: started
chia_full_node: started
chia_wallet: started
PS C:\Users\administrator.RESEARCH\AppData\Local\chia-blockchain\app-1.1.6\resources\app.asar.unpacked\daemon> Traceback (most recent call last):
  File "chia\server\start_full_node.py", line 65, in <module>
  File "chia\server\start_full_node.py", line 60, in main
Exception in thread Thread-3:
Traceback (most recent call last):
  File "aiosqlite\core.py", line 109, in run
  File "asyncio\base_events.py", line 736, in call_soon_threadsafe
  File "asyncio\base_events.py", line 479, in _check_closed
RuntimeError: Event loop is closed

During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "threading.py", line 926, in _bootstrap_inner
      File "aiosqlite\core.py", line 117, in run
      File "asyncio\base_events.py", line 736, in call_soon_threadsafe
      File "asyncio\base_events.py", line 479, in _check_closed
    RuntimeError: Event loop is closed

      File "chia\server\start_service.py", line 226, in run_service
      File "asyncio\runners.py", line 43, in run
      File "asyncio\base_events.py", line 587, in run_until_complete
      File "chia\server\start_service.py", line 220, in async_run_service
      File "chia\server\start_service.py", line 160, in run
      File "chia\server\start_service.py", line 136, in start
      File "chia\server\server.py", line 218, in start_server
      File "aiohttp\web_runner.py", line 128, in start
      File "asyncio\base_events.py", line 1389, in create_server
    OSError: [Errno 10013] error while attempting to bind on address ('0.0.0.0', 8444): an attempt was made to access a socket in a way forbidden by its access permissions
    [6416] Failed to execute script start_full_node
4

Aaarg - just checked listen ports on all machines java listens to 8444.
Need to check this first it seems

2 Likes
5

Problem solved - it was SuperDoctor SD5 Monitoring App from SuperMicro using the ports on all Servers.
In case someone else falls into this trap.

1 Like
6

@endurance I’ve been getting this same error (10013). I see where Java is listening on port 8444, but how did you determine which app’s Java was responsible?

Edit: I think I saw this yesterday with the netstat -aon command and the task manager, but didn’t notice any info more detailed than Java. Will check again tonight.

7

Turns out this was exactly my problem, too. SuperDoctor5 listening on port 8444, preventing any connections, and causing error 10013.

1 Like
8

I had only one Java app running on the server - so it was finally easy.