This is what I get when I do sudo pacman -Syu. Any help would be deeply appreciated.

:: Synchronizing package databases...

error: failed retrieving file 'core.db' from mirror3.layerjet.com : Failed to connect to mirror3.layerjet.com port 80: Network is unreachable

error: failed retrieving file 'core.db' from mirror.dacentec.com : Failed to connect to mirror.dacentec.com port 80: Network is unreachable

core is up to date

error: failed retrieving file 'main.db' from mirror3.layerjet.com : Failed to connect to mirror3.layerjet.com port 80: Network is unreachable

error: failed retrieving file 'main.db' from mirror.dacentec.com : Failed to connect to mirror.dacentec.com port 80: Network is unreachable

main is up to date

error: failed retrieving file 'apps.db' from mirror3.layerjet.com : Failed to connect to mirror3.layerjet.com port 80: Network is unreachable

error: failed retrieving file 'apps.db' from mirror.dacentec.com : Failed to connect to mirror.dacentec.com port 80: Network is unreachable

apps is up to date

:: Starting full system upgrade...

resolving dependencies...

looking for inter-conflicts...

A couple of things to check, to see what is stuck.

Run 'mirror-check' see if that connects.

sudo pacman -Syy, to force syncing of your pacman datatbases

If that doesn't help, make sure to save all packages you want to keep from your /var/cache/pacman/pkg cache and run:

sudo pacman -Scc answer 'yes' to questions asked.

If that doesn't fix it, then post both your /etc/pacman.conf and /etc/pacman.d/mirrorlist

after mirror-check

Checking core main apps...

[core] is synced.

[main] is synced.

[apps] is synced.

After sudo pacman -Syy

:: Synchronizing package databases...

error: failed retrieving file 'core.db' from mirror3.layerjet.com : Failed to connect to mirror3.layerjet.com port 80: Network is unreachable

error: failed retrieving file 'core.db' from mirror.dacentec.com : Failed to connect to mirror.dacentec.com port 80: Network is unreachable

core is up to date

error: failed retrieving file 'main.db' from mirror3.layerjet.com : Failed to connect to mirror3.layerjet.com port 80: Network is unreachable

error: failed retrieving file 'main.db' from mirror.dacentec.com : Failed to connect to mirror.dacentec.com port 80: Network is unreachable

main is up to date

error: failed retrieving file 'apps.db' from mirror3.layerjet.com : Failed to connect to mirror3.layerjet.com port 80: Network is unreachable

error: failed retrieving file 'apps.db' from mirror.dacentec.com : Failed to connect to mirror.dacentec.com port 80: Network is unreachable

apps is up to date

:: Starting full system upgrade...

resolving dependencies...

looking for inter-conflicts...

I'm not comfortable to do the third bit unless you lead me step by step :

Thanks.

Nothing step by step, either you want to save your cache or not (only useful if you ever want to downgrade a package).

pacman -Scc removes old packages and cleans the databases.

pacman.conf

#

# /etc/pacman.conf

#

# See the pacman.conf(5) manpage for option and repository directives

#

# GENERAL OPTIONS

#

[options]

# The following paths are commented out with their default values listed.

# If you wish to use different paths, uncomment and update the paths.

#RootDir = /

#DBPath = /var/lib/pacman/

#CacheDir = /var/cache/pacman/pkg/

#LogFile = /var/log/pacman.log

HoldPkg = pacman glibc pacman-helpme

#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u

#XferCommand = /usr/bin/curl %u > %o

#CleanMethod = KeepInstalled

#UseDelta = 0.7

Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup

IgnorePkg =

#IgnoreGroup =

#NoUpgrade =

#NoExtract =

# Misc options (all disabled by default)

#NoPassiveFtp

#UseSyslog

Color

#TotalDownload

CheckSpace

VerbosePkgLists

ILoveCandy

# By default, pacman accepts packages signed by keys that its local keyring

# trusts (see pacman-key and its man page), as well as unsigned packages.

SigLevel = Never

LocalFileSigLevel = Never

#RemoteFileSigLevel = Required

#

# REPOSITORIES

# - can be defined here or included from another file

# - pacman will search repositories in the order defined here

# - local/custom mirrors can be added here or in separate files

# - repositories listed first will take precedence when packages

# have identical names, regardless of version number

# - URLs will have $repo replaced by the name of the current repo

#

# Repository entries are of the format:

# [repo-name]

# Server = ServerName

# Include = IncludePath

#

# The header [repo-name] is crucial - it must be present and

# uncommented to enable the repo.

#

[core]

Include = /etc/pacman.d/mirrorlist

[main]

Include = /etc/pacman.d/mirrorlist

[apps]

Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository. See the pacman manpage for

# tips on creating your own repositories.

#[custom]

#Server = file:///home/custompkgs

mirrorlist

#

# KaOS repository mirrorlist

#

# Germany

Server = http://mirror3.layerjet.com/kaos/$repo

# United States

Server = http://mirror.dacentec.com/kaosx/$repo

Server = http://kaosx.us/repo/$repo

Yes, I did. As you can see, I entered the default options (so, N for the first and Y for the second). The cache is around 4.2gb and I was scared I would have to download all of it again!

Cache directory: /var/cache/pacman/pkg/

:: Do you want to remove ALL files from cache? [y/N]

Database directory: /var/lib/pacman/

:: Do you want to remove unused repositories? [Y/n]

removing unused sync repositories...

Well, I don't know what to make of this after I do sudo pacman -Syu :

:: Synchronizing package databases...

error: failed retrieving file 'core.db' from mirror3.layerjet.com : Failed to connect to mirror3.layerjet.com port 80: Network is unreachable

error: failed retrieving file 'core.db' from mirror.dacentec.com : Failed to connect to mirror.dacentec.com port 80: Network is unreachable

core is up to date

error: failed retrieving file 'main.db' from mirror3.layerjet.com : Failed to connect to mirror3.layerjet.com port 80: Network is unreachable

error: failed retrieving file 'main.db' from mirror.dacentec.com : Failed to connect to mirror.dacentec.com port 80: Network is unreachable

main is up to date

error: failed retrieving file 'apps.db' from mirror3.layerjet.com : Failed to connect to mirror3.layerjet.com port 80: Network is unreachable

error: failed retrieving file 'apps.db' from mirror.dacentec.com : Failed to connect to mirror.dacentec.com port 80: Network is unreachable

apps is up to date

But interestingly, the Octopi does not tell me anything.

If pacman -Syy did not fix, and still the port 80 error, seems you have that port blocked. Is this a vbox install? How are you connecting?

I'm running Kaos installed on my hd. I'm connected directly to the internet (ADSL Modem). I have no proxy servers and stuff like that.

Try to use pacman with wget, see if that lets you connect to port 80.

Uncomment this line (remove the #) in /etc/pacman.conf:

#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u

I think it does look promising. Should I retain the change?

:: Synchronizing package databases...

--2014-07-20 23:09:02-- http://mirror3.layerjet.com/kaos/core/core.db

Resolving mirror3.layerjet.com (mirror3.layerjet.com)... 176.9.53.178, 2a01:4f8:150:73a6::2

Connecting to mirror3.layerjet.com (mirror3.layerjet.com)|176.9.53.178|:80... connected.

HTTP request sent, awaiting response... 200 OK

Length: 57204 (56K)

Saving to: ‘/var/lib/pacman/sync/core.db.part’

100%[=============================================================================================================>] 57,204 90.9KB/s in 0.6s

2014-07-20 23:09:04 (90.9 KB/s) - ‘/var/lib/pacman/sync/core.db.part’ saved [57204/57204]

--2014-07-20 23:09:04-- http://mirror3.layerjet.com/kaos/main/main.db

Resolving mirror3.layerjet.com (mirror3.layerjet.com)... 176.9.53.178, 2a01:4f8:150:73a6::2

Connecting to mirror3.layerjet.com (mirror3.layerjet.com)|176.9.53.178|:80... connected.

HTTP request sent, awaiting response... 200 OK

Length: 207791 (203K)

Saving to: ‘/var/lib/pacman/sync/main.db.part’

100%[=============================================================================================================>] 207,791 138KB/s in 1.5s

2014-07-20 23:09:06 (138 KB/s) - ‘/var/lib/pacman/sync/main.db.part’ saved [207791/207791]

--2014-07-20 23:09:06-- http://mirror3.layerjet.com/kaos/apps/apps.db

Resolving mirror3.layerjet.com (mirror3.layerjet.com)... 176.9.53.178, 2a01:4f8:150:73a6::2

Connecting to mirror3.layerjet.com (mirror3.layerjet.com)|176.9.53.178|:80... connected.

HTTP request sent, awaiting response... 200 OK

Length: 174497 (170K)

Saving to: ‘/var/lib/pacman/sync/apps.db.part’

100%[=============================================================================================================>] 174,497 136KB/s in 1.3s

2014-07-20 23:09:08 (136 KB/s) - ‘/var/lib/pacman/sync/apps.db.part’ saved [174497/174497]

:: Starting full system upgrade...

Until you figure what blocks port 80, yes.

4 years later

Hello World, I am investigating the possibility of installing KaOS for the first time - the only thing holding me back is the fact that this distro uses pacman, which I have learned to distrust courtesy of the only other distro I've ever tried that used it, Manjaro. Several different versions of that distro, from 0.8.* and up. Which broke my distro-hopping heart because I really liked how Manjaro looked otherwise. The update database would inevitably get locked up like this, sometimes sooner, sometimes later, but every damn time on every install on every machine I ever installed it to. Even some of the commandline remedies suggested above (or at least similar IIRC) didn't work! I've never quite understood what's so horribly wrong with synaptic that it isn't universally adopted. Personally, I prefer to keep to gui when possible, console is only for when things go wrong 😉 PLEASE tell me that KaOS's take on pacman is more reliable?

Using a 4 year old technical issue thread, that has been solved for that long, to ask opinions.......time to close this one.

Start your own thread under Userspace - General Discussion for this.
Database errors have nothing to do with the package manager, any distro is fully dependent on mirrors and cannot control mirrors going bad. Large distros might have a whole bunch of servers they control, thus able to host a lot of mirrors under their control.

Closing.

demm locked the discussion .