Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation Sequence Failed at 'apt update' #541

Closed
bhsmither opened this issue Apr 25, 2021 · 18 comments
Closed

Installation Sequence Failed at 'apt update' #541

bhsmither opened this issue Apr 25, 2021 · 18 comments
Labels
bug waiting Waiting for the original poster (in most cases) or something else wontfix

Comments

@bhsmither
Copy link

bhsmither commented Apr 25, 2021

Describe the bug
Installing Manticore by following:
https://manual.manticoresearch.com/Installation/Debian_and_Ubuntu

The sequence failed at the command "apt update".

root@BrownBunny:/etc# apt-key adv --fetch-keys 'https://repo.manticoresearch.com/GPG-KEY-manticore'    
Executing: /tmp/apt-key-gpghome.tjWpvJMi1N/gpg.1.sh --fetch-keys https://repo.manticoresearch.com/GPG-KEY-manticore    
gpg: requesting key from 'https://repo.manticoresearch.com/GPG-KEY-manticore'    
gpg: key 14D612DB3D2730E2: public key "Manticore Search <support@manticoresearch.com>" imported    
gpg: Total number processed: 1    
gpg:               imported: 1    
root@BrownBunny:/etc# wget https://repo.manticoresearch.com/manticore-repo.noarch.deb    
--2021-04-24 15:05:07--  https://repo.manticoresearch.com/manticore-repo.noarch.deb    
Resolving repo.manticoresearch.com (repo.manticoresearch.com)... 167.233.8.205    
Connecting to repo.manticoresearch.com (repo.manticoresearch.com)|167.233.8.205|:443... connected.    
HTTP request sent, awaiting response... 200 OK    
Length: 2516 (2.5K) [application/octet-stream]    
Saving to: ‘manticore-repo.noarch.deb’    
    
manticore-repo.noarch.deb                    100%[===========================================================================================>]   2.46K  --.-KB/s    in 0s    
    
2021-04-24 15:05:08 (257 MB/s) - ‘manticore-repo.noarch.deb’ saved [2516/2516]    
    
root@BrownBunny:/etc# dpkg -i manticore-repo.noarch.deb    
Selecting previously unselected package manticore-repo.    
(Reading database ... 296464 files and directories currently installed.)    
Preparing to unpack manticore-repo.noarch.deb ...    
Unpacking manticore-repo (0.0.1) ...    
Setting up manticore-repo (0.0.1) ...    
root@BrownBunny:/etc# apt update    
E: Malformed entry 1 in list file /etc/apt/sources.list.d/manticoresearch.list (Component)    
E: The list of sources could not be read.    
root@BrownBunny:/etc#    

The contents of:
/etc/apt/sources.list.d/manticoresearch.list

deb http://repo.manticoresearch.com/repository/manticoresearch_  main    

Describe the environment:

  • OS version (uname -a if on a Unix-like system):
Linux BrownBunny 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux    

Linux Mint 19.3 Tricia

@sanikolaev
Copy link
Collaborator

@bhsmither

Good catch! We never tested Manticore in Linux Mint. I can't find an official docker to give it a try. Could you show what cat /etc/os-release returns so we can make sure the script in the repo installation package can understand it.

@sanikolaev sanikolaev added the waiting Waiting for the original poster (in most cases) or something else label Apr 27, 2021
@bhsmither
Copy link
Author

The command cat /etc/os-release says:

NAME="Linux Mint"
VERSION="19.3 (Tricia)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 19.3"
VERSION_ID="19.3"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.ubuntu.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=tricia
UBUNTU_CODENAME=bionic

@sanikolaev
Copy link
Collaborator

@bhsmither Can you try now?

wget https://repo.manticoresearch.com/manticore-repo.noarch.deb
dpkg -i manticore-repo.noarch.deb

@bhsmither
Copy link
Author

After apt update, these are the related responses:

Get:8 http://repo.manticoresearch.com/repository/manticoresearch_bionic bionic InRelease [1,224 B]
Err:8 http://repo.manticoresearch.com/repository/manticoresearch_bionic bionic InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 14D612DB3D2730E2
Reading package lists... Done
N: Ignoring file 'manticore-repo.noarch.deb' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
W: GPG error: http://repo.manticoresearch.com/repository/manticoresearch_bionic bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 14D612DB3D2730E2
E: The repository 'http://repo.manticoresearch.com/repository/manticoresearch_bionic bionic InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

@sanikolaev
Copy link
Collaborator

Not sure why it's happened. Here's what I get in a clean Linux Mint 19.3 docker:

snikolaev@dev:~$ docker run -it --rm linuxmintd/mint19.3-amd64 bash
root@58f24bcac165:/# apt update -y && apt install wget gnupg2 -y
...
root@58f24bcac165:/# apt-key adv --fetch-keys 'http://repo.manticoresearch.com/GPG-KEY-manticore'
Executing: /tmp/apt-key-gpghome.Ajd81Xampd/gpg.1.sh --fetch-keys http://repo.manticoresearch.com/GPG-KEY-manticore
gpg: requesting key from 'http://repo.manticoresearch.com/GPG-KEY-manticore'
gpg: key 14D612DB3D2730E2: public key "Manticore Search <support@manticoresearch.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1

root@58f24bcac165:/# wget https://repo.manticoresearch.com/manticore-repo.noarch.deb
--2021-04-27 16:07:36--  https://repo.manticoresearch.com/manticore-repo.noarch.deb
Resolving repo.manticoresearch.com (repo.manticoresearch.com)... 167.233.8.205
Connecting to repo.manticoresearch.com (repo.manticoresearch.com)|167.233.8.205|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2398 (2.3K) [application/octet-stream]
Saving to: ‘manticore-repo.noarch.deb’

manticore-repo.noarch.deb                  100%[========================================================================================>]   2.34K  --.-KB/s    in 0s

root@58f24bcac165:/# dpkg -i manticore-repo.noarch.deb
Selecting previously unselected package manticore-repo.
(Reading database ... 36080 files and directories currently installed.)
Preparing to unpack manticore-repo.noarch.deb ...
Unpacking manticore-repo (0.0.2) ...
Setting up manticore-repo (0.0.2) ...

root@58f24bcac165:/# apt update
Get:1 http://repo.manticoresearch.com/repository/manticoresearch_bionic bionic InRelease [1,224 B]
Hit:2 http://archive.canonical.com/ubuntu bionic InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:5 http://repo.manticoresearch.com/repository/manticoresearch_bionic bionic/main amd64 Packages [10.6 kB]
Get:6 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Ign:8 http://packages.linuxmint.com tricia InRelease
Hit:9 http://packages.linuxmint.com tricia Release
Fetched 264 kB in 1s (486 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
63 packages can be upgraded. Run 'apt list --upgradable' to see them.

root@58f24bcac165:/# apt install manticore
The following NEW packages will be installed:
  manticore
0 upgraded, 1 newly installed, 0 to remove and 63 not upgraded.
Need to get 26.9 MB of archives.
After this operation, 74.2 MB of additional disk space will be used.
Get:1 http://repo.manticoresearch.com/repository/manticoresearch_bionic bionic/main amd64 manticore amd64 3.5.4-210107-f70faec5 [26.9 MB]
Fetched 26.9 MB in 29s (930 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package manticore.
(Reading database ... 36082 files and directories currently installed.)
Preparing to unpack .../manticore_3.5.4-210107-f70faec5_amd64.deb ...
Unpacking manticore (3.5.4-210107-f70faec5) ...
Setting up manticore (3.5.4-210107-f70faec5) ...
Adding group `manticore' (GID 105) ...
Done.
Adding system user `manticore' (UID 104) ...
Adding new user `manticore' (UID 104) with group `manticore' ...
Not creating home directory `/home/manticore'.
Manticore Search (https://manticoresearch.com)

Getting Started with Manticore Search:
  https://manual.manticoresearch.com/Quick_start_guide

Learn Manticore with interactive courses:
  https://play.manticoresearch.com/

To start Manticore Search service:
  > systemctl start manticore

Configuration file:
  /etc/manticoresearch/manticore.conf

Created symlink /etc/systemd/system/manticore.service → /lib/systemd/system/manticore.service.
Created symlink /etc/systemd/system/searchd.service → /lib/systemd/system/manticore.service.
Created symlink /etc/systemd/system/multi-user.target.wants/manticore.service → /lib/systemd/system/manticore.service.
System has not been booted with systemd as init system (PID 1). Can't operate.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for systemd (237-3ubuntu10.43) ...


root@58f24bcac165:/# searchd -v
Manticore 3.5.4 f70faec5@210107 release
Copyright (c) 2001-2016, Andrew Aksyonoff
Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com)
Copyright (c) 2017-2020, Manticore Software LTD (http://manticoresearch.com)

@bhsmither
Copy link
Author

I should have also provided the responses from executing the commands given above:

root@BrownBunny:/etc/apt/sources.list.d# wget https://repo.manticoresearch.com/manticore-repo.noarch.deb
--2021-04-27 08:13:26--  https://repo.manticoresearch.com/manticore-repo.noarch.deb
Resolving repo.manticoresearch.com (repo.manticoresearch.com)... 167.233.8.205
Connecting to repo.manticoresearch.com (repo.manticoresearch.com)|167.233.8.205|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2398 (2.3K) [application/octet-stream]
Saving to: ‘manticore-repo.noarch.deb’

manticore-repo.noarch.deb                    100%[===========================================================================================>]   2.34K  --.-KB/s    in 0s

2021-04-27 08:13:27 (303 MB/s) - ‘manticore-repo.noarch.deb’ saved [2398/2398]

root@BrownBunny:/etc/apt/sources.list.d# dpkg -i manticore-repo.noarch.deb
(Reading database ... 296466 files and directories currently installed.)
Preparing to unpack manticore-repo.noarch.deb ...
Unpacking manticore-repo (0.0.2) over (0.0.1) ...
Warning: The postrm maintainerscript of the package manticore-repo
Warning: seems to use apt-key (provided by apt) without depending on gnupg or gnupg2.
Warning: This will BREAK in the future and should be fixed by the package maintainer(s).
Note: Check first if apt-key functionality is needed at all - it probably isn't!
OK
Setting up manticore-repo (0.0.2) ...

@bhsmither
Copy link
Author

Executing the following command:

apt-key list

Should I expect to see a mention of Manticore?

@bhsmither
Copy link
Author

In the folder /etc/apt/trusted.gpg.d, there is a file named manticore-keyring.gpg~.

@sanikolaev
Copy link
Collaborator

apt-key list
Should I expect to see a mention of Manticore?

Yes.

root@dbe4f27277e1:/# apt list|grep manticore

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

manticore/bionic 3.5.4-210107-f70faec5 amd64
manticore-all/bionic 3.5.4-210107-f70faec5 amd64
manticore-all-dbgsym/bionic 3.5.4-210107-f70faec5 amd64
manticore-bin/bionic 3.4.2-200410-69033058 amd64
manticore-converter/bionic 3.5.4-210107-f70faec5 amd64
manticore-dbgsym/bionic 3.5.4-210107-f70faec5 amd64
manticore-dev/bionic 3.5.4-210107-f70faec5 amd64
manticore-devel/bionic 3.5.0-200722-1d34c491 amd64
manticore-devel-dbgsym/bionic 3.5.0-200722-1d34c491 amd64
manticore-icudata/bionic 3.5.4-210107-f70faec5 amd64
manticore-lemmatizer-uk/bionic 1.0.0 amd64
manticore-repo/now 0.0.2 all [installed,local]
manticore-server/bionic 3.5.4-210107-f70faec5 amd64
manticore-server-dbgsym/bionic 3.5.4-210107-f70faec5 amd64
manticore-tools/bionic 3.5.4-210107-f70faec5 amd64
manticore-tools-dbgsym/bionic 3.5.4-210107-f70faec5 amd64

Can you try again

apt-key adv --fetch-keys 'http://repo.manticoresearch.com/GPG-KEY-manticore'
wget https://repo.manticoresearch.com/manticore-repo.noarch.deb
dpkg -i manticore-repo.noarch.deb
apt update
apt install manticore

? I've tried again and can't see any issue.

@bhsmither
Copy link
Author

No go.

root@BrownBunny:/etc/apt/trusted.gpg.d# apt-key adv --fetch-keys 'http://repo.manticoresearch.com/GPG-KEY-manticore'
Executing: /tmp/apt-key-gpghome.zf5kFLZsGg/gpg.1.sh --fetch-keys http://repo.manticoresearch.com/GPG-KEY-manticore
gpg: requesting key from 'http://repo.manticoresearch.com/GPG-KEY-manticore'
gpg: key 14D612DB3D2730E2: public key "Manticore Search <support@manticoresearch.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
root@BrownBunny:/etc/apt/trusted.gpg.d# wget https://repo.manticoresearch.com/manticore-repo.noarch.deb
--2021-04-28 22:58:13--  https://repo.manticoresearch.com/manticore-repo.noarch.deb
Resolving repo.manticoresearch.com (repo.manticoresearch.com)... 167.233.8.205
Connecting to repo.manticoresearch.com (repo.manticoresearch.com)|167.233.8.205|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2398 (2.3K) [application/octet-stream]
Saving to: ‘manticore-repo.noarch.deb’

manticore-repo.noarch.deb                    100%[===========================================================================================>]   2.34K  --.-KB/s    in 0s

2021-04-28 22:58:14 (315 MB/s) - ‘manticore-repo.noarch.deb’ saved [2398/2398]

root@BrownBunny:/etc/apt/trusted.gpg.d# dpkg -i manticore-repo.noarch.deb
(Reading database ... 296466 files and directories currently installed.)
Preparing to unpack manticore-repo.noarch.deb ...
Unpacking manticore-repo (0.0.2) over (0.0.2) ...
Warning: The postrm maintainerscript of the package manticore-repo
Warning: seems to use apt-key (provided by apt) without depending on gnupg or gnupg2.
Warning: This will BREAK in the future and should be fixed by the package maintainer(s).
Note: Check first if apt-key functionality is needed at all - it probably isn't!
OK
Setting up manticore-repo (0.0.2) ...
root@BrownBunny:/etc/apt/trusted.gpg.d# apt update
Hit:1 http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.4/ubuntu bionic InRelease
Ign:2 http://mintmirror.math.washington.edu/linuxmint-repo tricia InRelease
Hit:3 http://mintmirror.math.washington.edu/linuxmint-repo tricia Release
Get:4 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:5 http://ppa.launchpad.net/geany-dev/ppa/ubuntu bionic InRelease
Hit:6 http://archive.canonical.com/ubuntu bionic InRelease
Hit:7 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:10 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Hit:11 http://ppa.launchpad.net/gwendal-lebihan-dev/cinnamon-nightly/ubuntu bionic InRelease
Get:8 http://repo.manticoresearch.com/repository/manticoresearch_bionic bionic InRelease [1,224 B]
Hit:12 https://nginx.org/packages/mainline/ubuntu bionic InRelease
Hit:13 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease
Get:14 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Err:8 http://repo.manticoresearch.com/repository/manticoresearch_bionic bionic InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 14D612DB3D2730E2
Reading package lists... Done
N: Ignoring file 'manticore-repo.noarch.deb' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
W: GPG error: http://repo.manticoresearch.com/repository/manticoresearch_bionic bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 14D612DB3D2730E2
E: The repository 'http://repo.manticoresearch.com/repository/manticoresearch_bionic bionic InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
N: Skipping acquire of configured file 'nginx/binary-i386/Packages' as repository 'https://nginx.org/packages/mainline/ubuntu bionic InRelease' doesn't support architecture 'i386'

@bhsmither
Copy link
Author

# apt list|grep manticore

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

manticore-repo/now 0.0.2 all [installed,local]

@sanikolaev
Copy link
Collaborator

Can you check if when you run apt-key adv --fetch-keys 'http://repo.manticoresearch.com/GPG-KEY-manticore' your /etc/apt/trusted.gpg gets updated?

root@1d6862d7a87c:/etc/apt# md5sum trusted.gpg
571c3024a5a42792461689942cc3d5d6  trusted.gpg

root@1d6862d7a87c:/etc/apt# apt-key adv --fetch-keys 'http://repo.manticoresearch.com/GPG-KEY-manticore'
Executing: /tmp/apt-key-gpghome.eQkGLZ2WE6/gpg.1.sh --fetch-keys http://repo.manticoresearch.com/GPG-KEY-manticore
gpg: requesting key from 'http://repo.manticoresearch.com/GPG-KEY-manticore'
gpg: key 14D612DB3D2730E2: public key "Manticore Search <support@manticoresearch.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1

root@1d6862d7a87c:/etc/apt# md5sum trusted.gpg
803a82b57860f161bae880dedbdbeb30  trusted.gpg

If it's not maybe there's some permissions issue which prevents apt-key from updating it?

@bhsmither
Copy link
Author

I will do this, shortly.

But if a process, using a specific user/owner, is discovered that permissions are preventing the completion of a task, should that show up somewhere in a log?

@sanikolaev
Copy link
Collaborator

if a process, using a specific user/owner, is discovered that permissions are preventing the completion of a task

I would expect it, yes, but I'm not an expert in apt-key, so can't say for sure why it can't just import a key even though it says it has done that, and the fingerprint is the same in apt-key and apt update. The bad thing is that I can't reproduce it neither in Linux Mint nor in Ubuntu which makes it hard to debug.

@stale
Copy link

stale bot commented Jun 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Feel free to re-open the issue in case it becomes actual.

@stale stale bot added the wontfix label Jun 2, 2021
@stale stale bot closed this as completed Jun 9, 2021
@den1a
Copy link

den1a commented Oct 26, 2021

Hello. I have a similar debian 11 problem

apt update

Некорректная запись в строке 1 файла «list» /etc/apt/sources.list.d/manticoresearch.list (Component)
Не удалось прочитать перечень источников.
cat /etc/os-release

PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

@sanikolaev
Copy link
Collaborator

Debian 11 wasn't supported until recently. It's supported by the latest version 4.2.0 - https://manticoresearch.com/downloads/

@kskby
Copy link

kskby commented Dec 24, 2021

Debian 11 wasn't supported until recently. It's supported by the latest version 4.2.0 - https://manticoresearch.com/downloads/

Thanks ! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug waiting Waiting for the original poster (in most cases) or something else wontfix
Projects
None yet
Development

No branches or pull requests

5 participants