I see timeout in logs [smtp.yandex.ru]
I do not understand what the problem is
If you only see "sending" entries then there is a crash during the sending of email, otherwise you will also see the error that happened during the sending of the email.
Only timeouts or also other errors?
zotonic crashed
Can you share the crash log? Maybe we need to change something in gen_smtp or the emailer to catch this timeout.
2018-10-22 01:26:12.123 [error] <0.29249.0> gen_server z_email_server terminated with reason: no such process or port in call to gen\
_server:call('z_trans_server$skl', table) in gen_server:call/2 line 204
2018-10-22 01:26:12.123 [error] <0.29249.0> CRASH REPORT Process z_email_server with 0 neighbours exited with reason: no such proces\
s or port in call to gen_server:call('z_trans_server$skl', table) in gen_server:terminate/7 line 812
2018-10-22 01:26:12.124 [error] <0.273.0> Supervisor zotonic_sup had child z_email_server started with z_email_server:start_link() a\
t <0.29249.0> exit with reason no such process or port in call to gen_server:call('z_trans_server$skl', table) in context child_term\
inated
2018-10-22 01:26:17.139 [error] <0.29286.0> gen_server z_email_server terminated with reason: no such process or port in call to gen\
_server:call('z_trans_server$skl', table) in gen_server:call/2 line 204
2018-10-22 01:26:17.139 [error] <0.29286.0> CRASH REPORT Process z_email_server with 0 neighbours exited with reason: no such proces\
s or port in call to gen_server:call('z_trans_server$skl', table) in gen_server:terminate/7 line 812
2018-10-22 01:26:17.139 [error] <0.273.0> Supervisor zotonic_sup had child z_email_server started with z_email_server:start_link() a\
t <0.29286.0> exit with reason no such process or port in call to gen_server:call('z_trans_server$skl', table) in context child_term\
inated
2018-10-22 01:26:22.152 [error] <0.29333.0> gen_server z_email_server terminated with reason: no such process or port in call to gen\
_server:call('z_trans_server$skl', table) in gen_server:call/2 line 204
2018-10-22 01:26:22.152 [error] <0.29333.0> CRASH REPORT Process z_email_server with 0 neighbours exited with reason: no such proces\
s or port in call to gen_server:call('z_trans_server$skl', table) in gen_server:terminate/7 line 812
Do you have also just a bit earlier? When the email server crashed with the timeout?
Curious where the timeout is happening and how we can prevent this rather dramatic crash
event(_Msg,Context) ->
Url = <<"https://bbb.ru:8443/page/report">>,
Context1 = Context#context{actions=[{<<>>,<<>>,{redirect,[{location,Url}]}}]},
Context1.
that doesn't work
Or, if you have an id or dispatch rule:
z_render:wire({redirect, [{id, PageId}]}, Context)
Or even something like:
z_render:wire({redirect, [
{dispatch, course_timeline_copy},
{course_id, Id},
{class_id, ClassId},
{title, Title}
]}, Context)
This returns a new
Context with the redirect action, which will be rendered to some Javascript.
Hello. I have started the zotonic/zotonic:0.42.0 docker image and I can access the web server at localhost:8000, however when I try to create a site using docker exec 1798431ecb8f bin/zotonic addsite -s blog mysite I get the error:
<ERROR> get_cookie: can't open cookie fileerl_call: can't create C node c17@1798431ecb8f; 680385824
Zotonic is not running. You need to start Zotonic first to use this command.Have I done something wrong here?
i'see
2018-12-04 11:55:38.885 [info] <0.17611.0>@z_mqtt:opt_debug_pubsub:217 [skl] mod_mqtt publish: site/skl/barcode_send
'-export([
'mqtt:site/skl/barcode_send'/3
]).
'
'mqtt:site/skl/barcode_send'/3
]).
'
'mqtt:site/skl/barcode_send'(Message, ModulePid, Context)
but it does not work
observe_acl_is_allowed(#acl_is_allowed{action = publish ,object=#acl_mqtt{words = [<<"site">>,<<"skl">>,<<"barcode_send">>|_Rest]}},\
_Context) ->
true;
_Context) ->
true;
Hi @seannaswell , yes we did have that discussion, and also about possible other databases. We had a distributed version running and decided that it was too much (sysop) work for the benefits. That one was based on PostgresSQL and we ran a 5 node cluster for a customer. In the
zynamo branch there is still code for it.
Regarding Riak (and other NoSQL dbs), having SQL is making life a lot easier. One of my customers is running a rather large Riak cluster and it is great for its reliability and data-ingest capabilities. It is not so great for structured querying and range queries.
The newer PostgresSQL releases have good support for JSONB in database columns, and we are thinking of moving to that storage model at some time in the future.
For performance and reliability we don't really need distribution. Our systems are usually at 100% uptime, and that includes (hot code) upgrades. The minimal downtime is about even between our updates and data center problems. For scalability distribution is nice and we are looking into federation and luke-warm take/fail-over.