I’m trying to move ~100 posts to an existing topic. After a delay of about 10 seconds, it says there was an error when moving posts in a green alert area: [image] No new entries in /logs No useful information in console either: [image] What can be wrong and where to look for the error?

Very likely babble, I am guessing it has hooks that fire on post move.

Good to know. Thanks. And props to @featheredtoast for the fix.

My community recently started experiencing the 502 error issue when moving posts, especially between large threads. I had no custom plug-ins installed. Following the advice from another Discourse thread, I increased the unicorn_workers to 10 and db_shared_buffers to 4096MB, but that did not ameliorate the situation. Below is our forum’s ./discourse-doctor log. Hoping to get some pointers. Thank you! ==================== DOCKER INFO ==================== DOCKER VERSION: Docker version 17.10.0-ce, build f4ffd25 DOCKER PROCESSES (docker ps -a) CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ddfb2222fd64 local_discourse/app "/sbin/boot" 10 days ago Up 10 days 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app ddfb2222fd64 local_discourse/app "/sbin/boot" 10 days ago Up 10 days 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app Discourse container app is running ==================== PLUGINS ==================== - git clone https://github.com/discourse/docker_manager.git - git clone https://github.com/discourse/discourse-solved.git No non-official plugins detected. See https://github.com/discourse/discourse/blob/master/lib/plugin/metadata.rb for the official list. ======================================== Discourse 2.6.0.beta2 Discourse version at localhost: Discourse 2.6.0.beta2 ==================== MEMORY INFORMATION ==================== RAM (MB): 16434 total used free shared buff/cache available Mem: 16048 5605 919 4255 9523 5850 Swap: 2047 437 1610 ==================== DISK SPACE CHECK ==================== ---------- OS Disk Space ---------- Filesystem Size Used Avail Use% Mounted on /dev/disk/by-label/DOROOT 315G 132G 168G 45% / /dev/disk/by-label/DOROOT 315G 132G 168G 45% /var/lib/docker/aufs /dev/disk/by-label/DOROOT 315G 132G 168G 45% / /dev/disk/by-label/DOROOT 315G 132G 168G 45% /var/lib/docker/plugins /dev/disk/by-label/DOROOT 315G 132G 168G 45% / ---------- Container Disk Space ---------- unknown shorthand flag: 'w' in -w See 'docker exec --help'. ==================== DISK INFORMATION ==================== Disk /dev/vda: 320 GiB, 343597383680 bytes, 671088640 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 29B528BA-16C4-402E-BEE9-53555C8B6F10 Device Start End Sectors Size Type /dev/vda1 2048 671086591 671084544 320G Linux filesystem ==================== END DISK INFORMATION ====================

Hi, I encounter the same issue. Can’t split megatopics because of this. Also tried in safe-mode, didn’t change anything. [image] No issue in my development Discourse installation (same version 2.6.0.beta2) though. And nothing in the logs.

I’m getting this 502 errors for an year ;(

I don’t think we’ve asked you: what plugins are you running?

I disable all plugins to check is it plugin related bug. It looks like it repeated stable with long threads.

This most annoying bug is still with us. Could you give me instructions to nail the problem?

Unfortunately we are still running into this issue from time to time. I managed to collect some data about a recent problem where moving 27 posts into an existing topic (2013 posts) failed: Beginning move at 2021-05-25 20:54:57 +0000 create_temp_table 0.000134 0.000027 0.000161 ( 0.002810) delete_invalid_post_timings 0.000317 0.000065 0.000382 ( 0.306869) move_incoming_emails 0.000056 0.000006 0.000062 ( 0.000478) move_notifications 0.000074 0.000008 0.000082 ( 0.005584) update_reply_counts 0.000088 0.000010 0.000098 ( 0.001058) update_quotes 0.000079 0.000008 0.000087 ( 0.002426) move_first_post_replies 0.000071 0.000008 0.000079 ( 0.000695) delete_post_replies 0.000062 0.000006 0.000068 ( 0.000834) copy_first_post_timings 0.000064 0.000007 0.000071 ( 0.002660) move_post_timings 0.000082 0.000009 0.000091 ( 0.008195) copy_topic_users 0.000398 0.000043 0.000441 ( 0.043640) move_each_post 4.345220 0.132652 4.477872 ( 3.447047) create_moderator_post_in_original_topic 0.163962 0.000253 0.164215 ( 0.207101) update_statistics 0.217266 0.051660 0.268926 ( 45.258070) update_user_actions 0.000934 0.000101 0.001035 ( 0.178894) update_last_post_stats 0.001589 0.000171 0.001760 ( 0.003156) update_upload_security_status 0.000030 0.000003 0.000033 ( 0.000034) update_bookmarks 0.000492 0.000054 0.000546 ( 0.003832) Finished move at 2021-05-25 20:55:47 +0000 Most methods finish real quick, but update_statistics took over 45 seconds in this case. All that time is spent on the following method call: app/models/post_mover.rb 66d17fdd6 TopicUser.update_post_action_cache(topic_id: destination_topic.id)

Maybe we defer the update_statistics work to sidekiq?

החזרות של פוסטים נעים מחזירות שגיאת 502 gateway

תמיכה התקנה

נושא		תגובות	צפיות
Moving posts to a long topic fails Bug	4	265	28 בינואר,‏ 2025
Unable to move posts between topics Bug fixed	2	217	10 בדצמבר,‏ 2024
Moving shipments causes an error Bug	4	236	18 בדצמבר,‏ 2024
500 Error: There was an error moving posts Bug	3	464	25 באוקטובר,‏ 2023
"There was an error moving posts" Bug	2	193	12 בדצמבר,‏ 2024

החזרות של פוסטים נעים מחזירות שגיאת 502 gateway

נושאים קשורים