Trying this again without the screenshot, which got stuck in the filters.
Begin forwarded message:
From: Roy Smith roy@panix.com Subject: Installing elasticsearch on a VPS instance? Date: December 17, 2023 at 4:00:08 PM EST To: Wikimedia Cloud Services general discussion and support cloud@lists.wikimedia.org
I want to install elasticsearch on a VPS instance. I’m guessing this involves puppet, but can’t figure out the details. The instructions at https://wikitech.wikimedia.org/wiki/Help:Puppet don’t match what I’m actually seeing in Horizon. I go to the Puppet Configuration tab for my instance and there’s no project/common/all sub-pages as described under Apply a puppet role to or change hiera config of an individual instance.
https://horizon.wikimedia.org/project/instances/51660b10-1e33-4f49-a68f-e51f...
On Sun, Dec 17, 2023 at 10:04 PM Roy Smith roy@panix.com wrote:
I want to install elasticsearch on a VPS instance. I’m guessing this involves puppet, but can’t figure out the details. The instructions at https://wikitech.wikimedia.org/wiki/Help:Puppet don’t match what I’m actually seeing in Horizon. I go to the Puppet Configuration tab for my instance and there’s no project/common/all sub-pages as described under Apply a puppet role to or change hiera config of an individual instance.
Hi Roy,
Elasticsearch is licensed under a non-free license, so I would encourage you to use OpenSearch instead, as the Cloud Services terms of use [1] require that only OSI-compliant software is installed in Cloud VPS instances.
The screenshots included in https://wikitech.wikimedia.org/wiki/Help:Puppet are a bit old, the interface is now slightly different. We will update that page, but in the meantime my recommendation is to ignore Puppet and install OpenSearch by logging into your Cloud VPS instance and following the upstream instructions at https://opensearch.org/docs/latest/install-and-configure/install-opensearch/...
Let us know if that works or if you run into further issues!
Thanks, Francesco
[1] https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use
OK, thanks.
BTW, I updated https://wikitech.wikimedia.org/wiki/Help:Toolforge/Elasticsearch#Python_cons... with some useful info. Please feel free to correct anything I said there which isn’t accurate.
On Dec 18, 2023, at 6:08 AM, Francesco Negri fnegri@wikimedia.org wrote:
On Sun, Dec 17, 2023 at 10:04 PM Roy Smith roy@panix.com wrote:
I want to install elasticsearch on a VPS instance. I’m guessing this involves puppet, but can’t figure out the details. The instructions at https://wikitech.wikimedia.org/wiki/Help:Puppet don’t match what I’m actually seeing in Horizon. I go to the Puppet Configuration tab for my instance and there’s no project/common/all sub-pages as described under Apply a puppet role to or change hiera config of an individual instance.
Hi Roy,
Elasticsearch is licensed under a non-free license, so I would encourage you to use OpenSearch instead, as the Cloud Services terms of use [1] require that only OSI-compliant software is installed in Cloud VPS instances.
The screenshots included in https://wikitech.wikimedia.org/wiki/Help:Puppet are a bit old, the interface is now slightly different. We will update that page, but in the meantime my recommendation is to ignore Puppet and install OpenSearch by logging into your Cloud VPS instance and following the upstream instructions at https://opensearch.org/docs/latest/install-and-configure/install-opensearch/...
Let us know if that works or if you run into further issues!
Thanks, Francesco
[1] https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use
-- Francesco Negri (he/him) -- IRC: dhinus Site Reliability Engineer, Cloud Services team Wikimedia Foundation _______________________________________________ Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
I installed per the instructions at https://opensearch.org/docs/latest/install-and-configure/install-opensearch/..., but it fails to start:
$ sudo systemctl start opensearch Job for opensearch.service failed because the control process exited with error code. See "systemctl status opensearch.service" and "journalctl -xeu opensearch.service" for details.
$ systemctl status opensearch.service × opensearch.service - OpenSearch Loaded: loaded (/lib/systemd/system/opensearch.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Tue 2023-12-19 15:24:58 UTC; 7min ago Docs: https://opensearch.org/ Process: 43719 ExecStart=/usr/share/opensearch/bin/systemd-entrypoint -p ${PID_DIR}/opensearch.pid --quiet (code=exited, status=1/FAILURE) Main PID: 43719 (code=exited, status=1/FAILURE) CPU: 2.001s
This is on opensearch.spi-tools.eqiad1.wikimedia.cloud https://horizon.wikimedia.org/project/instances/c282d273-6007-4320-9df2-69cd949a1a37/. It’s a brand new debian bookworm instance I just spun up for this. The only configuration I’ve done was to increase vm.max_map_count per their recommendation:
$ cat /proc/sys/vm/max_map_count 262144
Any ideas?
On Dec 18, 2023, at 6:08 AM, Francesco Negri fnegri@wikimedia.org wrote:
On Sun, Dec 17, 2023 at 10:04 PM Roy Smith roy@panix.com wrote:
I want to install elasticsearch on a VPS instance. I’m guessing this involves puppet, but can’t figure out the details. The instructions at https://wikitech.wikimedia.org/wiki/Help:Puppet don’t match what I’m actually seeing in Horizon. I go to the Puppet Configuration tab for my instance and there’s no project/common/all sub-pages as described under Apply a puppet role to or change hiera config of an individual instance.
Hi Roy,
Elasticsearch is licensed under a non-free license, so I would encourage you to use OpenSearch instead, as the Cloud Services terms of use [1] require that only OSI-compliant software is installed in Cloud VPS instances.
The screenshots included in https://wikitech.wikimedia.org/wiki/Help:Puppet are a bit old, the interface is now slightly different. We will update that page, but in the meantime my recommendation is to ignore Puppet and install OpenSearch by logging into your Cloud VPS instance and following the upstream instructions at https://opensearch.org/docs/latest/install-and-configure/install-opensearch/...
Let us know if that works or if you run into further issues!
Thanks, Francesco
[1] https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use
-- Francesco Negri (he/him) -- IRC: dhinus Site Reliability Engineer, Cloud Services team Wikimedia Foundation _______________________________________________ Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
On Tue, Dec 19, 2023 at 4:41 PM Roy Smith roy@panix.com wrote:
I installed per the instructions at https://opensearch.org/docs/latest/install-and-configure/install-opensearch/..., but it fails to start:
Hi Roy,
"journalctl -u opensearch" shows the full log, that include the following error:
Dec 19 15:32:34 opensearch systemd-entrypoint[44087]: # There is insufficient memory for the Java Runtime Environment to continue. Dec 19 15:32:34 opensearch systemd-entrypoint[44087]: # Native memory allocation (mmap) failed to map 1073741824 bytes for committing reserved memory.
Increasing the server total memory from 1 to 2 GB should fix it, just pick a different "instance flavor" in Cloud VPS.
Yup, that did it. I resized it to g3.cores1.ram2.disk20 and now I’m running. Thanks.
On Dec 19, 2023, at 10:54 AM, Francesco Negri fnegri@wikimedia.org wrote:
On Tue, Dec 19, 2023 at 4:41 PM Roy Smith roy@panix.com wrote:
I installed per the instructions at https://opensearch.org/docs/latest/install-and-configure/install-opensearch/..., but it fails to start:
Hi Roy,
"journalctl -u opensearch" shows the full log, that include the following error:
Dec 19 15:32:34 opensearch systemd-entrypoint[44087]: # There is insufficient memory for the Java Runtime Environment to continue. Dec 19 15:32:34 opensearch systemd-entrypoint[44087]: # Native memory allocation (mmap) failed to map 1073741824 bytes for committing reserved memory.
Increasing the server total memory from 1 to 2 GB should fix it, just pick a different "instance flavor" in Cloud VPS.
-- Francesco Negri (he/him) -- IRC: dhinus Site Reliability Engineer, Cloud Services team Wikimedia Foundation _______________________________________________ Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/