Error updating repositories freebsd

Hi all, I'm getting the following error on my FreeBSD 12.1-RELEASE-p2: # pkg update Updating FreeBSD_latest repository catalogue... pkg: repository meta has wrong version 2 pkg: Repository FreeBSD_latest load error: meta cannot be loaded No error: 0 Fetching meta.txz: 100% 916 B 0.9kB/s...

  • #1

Hi all,

I’m getting the following error on my FreeBSD 12.1-RELEASE-p2:

Code: 

# pkg update
Updating FreeBSD_latest repository catalogue...
pkg: repository meta has wrong version 2
pkg: Repository FreeBSD_latest load error: meta cannot be loaded No error: 0
Fetching meta.txz: 100%    916 B   0.9kB/s    00:01
pkg: repository meta has wrong version 2
repository FreeBSD_latest has no meta file, using default settings
Fetching packagesite.txz: 100%    6 MiB   1.1MB/s    00:06
pkg: repository meta has wrong version 2
pkg: Repository FreeBSD_latest load error: meta cannot be loaded No error: 0
Unable to open created repository FreeBSD_latest
Unable to update repository FreeBSD_latest
Error updating repositories!

This is my pkg config:

Code: 

# pkg -vv
Version                 : 1.11.1
PKG_DBDIR = "/var/db/pkg";
PKG_CACHEDIR = "/var/cache/pkg";
PORTSDIR = "/usr/ports";
INDEXDIR = "";
INDEXFILE = "INDEX-12";
HANDLE_RC_SCRIPTS = false;
DEFAULT_ALWAYS_YES = false;
ASSUME_ALWAYS_YES = false;
REPOS_DIR [
    "/etc/pkg/",
    "/usr/local/etc/pkg/repos/",
]
PLIST_KEYWORDS_DIR = "";
SYSLOG = true;
ABI = "FreeBSD:12:amd64";
ALTABI = "freebsd:12:x86:64";
DEVELOPER_MODE = false;
VULNXML_SITE = "http://vuxml.freebsd.org/freebsd/vuln.xml.bz2";
FETCH_RETRY = 3;
PKG_PLUGINS_DIR = "/usr/local/lib/pkg/";
PKG_ENABLE_PLUGINS = true;
PLUGINS [
]
DEBUG_SCRIPTS = false;
PLUGINS_CONF_DIR = "/usr/local/etc/pkg/";
PERMISSIVE = false;
REPO_AUTOUPDATE = true;
NAMESERVER = "";
HTTP_USER_AGENT = "pkg/1.11.1";
EVENT_PIPE = "";
FETCH_TIMEOUT = 30;
UNSET_TIMESTAMP = false;
SSH_RESTRICT_DIR = "";
PKG_ENV {
}
PKG_SSH_ARGS = "";
DEBUG_LEVEL = 0;
ALIAS {
    all-depends = "query %dn-%dv";
    annotations = "info -A";
    build-depends = "info -qd";
    cinfo = "info -Cx";
    comment = "query -i "%c"";
    csearch = "search -Cx";
    desc = "query -i "%e"";
    download = "fetch";
    iinfo = "info -ix";
    isearch = "search -ix";
    prime-list = "query -e '%a = 0' '%n'";
    prime-origins = "query -e '%a = 0' '%o'";
    leaf = "query -e '%#r == 0' '%n-%v'";
    list = "info -ql";
    noauto = "query -e '%a == 0' '%n-%v'";
    options = "query -i "%n - %Ok: %Ov"";
    origin = "info -qo";
    provided-depends = "info -qb";
    rall-depends = "rquery %dn-%dv";
    raw = "info -R";
    rcomment = "rquery -i "%c"";
    rdesc = "rquery -i "%e"";
    required-depends = "info -qr";
    roptions = "rquery -i "%n - %Ok: %Ov"";
    shared-depends = "info -qB";
    show = "info -f -k";
    size = "info -sq";
}
CUDF_SOLVER = "";
SAT_SOLVER = "";
RUN_SCRIPTS = true;
CASE_SENSITIVE_MATCH = false;
LOCK_WAIT = 1;
LOCK_RETRIES = 5;
SQLITE_PROFILE = false;
WORKERS_COUNT = 0;
READ_LOCK = false;
PLIST_ACCEPT_DIRECTORIES = false;
IP_VERSION = 0;
AUTOMERGE = true;
VERSION_SOURCE = "";
CONSERVATIVE_UPGRADE = true;
PKG_CREATE_VERBOSE = false;
AUTOCLEAN = false;
DOT_FILE = "";
REPOSITORIES {
}
VALID_URL_SCHEME [
    "pkg+http",
    "pkg+https",
    "https",
    "http",
    "file",
    "ssh",
    "ftp",
    "ftps",
    "pkg+ssh",
    "pkg+ftp",
    "pkg+ftps",
]
ALLOW_BASE_SHLIBS = false;
WARN_SIZE_LIMIT = 1048576;
METALOG = "";
OSVERSION = 1201000;
IGNORE_OSVERSION = false;


Repositories:
  FreeBSD_latest: {
    url             : "pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/latest",
    enabled         : yes,
    priority        : 0,
    mirror_type     : "SRV",
    signature_type  : "FINGERPRINTS",
    fingerprints    : "/usr/share/keys/pkg"
  }

Any thoughts on what might cause the issue?

Thanks!

  • #2

Repositories: FreeBSD_latest: { url : «pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/latest», enabled : yes, priority : 0, mirror_type : «SRV», signature_type : «FINGERPRINTS», fingerprints : «/usr/share/keys/pkg» }

Can you keep this shorter? Mirror_type might not be always necessary; so also pkg+http in URL. You could look up the *Internet for sample conf files.

  • Thread Starter

  • #3

This is my

/usr/local/etc/pkg/repos/FreeBSD.conf

:

Code: 

FreeBSD: { enabled: no }
FreeBSD_latest: {
   url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
   mirror_type: "srv",
   signature_type: "fingerprints",
   fingerprints: "/usr/share/keys/pkg",
   enabled: yes
}

I would add that I’ve had the same setup for quite some time and it only recently broke.

Removing the pkg+http scheme results in a deprecation warning.

Even a bare-minimum .conf like so:

Code: 

FreeBSD_latest: {
   url: "http://pkg.FreeBSD.org/${ABI}/latest",
}

Results in:

Code: 

# pkg update
Updating FreeBSD repository catalogue...
pkg: repository meta has wrong version 2
pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0
Warning: use of http:// URL scheme with SRV records is deprecated: switch to pkg+http://
Fetching meta.txz: 100%    916 B   0.9kB/s    00:01
pkg: repository meta has wrong version 2
repository FreeBSD has no meta file, using default settings
Warning: use of http:// URL scheme with SRV records is deprecated: switch to pkg+http://
Fetching packagesite.txz: 100%    6 MiB 461.8kB/s    00:14
pkg: repository meta has wrong version 2
pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0
Unable to open created repository FreeBSD
Unable to update repository FreeBSD
Error updating repositories!

At any rate, I don’t think the problem is with the mirror or the connection, but rather with my local database.

SirDice


  • #4

Try this first: pkg-static install -f pkg. Then follow up with pkg update -f.

  • Thread Starter

  • #5

Code: 

# pkg-static install -f pkg
Updating FreeBSD repository catalogue...
pkg-static: repository meta has wrong version 2
pkg-static: Repository FreeBSD load error: meta cannot be loaded No error: 0
Fetching meta.txz: 100%    916 B   0.9kB/s    00:01
pkg-static: repository meta has wrong version 2
repository FreeBSD has no meta file, using default settings
Fetching packagesite.txz: 100%    6 MiB   1.1MB/s    00:06
pkg-static: repository meta has wrong version 2
pkg-static: Repository FreeBSD load error: meta cannot be loaded No error: 0
Unable to open created repository FreeBSD
Unable to update repository FreeBSD
Error updating repositories!

Looks like there is something wrong with the DB.
I remember reading that automatic backups of the DB are being performed, perhaps it’s worth investigating that?

SirDice


  • #6

I remember reading that automatic backups of the DB are being performed, perhaps it’s worth investigating that?

I don’t think your local registration database is at fault, it only complains about the meta data and SQL from the locally cached remote repositories. Try removing

/var/db/pkg/FreeBSD.meta

,

/var/db/pkg/FreeBSD_latest.meta

,

/var/db/pkg/repo-FreeBSD.sqlite

and

/var/db/pkg/repo-FreeBSD_latest.sqlite

. Then running pkg update again.

Do NOT remove

/var/db/pkg/local.sqlite

(it contains the registrations for your currently installed packages). In case you still want to checkout the backups, they’re in

/var/backups/

.

  • Thread Starter

  • #7

Thanks for your suggestions.

Unfortunately it sill gives the same «wrong version 2» error as before:

Code: 

# rm /var/db/pkg/FreeBSD.meta
# rm /var/db/pkg/FreeBSD_latest.meta
# rm /var/db/pkg/repo-FreeBSD.sqlite
# rm /var/db/pkg/
local.sqlite  vuln.xml
# pkg update
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%    916 B   0.9kB/s    00:01
pkg: repository meta has wrong version 2
repository FreeBSD has no meta file, using default settings
Fetching packagesite.txz: 100%    6 MiB   1.1MB/s    00:06
pkg: repository meta has wrong version 2
pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0
Unable to open created repository FreeBSD
Unable to update repository FreeBSD
Error updating repositories!

  • #8

Try updating

ports-mgmt/pkg

from the ports tree using

ports-mgmt/portmaster

.
If you haven’t fetched the ports tree yet, just do the following:

Code: 

# portsnap fetch
# portsnap extract

Once the process is over, assuming you have

ports-mgmt/portmaster

installed already, run:

At the end, you should see pkg version 1.13.2 installed (at the time of writing this post)

After I did the above, I got this:

Code: 

# pkg upgrade -F
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (3 candidates): 100%
Processing candidates (3 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.

  • Thread Starter

  • #9

  • #10

I have the same problem. The two portsnap commands worked, but I’m blocked on the «portmaster pkg» step as it is not installed, and «pkg install portmaster» also produces a «wrong version 2» error. Any ideas?

  • #11

If you are using ports (your mention of

portsnap

…), what happens if you try to build pkg from ports manually?
like this:

Code: 

cd /usr/ports/ports-mgmt/pkg
make install clean
cd

  • #13

Thanks for your replies. I can see how that likely would have worked.

Yesterday I continued playing with it and decided to upgrade since I was running an unsupported release (11.0). At some point in the process of moving to 12.1 I wound up with a new enough version of pkg that I was able to overcome the issue using the technique above. And now my server is up to date. :)

The upgrade went smoothly with no disruption to my local configurations — kudos to the FreeBSD team!

  • #14

I’ve been running into this with 12.0-RELEASE to 12.1-RELEASE and

freebsd-update

After a lot of frustration, I’ve had some success with (using the repo of your architecture and quarterly/latest choice)

Code: 

fetch https://pkg.freebsd.org/FreeBSD:12:amd64/latest/All/pkg-1.14.2.txz
sudo pkg add -f pkg-1.14.2.txz

pkg-add(8) suggests that

Code: 

sudo pkg add -f https://pkg.freebsd.org/FreeBSD:12:amd64/latest/All/pkg-1.14.2.txz

would work as a one-liner, though I have not now tried it successfully.

Last edited: Apr 16, 2020

  • #15

I got into this error after updating from 12.0-RELEASE to 12.1-RELEASE.
The solution that worked for me was to forcibly remove pkg

Code: 

root@server:/var/db/pkg # pkg update -f
Updating FreeBSD repository catalogue...
pkg: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0
Fetching meta.txz: 100%    916 B   0.9kB/s    00:01
pkg: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
repository FreeBSD has no meta file, using default settings
Fetching packagesite.txz: 100%    6 MiB  70.9kB/s    01:31
pkg: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0
Unable to open created repository FreeBSD
Unable to update repository FreeBSD
Error updating repositories!
root@server:/var/db/pkg # pkg add -f https://pkg.freebsd.org/FreeBSD:12:amd64/latest/All/pkg-1.14.2.txz
Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
34374852608:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
34374852608:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
Certificate verification failed for /C=US/O=Let's


root@server:/var/db/pkg # pkg delete -f pkg
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
    pkg-1.10.5_5

Number of packages to be removed: 1

The operation will free 13 MiB.

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling pkg-1.10.5_5...
[1/1] Deleting files for pkg-1.10.5_5: 100%
root@server:/var/db/pkg # pkg update -f pkg
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/quarterly, please wait...
Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done
Installing pkg-1.13.2...
Extracting pkg-1.13.2: 100%
Usage: pkg update [-fq] [-r reponame]

For more information, see 'pkg help update'.
root@server:/var/db/pkg # pkg update
Updating FreeBSD repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.txz: 100%    6 MiB 280.4kB/s    00:23
Processing entries: 100%
FreeBSD repository update completed. 31492 packages processed.
All repositories are up to date.
root@server:/var/db/pkg # pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Updating database digests format: 100%
Checking for upgrades (19 candidates): 100%
Processing candidates (19 candidates): 100%
The following 19 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
    python37: 3.7.7

Installed packages to be UPGRADED:
    fusefs-libs: 2.9.7 -> 2.9.9_1
    gawk: 4.1.4_3 -> 5.0.0
    gettext-runtime: 0.19.8.1_2 -> 0.20.1
    glib: 2.56.3_2,1 -> 2.56.3_7,1
    haproxy: 1.8.17 -> 2.0.13
    icu: 63.1_1,1 -> 66.1,1
    libdnet: 1.12_1 -> 1.13_3
    libmspack: 0.9.1 -> 0.10.1
    libssh2: 1.8.0,3 -> 1.8.2,3
    libxml2: 2.9.7 -> 2.9.10
    nginx: 1.14.2_3,2 -> 1.16.1_12,2
    open-vm-tools-nox11: 10.3.0_1,2 -> 11.0.1_3,2
    pcre: 8.42_1 -> 8.43_2
    perl5: 5.28.1 -> 5.30.2
    postfix: 3.3.3,1 -> 3.5.0,1
    python27: 2.7.15 -> 2.7.17_1
    readline: 7.0.5 -> 8.0.4
    sudo: 1.8.27 -> 1.8.31p1

Number of packages to be installed: 1
Number of packages to be upgraded: 18

The process will require 114 MiB more space.
62 MiB to be downloaded.

SirDice


  • #16

Try pkg-static install -f pkg or pkg bootstrap -f

  • #17

The first option didn’t work for me. I see the 2nd one for the first time now, I have no clue if it works or not, the problem was solved on my side.

SirDice


  • #18

I see the 2nd one for the first time now

You can learn a lot from the man pages ;)

Code: 

     bootstrap
             This is for compatibility with the pkg(7) bootstrapper.  If pkg
             is already installed, nothing is done.

             If invoked with the -f flag an attempt will be made to reinstall
             pkg from remote repository.

See pkg(8) and pkg(7).

  • #19

pkg delete -f pkg

pkg install pkg

dvl@


  • #20

Try pkg-static install -f pkg or pkg bootstrap -f

pkg bootstrap -f is what got us going.

dvl@


  • #22

For me:

sudo pkg bootstrap -f; sudo pkg update -f

got me back in business!

  • #23

I got into this error after updating from 12.0-RELEASE to 12.1-RELEASE.
The solution that worked for me was to forcibly remove pkg

Code: 

root@server:/var/db/pkg # pkg update -f
Updating FreeBSD repository catalogue...
pkg: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0
Fetching meta.txz: 100%    916 B   0.9kB/s    00:01
pkg: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
repository FreeBSD has no meta file, using default settings
Fetching packagesite.txz: 100%    6 MiB  70.9kB/s    01:31
pkg: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0
Unable to open created repository FreeBSD
Unable to update repository FreeBSD
Error updating repositories!
root@server:/var/db/pkg # pkg add -f https://pkg.freebsd.org/FreeBSD:12:amd64/latest/All/pkg-1.14.2.txz
Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
34374852608:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
34374852608:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
Certificate verification failed for /C=US/O=Let's


root@server:/var/db/pkg # pkg delete -f pkg
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
    pkg-1.10.5_5

Number of packages to be removed: 1

The operation will free 13 MiB.

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling pkg-1.10.5_5...
[1/1] Deleting files for pkg-1.10.5_5: 100%
root@server:/var/db/pkg # pkg update -f pkg
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/quarterly, please wait...
Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done
Installing pkg-1.13.2...
Extracting pkg-1.13.2: 100%
Usage: pkg update [-fq] [-r reponame]

For more information, see 'pkg help update'.
root@server:/var/db/pkg # pkg update
Updating FreeBSD repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.txz: 100%    6 MiB 280.4kB/s    00:23
Processing entries: 100%
FreeBSD repository update completed. 31492 packages processed.
All repositories are up to date.
root@server:/var/db/pkg # pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Updating database digests format: 100%
Checking for upgrades (19 candidates): 100%
Processing candidates (19 candidates): 100%
The following 19 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
    python37: 3.7.7

Installed packages to be UPGRADED:
    fusefs-libs: 2.9.7 -> 2.9.9_1
    gawk: 4.1.4_3 -> 5.0.0
    gettext-runtime: 0.19.8.1_2 -> 0.20.1
    glib: 2.56.3_2,1 -> 2.56.3_7,1
    haproxy: 1.8.17 -> 2.0.13
    icu: 63.1_1,1 -> 66.1,1
    libdnet: 1.12_1 -> 1.13_3
    libmspack: 0.9.1 -> 0.10.1
    libssh2: 1.8.0,3 -> 1.8.2,3
    libxml2: 2.9.7 -> 2.9.10
    nginx: 1.14.2_3,2 -> 1.16.1_12,2
    open-vm-tools-nox11: 10.3.0_1,2 -> 11.0.1_3,2
    pcre: 8.42_1 -> 8.43_2
    perl5: 5.28.1 -> 5.30.2
    postfix: 3.3.3,1 -> 3.5.0,1
    python27: 2.7.15 -> 2.7.17_1
    readline: 7.0.5 -> 8.0.4
    sudo: 1.8.27 -> 1.8.31p1

Number of packages to be installed: 1
Number of packages to be upgraded: 18

The process will require 114 MiB more space.
62 MiB to be downloaded.

Same thing for me 12.0 to 12.1 and removing and then bootstrapping worked! Thanks!

  • #24

This seems to be a chronic problem with 12.0 to 12.1 upgrades. I had 3 systems so far exhibit the same problem. The solution is

Code: 

pkg bootstrap -f
pkg update -f

Then you can proceed with pkg upgrade -fy as requested by freebsd-update()
(I figured I might as well add this for myself and others since this post is the first/second result on search engines)

Last edited: Aug 19, 2020

  • #25

I had the same problem , seems pkg bootstrap -f solve it. Thank you.

Источник

Jun 01, 2020


I work at Microsoft, and with that, I get free
Azure credits.

Considering where I work, I have no use for FreeBSD at work, only Windows.
However, I spent seven years of my life prior to getting $DAYJOB using
FreeBSD, going back to high school and basically built my personal setup on
it. I haven’t bothered to switch my personal desktop or home server to
Windows (yet*), so I’ll create a FreeBSD VM in Azure and try to update it.

If I create a FreeBSD VM in Azure and update, I get pkg errors as follows:

root@Inst1:/usr/home/neel # pkg upgrade
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%    916 B   0.9kB/s    00:01    
pkg: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
repository FreeBSD has no meta file, using default settings
Fetching packagesite.txz: 100%    6 MiB   6.5MB/s    00:01    
pkg: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0
Unable to open created repository FreeBSD
Unable to update repository FreeBSD
Error updating repositories!
root@Inst1:/usr/home/neel #

To fix, this you need to re-bootstrap pkg as follows:

root@Inst1:/usr/home/neel # pkg-static bootstrap -f
pkg(8) is already installed. Forcing reinstallation through pkg(7).
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/quarterly, please wait...
Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done
Installing pkg-1.13.2...
package pkg is already installed, forced install
Extracting pkg-1.13.2: 100%
root@Inst1:/usr/home/neel #

And then update as normal:

root@Inst1:/usr/home/neel # pkg update -f
Updating FreeBSD repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01    
Fetching packagesite.txz: 100%    6 MiB   3.3MB/s    00:02    
Processing entries: 100%
FreeBSD repository update completed. 31517 packages processed.
All repositories are up to date.
root@Inst1:/usr/home/neel # pkg upgrade
Updaing FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
...
Proceed with this action? [y/N]: y
...

I do recommend updating to a non-EOL release first, as the Azure images may
be out of date, as they are for 12.x.

At the time of writing, I don’t work on Azure, so I have no say in how often
FreeBSD images are updated.

* — Personal desktop/laptop does dual-boot Windows 10 and FreeBSD CURRENT

Источник

Содержание

  1. Solved pkg update returns in Permission denied and No route to host
  2. hilda
  3. SirDice
  4. hilda
  5. PKG ERROR
  6. coutter
  7. SirDice
  8. Unsupported FreeBSD Releases
  9. jimeha
  10. Deleted member 66267
  11. pkgsrc
  12. jimeha
  13. zirias@
  14. SirDice
  15. T-Daemon
  16. SirDice
  17. zirias@
  18. T-Daemon
  19. jimeha

Solved pkg update returns in Permission denied and No route to host

hilda

Hi,
I have problems with two FreeBSD 11.2-RELEASE-p8 prod machines when I try to run “pkg update”. The two machines is pretty much the same as one is master an the other is slave. They only get files from other servers via scp every hour and analyse them with some scripts, that’s it.

I installed 11.1 before and updated to 11.2 for some month ago. Everything worked perfect for some time with the updates etc. Recently, I can’t run “pkg update” any more. Freebsd-update fetch etc. works, it’s only pkg that’s is the problem.

On one machine I get:

I got the same on the other machine before (I think) and tried to reinstall pkg, but it won’t work. So I get this:

This is the info of the machines:

I have tried # pkg -o OSVERSION=1102000 update -f but no luck.

In /usr/local/etc/pkg.conf I tried:

The servers have deleted /var/db/pkg/repo-FreeBSD.sqlite. I have one backup repo-FreeBSD.sqlite.xz on one server, and I tried it, doesn’t work.

I have url: «pkg+http://pkg.FreeBSD.org/$/latest», in /etc/pkg/FreeBSD.conf .

DNS etc. works fine on the servers.

Does someone have some tip?

SirDice

Administrator

«No route to host» means you’re not online or there’s a firewall blocking your outgoing traffic. «Permission denied» might be caused by a proxy on your network.

hilda

Tnx for the answer… Did some tests here.

(OK… you can skip this section if you don’t want to read about my stupid…. Yheaaa.. the fix is in the last section)

My dmz-customer-net is back off multiply firewalls there I don’t control all of them.. The easiest way to control it was to set up a new machine on the same net, and it worked! No problem with any firewall or proxy.

I scp the brand new repo-FreeBSD.sqlite to one of the broken machine. I also made the /use/local/etc/pkg/repos/FreeBSD.conf file with:

Now I have 3 FreeBSD 11.2 boxes side by side (same net, same nameservers etc.). 2 is broken (old ones) and one with a clean install that work with pkg update. Same uname -a/UK.

The net (and applications) on the two broken machines work perfectly, it’s only # pkg update I get No route to host.

[The Fix]
In the middle when I write this.. Can it be my pf on the box? I have tcpdump with fplog0 running and nothing (I log more or less everything). But I have some heavy rules so I disable them with # pfctl -d and bam… it worked..

A couple a mount without pkg update and struggling to get it on track.. my own pf.. stupid stupid stupid…. You never ever learn.

So something had happen with the package repo, pf or something else. Time to go through the pf rules.

Tnx for the help.. sometime you need a kick somewhere.

Источник

PKG ERROR

coutter

When trying to run
pkg update && pkg upgrade -y
I get this error:
I tried several methods to solve this and none of them worked out. I’m kinda lost here.

SirDice

Administrator

The entire 10 branch is end-of-life and not supported any more.

Unsupported FreeBSD Releases

jimeha

Deleted member 66267

Guest

I don’t know if anything like that exists. The only thing that works is pkgsrc, which is designed just for this: continue the life of legacy systems!

pkgsrc

jimeha

Apologies for the delayed reply, life in the way. So for much older versions we still have ftp-archive.freebsd.org for versions 1.x through 9.x (on i386) and 5.x ot 9.x (on amd64). But on pkg.freebsd.org, 10.x has been wiped, so now we have a gap then 11+? I would’ve hoped FreeBSD would keep this available on some archive server, just like the older versions. That’s very unfortunate.

I glanced at pkgsrc, but that does seem to involve having to build all of ports at least once, or a portion of it if we want to be able to do final updates to our BSD 10.x systems, before they eventually migrate to 12.x or newer. Is there really no pkg archive of 10.x? Will 1.x through 9.x eventually disappear too then if the move is to only ‘new’ supported stuff to be available from pkg?

zirias@

Cause EOL always hits you like lightning in a clear sky, right?

Operating EOL systems is dangerous, you should never do it, so there’s no point in providing any support for shooting your foot. You can always fetch ports trees from ages ago and build yourself what you need if you insist, but the only sane way is: upgrade.

Reactions: Deleted member 30996

SirDice

Administrator

Those never existed.

There are archives of the releases. Some of those included packages. But they are packages that were built at the time of the release (you could find those included on the CD/DVD images). They are not the ‘last’ builds of that release.

T-Daemon

SirDice

Administrator

zirias@

T-Daemon

jimeha

Those never existed.

There are archives of the releases. Some of those included packages. But they are packages that were built at the time of the release (you could find those included on the CD/DVD images). They are not the ‘last’ builds of that release.

My fault that one; bad comparison then. I suppose a portion of my argument is also for consistency. One could, in theory (not recommended, yes, I know), install an older FreeBSD version right now and set PACKAGESITE to ftp-archive.freebsd.org so pkg_add et al work. Currently, I see no way to do that with, for example, FreeBSD 10.x and pkg without building ports and pointing pkg at that after setting up a frontend to my internal builds that were built and packaged nicely. The pkg.freebsd.org system just doesn’t have FreeBSD:10:amd64 (released or latest) and others anymore, only supported 12.x, etc, releases. This seems like a miss in consistency vs older FreeBSD versions unless this new practice for maintaining pkg.freebsd.org is posted somewhere I haven’t found yet which is entirely possible.

Zirias absolutely agree with your overall premise: 100% use new *supported* releases when possible. Badger those who ‘need’ the old systems to upgrade. However, I’m sure I’m not the only one trying to maintain an old server though for «reasons» by attempting to patch in the very last released builds of a package(s) as an attempt to update it ‘a little bit’ before that OS upgrade oppotunity comes. I had managed to upgrade several before FreeBSD:10:amd64 disappeared, was going to do more of them, but can’t.

Источник

Источник

Содержание

  1. PKG ERROR
  2. coutter
  3. SirDice
  4. Unsupported FreeBSD Releases
  5. jimeha
  6. Deleted member 66267
  7. pkgsrc
  8. jimeha
  9. zirias@
  10. SirDice
  11. T-Daemon
  12. SirDice
  13. zirias@
  14. T-Daemon
  15. jimeha
  16. sqlite error during update
  17. erdos
  18. Martin Paredes
  19. erdos
  20. richardtoohey2
  21. SirDice
  22. erdos
  23. Solved pkg update returns in Permission denied and No route to host
  24. hilda
  25. SirDice
  26. hilda
  27. Solved Non-recoverable resolver failure
  28. Fbsdnew
  29. Emrion
  30. Fbsdnew
  31. Emrion
  32. SirDice
  33. Fbsdnew
  34. Fbsdnew
  35. Fbsdnew
  36. Fbsdnew
  37. ralphbsz
  38. Fbsdnew
  39. ralphbsz

PKG ERROR

coutter

When trying to run
pkg update && pkg upgrade -y
I get this error:
I tried several methods to solve this and none of them worked out. I’m kinda lost here.

SirDice

Administrator

The entire 10 branch is end-of-life and not supported any more.

Unsupported FreeBSD Releases

jimeha

Deleted member 66267

Guest

I don’t know if anything like that exists. The only thing that works is pkgsrc, which is designed just for this: continue the life of legacy systems!

pkgsrc

jimeha

Apologies for the delayed reply, life in the way. So for much older versions we still have ftp-archive.freebsd.org for versions 1.x through 9.x (on i386) and 5.x ot 9.x (on amd64). But on pkg.freebsd.org, 10.x has been wiped, so now we have a gap then 11+? I would’ve hoped FreeBSD would keep this available on some archive server, just like the older versions. That’s very unfortunate.

I glanced at pkgsrc, but that does seem to involve having to build all of ports at least once, or a portion of it if we want to be able to do final updates to our BSD 10.x systems, before they eventually migrate to 12.x or newer. Is there really no pkg archive of 10.x? Will 1.x through 9.x eventually disappear too then if the move is to only ‘new’ supported stuff to be available from pkg?

zirias@

Cause EOL always hits you like lightning in a clear sky, right?

Operating EOL systems is dangerous, you should never do it, so there’s no point in providing any support for shooting your foot. You can always fetch ports trees from ages ago and build yourself what you need if you insist, but the only sane way is: upgrade.

Reactions: Deleted member 30996

SirDice

Administrator

Those never existed.

There are archives of the releases. Some of those included packages. But they are packages that were built at the time of the release (you could find those included on the CD/DVD images). They are not the ‘last’ builds of that release.

T-Daemon

SirDice

Administrator

zirias@

T-Daemon

jimeha

Those never existed.

There are archives of the releases. Some of those included packages. But they are packages that were built at the time of the release (you could find those included on the CD/DVD images). They are not the ‘last’ builds of that release.

My fault that one; bad comparison then. I suppose a portion of my argument is also for consistency. One could, in theory (not recommended, yes, I know), install an older FreeBSD version right now and set PACKAGESITE to ftp-archive.freebsd.org so pkg_add et al work. Currently, I see no way to do that with, for example, FreeBSD 10.x and pkg without building ports and pointing pkg at that after setting up a frontend to my internal builds that were built and packaged nicely. The pkg.freebsd.org system just doesn’t have FreeBSD:10:amd64 (released or latest) and others anymore, only supported 12.x, etc, releases. This seems like a miss in consistency vs older FreeBSD versions unless this new practice for maintaining pkg.freebsd.org is posted somewhere I haven’t found yet which is entirely possible.

Zirias absolutely agree with your overall premise: 100% use new *supported* releases when possible. Badger those who ‘need’ the old systems to upgrade. However, I’m sure I’m not the only one trying to maintain an old server though for «reasons» by attempting to patch in the very last released builds of a package(s) as an attempt to update it ‘a little bit’ before that OS upgrade oppotunity comes. I had managed to upgrade several before FreeBSD:10:amd64 disappeared, was going to do more of them, but can’t.

Источник

sqlite error during update

erdos

hi, i’m running 12.0-release-p5 on a HP desktop PC. Today when I tried to update Kodi, the system failed and rebooted.

During the reboot process, core crash file was created and dumped into /var/crash/ folder. I deleted the core, tried to rerun
pkg update and freebsd-update fetch install , but received the following error.

Martin Paredes

In my case (updating OPNsense), it was a problem with the index of the database of pkg system

What is the output of the .selftest command inside of SQLite?

erdos

Thanks, I followed steps above and was able to go past ‘pkg update’

it looks that my local.sqlite is damaged. I did a flurry string of fix following online instructions, in the process, I recreated the local.sqlite file with my regular username,

but when running ‘freebsd-update fetch’,
«fetching metadata signature for 12.0-RELEASE from update4.freebsd.org. done.
Fetching metadata index. done.
Inspecting system.. done
‘Preparing to download files. done.
(END)

Then it stuck and I have to ‘Control + Z’ to quit.

when i run ‘pkg instal kodi’, error is
‘pkg: /var/db/pkg/local.sqlite wrong user or group ownership (expected 0/0 versus actual 1001/1001)

crash log created during reboot —
‘/var/crash/core.txt.9’

«BFD: /boot/kernel/kernel: invalid relocation type 42
BFD: /boot/kernel/kernel: invalid relocation type 42
BFD: /boot/kernel/kernel: invalid relocation type 42
/dev/stdin:1: Error in sourced command file:
Cannot access memory at address 0x65657246
BFD: /boot/kernel/kernel: invalid relocation type 42
BFD: /boot/kernel/kernel: invalid relocation type 42
BFD: /boot/kernel/kernel: invalid relocation type 42
/dev/stdin:1: Error in sourced command file:
Cannot access memory at address 0x65657246
/dev/stdin:1: Error in sourced command file:
Cannot access memory at address 0x65657246
Unable to find matching kernel for /var/crash/vmcore.9″

how to fix this?

richardtoohey2

Can’t answer all of it but

pkg: /var/db/pkg/local.sqlite wrong user or group ownership (expected 0/0 versus actual 1001/1001)

0/0 is user/group root/wheel. You said earlier you created it under your own login — that will be user/group 1001/1001.

So I think that you will need to change the user & group on the local.sqlite file to root/wheel.

But that might be the least of your problems if you can’t reboot.

From your original message — No address record suggests DNS or network errors.

Maybe separate this into two tasks — can you complete the freebsd-update and reboot? Once that is cleaned and working, next look at the pkg issue(s).

SirDice

Administrator

You’re not connected or your name resolving is broken.

erdos

Thanks! I fixed the sqlite error during ‘pkg update’ and upgraded system to 12.1 release

now i’m on 12.1 release, but receiving following error whenever i run ‘pkg upgrade’

Источник

Solved pkg update returns in Permission denied and No route to host

hilda

Hi,
I have problems with two FreeBSD 11.2-RELEASE-p8 prod machines when I try to run “pkg update”. The two machines is pretty much the same as one is master an the other is slave. They only get files from other servers via scp every hour and analyse them with some scripts, that’s it.

I installed 11.1 before and updated to 11.2 for some month ago. Everything worked perfect for some time with the updates etc. Recently, I can’t run “pkg update” any more. Freebsd-update fetch etc. works, it’s only pkg that’s is the problem.

On one machine I get:

I got the same on the other machine before (I think) and tried to reinstall pkg, but it won’t work. So I get this:

This is the info of the machines:

I have tried # pkg -o OSVERSION=1102000 update -f but no luck.

In /usr/local/etc/pkg.conf I tried:

The servers have deleted /var/db/pkg/repo-FreeBSD.sqlite. I have one backup repo-FreeBSD.sqlite.xz on one server, and I tried it, doesn’t work.

I have url: «pkg+http://pkg.FreeBSD.org/$/latest», in /etc/pkg/FreeBSD.conf .

DNS etc. works fine on the servers.

Does someone have some tip?

SirDice

Administrator

«No route to host» means you’re not online or there’s a firewall blocking your outgoing traffic. «Permission denied» might be caused by a proxy on your network.

hilda

Tnx for the answer… Did some tests here.

(OK… you can skip this section if you don’t want to read about my stupid…. Yheaaa.. the fix is in the last section)

My dmz-customer-net is back off multiply firewalls there I don’t control all of them.. The easiest way to control it was to set up a new machine on the same net, and it worked! No problem with any firewall or proxy.

I scp the brand new repo-FreeBSD.sqlite to one of the broken machine. I also made the /use/local/etc/pkg/repos/FreeBSD.conf file with:

Now I have 3 FreeBSD 11.2 boxes side by side (same net, same nameservers etc.). 2 is broken (old ones) and one with a clean install that work with pkg update. Same uname -a/UK.

The net (and applications) on the two broken machines work perfectly, it’s only # pkg update I get No route to host.

[The Fix]
In the middle when I write this.. Can it be my pf on the box? I have tcpdump with fplog0 running and nothing (I log more or less everything). But I have some heavy rules so I disable them with # pfctl -d and bam… it worked..

A couple a mount without pkg update and struggling to get it on track.. my own pf.. stupid stupid stupid…. You never ever learn.

So something had happen with the package repo, pf or something else. Time to go through the pf rules.

Tnx for the help.. sometime you need a kick somewhere.

Источник

Solved Non-recoverable resolver failure

Fbsdnew

#pkg update -f
Updating FreeBSD repository catalogue.
pkg: http://pkg.freebsd.org/FreeBSD:12:i386/latest/meta.txz: Non-recoverable resolver failure
repository FreeBSD has no meta file, using default settings
pkg: http://pkg.freebsd.org/FreeBSD:12:i386/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository FreeBSD
Error updating repositories!

Emrion

Fbsdnew

Host pkg.freebsd.org not found: 2(SERVFAIL)

resolve.conf:
# Generated by resolvconf
search Home
# nameserver 192.168.0.1
# nameserver 205.171.3.25

nameserver 127.0.0.1
options edns0

Emrion

SirDice

Administrator

Fbsdnew

Fbsdnew

Fbsdnew

Fbsdnew

ralphbsz

You have to have the IP address of a functioning DNS server in your resolv.conf. This has very little to do with hardware, source, or downloads. Simple test: Can you do «host www.yahoo.com» from a command line? How about «dig forums.freebsd.org» from the same command line? Both need to work perfectly.

Here is a functioning resolv.conf:

To begin with, you need to set a sensible domain. «Home» will work, but «example.com» will work better (it has the correct format, and is known to the worldwide name service infrastructure, without resolving to a concrete host). Then you need the IP address of a functioning DNS server. Probably the best choices are 8.8.8.8 (available pretty much worldwide, and hardly ever filtered), and usually also 1.1.1.1 and 9.9.9.9. Once you have that, try «ping 8.8.8.8». If that fails, you have a more basic networking problem (lack of connectivity). If it works, you should have a functioning (barebones, ineffecient, but functioning) resolv.conf, and can make forward progress.

Also: You need to understand some networking fundamentals. The fact that you blame the lack of resolver configuration on unsupported hardware, and continue trying to update even when your networking isn’t working tells me that you need to learn a few things before attempting to manage a system.

Reactions: gutiersa

Fbsdnew

You have to have the IP address of a functioning DNS server in your resolv.conf. This has very little to do with hardware, source, or downloads. Simple test: Can you do «host www.yahoo.com» from a command line? How about «dig forums.freebsd.org» from the same command line? Both need to work perfectly.

Here is a functioning resolv.conf:

To begin with, you need to set a sensible domain. «Home» will work, but «example.com» will work better (it has the correct format, and is known to the worldwide name service infrastructure, without resolving to a concrete host). Then you need the IP address of a functioning DNS server. Probably the best choices are 8.8.8.8 (available pretty much worldwide, and hardly ever filtered), and usually also 1.1.1.1 and 9.9.9.9. Once you have that, try «ping 8.8.8.8». If that fails, you have a more basic networking problem (lack of connectivity). If it works, you should have a functioning (barebones, ineffecient, but functioning) resolv.conf, and can make forward progress.

Also: You need to understand some networking fundamentals. The fact that you blame the lack of resolver configuration on unsupported hardware, and continue trying to update even when your networking isn’t working tells me that you need to learn a few things before attempting to manage a system.

ralphbsz

Please read what the lines in resolv.conf really mean. For example, let’s begin with the «search» line. If you have multiple machines on your network (let’s call them for fun server, desktop and laptop), and they are all in a common domain (for example mydomain.example.com), then it is convenient to be able to say things like «ssh desktop» or «http://server/status.html». Normally, any name resolution requires a full domain name, so to connect to your desktop you would have to do «ssh desktop.mydomain.example.com», but the search line allows that to be shortened to just «ssh desktop». In a nutshell, the search line means: If you try to find a host and only use a short name, then append this domain name to it and try again.

The nameserver line is pretty self-explanatory: It’s just the IP address of a functioning name server.

Источник

Источник

Модератор: terminus

Правила форума
Убедительная просьба юзать теги [cоde] при оформлении листингов.
Сообщения не оформленные должным образом имеют все шансы быть незамеченными.

irr

проходил мимо
Сообщения: 4
Зарегистрирован: 2009-08-20 5:36:05

перестал работать pkg update на куче серверов с FreeBSD 10

Привет всем!

Сегодня 14.07 в районе 14:00 по московскому времени на всех серверах с FreeBSD 10 перестала работать команда

Код: Выделить всё

# pkg update
Updating FreeBSD repository catalogue...
pkg: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory
pkg: http://pkg.FreeBSD.org/FreeBSD:10:amd64/quarterly/meta.txz: Not Found
repository FreeBSD has no meta file, using default settings
pkg: http://pkg.FreeBSD.org/FreeBSD:10:amd64/quarterly/packagesite.txz: Not Found
Unable to update repository FreeBSD
Error updating repositories!

Эта же команда нормально работает на серверах с FreeBSD 9 и FreeBSD 11. Проблема именно на 10-й версии.

Кто-нибудь в курсе, как лечить?
Создается впечатление, что проблема глобальная, т.к. возникла сразу на многих серверах.
Проверьте у себя тоже.

Хостинговая компания Host-Food.ru

Хостинг HostFood.ru

 

Услуги хостинговой компании Host-Food.ru

Хостинг HostFood.ru

Тарифы на хостинг в России, от 12 рублей: https://www.host-food.ru/tariffs/hosting/
Тарифы на виртуальные сервера (VPS/VDS/KVM) в РФ, от 189 руб.: https://www.host-food.ru/tariffs/virtualny-server-vps/
Выделенные сервера, Россия, Москва, от 2000 рублей (HP Proliant G5, Intel Xeon E5430 (2.66GHz, Quad-Core, 12Mb), 8Gb RAM, 2x300Gb SAS HDD, P400i, 512Mb, BBU):
https://www.host-food.ru/tariffs/vydelennyi-server-ds/
Недорогие домены в популярных зонах: https://www.host-food.ru/domains/

Аватара пользователя

Alex Keda

стреляли…
Сообщения: 35413
Зарегистрирован: 2004-10-18 14:25:19
Откуда: Made in USSR
Контактная информация:

перестал работать pkg update на куче серверов с FreeBSD 10

Непрочитанное сообщение

Alex Keda » 2017-09-20 7:10:16

Подождать недолго? :)

Убей их всех! Бог потом рассортирует…

irr

проходил мимо
Сообщения: 4
Зарегистрирован: 2009-08-20 5:36:05

перестал работать pkg update на куче серверов с FreeBSD 10

Непрочитанное сообщение

irr » 2017-09-25 13:35:25

Да, в тот же вечер все само заработало. Зря запакниковал.

on-lite

проходил мимо
Сообщения: 3
Зарегистрирован: 2014-02-25 15:14:25

перестал работать pkg update на куче серверов с FreeBSD 10

Непрочитанное сообщение

on-lite » 2021-03-18 14:00:08

Та же самая проблема, FreeSD 10.3.

pkg: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory

уже невозможно что-то установить нового?

guest

проходил мимо

перестал работать pkg update на куче серверов с FreeBSD 10

Непрочитанное сообщение

guest » 2021-03-18 14:13:51

Та же самая проблема, FreeSD 10.3.

pkg: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory

уже невозможно что-то установить нового?

Вы с луны свалились? 10’ка уже много времени не поддерживается и пакеты
для нее в репозитории отсутствуют:
http://pkg.freebsd.org/
зайдите и убедитесь сами.

on-lite

проходил мимо
Сообщения: 3
Зарегистрирован: 2014-02-25 15:14:25

перестал работать pkg update на куче серверов с FreeBSD 10

Непрочитанное сообщение

on-lite » 2021-03-18 14:55:19

guest писал(а): ↑

2021-03-18 14:13:51


Вы с луны свалились?

Что ж так грубо.

теперь мне ничего не остаётся, как качать образ FreeBSD 12 или более воздний и поднимать сервер с нуля :(
думал что фряха наиболее стабильная и поддерживается до первых версий.

snorlov

подполковник
Сообщения: 3918
Зарегистрирован: 2008-09-04 11:51:25
Откуда: Санкт-Петербург

перестал работать pkg update на куче серверов с FreeBSD 10

Непрочитанное сообщение

snorlov » 2021-03-18 17:17:40

on-lite писал(а): ↑

2021-03-18 14:55:19


теперь мне ничего не остаётся, как качать образ FreeBSD 12 или более воздний и поднимать сервер с нуля :(
думал что фряха наиболее стабильная и поддерживается до первых версий.

Зачем с нуля то, взяли да и обновились или из исходников или бинарно через freebsd-update, следующая ветка (правда там версия 11.4, считай последняя в ветке) еще поддерживается. Самая большая трудность будет наверное в обновлении пакаджей, ну так включение извилин в любом случае придется делать…

guest

проходил мимо

перестал работать pkg update на куче серверов с FreeBSD 10

Непрочитанное сообщение

guest » 2021-03-18 18:21:15

Зачем с нуля то, взяли да и обновились или из исходников или бинарно через freebsd-update, следующая ветка (правда там версия 11.4, считай последняя в ветке) еще поддерживается. Самая большая трудность будет наверное в обновлении пакаджей, ну так включение извилин в любом случае придется делать…
Вернуться к началу

самое правильное и быстрое — это именно с нуля.
Не нужно включать извилины и иметь мозг с обновлением пакетов, обновить их вряд ли удастся,
а времени и геморроя займет немеряно и приведет к простому решению:
установить 12.2 со всем необходимым софтом, и будет это на порядок быстрей.

serzh

рядовой
Сообщения: 29
Зарегистрирован: 2014-08-05 14:20:30

перестал работать pkg update на куче серверов с FreeBSD 10

Непрочитанное сообщение

serzh » 2021-09-28 14:51:40

неоднократно обновлялся между мажорными версиями с помощью freebsd-update, проблем как правило не возникало. если что-то и ломалось то почти всё удалось починить. pkg upgrade проходит без проблем, главное не обновляться через релиз, с 8 на 10 обновление прошло, но ничего не работало после загрузки 8 версии с 10 ядром, пришлось откатываться и обновлять через 9

WideAreaNetwork

сержант
Сообщения: 225
Зарегистрирован: 2017-01-10 14:37:13

перестал работать pkg update на куче серверов с FreeBSD 10

Непрочитанное сообщение

WideAreaNetwork » 2022-01-06 21:51:34

guest писал(а): ↑

2021-03-18 18:21:15


а времени и геморроя займет немеряно и приведет к простому решению:
установить 12.2 со всем необходимым софтом, и будет это на порядок быстрей.

у меня на одном сервере где биллинг крутится столько всего настраивалось, что уже и не упомяну, и получается что легче помучится чем с нуля, кому как подходит, правда я стараюсь почти во время делать обновления, проблемы пока вылазили маленькие, с ipfw и MySQL , пока удавалась собственными силами фиксить их

Источник

45 / 6 / 1

Регистрация: 19.02.2013

Сообщений: 153

1

03.03.2017, 04:59. Показов 11458. Ответов 2

pkg: Warning: Major OS version upgrade detected. Running «pkg-static install -f pkg» recommended

Запускаю

pkg-static install -f pkg

Получаю

pkg-static: Warning: Major OS version upgrade detected. Running «pkg-static install -f pkg» recommended
Updating FreeBSD repository catalogue…
pkg-static: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory
pkg-static: http://pkg.FreeBSD.org/FreeBSD… /meta.txz: No route to host
repository FreeBSD has no meta file, using default settings
pkg-static: http://pkg.FreeBSD.org/FreeBSD… esite.txz: No route to host
Unable to update repository FreeBSD
Error updating repositories!

дёргаю этот файл руками
wget http://pkg.FreeBSD.org/FreeBSD… y/meta.txz
получаю

Распознаётся pkg.freebsd.org (pkg.freebsd.org)… 77.88.40.109
Подключение к pkg.freebsd.org (pkg.freebsd.org)|77.88.40.109|:80… ошибка: Недостаточно привилегий.
Повтор.

—2017-03-03 06:58:20— (попытка: 2) http://pkg.freebsd.org/FreeBSD… y/meta.txz
Подключение к pkg.freebsd.org (pkg.freebsd.org)|77.88.40.109|:80… ошибка: Недостаточно привилегий.
Повтор.

чё за фигня? почему не могу подключиться?

__________________
Помощь в написании контрольных, курсовых и дипломных работ, диссертаций здесь



0

Эксперт Hardware

6080 / 3579 / 305

Регистрация: 13.02.2014

Сообщений: 13,374

04.03.2017, 14:24

2

Проверь, не слетел ли маршрут по умолчанию.



0

45 / 6 / 1

Регистрация: 19.02.2013

Сообщений: 153

06.03.2017, 04:22

 [ТС]

3

ipfw отрубил — пошло дело



0

IT_Exp

Эксперт

87844 / 49110 / 22898

Регистрация: 17.06.2006

Сообщений: 92,604

 06.03.2017, 04:22

Помогаю со студенческими работами здесь

VirtualBox Host-only (host windows 7 х64 после установки обновлений перестал видеть guest ubuntu)
Доброго времени суток всем!

Нормально работали виртуальные машины, пока не захотелось мне…

Не могу обновить RecyclerView после изменения item
данные для списка берутся из Firebase,

у DatabaseReference//Firebase, есть два метода:
…

Не могу обновить программу стим после установки
У меня есть одна проблема. Значит скачал я стим, запускаю, он начинает обновляться , доходит до…

После обновления не могу зайти в нэт!
Обновила Mozilla Firefox,комп начал виснуть,перезагрузила,торрент работает…..Опера,Mozilla…

Не могу запустить скайп после обновления
здравствуйте уважаемые программисты . я новичок и у меня проблемы , у меня домашний ПК уже более 10…

Не могу установить режим b/g/n (после обновления)
У меня два роутера mikrotik RB951G-2HnD.

Пару дней назад обновил прошивку до последней версии…

Искать еще темы с ответами

Или воспользуйтесь поиском по форуму:

3

Источник

Понравилась статья? Поделить с друзьями:
  • Error update or delete on table violates foreign key constraint
  • Error update aborted при прошивке видеокарты
  • Error update aborted перевод
  • Error update aborted nvflash
  • Error unused parameter