search

10up / wp-local-docker-v2

ARCHIVED: A simple Docker based development environment for WordPress.
MIT License
484 stars 81 forks source link

Unable to connect to ElasticSearch after new site creation #210

Open ryanwelcher opened 3 years ago

ryanwelcher commented 3 years ago

Describe the bug After creating a new environment I am not able to connect to ElasticPress.

connetion_error

Steps to Reproduce

Expected behavior I am able to connect to the ES instance and index.

Environment information

version: 5.7.2 site_language: en_US user_language: en_US timezone: +00:00 permalink: /%postname%/ https_status: true multisite: false user_registration: 0 blog_public: 1 default_comment_status: open environment_type: production user_count: 1 dotorg_communication: true

wp-paths-sizes

wordpress_path: /var/www/html wordpress_size: 43.61 MB (45725607 bytes) uploads_path: /var/www/html/wp-content/uploads uploads_size: 0.00 B (0 bytes) themes_path: /var/www/html/wp-content/themes themes_size: 6.44 MB (6755643 bytes) plugins_path: /var/www/html/wp-content/plugins plugins_size: 7.18 MB (7526096 bytes) database_size: 2.13 MB (2228224 bytes) total_size: 59.35 MB (62235570 bytes)

wp-active-theme

name: Twenty Twenty-One (twentytwentyone) version: 1.3 author: the WordPress team author_website: https://wordpress.org/ parent_theme: none theme_features: core-block-patterns, automatic-feed-links, title-tag, post-formats, post-thumbnails, menus, html5, custom-logo, customize-selective-refresh-widgets, wp-block-styles, align-wide, editor-styles, editor-style, editor-font-sizes, custom-background, editor-color-palette, editor-gradient-presets, responsive-embeds, custom-line-height, experimental-link-color, custom-spacing, custom-units, widgets theme_path: /var/www/html/wp-content/themes/twentytwentyone auto_update: Disabled

wp-themes-inactive (2)

Twenty Nineteen: version: 2.0, author: the WordPress team, Auto-updates disabled Twenty Twenty: version: 1.7, author: the WordPress team, Auto-updates disabled

wp-plugins-active (1)

ElasticPress: version: 3.5.6, author: 10up, Auto-updates disabled

wp-plugins-inactive (2)

Akismet Anti-Spam: version: 4.1.9, author: Automattic, Auto-updates disabled Hello Dolly: version: 1.7.2, author: Matt Mullenweg, Auto-updates disabled

wp-media

image_editor: WP_Image_Editor_Imagick imagick_module_version: 1692 imagemagick_version: ImageMagick 6.9.12-8 Q16 x86_64 2021-04-17 https://imagemagick.org file_uploads: File uploads is turned off post_max_size: 150m upload_max_filesize: 150m max_effective_size: 150 MB max_file_uploads: 20 imagick_limits: imagick::RESOURCETYPE_AREA: 8 GB imagick::RESOURCETYPE_DISK: 9.2233720368548E+18 imagick::RESOURCETYPE_FILE: 786432 imagick::RESOURCETYPE_MAP: 8 GB imagick::RESOURCETYPE_MEMORY: 4 GB imagick::RESOURCETYPE_THREAD: 1 gd_version: 2.2.5 ghostscript_version: not available

wp-server

server_architecture: Linux 5.10.25-linuxkit x86_64 httpd_software: nginx/1.19.10 php_version: 7.3.27 64bit php_sapi: fpm-fcgi max_input_variables: 1000 time_limit: 30 memory_limit: 128M admin_memory_limit: 256M max_input_time: 60 upload_max_filesize: 150m php_post_max_size: 150m curl_version: 7.61.1 OpenSSL/1.1.1g suhosin: false imagick_availability: true pretty_permalinks: true

wp-database

extension: mysqli server_version: 10.5.9-MariaDB-1:10.5.9+maria~focal client_version: mysqlnd 5.0.12-dev - 20150407 - $Id: 7cc7cc96e675f6d72e5cf0f267f48e167c2abb23 $

wp-constants

WP_HOME: undefined WP_SITEURL: undefined WP_CONTENT_DIR: /var/www/html/wp-content WP_PLUGIN_DIR: /var/www/html/wp-content/plugins WP_MEMORY_LIMIT: 40M WP_MAX_MEMORY_LIMIT: 256M WP_DEBUG: false WP_DEBUG_DISPLAY: true WP_DEBUG_LOG: false SCRIPT_DEBUG: false WP_CACHE: false CONCATENATE_SCRIPTS: undefined COMPRESS_SCRIPTS: undefined COMPRESS_CSS: undefined WP_LOCAL_DEV: undefined DB_CHARSET: utf8 DB_COLLATE: undefined

wp-filesystem

wordpress: writable wp-content: writable uploads: writable plugins: writable themes: writable </details/>

tylercherpak commented 3 years ago

Hey @ryanwelcher can you run 10updocker start on this project and look in the docker for mac interface at the containers and let us know if there is anything in the elasticsearch container logs?

ryanwelcher commented 3 years ago

@tylercherpak I found the following in the logs:

ep-test_elasticsearch_1 exited with code 137
elasticsearch_1 | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
tylercherpak commented 2 years ago

Hey @ryanwelcher 👋

We just added m1 support in the latest v3.0.0 release. 😄

I think this should be resolved but let us know if you are still seeing this issue.

tylercherpak commented 2 years ago

Closing this ticket but feel free to reopen if you are still having this issue.

rebeccahum commented 2 years ago

@tylercherpak I'm still seeing that with the latest 10updocker version:

qemu: uncaught target signal 11 (Segmentation fault) - core dumped

barryceelen commented 2 years ago

@tylercherpak @rebeccahum I got the same error. Assuming you are on an M1 mac, updating the elasticsearch package in docker-compose.yml to the arm64 version:

image: docker.elastic.co/elasticsearch/elasticsearch-oss:7.9.3-arm64

..and removing the old volume:

docker volume rm <project-folder-name-here>_elasticsearchData

did the trick for me, as in, it allowed me to then run an elasticsearch index.

tylercherpak commented 2 years ago

I am working on a better solution for this: https://github.com/10up/wp-local-docker-v2/pull/260

For the meantime, Barry's solution is best for now.

tylercherpak commented 2 years ago

Hey everyone, I pushed a RC version that uses the 7.9.3 version of elasticsearch and will allow you to update your existing environments. You can test this version by running npm i -g wp-local-docker@next to install. Then, in the environment that you want to update to use the 7.9.3 version of elasticsearch, run 10updocker upgrade and say yes to the prompt. 😄 Let me know if you run into any issues or have any questions. Thanks!