I need to update the smtp settings in app.yml, but I do not want to change the version of discourse.
When I specify a version via the version tag, the rebuild fails with the error below. I am currently on version 2.4.0.beta8.
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} \+ failed with return #<Process::Status: pid 336 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem update bundler", "find $home ! -user discourse -exec chown discourse {} \\+"]}
6269af00c2a4671a6fd2cb13a55bd475743205262bae7f483bf468e4dcacbeed
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
ok, so that will read the yml even if it does not rebuild, sounds good. While that will fix my urgent issue, i am still intrested in why version does not work.
You said that you get “an error”. That means that you did something wrong. My best guess is a YML formatting error, but without knowing what the error was, there is really no way to know.
Sorry, “please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.”
Yes, I can see that the information i gave in the post was not detailed enough. I do not think it is a formatting error, since the yml works fine without the version tag.
I tested some more, and it seems like whatever bug I encountered does not trigger in version 10 and 11, but does trigger in version 4 to 9.
I can only find two errors in the print, and i think they are expected:
2020-02-22 10:42:33.410 UTC [62] postgres@postgres ERROR: database "discourse" already exists
2020-02-22 10:42:33.533 UTC [73] postgres@discourse ERROR: role "discourse" already exists
I looked at the release notes for version 10, and did not find a reference to a fix related to this.
Its good that it is fixed, and with your work around for the smpt settings (will test it on monday, dont want to mess with the production server during the weekend) there is no urgent need from me, but it would be good to know if there is an unknown error that the tests will not catch, and that may return, if it was ‘fixed’ by accident and not by a targeted change. I guess i want to know how stable the version function can be expected to be in the future.
This is a dump of the output from a run with v2.4.0.beta9 as target version. dump_disco_version_error.txt (127.5 KB)
I finally found time to test this, and it did not work. I can see that it prints the correct pw when the app starts, but emails still fail due to access denied.
كان لدي سبب للعودة إلى هذا، يبدو لي أن الإصدار يعمل مع الفروع، لكن ليس مع الوسوم. أفترض أن السبب هو أن المشغل لا يجلب جميع الوسوم أولاً، لكنني لا أعرف. هل هناك طريقة لتعديل نصوص المشغل؟
أخيرًا اكتشفت ما الذي يذهب خطأ: مستودع discourse_docker ومستودع discourse يعتمدان على بعضهما البعض، لذا يمكن تثبيت إصدار محدد من discourse فقط باستخدام إصدار محدد من مستودع discourse_docker. للأسف، لا توجد وسوم (tags) في مستودع discourse_docker، لذا فإن معرفة أي SHA يجب استخدامه لتثبيت إصدار معين ليس أمرًا سهلاً. من الجيد على الأقل الحصول على بعض الإغلاق. سأبدأ في تدوين ملاحظات حول هذا الأمر للتثبيتات التي سأقوم بها في المستقبل.