Hello Alain, Sorry if I am picking up on an old thread. I am just looking in to using Zotonic. Just wondering if you are still running zotonic on SmartOS?
SmartOS would be one of my platform choices for Zotonic. Any tips I can pick up from your experience running on SmartOS. Ed On Friday, October 23, 2015 at 6:43:00 PM UTC+1, Alain O'Dea wrote: > > fswatch now has File Events Notification (efficient native implementation > for Illumos) support: > > https://github.com/emcrisostomo/fswatch/commit/d951ef26722ccdb474aa9ec4b1231e84563ca7ad > > I've tested it to work well with Zotonic on SmartOS. That was > surprisingly smooth. Once Enrico publishes a release with that support > I'll get fswatch into PKGSRC to close the gap completely for anyone running > Zotonic there. > > On 18 October 2015 at 15:50, Alain O'Dea <[email protected] <javascript:> > > wrote: > >> Crisis averted. I "ported" fswatch (easily) to SmartOS: >> https://github.com/emcrisostomo/fswatch/pull/99 >> >> I'll get it into PKGSRC as time permits. >> >> Zotonic is runnable essentially out of the box on SmartOS modulo fswatch >> patch and install. >> >> On 18 October 2015 at 15:00, Alain O'Dea <[email protected] >> <javascript:>> wrote: >> >>> Yet again I'm struck again by my hipster insistence on running on >>> SmartOS ;) >>> >>> 0.13.0 introducted file watching with inotify/fswatch. All good. >>> >>> It's supposed to be disabled by default I'm guessing since it checks >>> z_config for filewatcher_enabled: >>> >>> https://github.com/zotonic/zotonic/blob/master/src/filewatcher/z_filewatcher_sup.erl#L38 >>> >>> It appears that z_filewatcher_sup won't fail gracefully on SmartOS which >>> doesn't have inotify-tools or fswatch available. >>> >>> I get the following when I run zotonic debug: >>> >>> Erlang/OTP 18 [erts-7.0] [source] [smp:8:8] [async-threads:10] >>> [kernel-poll:true] [dtrace] >>> >>> Eshell V7.0 (abort with ^G) >>> (zotonic001@blog2)1> ** Found 0 name clashes in code paths >>> 17:11:24.593 [info] Application lager started on node zotonic001@blog2 >>> Setup running ... >>> Directories verified. Res = {[ok],[]} >>> 17:11:24.605 [info] Application setup started on node zotonic001@blog2 >>> Setup finished processing hooks ... >>> 17:11:24.606 [error] Unable to read boot script (start_sasl.script): >>> {error,enoent} >>> >>> 17:11:24.660 [info] Starting reporters with [] >>> 17:11:24.660 [info] Application exometer_core started on node >>> zotonic001@blog2 >>> 17:11:24.663 [info] Application exometer started on node zotonic001@blog2 >>> 17:11:24.666 [info] Application depcache started on node zotonic001@blog2 >>> 17:11:24.678 [info] Application mimetypes started on node >>> zotonic001@blog2 >>> 17:11:24.732 [info] Application inets started on node zotonic001@blog2 >>> 17:11:24.754 [info] Application asn1 started on node zotonic001@blog2 >>> 17:11:24.754 [info] Application public_key started on node >>> zotonic001@blog2 >>> 17:11:24.773 [info] Application ssl started on node zotonic001@blog2 >>> 17:11:24.778 [info] Application xmerl started on node zotonic001@blog2 >>> 17:11:24.778 [info] Application mochiweb started on node zotonic001@blog2 >>> 17:11:24.784 [info] Application sendfile started on node zotonic001@blog2 >>> ** Found 0 name clashes in code paths >>> 17:11:24.884 [info] Application webzmachine started on node >>> zotonic001@blog2 >>> 17:11:24.884 [info] Application z_stdlib started on node zotonic001@blog2 >>> 17:11:24.886 [info] Application poolboy started on node zotonic001@blog2 >>> 17:11:24.898 [info] Application jobs started on node zotonic001@blog2 >>> 17:11:24.919 [info] Application gproc started on node zotonic001@blog2 >>> ** Found 0 name clashes in code paths >>> 17:11:25.066 [info] starting emqtt on node 'zotonic001@blog2' >>> 17:11:25.081 [info] emqtt_auth is started >>> 17:11:25.081 [warning] lager_error_logger_h dropped 2 messages in the >>> last second that exceeded the limit of 50 messages/sec >>> 17:11:25.083 [info] emqtt_retained is started. >>> 17:11:25.085 [info] emqtt_router is started. >>> 17:11:25.087 [info] emqtt_registry is started. >>> 17:11:25.090 [info] emqtt_client_monitor is started. >>> 17:11:25.095 [info] emqtt broker is running now. >>> 17:11:25.095 [info] Application emqtt started on node zotonic001@blog2 >>> 17:11:25.181 [info] gen_smtp_server starting at zotonic001@blog2 >>> >>> 17:11:25.184 [info] gen_smtp_server listening on {127,0,0,1}:2525 via tcp >>> >>> 17:11:25.290 [info] Site started: zotonic_status (<0.247.0>) >>> 17:11:25.374 [info] [fswatch] Starting fswatch file monitor. >>> 17:11:25.396 [info] Application zotonic started on node zotonic001@blog2 >>> 17:11:25.487 [error] gen_server z_filewatcher_fswatch terminated with >>> reason: {enoent,[{erlang,open_port,[{spawn_executable,"no fswatch in >>> /opt/local/lib/erlang/erts-7.0/bin /opt/local/lib/erlang/bin >>> /usr/local/sbin /usr/local/bin /opt/local/sbin /opt/local/bin /usr/sbin >>> /usr/bin >>> /sbin"},[{args,["-0","-x","-r","-L","/home/zotonic/zotonic/src","/home/zotonic/zotonic/modules","/home/zotonic/zotonic/ebin","/home/zotonic/zotonic/priv/sites","/home/zotonic/zotonic/priv/modules","/home/zotonic/zotonic/user/sites","/home/zotonic/zotonic/user/modules","/home/zotonic/zotonic...",...]},...]],...},...]} >>> 17:11:25.487 [error] CRASH REPORT Process z_filewatcher_fswatch with 0 >>> neighbours exited with reason: >>> {enoent,[{erlang,open_port,[{spawn_executable,"no fswatch in >>> /opt/local/lib/erlang/erts-7.0/bin /opt/local/lib/erlang/bin >>> /usr/local/sbin /usr/local/bin /opt/local/sbin /opt/local/bin /usr/sbin >>> /usr/bin >>> /sbin"},[{args,["-0","-x","-r","-L","/home/zotonic/zotonic/src","/home/zotonic/zotonic/modules","/home/zotonic/zotonic/ebin","/home/zotonic/zotonic/priv/sites","/home/zotonic/zotonic/priv/modules","/home/zotonic/zotonic/user/sites","/home/zotonic/zotonic/user/modules","/home/zotonic/zotonic...",...]},...]],...},...]} >>> >>> in gen_server:terminate/7 line 826 >>> 17:11:25.488 [error] Supervisor z_filewatcher_sup had child undefined >>> started with z_filewatcher_fswatch:start_link() at <0.300.0> exit with >>> reason {enoent,[{erlang,open_port,[{spawn_executable,"no fswatch in >>> /opt/local/lib/erlang/erts-7.0/bin /opt/local/lib/erlang/bin >>> /usr/local/sbin /usr/local/bin /opt/local/sbin /opt/local/bin /usr/sbin >>> /usr/bin >>> /sbin"},[{args,["-0","-x","-r","-L","/home/zotonic/zotonic/src","/home/zotonic/zotonic/modules","/home/zotonic/zotonic/ebin","/home/zotonic/zotonic/priv/sites","/home/zotonic/zotonic/priv/modules","/home/zotonic/zotonic/user/sites","/home/zotonic/zotonic/user/modules","/home/zotonic/zotonic...",...]},...]],...},...]} >>> >>> in context child_terminated >>> >>> It keeps sending theese messages to the console continuously: >>> >>> hh:mm:ss.SSS [info] [fswatch] Starting ... >>> hh:mm:ss.SSS [error] gen_server z_filewatcher_fswatch terminated .. >>> hh:mm:ss.SSS [error] CRASH REPORT Process z_fielwatch_fswatch ... >>> hh:mm:ss.SSS [error] Supervisor z_filewatcher_sup had child undefined ... >>> >>> How do I disable or get past this on a system like SmartOS where neither >>> inotify-tools nor fswatch are available? >>> >>> Thanks, >>> Alain >>> >> >> > -- --- You received this message because you are subscribed to the Google Groups "Zotonic developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
