Timeout while connecting to the selected mirror

[tre4bax]

I loaded NTOPNG the other day to do traffic analysis.  What I didn't spot until I went in to configure it was I need to install Redis.  When I have tried to update the plugins to see this and install it I constantly get the above.  I have tried everything I can think of.  I have tried rebooting the router, several times and I have tried changing the mirrors.  To no avail.

Yesterday I read something about pinging opnsense.org.

If I do this from my router it pings 81.171.2.181 and gets 100% packet loss

If I do it from a workstation connected to the same router this pings fine 0% packet loss average 14ms

Is this the source of my issue with updating the plugins?  and if so what the heck have I done here?  Really wish the config on this could be source managed through GIT or something so I can unwrap ;-)

[tre4bax]

Still cannot do any form of update.  surely someone has encountered this before?

[tre4bax]

Looks like this might be the issue:

configd.py: [c02ed810-623c-4d1e-9b21-8eed1e89e80f] Script action failed with Command 'pkg rquery "%n|||%v|||%c|||%sh|||0|||%L"' returned non-zero exit status 74 at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 481, in execute stdout=output_stream, stderr=error_stream) File "/usr/local/lib/python2.7/subprocess.py", line 190, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command 'pkg rquery "%n|||%v|||%c|||%sh|||0|||%L"' returned non-zero exit status 74

[tre4bax]

Where is a mirror address so I can ping it from the box?

[franco]

Running this from the console will reveal the mirror address:

# opnsense-update -M


Cheers,
Franco

[tre4bax]

Many thanks Franco.  I will give it a try.

Trev

[Andreas_]

I had the same problem; couldn't update my 18.7.4 to .5 or .6 via GUI on one of two routers (carp pair). changelog was downloaded/unpacked successfully, but then things stopped. Connectivity to update site (pkg.opnsense) was fine.

I finally conducted the update via CLI successfully.

[Stifler]

Just registered to share my issue that caused this same problem.

If you installed the Sunny Valley Networks "Sensei" package for OPNSense, and then uninstalled it, it leaves behind traces in the /etc/local/etc/pkg/repo folder.

The best thing to do is open the file left behind (sunneyvalley.conf) and disable the repo. Then update the pkg system.

pkg update -f

Might not be Sensei, but could be something installed that left cruft on your system.