Ошибка установки anaconda

Cause¶

When running the .pkg installer, you may encounter this error during the “Installation” step:

This error occurs when the installation attempts to write to a directory for which it does not have write permissions.

Solution¶

Manually select an appropriate install location. The following example shows how to select your user’s home directory.

1. Re-run the installer. When you get to the Installation Type page, click Change Install Location….

   

2. Click Install on a specific disk….

   

3. Select the appropriate destination drive. Then click Choose Folder….

   

4. Select your user’s home directory (e.g. /Users/johndoe/). Then click Choose.

   

5. In the message box, confirm the name of the install folder you chose in the previous step. Then click Continue.

   

6. Click Install, and then proceed with the rest of the installation.

   

If you continue to receive the same error message, please open an issue here, and be sure to include the installation log output from your install.log file, which can be found at /var/log/install.log.

Cause¶

A 403 errors is a generic Forbidden error issued by a web server in the event the client is forbidden from accessing a resource.

The 403 error you are receiving may look like the following:

Collecting package metadata (current_repodata.json): failed

UnavailableInvalidChannel: The channel is not accessible or is invalid.
  channel name: pkgs/main
  channel url: https://repo.anaconda.com/pkgs/main
  error code: 403

You will need to adjust your conda configuration to proceed.
Use `conda config --show channels` to view your configuration's current state,
and use `conda config --show-sources` to view config file locations.
There are several reasons a 403 error could be received:

• The user has misconfigured their channels in their configuration (most common)
• A firewall or other security device or system is preventing user access (second most common)
• We are blocking their access because of a potential terms of service violation (third most common)

Solution¶

1. First, run the following to undo your configuration of Anaconda Professional:

   conda config --remove-key default_channels
   

2. Next, install or upgrade the conda-token tool:

   conda install --freeze-installed conda-token
   

3. Lastly, re-apply the token and configuration settings:

   # Replace <TOKEN> with your token
   conda token set <TOKEN>
   

If this doesn’t resolve the issue, Anaconda recommends consulting our Terms of Service error page.

conda config --set ssl_verify false

Cause¶

The Anaconda installer files are large (over 300 MB), and some users have
problems with errors and interrupted downloads when downloading large files.

Solution¶

One option is to download and install the smaller Miniconda (under 60MB) and then use the command
conda install anaconda to download and install all the remaining packages
in Anaconda. If the package downloads are interrupted, just run
conda install anaconda again. Conda only downloads the packages that were
not finished in any previous attempts.

A second option is to download the large Anaconda installer file, and restart
it if the download is interrupted or you need to pause it.

Windows

If you use Internet Explorer:

1. Click the Settings icon.
2. Click “View Downloads” to open the Download Manager.
3. Click on the “Resume” button next to the stopped download to restart
   downloading. The download resumes at the point where it stopped.

If you use Edge browser:

1. In Windows Explorer, open your downloads folder. There will be
   temporary files there associated with the partial downloads. Delete all of
   the temporary files except for the download you want to resume.
2. In Edge, click the file to download it again. Pause the download but do not
   cancel it.
3. In Windows Explorer, open your downloads folder. You will see two files: the
   partially downloaded file from earlier, and the paused download you just
   started. Copy the name of the file you just started, delete this file, and
   rename the other file with the copied name.
4. In Edge, resume the download.

If you use Chrome browser:

Download the plugin for Chrome called Chrono Download manager. In your Chrome
browser, go to https://chrome.google.com/webstore/category/extensions, search
on “Chrono Download” and select, “Add to Chrome.”

To resume the download using Chrono Download, from your top browser menu, click
on the Chrome menu button, then click “Downloads.” Select the filename, then
click “Resume” to restart your download.

macOS and Linux

• In your terminal window, download the file with the command
  curl -O FILENAME.

  Note

  Replace FILENAME with the full path and name of the file, including
  http:// or https://.

• To pause the download, use CTRL-c.

  Note

  While a download is paused, you can shut down or restart your computer.

• When ready to resume your download, use curl -O -C FILENAME.

  Where “-C” is the option for “continue”. You can pause and restart a download
  as many times as you wish.

Cause¶

Anaconda 5.0.1 sometimes does not install completely on Windows.

Solution¶

Until a new version is released, you can install Miniconda, and then use conda
to install the rest of the packages in Anaconda with these instructions:

Open the command prompt (Windows key + the R key on your keyboard) which brings
up the Run… dialog box. Enter cmd.exe and then press enter)

Copy the following text:

cd %UserProfile%
powershell -command "& { (New-Object Net.WebClient).DownloadFile('https://repo.anaconda.com/miniconda/Miniconda3-latest-Windows-x86_64.exe', 'mc3.exe') }"
start /wait "" mc3.exe /InstallationType=JustMe /AddToPath=0 /RegisterPython=0 /NoRegistry=0 /S /D=%UserProfile%anaconda3
%UserProfile%anaconda3Scriptsactivate.bat
conda install -y anaconda=5.0.1 conda-build _ipyw_jlab_nb_ext_conf

Then paste it into the command prompt window.

Cause¶

The cause could be any number of issues.

Solution¶

Anaconda 4.4 added a feature to the Windows installer so that the “verbose” install information is printed out to a special debug stream via the Win32 API function OutputDebugStream. To see these messages, during installation you need to run the Microsoft utility https://technet.microsoft.com/en-us/sysinternals/debugview.aspx. This may provide useful clues for troubleshooting or submitting bug reports.

Cause¶

Most likely when you were installing Anaconda or Miniconda, you answered “NO” to the question whether or not to prepend the conda prompt to your path.

Solution¶

Uninstall and then reinstall Anaconda or Miniconda, answering “YES” to the question about prepending the conda prompt.

Or, you can manually edit your .bashrc file to prepend the Anaconda or Miniconda install location. Open a text editor and in your home directory, locate the hidden file .bashrc. Add this line to it and save:

export PATH=/Users/your-username/anaconda3/bin:$PATH

Close your terminal window and re-open before running a conda command.

Step 1¶

Download a new installer, then follow
the instructions for your system Windows, macOS, or Linux.

robocopy Anaconda_old Anaconda /S
rd /s Anaconda_old

bash Anaconda3-4.0.0-MacOSX-x86_64.sh
rsync -a anaconda_orig/ anaconda/
rm -rf anaconda_orig

bash Anaconda3-4.0.0-Linux-x86_64.sh
rsync -a anaconda_orig/ anaconda/

Step 2¶

Run conda list to view the packages from the previous installation.

Run conda info -e to list the environments created in the previous installation which are now available in the new installation.

Solution¶

To add the proxy information you will need to add two entries to your
.condarc file located in the user’s home directory. This information
should be made available by your IT team and may contain a username and
password that is included in the URL. Read more about the
.condarc configuration.

Example configuration:

channels:
- defaults

proxy_servers:
- http: http://username:password@proxyurl.com:8080
- https: https://username:password@proxyurl.com:8443

In some situations it may be necessary to export the HTTP_PROXY and
HTTPS_PROXY environment variables.

MacOS/Linux

Windows

If these steps have not allowed connections you should speak to your IT
team to verify that security policies are not blocking connections to
https://anaconda.com and https://repo.continuum.io.

Cause¶

MacOS Catalina changed the default shell from Bash to zsh.

Solution¶

Run bash -c "conda init zsh" and then restart your shell to initialize conda for zsh.

Cause¶

“InsecurePlatformWarning” appears only when the installed version of Python is
older than version 2.7.9. This message warns only that the validity of the SSL
connection is not being verified. It should not affect your package downloads.

Solution¶

To resolve this on Windows, install the updated package ndg-httpsclient:

conda install ndg-httpsclient

Cause¶

The conda shell function is not available, or is not working
properly. Some causes:

• You have set conda_auto_activate_base to false. You need to run conda activate [env]. Env is optional, the default if not provided is base.
• You haven’t started a new shell after installing Anaconda/Miniconda (assuming you allow it to modify your startup script)
• You didn’t allow the installer to modify your startup script
• Conda has been corrupted, usually by a change in the Python package (e.g. 3.6->3.7)

Solution¶

Run /full/path/to/bin/conda init to modify ~/.bashrc.

Either start a new shell or source the modified ~/.bash_profile
(Windows/MSYS2, Windows/Cygwin and macOS) or ~/.bashrc (Linux and Windows Subsystem for Linux).
Source them via . ~/.bash_profile.

You may prefer that conda not automatically activate your base
environment when a new shell is started. This behavior shadows
your system Python, and some users prefer to have their conda
environment be inactive until they need it. To achieve this,
you can set a .condarc setting:

conda config --set auto_activate_base false

If you have this set, the conda command will still be available
as a shell function, but your base environment will not be
active when a new shell is started. To activate your base
environment, run conda activate.

Cause¶

After a user has configured their .condarc for either Professional or Business, in some cases they are unable to install packages. They may receive an error message that the channel or package is unavailable or missing.

Solution¶

One potential fix for all of these is to run the following command:

This will clear the “index cache” and force conda to sync metadata from the repo server.

Cause¶

If a user chooses to add Anaconda to the Windows PATH, this can cause programs
to use the new Anaconda versions of software such as Python and not the
versions that were already in place. In some cases this can cause
incompatibility and errors.

Solution¶

Anaconda recommends against adding Anaconda to the Windows PATH manually. Instead, use Anaconda
software by opening Anaconda Navigator or the Anaconda Prompt from the
Start Menu.

C:Usersusername>anaconda search -t conda packagename
No environment named "search" exists in C:Anacondaenvs
Solution

Cause¶

This situation can occur if you are getting a conda error and you want to reinstall Miniconda to fix it.

Solution¶

For macOS and Linux, download and install the appropriate Miniconda for your operating system from the Miniconda download page using the force or -f option:

bash Miniconda3-latest-MacOSX-x86_64.sh -f

Cause¶

For users who have installed packages that are not compatible with the latest version of the Anaconda metapackage, running conda update anaconda updates the Anaconda metapackage to the latest compatible version, but this may not be the latest version.

Solution¶

Obtain a list of the conflicting packages by running conda update anaconda or conda install anaconda=5.2.

Once you know which packages are conflicting, you can update all current packages without upgrading to the latest version of Anaconda, or you can remove the conflicting packages and then upgrade to the latest version of Anaconda.

To update all current packages without upgrading to the latest version of Anaconda:

1. Use conda remove anaconda to remove the Anaconda metapackage itself. (This will not remove any of the packages included with Anaconda.)
2. Use conda update --all to update all currently installed packages.

To remove the conflicting packages and upgrade to the latest version of Anaconda:

1. Remove the conflicting packages by running conda remove package-name for each one.

   Note

   Replace package-name with the name of the package.

2. Run conda update anaconda.

Cause¶

When compiling Python extensions with gcc on Windows, linking problems may result.

Solution¶

To resolve these linking problems, use the mingw import library–the conda package libpython–which Anaconda builds and includes with the Anaconda Distribution.

Error: Unable to remove files for package: <package-name>
Please close all processes running code from conda and try again.

Cause¶

This may be caused by a file lock issue.

Solution¶

Before updating or installing any packages with conda, be sure to terminate any running Anaconda processes such as Spyder or IPython.

You can also force the installation of the package: conda install -f package-name.

Cause¶

Some users may need to keep settings files and other users may need to delete them, so Anaconda leaves some settings files in place when it is uninstalled. Specifically, the directories .spyder2, .ipython, .matplotlib, and .astropy remain. Depending on your version of Windows these may be in C:Documents and SettingsYour_User_Name or in C:UsersYour_User_Name.

Solution¶

Manually delete any unneeded settings files.

Cause¶

This may be caused by errors in the Spyder setting and configuration files.

Solution¶

1. Close and relaunch Spyder and see if the problem remains.

2. On the menu, select Start, then select Reset Spyder Settings and see if the problem remains.

3. Close Spyder and relaunch it from the Anaconda Prompt:

   1. From the Start menu, open the Anaconda Prompt.
   2. At the Anaconda Prompt, enter Spyder.
   3. See if the problem remains.

4. Delete the directory .spyder2 and then repeat the previous steps from Step 1. Depending on your version of Windows, .spyder2 may be in C:Documents and SettingsYour_User_Name or in C:UsersYour_User_Name.

   Note

   Replace Your_User_Name, with your Windows user name as it appears in the Documents and Settings folder.

Cause¶

Some installations of Anaconda on macOS 10.12.2 experienced incorrect file and
directory permissions, which caused a range of errors with Navigator and other
parts of Anaconda.

Solution¶

Anaconda recommends that any users with Anaconda on macOS 10.12.2 follow these steps:

1. Uninstall Anaconda. Open the Terminal.app or iTerm2 terminal application and
   remove your Anaconda directory, which will have a name such as “anaconda2”
   or “anaconda3”, by entering a command such as this: rm -rf ~/anaconda3
2. Use a text editor such as TextEdit to open the file named .bash_profile
   in your home directory. If you see a line that adds Anaconda or Miniconda to
   your PATH environment variable, remove this line, and then save and close
   the file. For example, if you see a line such as
   export PATH="/Users/jsmith/anaconda3/bin:$PATH", remove that line.
3. Update to macOS 10.12.3 or later.
4. Reinstall Anaconda.

Cause¶

This version of macOS seems to have a bug affecting some of the ways for a program to open a web page in a browser.

Solution¶

Several possible workarounds have been found for this bug.

You can explicitly set the browser in ~/.jupyter/jupyter_notebook_config.py with a line such as this:

c.NotebookApp.browser = u'Safari'

Or you can copy the Jupyter notebook URL from the log messages on the command line and paste it into your browser.

Or you can set the BROWSER environment variable: export BROWSER=/Applications/Google Chrome.app/Contents/MacOS/Google Chrome

Further information is available at the Jupyter bug tracker, the Python bug tracker, and this blog post.

Cause¶

Anaconda 4.4.0.0 for Power8 did not include libgfortran.

Solution¶

Anaconda 4.4.0.1 and later for Power8 do include libgfortran.

Upgrade to the latest version of Anaconda:

Anaconda 4.4.0.0 users who do not wish to upgrade may instead install libgfortran with this command:

conda install libgfortran

Cause¶

Most Power8 Linux distributions include libgomp, but some may not.

Solution¶

Check whether the system is missing libgomp with this command:

conda inspect linkages -n root numpy

If libgomp.so.1 is listed in the “not found:” section, it must be installed.

Install libgomp on Ubuntu with this command:

Install libgomp on Red Hat Enterprise Linux (RHEL) or CentOS with this command:

Cause¶

Anaconda on Power8 only supports little endian mode. The little endian Python binary will not execute on a big endian operating system.

Solution¶

Install Anaconda on Power8 on a little endian Linux installation or VM.

Cause¶

After installing Anaconda or Miniconda as a non-administrative user on Windows,
uninstalling may prompt for administrative privileges.

This occurs when running the uninstaller by choosing Control Panel, System,
Apps & features, Python x.x.x (Miniconda3 4.3.xx 64-bit), Uninstall.

Solution¶

Open the Anaconda or Miniconda installation folder and run the .exe file
uninstaller from that location. Uninstallation will complete without prompting
for administrative privileges.

EXAMPLE: If you installed Miniconda3, the uninstall file will be
Uninstall-Miniconda3.exe. Users who installed Miniconda2 or Anaconda will
find a similar file with the appropriate name.

Cause¶

The Windows Favorites folder has unusual permissions and may cause permission
errors with installers of any software. If you try launching the installer from
the Favorites folder you may see errors such as “Setup was unable to create the
directory”, “Access is denied”, or “Error opening file for writing”.

Solution¶

Move the installer to a different folder and run the installer from the new
folder.

Solution¶

If you run into the following backtrace on Windows:

File "C:UsersdamiaMiniconda3libsite-packagescondaactivate.py", line 550, in _replace_prefix_in_path
assert last_idx is not None
AssertionError

Open a cmd.exe prompt. cd to where you installed conda and run:

Close the cmd.exe prompt and the Anaconda Prompt or the Anaconda
PowerShell Prompt as usual.

If this doesn’t work, try running:

PREFIX=/home/myname/anaconda3
Unpacking payload ...
[13822] Error loading Python lib '/tmp/_MEI<randomstring>/libpython3.6m.so.1.0': dlopen /tmp_MEI<randomstring>/libpython3.6m.so.1.0: failed to map segment from shared object: Operation not permitted
ERROR: could not extract tar starting at offset 00000000000020980+9231072+2

Cause¶

This is caused by having TMP as a noexec.

Solution¶

To enable installation, you can temporarily
set TMP to somewhere else from which you can execute software.

For example:

cd
mkdir TMPconda
TMP=~/TMPconda bash Anaconda3-2019.07-Linux-x86_64.sh

After installing, set the TMP folder back to its initial location.

Cause¶

This is because of the command-line flags returned by python3-config. Before Python 3.8,
those are needed to embed the core Python interpreter into a different project altogether
and not those that should be used when linking a Python extension module.

Python modules should never link to the core Python interpreter library directly,
either statically at build time or dynamically at runtime. This is because the Python
executable itself provides all the necessary functions and symbols.

Solution¶

You should only use python*-config —ldflags when linking to an interpreter library (either static or shared).

python3-config doesn’t include the command/compiler name whereas the sysconfig way
does. This works provided none of your arguments have spaces:

python -c "import sysconfig; print(' '.join(sysconfig.get_config_var('LDSHARED').split(' ')[1:]))"

Caution

Always specify which version you want to work with because mixing 32- and 64-bit
packages can cause problems in your environment.

Cause¶

When running the .pkg installer, you may see this message at the end of the installation:

If so, check for the following:

1. Open your /var/log/install.log file and check whether the most recent lines show errors following a call to conda init --all.

   open /var/log/install.log
   

2. In your $HOME directory, check whether the owner of your shell config files is root:

   ls -la ~/.bash_profile ~/.config/fish/config.fish ~/.tcshrc ~/.xonshrc ~/.zshrc
   

   

Solution¶

If both of the above are true, do the following:

1. Change the owner of your shell config files to your current user:

   sudo chown -R $USER ~/.bash_profile ~/.config/fish/config.fish ~/.tcshrc ~/.xonshrc ~/.zshrc
   

   

2. Uninstall the previous installation. Then re-run the installer, making sure to select the “Install for me only” option.