So, the hostname is now OK. But as I understood from previous emails
> addsite does work for you now, doesn't it?
Yes, now all commands work fine. Seems problem was in the incorrect hostname
> The lack of pictures is probably due to the fact that module Bootstrap > isn't enabled by default. At least that was the reason for me.
How check status of this module? And how enable it? I try to build latest ImageMagick on my server - but not enough RAM to do it. I think because of 64bit-architecture (on the same system but x86-architecture ImageMagick successfully built). So may be your advice helps me
You can enable modules under System | Modules in Admin. It is also accessible at http://example.com/admin/modules where example.com is your domain name :)
On Monday, October 1, 2012 7:18:14 PM UTC-2:30, Alexey Marunin wrote:
> Hi Amiramix
> So, the hostname is now OK. But as I understood from previous emails >> addsite does work for you now, doesn't it?
> Yes, now all commands work fine. Seems problem was in the incorrect > hostname
>> The lack of pictures is probably due to the fact that module Bootstrap >> isn't enabled by default. At least that was the reason for me.
> How check status of this module? And how enable it? > I try to build latest ImageMagick on my server - but not enough RAM to do > it. I think because of 64bit-architecture (on the same system but > x86-architecture ImageMagick successfully built). So may be your advice > helps me
> You can enable modules under System | Modules in Admin. It is also > accessible at http://example.com/admin/modules where example.com is your > domain name :)
This module activated in my admin. But pictures still don`t display correctly
Do you have the module for your site activated? For me it is simply called "blog zotonic site". If this is deactivated, you will not get a functional site.
Do you also have Zotonic Base activated?
I hope you don't mind the trial and error approach. It can be quite difficult to know the specific issue sometimes :)
On Tuesday, October 2, 2012 4:57:04 PM UTC-2:30, Alexey Marunin wrote:
> Hi Alain
>> You can enable modules under System | Modules in Admin. It is also >> accessible at http://example.com/admin/modules where example.com is your >> domain name :)
> This module activated in my admin. But pictures still don`t display > correctly
> Do you have the module for your site activated? For me it is simply > called "blog zotonic site". If this is deactivated, you will not get a > functional site.
Yes, green light :)
Do you also have Zotonic Base activated?
Yes
> I hope you don't mind the trial and error approach. It can be quite > difficult to know the specific issue sometimes :)
I know sometimes difficult questions have a simple solution :)
dawid@asusek:$ cd bin dawid@asusek:$ ./zotonic start Starting zotonic zotonic...@asusek.local dawid@asusek:$ ./zotonic status Running: zotonic...@asusek.local
Sites Status: ============= {"init terminating in do_boot",{function_clause,[{zotonic,'-status/1-lc$^0/1-0-',[{badrpc,nodedow n}],[{file,"src/zotonic.erl"},{line,83}]},{zotonic,status,1,[{file,"src/zot onic.erl"},{line,83}]},{init,start_it,1,[]},{init,start_em,1,[]}]}}
Crash dump was written to: erl_crash.dump init terminating in do_boot ()
dawid@asusek:$ erl_call -name zotonic...@asusek.local erl_call: failed to connect to node zotonic...@asusek.local
dawid@asusek:$ ./zotonic stop Stopping zotonic zotonic...@asusek.local Stopping:'zotonic...@asusek.local' There is no node with this name
(zotonic...@asusek.local)3> zotonic:status(). zotonic_status - running ok
My environment:
Zotonic - from git repository.
host 127.0.0.1 1.0.0.127.in-addr.arpa domain name pointer localhost.
dawid@asusek:$ cd bin dawid@asusek:$ ./zotonic start Starting zotonic zotonic...@asusek.local dawid@asusek:$ ./zotonic status Running: zotonic...@asusek.local
Sites Status: ============= {"init terminating in do_boot",{function_clause,[{zotonic,'-status/1-lc$^0/1-0-',[{badrpc,nodedow n}],[{file,"src/zotonic.erl"},{line,83}]},{zotonic,status,1,[{file,"src/zot onic.erl"},{line,83}]},{init,start_it,1,[]},{init,start_em,1,[]}]}}
Crash dump was written to: erl_crash.dump init terminating in do_boot ()
dawid@asusek:$ erl_call -name zotonic...@asusek.local erl_call: failed to connect to node zotonic...@asusek.local
dawid@asusek:$ ./zotonic stop Stopping zotonic zotonic...@asusek.local Stopping:'zotonic...@asusek.local' There is no node with this name
(zotonic...@asusek.local)3> zotonic:status(). zotonic_status - running ok
My environment:
Zotonic - from git repository.
host 127.0.0.1 1.0.0.127.in-addr.arpa domain name pointer localhost.
I just committed some changes which deal with the issues in this thread:
- Zotonic now uses code:priv_dir to locate the *erl_call* binary within the distribution, so that should always work (famous last words)
- Zotonic now runs using *-sname* by default; which prevents these hostname issues people were getting. No more need to add *foo.local* to your hosts file!
{error_logger,{{2012,11,1},{13,27,9}},"Can't set short node name!\nPlease check your configuration\n",[]} {error_logger,{{2012,11,1},{13,27,9}},crash_report,[[{initial_call,{net_ker nel,init,['Argument__1']}},{pid,<0.19.0>},{registered_name,[]},{error_info, {exit,{error,badarg},[{gen_server,init_it,6,[{file,"gen_server.erl"},{line, 320}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,227}]}]}},{ ancestors,[net_sup,kernel_sup,<0.9.0>]},{messages,[]},{links,[<0.16.0>]},{d ictionary,[{longnames,false}]},{trap_exit,true},{status,running},{heap_size ,377},{stack_size,24},{reductions,206}],[]]} {error_logger,{{2012,11,1},{13,27,9}},supervisor_report,[{supervisor,{local ,net_sup}},{errorContext,start_error},{reason,{'EXIT',nodistribution}},{off ender,[{pid,undefined},{name,net_kernel},{mfargs,{net_kernel,start_link,[[' zotonic...@combenoire.local',shortnames]]}},{restart_type,permanent},{shutdown,2000}, {child_type,worker}]}]} {error_logger,{{2012,11,1},{13,27,9}},supervisor_report,[{supervisor,{local ,kernel_sup}},{errorContext,start_error},{reason,shutdown},{offender,[{pid, undefined},{name,net_sup},{mfargs,{erl_distribution,start_link,[]}},{restar t_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]} {error_logger,{{2012,11,1},{13,27,9}},std_info,[{application,kernel},{exite d,{shutdown,{kernel,start,[normal,[]]}}},{type,permanent}]} {"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{shut down,{kernel,start,[normal,[]]}}}"}
Crash dump was written to: erl_crash.dump Kernel pid terminated (application_controller) ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})
Op dinsdag 30 oktober 2012 21:21:30 UTC+1 schreef Arjan Scherpenisse het volgende:
> I just committed some changes which deal with the issues in this thread:
> - Zotonic now uses code:priv_dir to locate the *erl_call* binary within > the distribution, so that should always work (famous last words) > - Zotonic now runs using *-sname* by default; which prevents these > hostname issues people were getting. No more need to add *foo.local* to > your hosts file!
> Hopefully this makes everybody's life easier.
> Arjan
> On 09/23/2012 07:42 PM, Alexey Marunin wrote:
> Hi, all!
> Try to create new site:
> cd bin > ./zotonic addsite
> Zotonic is not running. You need to start zotonic first to use this > command.
core: Make configurable whether we run with -name or with -sname
This fixes the fact that Zotonic always required a FQDN and the
"zotonic shell" command was not working reliably.
Zotonic now defaults to running with "-sname". To use "-name", set the
envirnoment variable ZOTONIC_DISTRIBUTED=true. Distributed
mode *really* requires a proper FQDN as returned by "hostname -f".
A better way to determine if Zotonic is running has also been added,
using "erl_call", and we determine more reliably where the "erl_call"
binary is located.
//Andreas
2012/11/1 Jan Willem Luiten <janwillem.lui...@gmail.com>
> Crash dump was written to: erl_crash.dump
> Kernel pid terminated (application_controller)
> ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})
> Op dinsdag 30 oktober 2012 21:21:30 UTC+1 schreef Arjan Scherpenisse het
> volgende:
>> I just committed some changes which deal with the issues in this thread:
>> - Zotonic now uses code:priv_dir to locate the *erl_call* binary within
>> the distribution, so that should always work (famous last words)
>> - Zotonic now runs using *-sname* by default; which prevents these
>> hostname issues people were getting. No more need to add *foo.local* to
>> your hosts file!
>> Hopefully this makes everybody's life easier.
>> Arjan
>> On 09/23/2012 07:42 PM, Alexey Marunin wrote:
>> Hi, all!
>> Try to create new site:
>> cd bin
>> ./zotonic addsite
>> Zotonic is not running. You need to start zotonic first to use this
>> command.
Do you start with "zotonic start" or "zotonic debug"?
With either of those, can you open src/scripts/zotonic-start (or zotonic-debug) and, on the last line of the file add an "echo" in frond of the call to $ERL?
and then run zotonic start, copypaste that line here.
Hmm, come to think of it, does the *-sname* part need a hostname (-sname foo@bar) at all, or without? (just -sname foo)
Erlang gurus, are you listening? :)
> Crash dump was written to: erl_crash.dump
> Kernel pid terminated (application_controller) > ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})
> Op dinsdag 30 oktober 2012 21:21:30 UTC+1 schreef Arjan Scherpenisse > het volgende:
> I just committed some changes which deal with the issues in this
> thread:
> - Zotonic now uses code:priv_dir to locate the *erl_call* binary
> within the distribution, so that should always work (famous last
> words)
> - Zotonic now runs using *-sname* by default; which prevents these
> hostname issues people were getting. No more need to add
> *foo.local* to your hosts file!
> Crash dump was written to: erl_crash.dump
> Kernel pid terminated (application_controller) > ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})
> Op dinsdag 30 oktober 2012 21:21:30 UTC+1 schreef Arjan Scherpenisse > het volgende:
> I just committed some changes which deal with the issues in this
> thread:
> - Zotonic now uses code:priv_dir to locate the *erl_call* binary
> within the distribution, so that should always work (famous last
> words)
> - Zotonic now runs using *-sname* by default; which prevents these
> hostname issues people were getting. No more need to add
> *foo.local* to your hosts file!
Makes the Erlang runtime system into a distributed node, similar to -name,
but the host name portion of the node name Name@Host will be the short
name, not fully qualified.
This is sometimes the only way to run distributed Erlang if the DNS (Domain
Name System) is not running. There can be no communication between nodes
running with the -sname flag and those running with the -name flag, as node
names must be unique in distributed Erlang systems.
*-name Name*
Makes the Erlang runtime system into a distributed node. This flag invokes
all network servers necessary for a node to become distributed. See
net_kernel(3) <http://erlang.org/doc/man/net_kernel.html>. It is also
ensured that epmd runs on the current host before Erlang is started. See
epmd(1) <http://erlang.org/doc/man/epmd.html>.
The name of the node will be Name@Host, where Host is the fully qualified
host name of the current host. For short names, use the -sname flag instead.
> Do you start with "zotonic start" or "zotonic debug"?
> With either of those, can you open src/scripts/zotonic-start (or
> zotonic-debug) and, on the last line of the file add an "echo" in frond of
> the call to $ERL?
> and then run zotonic start, copypaste that line here.
> Hmm, come to think of it, does the *-sname* part need a hostname (-sname
> foo@bar) at all, or without? (just -sname foo)
> Erlang gurus, are you listening? :)
> Arjan
> On 11/01/2012 01:30 PM, Jan Willem Luiten wrote:
> Hmmm,
> I did a fresh clone and get the following error:
> {error_logger,{{2012,11,1},{13,27,9}},"Can't set short node
> name!\nPlease check your configuration\n",[]}
> Crash dump was written to: erl_crash.dump
> Kernel pid terminated (application_controller)
> ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})
> Op dinsdag 30 oktober 2012 21:21:30 UTC+1 schreef Arjan Scherpenisse het
> volgende:
>> I just committed some changes which deal with the issues in this thread:
>> - Zotonic now uses code:priv_dir to locate the *erl_call* binary within
>> the distribution, so that should always work (famous last words)
>> - Zotonic now runs using *-sname* by default; which prevents these
>> hostname issues people were getting. No more need to add *foo.local* to
>> your hosts file!
>> Hopefully this makes everybody's life easier.
>> Arjan
>> On 09/23/2012 07:42 PM, Alexey Marunin wrote:
>> Hi, all!
>> Try to create new site:
>> cd bin
>> ./zotonic addsite
>> Zotonic is not running. You need to start zotonic first to use this
>> command.
