HTTP Error 403 when running second pass of install_saturne.py

All questions about installation
Forum rules
Please read the forum usage recommendations before posting.
Post Reply
saintlyknighted
Posts: 14
Joined: Sun Aug 06, 2023 3:40 am

HTTP Error 403 when running second pass of install_saturne.py

Post by saintlyknighted »

Hello, I'm trying to install Code_Saturne v7.0.4 on a new machine and I'm running into a HTTP Error 403 (I attached the console log below) when running the install_saturne.py script the second time. Not sure what is causing this, I have successfully installed Code_Saturne on another computer before without running into this problem. Any help would be appreciated!

Code: Select all

        Installation of Code_Saturne
        ____________________________

The process will take several minutes.
You can have a look at the log file meanwhile.

Check the setup file and some utilities presence.

   o Checking for cc...  /usr/bin/cc
   o Checking for mpicc...  /usr/bin/mpicc
   o Checking for f95...  /usr/bin/f95
   o Checking for python3...  /opt/hpds/miniconda/bin/python3
     Python version is 3.9
   o Checking for make...  /usr/bin/make

Download of HDF5
  (https://support.hdfgroup.org/ftp/HDF5/releases/hdf5-1.10/hdf5-1.10.6/src/hdf5-1.10.6.tar.gz)
Download of CGNS
  (https://github.com/CGNS/CGNS/archive/v4.1.2.tar.gz)
Download of MED
  (http://files.salome-platform.org/Salome/other/med-4.1.0.tar.gz)
Traceback (most recent call last):
  File "/mnt/d/code_saturne/saturne_build/../code_saturne-7.0.4/install_saturne.py", line 1354, in <module>
    setup.install()
  File "/mnt/d/code_saturne/saturne_build/../code_saturne-7.0.4/install_saturne.py", line 1092, in install
    p.download()
  File "/mnt/d/code_saturne/saturne_build/../code_saturne-7.0.4/install_saturne.py", line 246, in download
    urllib.request.urlretrieve(self.url, self.archive)
  File "/opt/hpds/miniconda/lib/python3.9/urllib/request.py", line 239, in urlretrieve
    with contextlib.closing(urlopen(url, data)) as fp:
  File "/opt/hpds/miniconda/lib/python3.9/urllib/request.py", line 214, in urlopen
    return opener.open(url, data, timeout)
  File "/opt/hpds/miniconda/lib/python3.9/urllib/request.py", line 523, in open
    response = meth(req, response)
  File "/opt/hpds/miniconda/lib/python3.9/urllib/request.py", line 632, in http_response
    response = self.parent.error(
  File "/opt/hpds/miniconda/lib/python3.9/urllib/request.py", line 561, in error
    return self._call_chain(*args)
  File "/opt/hpds/miniconda/lib/python3.9/urllib/request.py", line 494, in _call_chain
    result = func(*args)
  File "/opt/hpds/miniconda/lib/python3.9/urllib/request.py", line 641, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 403: Forbidden
This is my setup file:

Code: Select all

#========================================================
# Setup file for Code_Saturne installation
#========================================================
#
#--------------------------------------------------------
# Download packages ?
#--------------------------------------------------------
download  yes
#
#--------------------------------------------------------
# Install Code_Saturne with debugging symbols
#--------------------------------------------------------
debug     no
#
#--------------------------------------------------------
# Installation directory
#--------------------------------------------------------
prefix    /home/bryan/Code_Saturne/7.0.4
#
#--------------------------------------------------------
# Optional architecture Name (installation subdirectory)
#--------------------------------------------------------
use_arch  no
arch      Linux_x86_64
#
#--------------------------------------------------------
# C compiler and optional MPI wrapper
#--------------------------------------------------------
compC     /usr/bin/cc
mpiCompC  /usr/bin/mpicc
#
#--------------------------------------------------------
# Fortran compiler
#--------------------------------------------------------
compF    /usr/bin/f95
#
#--------------------------------------------------------
# C++ compiler and MPI wrapper for optional packages
#
# Required only for static builds using the MED library
# or for build of optional modules such as MEDCoupling
# support.
#--------------------------------------------------------
compCxx     /usr/bin/c++
mpiCompCxx  /usr/bin/mpicxx
#
#--------------------------------------------------------
# Python interpreter.
#--------------------------------------------------------
python    /opt/hpds/miniconda/bin/python3
#
#--------------------------------------------------------
# Disable the Graphical user Interface ?
#--------------------------------------------------------
disable_gui  no
#
#--------------------------------------------------------
# Disable frontend (also disables GUI) ?
# May be useful for debug builds and HPC cluster builds
# installed side-by side with a full build.
#--------------------------------------------------------
disable_frontend  no
#
#--------------------------------------------------------
# Optional SALOME platform install path.
#
# This is the path for the main SALOME directory,
# not the application directory.
#
# If Code_Saturne is built with SALOME support,
# running "code_saturne salome" will launch the
# associated application, containing the CFDSTUDY module.
#--------------------------------------------------------
salome    no
#
#--------------------------------------------------------
# Optional packages:
# ------------------
#
# MED / HDF5  For MED file format support
#             (used by SALOME and by Gmsh)
#
# CGNS / HDF5 For CGNS file support
#             (used by many meshing tools)
#
# Scotch (includes PT-Scotch) and/or ParMetis
# for parallel partitioning
#
#   For Linux workstations, HDF5, CGNS, and even MED
# packages may be available through the package manager.
# HDF5 is also often available on large systems.
# When building with SALOME, the platform distribution's
# packages may be used, by setting in the matching entry
# 'yes' under the "Use" column and simply 'salome' under
# the path column.
#
# Scotch and Pt-Scotch are available in some Linux
# distributions, but may be built with options
# incompatible with non-threaded Code_Saturne runs.
#
#   To install CGNS or ParMetis, the CMake
# configuration/installation tool is required
# (it is available in most Linux distributions).
#--------------------------------------------------------
#
#  Name    Use   Install  Path
#
hdf5       yes   yes      None
cgns       yes   yes      None
med        yes   yes      None
scotch     no    no       None
parmetis   no    no       None
#
#========================================================
Yvan Fournier
Posts: 4107
Joined: Mon Feb 20, 2012 3:25 pm

Re: HTTP Error 403 when running second pass of install_saturne.py

Post by Yvan Fournier »

Hello,

The error seems to be when downloading MED, so is the same as that described in this post : viewtopic.php?t=3159.

You can try the solution given there, or download MED manually.

Also, why install v7.04 instead of v7.0.6, the latest bug-fix release for that branch ? And even that is assuming you already have computations started on another machine with v7.0. Otherwise, for new studies, v8.0 is recommended.

Best regards,

Yvan
saintlyknighted
Posts: 14
Joined: Sun Aug 06, 2023 3:40 am

Re: HTTP Error 403 when running second pass of install_saturne.py

Post by saintlyknighted »

Hello Yvan,

I have tried the solution suggested in the other thread (editing install_saturne.py) and it works. Thank you!

I am using v7.0.4 as I am using a code written by someone else in that version.

Cheers,
Bryan
Yvan Fournier
Posts: 4107
Joined: Mon Feb 20, 2012 3:25 pm

Re: HTTP Error 403 when running second pass of install_saturne.py

Post by Yvan Fournier »

Hello,

If the code written by someone else is only user-defined code, it should work in v7.0.6. If other functions are modifed, than it is a derivative version and it is best to stay on the same release (but the "someone else" should handle the support aspect in this case, and if they are not here anymore, things quickly become messy with unmaintained code ; unfortunately common in research labs).

Actually, if you pull a Git branch based on v7.0.4, commit the previous developer's changes to that, and rebase it on the v7.0 branch head, you can probably follow the v7.0 release fixes without much effort. Switching to v8.0 would probably be more involved...

Best regards,

Yvan
Post Reply