Is something wrong with the update mirror? [RESOLVED]

Started by gsellc, May 04, 2018, 05:25:36 PM

Previous topic - Next topic
Print
Go Down Pages1
User actions
May 04, 2018, 05:25:36 PM Last Edit: May 04, 2018, 06:37:17 PM by gsellc
Code Select
root@opnsense:~ # pkg upgrade -n
Updating OPNsense repository catalogue...
pkg: Repository OPNsense load error: access repo file(/var/db/pkg/repo-OPNsense.sqlite) failed: No such file or directory
pkg: http://pkg.opnsense.org/FreeBSD:11:i386/18.1/latest/meta.txz: Not Found
repository OPNsense has no meta file, using default settings
pkg: http://pkg.opnsense.org/FreeBSD:11:i386/18.1/latest/packagesite.txz: Not Found
Unable to update repository OPNsense
Error updating repositories!
root@opnsense:~ # curl http://pkg.opnsense.org/FreeBSD:11:i386/18.1/latest/packagesite.txz
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /FreeBSD:11:i386/18.1/latest/packagesite.txz was not found on this server.</p>
</body></html>
May 04, 2018, 05:33:49 PM #1
Hotfix in progress. Will be back soon.
May 04, 2018, 06:12:00 PM #2
Should be back now. Changelogs have also been updated:

https://github.com/opnsense/changelog/commit/3843da73e


Cheers,
Franco
May 04, 2018, 06:37:28 PM #3
Looks good! Thanks
May 04, 2018, 10:43:37 PM #4
I still have the same error. GUI says "connecton error" under System -> Firmware.

The try on the shell:

Code Select
----------------------------------------------
|      Hello, this is OPNsense 18.1          |         @@@@@@@@@@@@@@@
|                                            |        @@@@         @@@@
| Website:      https://opnsense.org/        |         @@@\\\   ///@@@
| Handbook:     https://docs.opnsense.org/   |       ))))))))   ((((((((
| Forums:       https://forum.opnsense.org/  |         @@@///   \\\@@@
| Lists:        https://lists.opnsense.org/  |        @@@@         @@@@
| Code:         https://github.com/opnsense  |         @@@@@@@@@@@@@@@
----------------------------------------------

  0) Logout                              7) Ping host
  1) Assign interfaces                   8) Shell
  2) Set interface IP address            9) pfTop
  3) Reset the root password            10) Firewall log
  4) Reset to factory defaults          11) Reload all services
  5) Power off system                   12) Upgrade from console
  6) Reboot system                      13) Restore a backup

Enter an option: 12

Fetching change log information, please wait... done

This will automatically fetch all available updates, apply them,
and reboot if necessary.

Proceed with this action? [y/N]: y

Updating OPNsense repository catalogue...
pkg-static: Repository OPNsense load error: access repo file(/var/db/pkg/repo-OPNsense.sqlite) failed: No such file or directory
pkg-static: https://opnsense-update.deciso.com/FreeBSD:11:amd64/18.1/libressl/meta.txz: No route to host
repository OPNsense has no meta file, using default settings
pkg-static: https://opnsense-update.deciso.com/FreeBSD:11:amd64/18.1/libressl/packagesite.txz: No route to host
Unable to update repository OPNsense
Error updating repositories!
A firmware update is currently in progress.

and this one:

Code Select
# pkg upgrade -n
Updating OPNsense repository catalogue...
pkg: Repository OPNsense load error: access repo file(/var/db/pkg/repo-OPNsense.sqlite) failed: No such file or directory
pkg: https://opnsense-update.deciso.com/FreeBSD:11:amd64/18.1/libressl/meta.txz: No route to host
repository OPNsense has no meta file, using default settings
pkg: https://opnsense-update.deciso.com/FreeBSD:11:amd64/18.1/libressl/packagesite.txz: No route to host
Unable to update repository OPNsense
Error updating repositories!


I´m on 18.1.7.

Thanks for any help!
May 05, 2018, 11:15:14 AM #5
Do you use a commercial offering? opnsense-update.deciso.com is only for that. Host looks down as stated...

https://opnsense-update.deciso.com/

Normal mirror is up and running fine:

https://pkg.opnsense.org/


Cheers,
Franco
May 05, 2018, 02:34:36 PM #6
QuoteDo you use a commercial offering ?
No. I tested the default and this one yesterday. Back on "default" today and it works well.

Thanks!
May 05, 2018, 07:22:38 PM #7
Okay, glad to hear. :)

The CDN server dns-root.de was acting up again due to excessive caching. All other servers don't seem to have problems syncing even when hotfixes are pushed.


Cheers,
Franco
Print
Go Up Pages1
User actions