Package Fetch/Repository Problem
Showing results for 
Search instead for 
Did you mean: 

Package Fetch/Repository Problem

L1 Bithead

Taken from the install guide, but is this still the correct repostitory:

:~$ sudo add-apt-repository "deb trusty-minemeld main"

:~$ sudo apt-get update

Hit wheezy/updates Release.gpg
Hit wheezy/updates Release
Hit wheezy/updates/main Sources
Hit wheezy/updates/main amd64 Packages
Hit wheezy/updates/main Translation-en
Hit wheezy Release.gpg
Hit wheezy-updates Release.gpg
Hit wheezy Release
Hit wheezy-updates Release
Hit wheezy/main Sources
Hit wheezy/main amd64 Packages
Hit wheezy/main Translation-en
Hit wheezy-updates/main Sources
Hit wheezy-updates/main amd64 Packages/DiffIndex
Hit wheezy-updates/main Translation-en/DiffIndex
Hit trusty-minemeld Release.gpg
Hit trusty-minemeld Release
W: Failed to fetch Unable to find expected entry 'main/source/Sources' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.


Installing on Debian 3.2.73-2+deb7u2 x86_64 GNU/Linux 3.2.0-4-amd64 ...'cause its what I got.


Accepted Solutions

Thank you. Youve been extremely helpful.


I think rather than put any more time into fixing a deprecated platform, I will first move our test assets onto a supported platform.

View solution in original post


L7 Applicator

Hi @Sam_Sylar,

MineMeld packages are not supported on Debian.

You could try installing MineMeld via Ansible:

Which Debian versions have you access to? Anything more recent than wheezy ?

Yes, Ansible. Ansible gets stuck here:

TASK [minemeld : virtualenv permissions] ************************************************************************************************************************************************************************************************
fatal: []: FAILED! => {"failed": true, "msg": "the field 'args' has an invalid value, which appears to include a variable that is undefined. The error was: 'file_permissions' is undefined\n\nThe error appears to have been in '/home/sam/minemeld-ansible/roles/minemeld/tasks/core.yml': line 14, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n command: virtualenv \"{{venv_directory}}\" -p python2.7 creates=\"{{venv_directory}}\"\n- name: virtualenv permissions\n ^ here\n"}

I havent edited the correct module to set the venv_directory variable, but Im not sure which needs the editing.


Nothing more recent installed. It looked like our current Deb7Net image was close enough to 14.04 to work. Loads of paperwork required to spin up a new tools image in our environment.

Hi @Sam_Sylar,

let me fix the problem with ansible on Debian, it shouldn't take long. Are you also behind a proxy ?



Thank you!


This server does not proxy.

Hi @Sam_Sylar,

done, minemeld-ansible now supports Debian 7:

Make sure you select the stable branch, see the note about the version in the file.

minemeld-ansible now installs Deb7 and all services start: minemeld-engine RUNNING pid 54668, uptime 0:05:03 minemeld-supervisord-listener RUNNING pid 54667, uptime 0:05:03 minemeld-traced RUNNING pid 54669, uptime 0:05:03 minemeld-web RUNNING pid 20517, uptime 0:05:03 however, I cant log in: [2017-08-22 12:01:03 CDT] [20533] [DEBUG] redis session connection pool: in use: 0 available: 0 [2017-08-22 12:01:03 CDT] [20533] [INFO] Loading running config in memory [2017-08-22 12:01:03 CDT] [20533] [ERROR] Exception on /login [POST] Traceback (most recent call last): File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/flask/", line 1988, in wsgi_app response = self.full_dispatch_request() File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/flask/", line 1634, in full_dispatch_request self.try_trigger_before_first_request_functions() File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/flask/", line 1660, in try_trigger_before_first_request_functions func() File "/opt/minemeld/engine/core/minemeld/flask/", line 130, in _redlocked result = f(*args, **kwargs) File "/opt/minemeld/engine/core/minemeld/flask/", line 580, in _init_config _load_running_config() File "/opt/minemeld/engine/core/minemeld/flask/", line 175, in _load_running_config return _load_config_from_file(utils.running_config_path()) File "/opt/minemeld/engine/core/minemeld/flask/", line 222, in _load_config_from_file clock = _lock_timeout(REDIS_KEY_CONFIG) File "/opt/minemeld/engine/core/minemeld/flask/", line 97, in _lock_timeout result = _lock(resource) File "/opt/minemeld/engine/core/minemeld/flask/", line 84, in _lock nx=True, px=LOCK_TIMEOUT) File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/redis/", line 1072, in set return self.execute_command('SET', *pieces) File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/redis/", line 573, in execute_command return self.parse_response(connection, command_name, **options) File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/redis/", line 585, in parse_response response = connection.read_response() File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/redis/", line 582, in read_response raise response ResponseError: wrong number of arguments for 'set' command [2017-08-22 12:01:03 CDT] [20533] [DEBUG] redis connection pool: in use: 0 available: 1 - - [22/Aug/2017:12:01:03 -0500] "POST /login?_=1503421263 HTTP/1.0" 500 291 "" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36"

Hi @Sam_Sylar,

let me look into this. I have added an issue on the github repo:




Thank you. Youve been extremely helpful.


I think rather than put any more time into fixing a deprecated platform, I will first move our test assets onto a supported platform.

View solution in original post

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!