I've also looked in all the logs for that problem (even lowering the log level) and still, no trace of it ... In fact, this is the problem: if something is wrong in my function/module (runtime problem, as the compilation passed), I'm not able to know. There is other recommended way of looking for such things ?
Thanks, Alin On Fri, Feb 3, 2012 at 3:36 PM, Sean Cribbs <[email protected]> wrote: > Alin, > > Riak no longer uses the default sasl error_logger, but our own logging > library, lager. You can find the output in crash.log (and probably a > transformed version of it in console.log). > > On Fri, Feb 3, 2012 at 5:53 AM, Alin Popa <[email protected]> wrote: > >> Forgot to mention that I've also configured the bucket to be using the >> postcommit hook: >> >> curl -v -X PUT -H "Content-Type: application/json" -d >> '{"props":{"postcommit":[{"mod":"post_commit_hooks","fun":"log"}]}}' >> http://127.0.0.1:8098/riak/mybucket >> >> Alin >> >> >> On Fri, Feb 3, 2012 at 12:37 PM, Alin Popa <[email protected]> wrote: >> >>> Hi guys, >>> >>> I've worked a bit with the Riak's post commit hooks: >>> >>> 1. Create a post commit module/function: >>> >>> *-module(post_commit_hooks).* >>> * >>> * >>> *-export([log/1]).* >>> * >>> * >>> *log(Object) ->* >>> * error_logger:info_msg("OBJECT: ~p~n",[Object]).* >>> >>> 2. Updated the app.conf file in order to pick it up >>> 3. Compiled the file using the erts that's embedded into the riak >>> distribution (which is 1.0.3 btw) >>> 4. Started the riak node >>> 5. Done some simple operations (get and save of objects) and I was able >>> to see the object being dumped to the console.log file. >>> >>> For the failing scenario: >>> 1. Changed the function a bit in order to call an inexistent function >>> >>> *-module(post_commit_hooks).* >>> * >>> * >>> *-export([log/1]).* >>> * >>> * >>> *log(Object) ->* >>> * error_loggerrrrr:info_msg("OBJECT: ~p~n",[Object]).* >>> >>> 2. Stop riak >>> 3. Enabled sasl logging {sasl,[{error_logger_mf_maxfiles, >>> 5},{sasl_error_logger, {file, >>> "/Users/alin/riak/log/sasl-error.log"}},{error_logger_mf_maxbytes, >>> 10485760},{errorlog_type, error},{error_logger_mf_dir, >>> "/Users/alin/riak/log"}]} >>> 4. Recompile the file, using the same erts version >>> 5. Start riak >>> 6. Read and save of the riak objects, but this time, can't see any error >>> to the log files (especially sasl-error.log, as basho's wiki is suggesting >>> [1], even though I can see different kind of messages to sasl-error.log >>> that are not related to the failing execution). >>> >>> Is it something that I'm missing, or is this a bug ? >>> >>> Thanks, >>> Alin >>> >>> [1] http://wiki.basho.com/Commit-Hooks.html >>> >> >> >> _______________________________________________ >> riak-users mailing list >> [email protected] >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> >> > > > -- > Sean Cribbs <[email protected]> > Software Engineer > Basho Technologies, Inc. > http://basho.com/ > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
