Hello!
We are getting an error others have discussed on this forum, but none of the solutions have worked for us.

We have v2.0 hardware and artiq 7.8176.6fbfa12.

The error we are getting is:
artiq.dashboard.moninj:failed to connect to moninj. Is aqctl_moninj_proxy running?
Traceback (most recent call last):
File "C:\Users\iontrap\anaconda3\envs\artiq\lib\site-packages\artiq\dashboard\moninj.py", line 724, in mi_connector
await new_mi_connection.connect(self.mi_addr, self.mi_port)
File "C:\Users\iontrap\anaconda3\envs\artiq\lib\site-packages\artiq\coredevice\comm_moninj.py", line 32, in connect
self._reader, self._writer = await async_open_connection(
File "C:\Users\iontrap\anaconda3\envs\artiq\lib\site-packages\sipyco\keepalive.py", line 80, in async_open_connection
reader, writer = await asyncio.open_connection(host, port, *args, **kwargs)
File "C:\Users\iontrap\anaconda3\envs\artiq\lib\asyncio\streams.py", line 52, in open_connection
transport, _ = await loop.create_connection(
File "C:\Users\iontrap\anaconda3\envs\artiq\lib\asyncio\base_events.py", line 1025, in create_connection
raise exceptions[0]
File "C:\Users\iontrap\anaconda3\envs\artiq\lib\asyncio\base_events.py", line 1010, in create_connection
sock = await self._connect_sock(
File "C:\Users\iontrap\anaconda3\envs\artiq\lib\asyncio\base_events.py", line 924, in _connect_sock
await self.sock_connect(sock, address)
File "C:\Users\iontrap\anaconda3\envs\artiq\lib\asyncio\proactor_events.py", line 702, in sock_connect
return await self._proactor.connect(sock, address)
File "C:\Users\iontrap\anaconda3\envs\artiq\lib\site-packages\qasync\_windows.py", line 43, in _process_events
value = callback(transferred, key, ov)
File "C:\Users\iontrap\anaconda3\envs\artiq\lib\asyncio\windows_events.py", line 599, in finish_connect
ov.getresult()
ConnectionRefusedError: [WinError 1225] The remote computer refused the network connection

If we can successfully ping the Kasli. We are confident it's the correct IP address because when we unplug the ethernet cable, the ping fails. This Kasli was working last year, but we haven't used it much since then. We tried to bring it up online recently, but we get the above error. We did have to reinstall anaconda and artiq, so that might be part of it, but so far it doesn't seem directly related to the error message we are seeing.

The steps we've taken based on various forum discussions are to downgrade python to 3.8.2. Tried the rv32ima and ``rv32g``` target, and power cycled the Kasli many times. We get the same error repeating every few seconds on the dashboard. What's stranger still is we can run an experiment that outputs voltages on the zotino.

I feel a bit lost in debugging this situation in the first place because I don't know how to confirm if aqctl_moninj_proxy is running or why it would not be running by default.

Can you check on the core device log and send here, via artiq_coremgmt log or uart.

[ 0.000013s] INFO(runtime): ARTIQ runtime starting...
[ 0.003935s] INFO(runtime): software ident 7.0.8a7af3f.beta;indiana2
[ 0.010385s] INFO(runtime): gateware ident 7.0.8a7af3f.beta;indiana2
[ 0.016854s] INFO(runtime): log level set to INFO by default
[ 0.022574s] INFO(runtime): UART log level set to INFO by default
[ 0.139376s] WARN(runtime::rtio_clocking): rtio_clock setting not recognised. Falling back to default.
[ 0.147484s] INFO(runtime::rtio_clocking): using internal 125MHz RTIO clock
[ 0.423963s] INFO(board_artiq::si5324): waiting for Si5324 lock...
[ 3.523069s] INFO(board_artiq::si5324): ...locked
[ 3.526708s] INFO(runtime::rtio_clocking::crg): Using internal RTIO clock
[ 3.559120s] INFO(runtime): network addresses: MAC=e8-eb-1b-45-65-88 IPv4=192.168.1.75 IPv6-LL=fe80::eaeb:1bff:fe45:6588 IPv6=no configured address
[ 3.573001s] INFO(runtime::mgmt): management interface active
[ 3.599377s] INFO(runtime::session): accepting network sessions
[ 3.612429s] INFO(runtime::session): running startup kernel
[ 3.616891s] INFO(runtime::session): no startup kernel found
[ 3.622691s] INFO(runtime::session): no connection, starting idle kernel
[ 3.629531s] INFO(runtime::session): no idle kernel found
[ 39.831188s] INFO(runtime::session): new connection from 192.168.1.70:53929
[ 39.908258s] INFO(runtime::session): no connection, starting idle kernel
[ 39.913991s] INFO(runtime::session): no idle kernel found
[ 6558.920698s] INFO(runtime::moninj): new connection from 192.168.1.70:63947
[ 7671.118272s] INFO(runtime::session): new connection from 192.168.1.70:64238
[ 7671.166276s] INFO(runtime::kern_hwreq): resetting RTIO
[ 7671.273290s] INFO(runtime::session): no connection, starting idle kernel
[ 7671.278964s] INFO(runtime::session): no idle kernel found
[ 7814.936168s] INFO(runtime::session): new connection from 192.168.1.70:64271
[ 7814.984055s] INFO(runtime::kern_hwreq): resetting RTIO
[ 7815.056817s] INFO(runtime::session): no connection, starting idle kernel
[ 7815.062497s] INFO(runtime::session): no idle kernel found
[ 7888.464048s] INFO(runtime::session): new connection from 192.168.1.70:51312
[ 7888.511699s] INFO(runtime::kern_hwreq): resetting RTIO
[ 7888.581677s] INFO(runtime::session): no connection, starting idle kernel
[ 7888.587346s] INFO(runtime::session): no idle kernel found
[ 87580.941257s] INFO(runtime::mgmt): new connection from 192.168.1.70:65482

11 days later

This error is just about moninj (the monitor-injector system that lets you directly set TTLs and DDSs from the dashboard), your system and experiments should run just fine without it.
If you don't want this error or need moninj to be working, you can run it by simply running "aqctl_moninj_proxy <core ip address>" in your artiq environment.

Thank you! That fixed the error. I would like this to work correctly when Artiq starts up. Why might this not be executed correctly on startup?

You can use artiq_session to start those processes.

Worked like a charm! Thank you!

I hadn't known that command existed. Could it mentioned in the management tutorial section of the docs? I think others may find it helpful.