From 760eb9ad5ae9777b4f1a609be7f43ac1fe7c83e9 Mon Sep 17 00:00:00 2001 From: katarinasupe Date: Tue, 27 Oct 2026 12:32:45 +0100 Subject: [PATCH 1/4] Merge the six Linux install pages into one Since 3.13 there is one DEB and one RPM package that run on any Linux with glibc 2.31 or newer, so Debian, Ubuntu, CentOS, Fedora, Rocky and Red Hat no longer need their own pages. The new Linux page has a DEB and an RPM section, shared start/stop/configuration and troubleshooting, and states the glibc requirement instead of per-distro versions. Old URLs redirect; check-release step 11 names the new page. --- next.config.mjs | 68 ++++- pages/advanced-algorithms/install-mage.mdx | 5 +- .../custom-query-modules/cpp/cpp-example.mdx | 2 +- pages/deployment/environments/aws.mdx | 11 +- pages/deployment/environments/azure.mdx | 11 +- pages/deployment/environments/gcp.mdx | 11 +- pages/getting-started/install-memgraph.mdx | 35 +-- .../getting-started/install-memgraph/_meta.ts | 7 +- .../install-memgraph/centos.mdx | 160 ------------ .../install-memgraph/debian.mdx | 214 --------------- .../direct-download-links.mdx | 6 +- .../install-memgraph/fedora.mdx | 159 ------------ .../install-memgraph/linux.mdx | 244 ++++++++++++++++++ .../install-memgraph/redhat.mdx | 173 ------------- .../install-memgraph/rocky.mdx | 160 ------------ .../install-memgraph/ubuntu.mdx | 191 -------------- skills/check-release/SKILL.md | 12 +- 17 files changed, 334 insertions(+), 1135 deletions(-) delete mode 100644 pages/getting-started/install-memgraph/centos.mdx delete mode 100644 pages/getting-started/install-memgraph/debian.mdx delete mode 100644 pages/getting-started/install-memgraph/fedora.mdx create mode 100644 pages/getting-started/install-memgraph/linux.mdx delete mode 100644 pages/getting-started/install-memgraph/redhat.mdx delete mode 100644 pages/getting-started/install-memgraph/rocky.mdx delete mode 100644 pages/getting-started/install-memgraph/ubuntu.mdx diff --git a/next.config.mjs b/next.config.mjs index d7f086217..6d44c94ab 100644 --- a/next.config.mjs +++ b/next.config.mjs @@ -19,6 +19,66 @@ export default withNextra({ reactStrictMode: true, async redirects() { return [ + { + source: '/getting-started/install-memgraph/debian', + destination: '/getting-started/install-memgraph/linux', + permanent: true + }, + { + source: '/getting-started/install-memgraph/debian.md', + destination: '/getting-started/install-memgraph/linux.md', + permanent: true + }, + { + source: '/getting-started/install-memgraph/ubuntu', + destination: '/getting-started/install-memgraph/linux', + permanent: true + }, + { + source: '/getting-started/install-memgraph/ubuntu.md', + destination: '/getting-started/install-memgraph/linux.md', + permanent: true + }, + { + source: '/getting-started/install-memgraph/centos', + destination: '/getting-started/install-memgraph/linux', + permanent: true + }, + { + source: '/getting-started/install-memgraph/centos.md', + destination: '/getting-started/install-memgraph/linux.md', + permanent: true + }, + { + source: '/getting-started/install-memgraph/fedora', + destination: '/getting-started/install-memgraph/linux', + permanent: true + }, + { + source: '/getting-started/install-memgraph/fedora.md', + destination: '/getting-started/install-memgraph/linux.md', + permanent: true + }, + { + source: '/getting-started/install-memgraph/rocky', + destination: '/getting-started/install-memgraph/linux', + permanent: true + }, + { + source: '/getting-started/install-memgraph/rocky.md', + destination: '/getting-started/install-memgraph/linux.md', + permanent: true + }, + { + source: '/getting-started/install-memgraph/redhat', + destination: '/getting-started/install-memgraph/linux', + permanent: true + }, + { + source: '/getting-started/install-memgraph/redhat.md', + destination: '/getting-started/install-memgraph/linux.md', + permanent: true + }, { source: '/ai-ecosystem/mcp', destination: '/ai-ecosystem/integrations/mcp', @@ -1226,7 +1286,7 @@ export default withNextra({ }, { source: '/memgraph/install-memgraph-on-debian', - destination: '/getting-started/install-memgraph/debian', + destination: '/getting-started/install-memgraph/linux', permanent: true }, { @@ -1276,7 +1336,7 @@ export default withNextra({ }, { source: '/memgraph/linux-installation-troubleshooting', - destination: '/getting-started/install-memgraph/ubuntu', + destination: '/getting-started/install-memgraph/linux#troubleshooting', permanent: true }, { @@ -1326,7 +1386,7 @@ export default withNextra({ }, { source: '/memgraph/install-memgraph-on-ubuntu', - destination: '/getting-started/install-memgraph/ubuntu', + destination: '/getting-started/install-memgraph/linux', permanent: true }, { @@ -2399,7 +2459,7 @@ export default withNextra({ }, { source: '/memgraph/getting-started/installation/debian-installation', - destination: '/getting-started/install-memgraph/debian', + destination: '/getting-started/install-memgraph/linux', permanent: true }, { diff --git a/pages/advanced-algorithms/install-mage.mdx b/pages/advanced-algorithms/install-mage.mdx index 82853fb85..225cff9a7 100644 --- a/pages/advanced-algorithms/install-mage.mdx +++ b/pages/advanced-algorithms/install-mage.mdx @@ -66,9 +66,8 @@ are untested. {

Install Memgraph

} Install the Memgraph package first — the `memgraph-mage` package depends on a -matching `memgraph` package of the same version. Follow the -[Ubuntu](/getting-started/install-memgraph/ubuntu) or -[CentOS](/getting-started/install-memgraph/centos) installation guide. +matching `memgraph` package of the same version. Follow [Install Memgraph on +Linux](/getting-started/install-memgraph/linux). {

Download the MAGE package

} diff --git a/pages/custom-query-modules/cpp/cpp-example.mdx b/pages/custom-query-modules/cpp/cpp-example.mdx index 1cfbf7ea0..38849594a 100644 --- a/pages/custom-query-modules/cpp/cpp-example.mdx +++ b/pages/custom-query-modules/cpp/cpp-example.mdx @@ -26,7 +26,7 @@ First, you need to run the Memgraph instance. You can do this by running the fol docker run -p 7687:7687 -p 7444:7444 --name memgraph memgraph/memgraph-mage ``` Keep in mind that you can use the Docker image with just Memgraph or with Memgraph and MAGE. It won't change the way you develop your C++ query module. -If you want to run Memgraph on a native Linux machine, follow these [installation steps](/getting-started/install-memgraph/ubuntu) +If you want to run Memgraph on a native Linux machine, follow these [installation steps](/getting-started/install-memgraph/linux) ### Enter into memgraph container shell diff --git a/pages/deployment/environments/aws.mdx b/pages/deployment/environments/aws.mdx index 74f6172a8..6d7d1fb83 100644 --- a/pages/deployment/environments/aws.mdx +++ b/pages/deployment/environments/aws.mdx @@ -168,15 +168,8 @@ to follow the steps below: - Depending on the Linux distribution you are using, you can follow the guide for - installing Memgraph on each distribution: - - - [Ubuntu](/getting-started/install-memgraph/ubuntu) - - [Fedora](/getting-started/install-memgraph/fedora) - - [Debian](/getting-started/install-memgraph/debian) - - [Centos](/getting-started/install-memgraph/centos) - - [Red Hat](/getting-started/install-memgraph/redhat) - - [Rocky](/getting-started/install-memgraph/rocky) + Follow [Install Memgraph on Linux](/getting-started/install-memgraph/linux), + which covers Debian, Ubuntu, CentOS, Fedora, Rocky Linux and Red Hat. diff --git a/pages/deployment/environments/azure.mdx b/pages/deployment/environments/azure.mdx index 3de908e29..9288ebaae 100644 --- a/pages/deployment/environments/azure.mdx +++ b/pages/deployment/environments/azure.mdx @@ -166,15 +166,8 @@ to follow the steps below: - Depending on the Linux distribution you are using, you can follow the guide for - installing Memgraph on each distribution: - - - [Ubuntu](/getting-started/install-memgraph/ubuntu) - - [Fedora](/getting-started/install-memgraph/fedora) - - [Debian](/getting-started/install-memgraph/debian) - - [Centos](/getting-started/install-memgraph/centos) - - [Red Hat](/getting-started/install-memgraph/redhat) - - [Rocky](/getting-started/install-memgraph/rocky) + Follow [Install Memgraph on Linux](/getting-started/install-memgraph/linux), + which covers Debian, Ubuntu, CentOS, Fedora, Rocky Linux and Red Hat. diff --git a/pages/deployment/environments/gcp.mdx b/pages/deployment/environments/gcp.mdx index 4c2ddd921..e0d50d393 100644 --- a/pages/deployment/environments/gcp.mdx +++ b/pages/deployment/environments/gcp.mdx @@ -176,15 +176,8 @@ to follow the steps below: - Depending on the Linux distribution you are using, you can follow the guide for - installing Memgraph on each distribution: - - - [Ubuntu](/getting-started/install-memgraph/ubuntu) - - [Fedora](/getting-started/install-memgraph/fedora) - - [Debian](/getting-started/install-memgraph/debian) - - [Centos](/getting-started/install-memgraph/centos) - - [Red Hat](/getting-started/install-memgraph/redhat) - - [Rocky](/getting-started/install-memgraph/rocky) + Follow [Install Memgraph on Linux](/getting-started/install-memgraph/linux), + which covers Debian, Ubuntu, CentOS, Fedora, Rocky Linux and Red Hat. diff --git a/pages/getting-started/install-memgraph.mdx b/pages/getting-started/install-memgraph.mdx index e528dc602..533b0f16f 100644 --- a/pages/getting-started/install-memgraph.mdx +++ b/pages/getting-started/install-memgraph.mdx @@ -41,11 +41,11 @@ installation options and pick the preferred one. As of version 3.13, the native Linux packages are **distro-agnostic**: there is -a single `.deb` package for all Debian-family distributions (Debian 12+, Ubuntu -22.04+) and a single `.rpm` package for all RHEL-family distributions -(RHEL/CentOS/Rocky 9+, Fedora 42+), per architecture. Any Linux with glibc 2.31 -or newer is supported. The per-distribution pages below therefore install the -same package — they differ only in distribution-specific setup steps. +a single `.deb` package for all Debian-family distributions and a single +`.rpm` package for all RHEL-family distributions, per architecture. Any Linux +with glibc 2.31 or newer is supported. [Install Memgraph on +Linux](/getting-started/install-memgraph/linux) covers both packages and how to +check your glibc version. Memgraph requires **Python 3.10 or newer** on the host (used by Python query modules and the auth/SSO modules). Memgraph binds to the host's Python at @@ -61,24 +61,8 @@ Python already. href="/getting-started/install-memgraph/docker" /> - - - - - diff --git a/pages/getting-started/install-memgraph/_meta.ts b/pages/getting-started/install-memgraph/_meta.ts index 1b1f632bb..d6a31e3ec 100644 --- a/pages/getting-started/install-memgraph/_meta.ts +++ b/pages/getting-started/install-memgraph/_meta.ts @@ -1,11 +1,6 @@ export default { "docker": "Docker", - "debian": "Debian", - "ubuntu": "Ubuntu", - "centos": "CentOS", - "fedora": "Fedora", - "rocky": "Rocky", - "redhat": "Red Hat", + "linux": "Linux", "memgraph-cloud": "Memgraph Cloud", "docker-compose": "Docker Compose", "kubernetes": "Kubernetes", diff --git a/pages/getting-started/install-memgraph/centos.mdx b/pages/getting-started/install-memgraph/centos.mdx deleted file mode 100644 index 68e37ae0a..000000000 --- a/pages/getting-started/install-memgraph/centos.mdx +++ /dev/null @@ -1,160 +0,0 @@ ---- -title: Install Memgraph on CentOS from RPM package -description: Install Memgraph from RPM package on CentOS simply and efficiently using our documentation. ---- - -import { Callout } from 'nextra/components' -import { Steps } from 'nextra/components' -import CodeSnippet from '/components/code-snippet/CodeSnippet' - -# Install Memgraph on CentOS from RPM package - -Install and run Memgraph from a RPM package on: - - **CentOS 9** - - **CentOS 10** - - -Newer versions of Memgraph might not be backward -compatible with older versions and you might not be able to load storage -snapshots between different versions. In that case, please contact the Memgraph -team and we'll help with the migration as much as possible. - - -## Installation guide - - -{

Download Memgraph RPM CentOS package

} - -Downloaded the latest Memgraph RPM CentOS package from the [Memgraph Download -Hub](https://memgraph.com/download/). - -You can also use [direct download -links](/getting-started/install-memgraph/direct-download-links) to get the -latest Memgraph packages. - -For example: - - - - - -For the latest version of Memgraph, replace the version in the download command -with the one from the [direct download -links](/getting-started/install-memgraph/direct-download-links) page. - - - -{

Install Memgraph

} - -After downloading the Memgraph RPM package, you can install it by issuing the -following command: - -``` -sudo dnf install -y ./memgraph-3.14.0_1-1.x86_64.rpm -``` - -If you run into any troubles while installing Memgraph, contact us on -[Discord](https://discord.gg/memgraph). - -{

Start Memgraph

} - -After successful installation, Memgraph can be started as a service using the -following command: - -``` -sudo systemctl start memgraph -``` -To verify that Memgraph is running, run the following command: - -``` -journalctl --unit memgraph -``` - -If successful, you should receive an output similar to the following: - -``` -You are running Memgraph vX.X.X -``` - -If you want the Memgraph database instance to start automatically on each startup, run the -following command: - -``` -systemctl enable memgraph -``` - -You can also check the status of the Memgraph database instance by running: -``` -systemctl status memgraph -``` - -{

Troubleshooting

} - -As of Memgraph 3.13, the package installs the Python libraries used by the -bundled query modules — including [NumPy](https://numpy.org/), [SciPy](https://www.scipy.org/) and [NetworkX](https://networkx.org/) — automatically -during package installation (the machine needs network access at install -time). If that automatic installation was skipped (`MG_SKIP_PYTHON_DEPS=1`) or -failed, Memgraph reports it with a note like this on startup: - -``` -You are running Memgraph v3.14.0 -To get started with Memgraph, visit https://memgr.ph/start -NOTE: Please install networkx, numpy, scipy to be able to use proxied NetworkX algorithms. E.g., CALL nxalg.pagerank(...). -``` - -In that case, install the missing libraries manually as the `memgraph` user -(they must land in the `memgraph` user's environment, since the embedded -interpreter runs as `memgraph`): - -```bash -sudo runuser -l memgraph -c 'python3 -m pip install --user networkx numpy scipy' -``` - -If you are not interested in working with query modules that depend on these -libraries, you can ignore the warnings. - -{

Connect to the database

} - -To [query](/querying) the database from the console, you need to install -[`mgconsole`](/getting-started/cli). - -You can also connect to the database using one of the [client -libraries](/client-libraries) or visual-user interface [Memgraph -Lab](/memgraph-lab). - - - -## Stop Memgraph - -To shut down the Memgraph server, issue the following command: - -``` -systemctl stop memgraph -``` - -## Start Memgraph - -Memgraph can be started as a service using the following command: - -``` -systemctl start memgraph -``` - -## Configuration - - - -If you're experiencing issues related to the maximum number of memory map areas, -you can resolve them by [adjusting the `vm.max_map_count` -parameter](/database-management/system-configuration#increasing-memory-map-areas). Keep in -mind that the linked configuration guide is not written for CentOS, steps will be -different, but the goal is the same. - - - -The Memgraph configuration is available in `/etc/memgraph/memgraph.conf`. If the -configuration file is altered, Memgraph needs to be restarted. Check all the -configuration options in the [configuration -settings](/database-management/configuration). diff --git a/pages/getting-started/install-memgraph/debian.mdx b/pages/getting-started/install-memgraph/debian.mdx deleted file mode 100644 index d795cc371..000000000 --- a/pages/getting-started/install-memgraph/debian.mdx +++ /dev/null @@ -1,214 +0,0 @@ ---- -title: Install Memgraph on Debian -description: Navigate Memgraph's installation and utilization on Debian systems with our strategically crafted guide. Ensuring a seamless graph computing experience. ---- - -import { Callout } from 'nextra/components' -import { Steps } from 'nextra/components' -import CodeSnippet from '/components/code-snippet/CodeSnippet' - -# Install Memgraph on Debian - -Install and run Memgraph on Debian 12 or Debian 13. - - -Newer versions of Memgraph might not be backward -compatible with older versions and you might not be able to load storage -snapshots between different versions. In that case, please contact the Memgraph -team and we'll help with the migration as much as possible. - - -## Installation guide - - - -{

Download Memgraph Debian Package

} - -Downloaded the latest Memgraph Debian Package from the [Memgraph Download Hub](https://memgraph.com/download/). - -You can also use [direct download -links](/getting-started/install-memgraph/direct-download-links) to get the -latest Memgraph packages. - -For example, for Debian 12: - - - - - -For the latest version of Memgraph, replace the version in the download command -with the one from the [direct download -links](/getting-started/install-memgraph/direct-download-links) page. - - - -{

Install Memgraph

} - -After downloading Memgraph as a Debian package, install it by running the -following: - -``` -sudo dpkg -i /path-to/memgraph_.deb -``` - - - -Why use sudo? - -In order to perform some actions on your operating system like installing new -software, you may need **superuser** privileges (commonly called **root**). - - - -{

Troubleshooting

} - -**Unable to use `sudo`** - -If you encounter the following error: - -``` --bash: sudo: command not found -``` - -Install `sudo` with: - -``` -apt update -y -apt install sudo -y -``` - -**Unable to install the Memgraph package with `dpkg`** - -While running the following `dpkg` command: - -```bash -dpkg -i /path-to/memgraph_.deb -``` - -you may encounter errors that resemble the following: - -``` -dpkg: error processing package memgraph (--install): dependency problems - -leaving unconfigured Errors were encountered while processing: memgraph -``` - -These errors indicate that you don’t have all of the necessary dependencies -installed. Before attempting to resolve these dependency issues, it's -recommended to update your package lists to ensure you have the latest -information about available packages. Run the following command: - -``` -sudo apt update -``` - -After updating the package lists, you can install the missing dependencies and -finish the installation of Memgraph by issuing the following command: - -``` -sudo apt-get install -f -``` - -This command tells `apt` to fix broken dependencies; it will attempt to correct -a system with broken dependencies in place. - -{

Verify that Memgraph is running

} - -To verify that Memgraph is running, run the following: - -``` -sudo journalctl --unit memgraph -``` - -If successful, you should receive an output similar to the following: - -``` -You are running Memgraph vX.X.X -``` - -If the Memgraph database instance is not running, you can start it explicitly: - -``` -sudo systemctl start memgraph -``` - -If you want the Memgraph database instance to start automatically on each startup, run the -following command: - -``` -systemctl enable memgraph -``` - -You can also check the status of the Memgraph database instance by running: -``` -sudo systemctl status memgraph -``` - -{

Troubleshooting

} - -As of Memgraph 3.13, the package installs the Python libraries used by the -bundled query modules — including [NumPy](https://numpy.org/), [SciPy](https://www.scipy.org/) and [NetworkX](https://networkx.org/) — automatically -during package installation (the machine needs network access at install -time). If that automatic installation was skipped (`MG_SKIP_PYTHON_DEPS=1`) or -failed, Memgraph reports it with a note like this on startup: - -``` -You are running Memgraph v3.14.0 -To get started with Memgraph, visit https://memgr.ph/start -NOTE: Please install networkx, numpy, scipy to be able to use proxied NetworkX algorithms. E.g., CALL nxalg.pagerank(...). -``` - -In that case, install the missing libraries manually as the `memgraph` user -(they must land in the `memgraph` user's environment, since the embedded -interpreter runs as `memgraph`): - -```bash -sudo runuser -l memgraph -c 'python3 -m pip install --user networkx numpy scipy' -``` - -If you are not interested in working with query modules that depend on these -libraries, you can ignore the warnings. - -If you run into any troubles while installing Memgraph, contact us on -[Discord](https://discord.gg/memgraph). - -{

Connect to the database

} - -To [query](/querying) the database from the console, you need to install -[`mgconsole`](/getting-started/cli). - -You can also connect to the database using one of the [client -libraries](/client-libraries) or visual-user interface [Memgraph -Lab](/memgraph-lab). - - - -## Stop Memgraph - -To shut down the Memgraph server, issue the following command: - -``` -sudo systemctl stop memgraph -``` - -## Start Memgraph - -To start the Memgraph server, issue the following command: - -``` -sudo systemctl start memgraph -``` - -## Configuration - - - -If you're experiencing issues related to the maximum number of memory map areas, -you can resolve them by [adjusting the `vm.max_map_count` -parameter](/database-management/system-configuration#increasing-memory-map-areas). - - - -The Memgraph configuration is available in `/etc/memgraph/memgraph.conf`. If the -configuration file is altered, Memgraph needs to be restarted. Check all the -configuration options in the [Configuration -section](/database-management/configuration). diff --git a/pages/getting-started/install-memgraph/direct-download-links.mdx b/pages/getting-started/install-memgraph/direct-download-links.mdx index c96248107..8e82449f2 100644 --- a/pages/getting-started/install-memgraph/direct-download-links.mdx +++ b/pages/getting-started/install-memgraph/direct-download-links.mdx @@ -15,7 +15,7 @@ latest version of Memgraph database, take a look at the list below. As of version 3.13, the Linux packages are **distro-agnostic**: there is a single `.deb` for all Debian-family distributions and a single `.rpm` for all RHEL-family distributions, per architecture. They run on any Linux with glibc -2.31 or newer (Debian 12+, Ubuntu 22.04+, RHEL/CentOS/Rocky 9+, Fedora 42+). +2.31 or newer. The Linux packages (`.deb` and `.rpm`) are built in stripped `RelWithDebInfo` mode and are performance-equivalent to the former `Release` builds. Their debug @@ -43,8 +43,8 @@ what they contain and how to run them. ## Linux One package per package format and architecture. The `.deb` installs on any -Debian-family distribution (Debian 12+, Ubuntu 22.04+) and the `.rpm` on any -RHEL-family distribution (RHEL/CentOS/Rocky 9+, Fedora 42+). Each main package +Debian-family distribution and the `.rpm` on any RHEL-family distribution with +glibc 2.31 or newer. Each main package has a matching `memgraph-debuginfo` package containing its debug symbols. The `-malloc` variants are builds without jemalloc, using the system allocator diff --git a/pages/getting-started/install-memgraph/fedora.mdx b/pages/getting-started/install-memgraph/fedora.mdx deleted file mode 100644 index 70e5fc1ac..000000000 --- a/pages/getting-started/install-memgraph/fedora.mdx +++ /dev/null @@ -1,159 +0,0 @@ ---- -title: Install Memgraph on Fedora from RPM package -description: Install Memgraph from RPM package on Fedora simply and efficiently using our documentation. ---- - -import { Callout } from 'nextra/components' -import { Steps } from 'nextra/components' -import CodeSnippet from '/components/code-snippet/CodeSnippet' - -# Install Memgraph on Fedora from RPM package - -Install and run Memgraph from a RPM package on: - - **Fedora 43** - - **Fedora 44** - - -Newer versions of Memgraph might not be backward -compatible with older versions and you might not be able to load storage -snapshots between different versions. In that case, please contact the Memgraph -team and we'll help with the migration as much as possible. - - - ## Installation guide - - - -{

Download Memgraph RPM Fedora package

} - -Downloaded the latest Memgraph RPM Fedora package from the [Memgraph Download -Hub](https://memgraph.com/download/). - -You can also use [direct download -links](/getting-started/install-memgraph/direct-download-links) to get the -latest Memgraph packages. - -For example: - - - - - -For the latest version of Memgraph, replace the version in the download command -with the one from the [direct download -links](/getting-started/install-memgraph/direct-download-links) page. - - - -{

Install Memgraph

} - -After downloading the Memgraph RPM package, you can install it by issuing the -following command: - -``` console -sudo dnf install -y ./memgraph-3.14.0_1-1.x86_64.rpm -``` - -If you run into any troubles while installing Memgraph, contact us on -[Discord](https://discord.gg/memgraph). - -{

Start Memgraph

} - -After successful installation, Memgraph can be started as a service using the -following command: - -``` -sudo systemctl start memgraph -``` -To verify that Memgraph is running, run the following command: - -``` -journalctl --unit memgraph -``` - -If successful, you should receive an output similar to the following: - -``` -You are running Memgraph vX.X.X -``` - -If you want the Memgraph database instance to start automatically on each startup, run the -following command: - -``` -systemctl enable memgraph -``` - -You can also check the status of the Memgraph database instance by running: -``` -systemctl status memgraph -``` - -{

Troubleshooting

} - -As of Memgraph 3.13, the package installs the Python libraries used by the -bundled query modules — including [NumPy](https://numpy.org/), [SciPy](https://www.scipy.org/) and [NetworkX](https://networkx.org/) — automatically -during package installation (the machine needs network access at install -time). If that automatic installation was skipped (`MG_SKIP_PYTHON_DEPS=1`) or -failed, Memgraph reports it with a note like this on startup: - -``` -You are running Memgraph v3.14.0 -To get started with Memgraph, visit https://memgr.ph/start -NOTE: Please install networkx, numpy, scipy to be able to use proxied NetworkX algorithms. E.g., CALL nxalg.pagerank(...). -``` - -In that case, install the missing libraries manually as the `memgraph` user -(they must land in the `memgraph` user's environment, since the embedded -interpreter runs as `memgraph`): - -```bash -sudo runuser -l memgraph -c 'python3 -m pip install --user networkx numpy scipy' -``` - -If you are not interested in working with query modules that depend on these -libraries, you can ignore the warnings. - -{

Connect to the database

} - -To [query](/querying) the database from the console, you need to install -[`mgconsole`](/getting-started/cli). - -You can also connect to the database using one of the [client -libraries](/client-libraries) or visual-user interface [Memgraph -Lab](/memgraph-lab). - - - -## Stop Memgraph - -To shut down the Memgraph server, issue the following command: - -``` -systemctl stop memgraph -``` - -## Start Memgraph - -Memgraph can be started as a service using the following command: - -``` -systemctl start memgraph -``` - -## Configuration - - - -If you're experiencing issues related to the maximum number of memory map areas, -you can resolve them by [adjusting the `vm.max_map_count` -parameter](/database-management/system-configuration#increasing-memory-map-areas). Keep in -mind that the linked configuration guide is not written for Fedora, steps will be -different, but the goal is the same. - - - -The Memgraph configuration is available in `/etc/memgraph/memgraph.conf`. If the -configuration file is altered, Memgraph needs to be restarted. Check all the -configuration options in the [configuration -settings](/database-management/configuration). diff --git a/pages/getting-started/install-memgraph/linux.mdx b/pages/getting-started/install-memgraph/linux.mdx new file mode 100644 index 000000000..aadcc5fcd --- /dev/null +++ b/pages/getting-started/install-memgraph/linux.mdx @@ -0,0 +1,244 @@ +--- +title: Install Memgraph on Linux +description: Install Memgraph from the DEB or RPM package on Debian, Ubuntu, CentOS, Fedora, Rocky Linux and Red Hat, then run it as a systemd service. +--- + +import { Callout } from 'nextra/components' +import { Steps } from 'nextra/components' +import CodeSnippet from '/components/code-snippet/CodeSnippet' + +# Install Memgraph on Linux + +Install Memgraph natively on Linux from a DEB or RPM package and run it as a +systemd service. Since Memgraph 3.13, there is one DEB package and one RPM +package per architecture (x86_64 and ARM64), not one per distribution. They +run on any Linux distribution with glibc 2.31 or newer. + +| Distribution family | Package | +|---|---| +| Debian, Ubuntu and other distributions that use `apt` | DEB | +| Red Hat Enterprise Linux, CentOS, Rocky Linux, Fedora and other distributions that use `dnf` | RPM | + +To check your glibc version, run: + +```bash +ldd --version +``` + +The packages also need Python 3.10 or newer on the host. On +distributions whose default `python3` is older, such as CentOS 9, the package +installs and uses a newer Python interpreter. + +To install on Windows, see [Install Memgraph on Windows with +WSL](/getting-started/install-memgraph/wsl). To run Memgraph in a container, +see [Docker](/getting-started/install-memgraph/docker). + + +Storage snapshots from one Memgraph version might not load in another. Before +you install a newer version over an existing one, follow +[Upgrades](/database-management/upgrades). + + +## Install the DEB package on Debian or Ubuntu + +Download the DEB package, then install it with `dpkg`. + + + +{

Download the DEB package

} + +Download the package from the [Memgraph Download +Hub](https://memgraph.com/download/) or with a link from [direct download +links](/getting-started/install-memgraph/direct-download-links). For example, +the x86_64 package: + + + +For the ARM64 package, the system allocator build or a newer version, take the +link from [direct download +links](/getting-started/install-memgraph/direct-download-links) and use its +file name in the next step. + +{

Install the DEB package

} + +Install the package with `dpkg`: + +```bash +sudo dpkg -i ./memgraph_3.14.0-1_amd64.deb +``` + +If `sudo` isn't installed or `dpkg` reports dependency problems, see +[Troubleshooting](#troubleshooting). + + + +When the package is installed, [start Memgraph](#start-memgraph). + +## Install the RPM package on CentOS, Fedora, Rocky Linux or Red Hat + +Download the RPM package, then install it with `dnf`. + + + +{

Download the RPM package

} + +Download the package from the [Memgraph Download +Hub](https://memgraph.com/download/) or with a link from [direct download +links](/getting-started/install-memgraph/direct-download-links). For example, +the x86_64 package: + + + +For the ARM64 (aarch64) package, the system allocator build or a newer version, +take the link from [direct download +links](/getting-started/install-memgraph/direct-download-links) and use its +file name in the next step. + +{

Install the RPM package

} + +Install the package with `dnf`: + +```bash +sudo dnf install -y ./memgraph-3.14.0_1-1.x86_64.rpm +``` + +On Red Hat Enterprise Linux, SELinux can block Memgraph's access to system +resources. See [SELinux blocks Memgraph](#selinux-blocks-memgraph). + + + +When the package is installed, [start Memgraph](#start-memgraph). + +## Start Memgraph + +Start Memgraph as a service. If it's already running, the command does +nothing: + +```bash +sudo systemctl start memgraph +``` + +To check that Memgraph is running, read its log: + +```bash +sudo journalctl --unit memgraph +``` + +The log contains a line like this: + +```plaintext copy=false +You are running Memgraph vX.X.X +``` + +To check the state of the service: + +```bash +sudo systemctl status memgraph +``` + +To start Memgraph automatically when the machine boots: + +```bash +sudo systemctl enable memgraph +``` + +## Connect to Memgraph + +To [run queries](/querying) from the terminal, install +[`mgconsole`](/getting-started/cli). You can also connect with one of the +[client libraries](/client-libraries) or with [Memgraph Lab](/memgraph-lab), the +visual user interface. + +## Configure Memgraph + +The configuration file is `/etc/memgraph/memgraph.conf`. For all options, see +[Configuration](/database-management/configuration). Memgraph reads the file on +startup, so restart it after you change the file: + +```bash +sudo systemctl restart memgraph +``` + +If Memgraph runs out of memory map areas on large workloads, [increase the +`vm.max_map_count` +parameter](/database-management/system-configuration#increasing-memory-map-areas). + +## Stop Memgraph + +```bash +sudo systemctl stop memgraph +``` + +## Troubleshooting + +The problems below can come up during or after installation. If yours isn't +listed, ask on [Discord](https://discord.gg/memgraph). + +### sudo is not installed on Debian + +If Debian reports the following error: + +```plaintext copy=false +-bash: sudo: command not found +``` + +install `sudo` as the root user: + +```bash +apt update -y +apt install sudo -y +``` + +### dpkg reports dependency problems + +If `dpkg -i` ends with an error like this: + +```plaintext copy=false +dpkg: error processing package memgraph (--install): dependency problems - +leaving unconfigured Errors were encountered while processing: memgraph +``` + +some of the package's dependencies are missing. Update the package lists, then +let `apt` install the missing dependencies and finish installing Memgraph: + +```bash +sudo apt update +sudo apt-get install -f +``` + +### Python libraries for query modules are missing + +Since Memgraph 3.13, the package installs the Python libraries that the bundled +query modules use, including [NumPy](https://numpy.org/), +[SciPy](https://www.scipy.org/) and [NetworkX](https://networkx.org/), during +installation. The machine needs network access at install time. + +If that step was skipped (`MG_SKIP_PYTHON_DEPS=1`) or failed, Memgraph prints a +note like this on startup: + +```plaintext copy=false +You are running Memgraph v3.14.0 +To get started with Memgraph, visit https://memgr.ph/start +NOTE: Please install networkx, numpy, scipy to be able to use proxied NetworkX algorithms. E.g., CALL nxalg.pagerank(...). +``` + +Install the libraries as the `memgraph` user, because Memgraph's embedded +Python interpreter runs as that user and only sees its environment: + +```bash +sudo runuser -l memgraph -c 'python3 -m pip install --user networkx numpy scipy' +``` + +If you don't use the query modules that need these libraries, you can ignore +the note. + +### SELinux blocks Memgraph + +Red Hat Enterprise Linux uses SELinux (Security-Enhanced Linux) to enforce +mandatory access control: each program can reach only the resources its policy +allows. In a [high +availability](/database-management/clustering/high-availability) deployment, +check the SELinux policies if the instances can't see each other. Even with the +firewall open, you might need to disable SELinux, as the [networking +configuration](/deployment/best-practices#networking-configuration) best +practices describe. diff --git a/pages/getting-started/install-memgraph/redhat.mdx b/pages/getting-started/install-memgraph/redhat.mdx deleted file mode 100644 index ec4a685bd..000000000 --- a/pages/getting-started/install-memgraph/redhat.mdx +++ /dev/null @@ -1,173 +0,0 @@ ---- -title: Install Memgraph on Red Hat from RPM package -description: Install Memgraph from RPM package on Red Hat simply and efficiently using our documentation. ---- - -import { Callout } from 'nextra/components' -import { Steps } from 'nextra/components' -import CodeSnippet from '/components/code-snippet/CodeSnippet' - -# Install Memgraph on Red Hat from RPM package - -Install and run Memgraph from a RPM package on: - - **Red Hat 9** - - **Red Hat 10** - - -Newer versions of Memgraph might not be backward -compatible with older versions and you might not be able to load storage -snapshots between different versions. In that case, please contact the Memgraph -team and we'll help with the migration as much as possible. - - - -Red Hat uses SELinux to enforce security policies. -SELinux (Security-Enhanced Linux) is a security mechanism for implementing mandatory access control (MAC) in the Linux kernel. -It restricts programs, users, and processes to only the resources they require, following a least-privilege model. -When deploying Memgraph with high availability (HA), consider checking out this attribute for instance visibility. - - -## Installation guide - - - -{

Download Memgraph RPM Red Hat (CentOS) package

} - -Memgraph ships a single distro-agnostic RPM package per architecture that -installs on any RHEL-family distribution — there are no specifically built -Red Hat packages. - -Download the latest Memgraph RPM package from the [Memgraph Download -Hub](https://memgraph.com/download/). - -You can also use [direct download -links](/getting-started/install-memgraph/direct-download-links) to get the -latest Memgraph packages. - -For example: - - - - - - - -For the latest version of Memgraph, replace the version in the download command -with the one from the [direct download -links](/getting-started/install-memgraph/direct-download-links) page. - - - - -{

Install Memgraph

} - -After downloading the Memgraph RPM package, you can install it by issuing the -following command: - -``` console -sudo dnf install -y ./memgraph-3.14.0_1-1.x86_64.rpm -``` - -If you run into any troubles while installing Memgraph, contact us on -[Discord](https://discord.gg/memgraph). - -{

Start Memgraph

} - -After successful installation, Memgraph can be started as a service using the -following command: - -``` -sudo systemctl start memgraph -``` -To verify that Memgraph is running, run the following command: - -``` -journalctl --unit memgraph -``` - -If successful, you should receive an output similar to the following: - -``` -You are running Memgraph vX.X.X -``` - -If you want the Memgraph database instance to start automatically on each startup, run the -following command: - -``` -systemctl enable memgraph -``` - -You can also check the status of the Memgraph database instance by running: -``` -systemctl status memgraph -``` - -{

Troubleshooting

} - -As of Memgraph 3.13, the package installs the Python libraries used by the -bundled query modules — including [NumPy](https://numpy.org/), [SciPy](https://www.scipy.org/) and [NetworkX](https://networkx.org/) — automatically -during package installation (the machine needs network access at install -time). If that automatic installation was skipped (`MG_SKIP_PYTHON_DEPS=1`) or -failed, Memgraph reports it with a note like this on startup: - -``` -You are running Memgraph v3.14.0 -To get started with Memgraph, visit https://memgr.ph/start -NOTE: Please install networkx, numpy, scipy to be able to use proxied NetworkX algorithms. E.g., CALL nxalg.pagerank(...). -``` - -In that case, install the missing libraries manually as the `memgraph` user -(they must land in the `memgraph` user's environment, since the embedded -interpreter runs as `memgraph`): - -```bash -sudo runuser -l memgraph -c 'python3 -m pip install --user networkx numpy scipy' -``` - -If you are not interested in working with query modules that depend on these -libraries, you can ignore the warnings. - -{

Connect to the database

} - -To [query](/querying) the database from the console, you need to install -[`mgconsole`](/getting-started/cli). - -You can also connect to the database using one of the [client -libraries](/client-libraries) or visual-user interface [Memgraph -Lab](/memgraph-lab). - - - -## Stop Memgraph - -To shut down the Memgraph server, issue the following command: - -``` -systemctl stop memgraph -``` - -## Start Memgraph - -Memgraph can be started as a service using the following command: - -``` -systemctl start memgraph -``` - -## Configuration - - - -If you're experiencing issues related to the maximum number of memory map areas, -you can resolve them by [adjusting the `vm.max_map_count` -parameter](/database-management/system-configuration#increasing-memory-map-areas). Keep in -mind that the linked configuration guide is not written for Red Hat, steps will be -different, but the goal is the same. - - - -The Memgraph configuration is available in `/etc/memgraph/memgraph.conf`. If the -configuration file is altered, Memgraph needs to be restarted. Check all the -configuration options in the [configuration -settings](/database-management/configuration). diff --git a/pages/getting-started/install-memgraph/rocky.mdx b/pages/getting-started/install-memgraph/rocky.mdx deleted file mode 100644 index d4af52039..000000000 --- a/pages/getting-started/install-memgraph/rocky.mdx +++ /dev/null @@ -1,160 +0,0 @@ ---- -title: Install Memgraph on Rocky from RPM package -description: Install Memgraph from RPM package on Rocky simply and efficiently using our documentation. ---- - -import { Callout } from 'nextra/components' -import { Steps } from 'nextra/components' -import CodeSnippet from '/components/code-snippet/CodeSnippet' - -# Install Memgraph on Rocky from RPM package - - -Install and run Memgraph from a RPM package on: - - **Rocky 9** - - **Rocky 10** - - -Newer versions of Memgraph might not be backward -compatible with older versions and you might not be able to load storage -snapshots between different versions. In that case, please contact the Memgraph -team and we'll help with the migration as much as possible. - - - ## Installation guide - - - -{

Download Memgraph RPM Rocky Package

} - -Downloaded the latest Memgraph RPM Rocky package from the [Memgraph Download -Hub](https://memgraph.com/download/). - -You can also use [direct download -links](/getting-started/install-memgraph/direct-download-links) to get the -latest Memgraph packages. - -For example: - - - - - -For the latest version of Memgraph, replace the version in the download command -with the one from the [direct download -links](/getting-started/install-memgraph/direct-download-links) page. - - - -{

Install Memgraph

} - -After downloading the Memgraph RPM package, you can install it by issuing the -following command: - -``` -sudo dnf install -y ./memgraph-3.14.0_1-1.x86_64.rpm -``` - -If you run into any troubles while installing Memgraph, contact us on -[Discord](https://discord.gg/memgraph). - -{

Start Memgraph

} - -After successful installation, Memgraph can be started as a service using the -following command: - -``` -sudo systemctl start memgraph -``` -To verify that Memgraph is running, run the following command: - -``` -journalctl --unit memgraph -``` - -If successful, you should receive an output similar to the following: - -``` -You are running Memgraph vX.X.X -``` - -If you want the Memgraph database instance to start automatically on each startup, run the -following command: - -``` -systemctl enable memgraph -``` - -You can also check the status of the Memgraph database instance by running: -``` -systemctl status memgraph -``` - -{

Troubleshooting

} - -As of Memgraph 3.13, the package installs the Python libraries used by the -bundled query modules — including [NumPy](https://numpy.org/), [SciPy](https://www.scipy.org/) and [NetworkX](https://networkx.org/) — automatically -during package installation (the machine needs network access at install -time). If that automatic installation was skipped (`MG_SKIP_PYTHON_DEPS=1`) or -failed, Memgraph reports it with a note like this on startup: - -``` -You are running Memgraph v3.14.0 -To get started with Memgraph, visit https://memgr.ph/start -NOTE: Please install networkx, numpy, scipy to be able to use proxied NetworkX algorithms. E.g., CALL nxalg.pagerank(...). -``` - -In that case, install the missing libraries manually as the `memgraph` user -(they must land in the `memgraph` user's environment, since the embedded -interpreter runs as `memgraph`): - -```bash -sudo runuser -l memgraph -c 'python3 -m pip install --user networkx numpy scipy' -``` - -If you are not interested in working with query modules that depend on these -libraries, you can ignore the warnings. - -{

Connect to the database

} - -To [query](/querying) the database from the console, you need to install -[`mgconsole`](/getting-started/cli). - -You can also connect to the database using one of the [client -libraries](/client-libraries) or visual-user interface [Memgraph -Lab](/memgraph-lab). - - - -## Stop Memgraph - -To shut down the Memgraph server, issue the following command: - -``` -systemctl stop memgraph -``` - -## Start Memgraph - -Memgraph can be started as a service using the following command: - -``` -systemctl start memgraph -``` - -## Configuration - - - -If you're experiencing issues related to the maximum number of memory map areas, -you can resolve them by [adjusting the `vm.max_map_count` -parameter](/database-management/system-configuration#increasing-memory-map-areas). Keep in -mind that the linked configuration guide is not written for Rocky, steps will be -different, but the goal is the same. - - - -The Memgraph configuration is available in `/etc/memgraph/memgraph.conf`. If the -configuration file is altered, Memgraph needs to be restarted. Check all the -configuration options in the [configuration -settings](/database-management/configuration). \ No newline at end of file diff --git a/pages/getting-started/install-memgraph/ubuntu.mdx b/pages/getting-started/install-memgraph/ubuntu.mdx deleted file mode 100644 index 037681877..000000000 --- a/pages/getting-started/install-memgraph/ubuntu.mdx +++ /dev/null @@ -1,191 +0,0 @@ ---- -title: Install Memgraph on Ubuntu -description: Downloaded the Memgraph Ubuntu package without a hassle. Your resource for improved graph computing execution. ---- - -import { Steps } from 'nextra/components' -import { Callout } from 'nextra/components' -import CodeSnippet from '/components/code-snippet/CodeSnippet' - -# Install Memgraph on Ubuntu - -Install and run Memgraph on: - - **Ubuntu 22.04** - - **Ubuntu 24.04** - - **Ubuntu 26.04** - - -Newer versions of Memgraph might not be backward -compatible with older versions and you might not be able to load storage -snapshots between different versions. In that case, please contact the Memgraph -team and we'll help with the migration as much as possible. - - -## Installation guide - - - -{

Download Memgraph Ubuntu Package

} - -Downloaded the latest Memgraph Ubuntu Package from the [Memgraph Download Hub](https://memgraph.com/download/). - -You can also use [direct download -links](/getting-started/install-memgraph/direct-download-links) to get the -latest Memgraph packages. - -For example: - - - - - -For the latest version of Memgraph, replace the version in the download command -with the one from the [direct download -links](/getting-started/install-memgraph/direct-download-links) page. - - - -{

Install Memgraph

} - -After downloading Memgraph as an Ubuntu package, install it by running the -following: - -``` -sudo dpkg -i /path-to/memgraph_.deb -``` - - - -Why use sudo? - -In order to perform some actions on your operating system like installing new -software, you may need **superuser** privileges (commonly called **root**). - - - -{

Troubleshooting

} - -**Unable to install the Memgraph package with `dpkg`** - -While running the following `dpkg` command: - -```bash -dpkg -i /path-to/memgraph_.deb -``` - -you may encounter errors that resemble the following: - -``` -dpkg: error processing package memgraph (--install): dependency problems - -leaving unconfigured Errors were encountered while processing: memgraph -``` - -These errors indicate that you don’t have all of the necessary dependencies -installed. To install the missing dependencies and finish the installation, -issue the following command: - -``` -sudo apt-get install -f -``` - -{

Verify that Memgraph is running

} - -To verify that Memgraph is running, run the following: - -``` -sudo journalctl --unit memgraph -``` - -If successful, you should receive an output similar to the following: - -``` -You are running Memgraph vX.X.X -``` - -If the Memgraph database instance is not running, you can start it explicitly: - -``` -sudo systemctl start memgraph -``` - -If you want the Memgraph database instance to start automatically on each startup, run the -following command: - -``` -systemctl enable memgraph -``` - -You can also check the status of the Memgraph database instance by running: -``` -sudo systemctl status memgraph -``` - -{

Troubleshooting

} - -As of Memgraph 3.13, the package installs the Python libraries used by the -bundled query modules — including [NumPy](https://numpy.org/), [SciPy](https://www.scipy.org/) and [NetworkX](https://networkx.org/) — automatically -during package installation (the machine needs network access at install -time). If that automatic installation was skipped (`MG_SKIP_PYTHON_DEPS=1`) or -failed, Memgraph reports it with a note like this on startup: - -``` -You are running Memgraph v3.14.0 -To get started with Memgraph, visit https://memgr.ph/start -NOTE: Please install networkx, numpy, scipy to be able to use proxied NetworkX algorithms. E.g., CALL nxalg.pagerank(...). -``` - -In that case, install the missing libraries manually as the `memgraph` user -(they must land in the `memgraph` user's environment, since the embedded -interpreter runs as `memgraph`): - -```bash -sudo runuser -l memgraph -c 'python3 -m pip install --user networkx numpy scipy' -``` - -If you are not interested in working with query modules that depend on these -libraries, you can ignore the warnings. - -If you run into any troubles while installing Memgraph, contact us on -[Discord](https://discord.gg/memgraph). - -{

Connect to the database

} - -To [query](/querying) the database from the console, you need to install -[`mgconsole`](/getting-started/cli). - -You can also connect to the database using one of the [client -libraries](/client-libraries) or visual-user interface [Memgraph -Lab](/memgraph-lab). - - - -## Stop Memgraph - -To shut down the Memgraph server, issue the following command: - -``` -sudo systemctl stop memgraph -``` - -## Start Memgraph - -To start the Memgraph server, issue the following command: - -``` -sudo systemctl start memgraph -``` - -## Configuration - - - -If you're experiencing issues related to the maximum number of memory map areas, -you can resolve them by [adjusting the `vm.max_map_count` -parameter](/database-management/system-configuration#increasing-memory-map-areas). - - - -The Memgraph configuration is available in `/etc/memgraph/memgraph.conf`. If the -configuration file is altered, Memgraph needs to be restarted. Check all the -configuration options in the [Configuration -section](/database-management/configuration). diff --git a/skills/check-release/SKILL.md b/skills/check-release/SKILL.md index b6def9ba5..03d30dfe2 100644 --- a/skills/check-release/SKILL.md +++ b/skills/check-release/SKILL.md @@ -319,18 +319,18 @@ In `pages/release-notes.mdx`, set the date on the release's In `pages/getting-started/install-memgraph/direct-download-links.mdx`, replace **every** occurrence of the previous version with the new one. -- The file has download URLs for Docker, CentOS, Debian, Fedora, Rocky, Red - Hat and Ubuntu packages, with the version both in path segments (`v3.8.1`) - and file names (`3.8.1`). +- The file has download URLs for the Docker images and the DEB and RPM + packages, with the version both in path segments (`v3.8.1`) and file names + (`3.8.1`). - A global find-and-replace of the bare old version string (e.g. `3.8.1` → `3.9.0`) covers both patterns in one pass. - Verify every URL in the file references only the new version. Do the same in the pages that pin the version in their install steps: -- `debian`, `ubuntu`, `centos`, `fedora`, `rocky`, `redhat` and `wsl` under - `pages/getting-started/install-memgraph/`: the download URL, the package - file name and the sample `You are running Memgraph v` output. +- `linux.mdx` and `wsl.mdx` under `pages/getting-started/install-memgraph/`: + the download URLs, the package file names and the sample `You are running + Memgraph v` output. - `pages/getting-started/install-memgraph/docker.mdx`: the `memgraph/memgraph:` and `memgraph/memgraph:-fips` tags. From 24025f942fcf677359b5e84d7df6c14424ae17a6 Mon Sep 17 00:00:00 2001 From: katarinasupe Date: Tue, 27 Oct 2026 12:33:30 +0100 Subject: [PATCH 2/4] List the distributions the Linux packages are tested on --- pages/getting-started/install-memgraph/linux.mdx | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/pages/getting-started/install-memgraph/linux.mdx b/pages/getting-started/install-memgraph/linux.mdx index aadcc5fcd..b92a03986 100644 --- a/pages/getting-started/install-memgraph/linux.mdx +++ b/pages/getting-started/install-memgraph/linux.mdx @@ -14,10 +14,13 @@ systemd service. Since Memgraph 3.13, there is one DEB package and one RPM package per architecture (x86_64 and ARM64), not one per distribution. They run on any Linux distribution with glibc 2.31 or newer. -| Distribution family | Package | -|---|---| -| Debian, Ubuntu and other distributions that use `apt` | DEB | -| Red Hat Enterprise Linux, CentOS, Rocky Linux, Fedora and other distributions that use `dnf` | RPM | +| Distribution family | Package | Tested on | +|---|---|---| +| Debian, Ubuntu and other distributions that use `apt` | DEB | Debian 12, 13; Ubuntu 22.04, 24.04, 26.04 | +| Red Hat Enterprise Linux, CentOS, Rocky Linux, Fedora and other distributions that use `dnf` | RPM | CentOS 9, 10; Fedora 43, 44; Rocky Linux 10 | + +Each release is smoke-tested on the distributions in the last column. Other +distributions with glibc 2.31 or newer should work but aren't tested. To check your glibc version, run: From 42491ee5bcf7f6186465592515d3a479155e46fd Mon Sep 17 00:00:00 2001 From: katarinasupe Date: Tue, 27 Oct 2026 12:34:37 +0100 Subject: [PATCH 3/4] Revert "List the distributions the Linux packages are tested on" This reverts commit 24025f942fcf677359b5e84d7df6c14424ae17a6. --- pages/getting-started/install-memgraph/linux.mdx | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/pages/getting-started/install-memgraph/linux.mdx b/pages/getting-started/install-memgraph/linux.mdx index b92a03986..aadcc5fcd 100644 --- a/pages/getting-started/install-memgraph/linux.mdx +++ b/pages/getting-started/install-memgraph/linux.mdx @@ -14,13 +14,10 @@ systemd service. Since Memgraph 3.13, there is one DEB package and one RPM package per architecture (x86_64 and ARM64), not one per distribution. They run on any Linux distribution with glibc 2.31 or newer. -| Distribution family | Package | Tested on | -|---|---|---| -| Debian, Ubuntu and other distributions that use `apt` | DEB | Debian 12, 13; Ubuntu 22.04, 24.04, 26.04 | -| Red Hat Enterprise Linux, CentOS, Rocky Linux, Fedora and other distributions that use `dnf` | RPM | CentOS 9, 10; Fedora 43, 44; Rocky Linux 10 | - -Each release is smoke-tested on the distributions in the last column. Other -distributions with glibc 2.31 or newer should work but aren't tested. +| Distribution family | Package | +|---|---| +| Debian, Ubuntu and other distributions that use `apt` | DEB | +| Red Hat Enterprise Linux, CentOS, Rocky Linux, Fedora and other distributions that use `dnf` | RPM | To check your glibc version, run: From 306eb0724b578f1b5db82673bd23ebbceb0c712c Mon Sep 17 00:00:00 2001 From: katarinasupe Date: Tue, 27 Oct 2026 14:24:48 +0100 Subject: [PATCH 4/4] Install DEB packages with apt and add a system configuration step Use apt instead of dpkg on the Linux and WSL pages so dependencies install with the package, drop sudo from the downloads, add running without systemd and a Configure the system section, and explain glibc on direct download links. --- pages/deployment/environments/aws.mdx | 3 +- pages/deployment/environments/azure.mdx | 3 +- pages/deployment/environments/gcp.mdx | 3 +- .../direct-download-links.mdx | 4 ++ .../install-memgraph/linux.mdx | 64 ++++++++++--------- .../getting-started/install-memgraph/wsl.mdx | 51 +-------------- 6 files changed, 47 insertions(+), 81 deletions(-) diff --git a/pages/deployment/environments/aws.mdx b/pages/deployment/environments/aws.mdx index 6d7d1fb83..5197e91be 100644 --- a/pages/deployment/environments/aws.mdx +++ b/pages/deployment/environments/aws.mdx @@ -169,7 +169,8 @@ to follow the steps below: Follow [Install Memgraph on Linux](/getting-started/install-memgraph/linux), - which covers Debian, Ubuntu, CentOS, Fedora, Rocky Linux and Red Hat. + which covers DEB- and RPM-based distributions, such as Debian, Ubuntu, + CentOS, Fedora, Rocky Linux and Red Hat. diff --git a/pages/deployment/environments/azure.mdx b/pages/deployment/environments/azure.mdx index 9288ebaae..b2a18677c 100644 --- a/pages/deployment/environments/azure.mdx +++ b/pages/deployment/environments/azure.mdx @@ -167,7 +167,8 @@ to follow the steps below: Follow [Install Memgraph on Linux](/getting-started/install-memgraph/linux), - which covers Debian, Ubuntu, CentOS, Fedora, Rocky Linux and Red Hat. + which covers DEB- and RPM-based distributions, such as Debian, Ubuntu, + CentOS, Fedora, Rocky Linux and Red Hat. diff --git a/pages/deployment/environments/gcp.mdx b/pages/deployment/environments/gcp.mdx index e0d50d393..5f207534c 100644 --- a/pages/deployment/environments/gcp.mdx +++ b/pages/deployment/environments/gcp.mdx @@ -177,7 +177,8 @@ to follow the steps below: Follow [Install Memgraph on Linux](/getting-started/install-memgraph/linux), - which covers Debian, Ubuntu, CentOS, Fedora, Rocky Linux and Red Hat. + which covers DEB- and RPM-based distributions, such as Debian, Ubuntu, + CentOS, Fedora, Rocky Linux and Red Hat. diff --git a/pages/getting-started/install-memgraph/direct-download-links.mdx b/pages/getting-started/install-memgraph/direct-download-links.mdx index 8e82449f2..b270b98e6 100644 --- a/pages/getting-started/install-memgraph/direct-download-links.mdx +++ b/pages/getting-started/install-memgraph/direct-download-links.mdx @@ -47,6 +47,10 @@ Debian-family distribution and the `.rpm` on any RHEL-family distribution with glibc 2.31 or newer. Each main package has a matching `memgraph-debuginfo` package containing its debug symbols. +glibc is the system C library. Current releases such as Debian 12, Ubuntu +22.04, Fedora 42 and Red Hat Enterprise Linux 9 ship 2.31 or newer. To check yours, see +[Install Memgraph on Linux](/getting-started/install-memgraph/linux). + The `-malloc` variants are builds without jemalloc, using the system allocator (x86_64 only). diff --git a/pages/getting-started/install-memgraph/linux.mdx b/pages/getting-started/install-memgraph/linux.mdx index aadcc5fcd..32c710413 100644 --- a/pages/getting-started/install-memgraph/linux.mdx +++ b/pages/getting-started/install-memgraph/linux.mdx @@ -41,7 +41,7 @@ you install a newer version over an existing one, follow ## Install the DEB package on Debian or Ubuntu -Download the DEB package, then install it with `dpkg`. +Download the DEB package, then install it with `apt`. @@ -52,7 +52,7 @@ Hub](https://memgraph.com/download/) or with a link from [direct download links](/getting-started/install-memgraph/direct-download-links). For example, the x86_64 package: - + For the ARM64 package, the system allocator build or a newer version, take the link from [direct download @@ -61,18 +61,18 @@ file name in the next step. {

Install the DEB package

} -Install the package with `dpkg`: +Install the package with `apt`, which also installs its dependencies: ```bash -sudo dpkg -i ./memgraph_3.14.0-1_amd64.deb +sudo apt install ./memgraph_3.14.0-1_amd64.deb ``` -If `sudo` isn't installed or `dpkg` reports dependency problems, see -[Troubleshooting](#troubleshooting). +If `sudo` isn't installed, see [sudo is not installed on +Debian](#sudo-is-not-installed-on-debian). -When the package is installed, [start Memgraph](#start-memgraph). +When the package is installed, [configure the system](#configure-the-system). ## Install the RPM package on CentOS, Fedora, Rocky Linux or Red Hat @@ -87,7 +87,7 @@ Hub](https://memgraph.com/download/) or with a link from [direct download links](/getting-started/install-memgraph/direct-download-links). For example, the x86_64 package: - + For the ARM64 (aarch64) package, the system allocator build or a newer version, take the link from [direct download @@ -107,7 +107,26 @@ resources. See [SELinux blocks Memgraph](#selinux-blocks-memgraph). -When the package is installed, [start Memgraph](#start-memgraph). +When the package is installed, [configure the system](#configure-the-system). + +## Configure the system + +The default limits on most Linux distributions are too low for Memgraph. Check +two of them before you load data: + +- **Open files (`nofile`)**: Memgraph uses a file descriptor for each client + connection and for its storage files. The packaged systemd service sets + `LimitNOFILE=1048576`. If you run Memgraph without systemd, raise the limit + yourself, as [Handle numerous open files + simultaneously](/database-management/system-configuration#handle-numerous-open-files-simultaneously) + describes. +- **Memory map areas (`vm.max_map_count`)**: large workloads can run out of + them. [Increase the `vm.max_map_count` + parameter](/database-management/system-configuration#increasing-memory-map-areas) + to the recommended value for your machine's memory. + +For the other settings, see [System +configuration](/database-management/system-configuration). ## Start Memgraph @@ -142,6 +161,12 @@ To start Memgraph automatically when the machine boots: sudo systemctl enable memgraph ``` +On a system without systemd, run Memgraph as the `memgraph` user: + +```bash +sudo -u memgraph /usr/lib/memgraph/memgraph +``` + ## Connect to Memgraph To [run queries](/querying) from the terminal, install @@ -159,10 +184,6 @@ startup, so restart it after you change the file: sudo systemctl restart memgraph ``` -If Memgraph runs out of memory map areas on large workloads, [increase the -`vm.max_map_count` -parameter](/database-management/system-configuration#increasing-memory-map-areas). - ## Stop Memgraph ```bash @@ -189,23 +210,6 @@ apt update -y apt install sudo -y ``` -### dpkg reports dependency problems - -If `dpkg -i` ends with an error like this: - -```plaintext copy=false -dpkg: error processing package memgraph (--install): dependency problems - -leaving unconfigured Errors were encountered while processing: memgraph -``` - -some of the package's dependencies are missing. Update the package lists, then -let `apt` install the missing dependencies and finish installing Memgraph: - -```bash -sudo apt update -sudo apt-get install -f -``` - ### Python libraries for query modules are missing Since Memgraph 3.13, the package installs the Python libraries that the bundled diff --git a/pages/getting-started/install-memgraph/wsl.mdx b/pages/getting-started/install-memgraph/wsl.mdx index 2c45737f1..32197e310 100644 --- a/pages/getting-started/install-memgraph/wsl.mdx +++ b/pages/getting-started/install-memgraph/wsl.mdx @@ -47,20 +47,20 @@ You can also run Ubuntu from the *Start* menu. To set up the Memgraph database, use the command below in the Ubuntu terminal: - + You can also obtain the Memgraph package using the [direct download link](/getting-started/install-memgraph/direct-download-links). On that page, you will always find the links to the latest release. Make sure to replace the link in the command below with the most recent one: ``` wget [YOUR_DIRECT_DOWNLOAD_LINK_HERE] -O memgraph.deb -sudo dpkg -i memgraph.deb +sudo apt install ./memgraph.deb ``` For example: ``` wget https://download.memgraph.com/memgraph/v3.14.0/x86_64-deb/memgraph_3.14.0-1_amd64.deb -O memgraph.deb -sudo dpkg -i memgraph.deb +sudo apt install ./memgraph.deb ``` For the latest version of Memgraph, replace the version in the download command @@ -103,28 +103,6 @@ the [Configuration section](#configuration).
At this point, Memgraph is ready for you to [submit queries](/querying). - -Potential installation error You could get errors while installing the package -with the above commands if you don't have all of Memgraph's dependencies -installed. The issues mostly look like the following: - -``` -dpkg: error processing package memgraph (--install): - dependency problems - leaving unconfigured -Errors were encountered while processing: - memgraph -``` - -To install missing dependencies and finish the installation of the Memgraph -package, just issue the following command: - -``` -sudo apt-get install -f -``` - -The above command will install all missing dependencies and will finish -configuring the Memgraph package. - @@ -147,29 +125,6 @@ Usually, you can find the Windows users directories in this location: /mnt//Users/ ``` -### Unable to install the Memgraph package with `dpkg` - -While running the following `dpkg` command: - -```bash -sudo dpkg -i /mnt//Users//Downloads/memgraph_.deb -``` - -you may encounter errors that resemble the following: - -``` -dpkg: error processing package memgraph (--install): dependency problems - -leaving unconfigured Errors were encountered while processing: memgraph -``` - -These errors indicate that you don’t have all of the necessary dependencies -installed. To install the missing dependencies and finish the installation, -issue the following command: - -``` -sudo apt-get install -f -``` - ### Multiple notes when starting Memgraph As of Memgraph 3.13, the package installs the Python libraries used by the