Thanks for looking into this!

Same machine:

escorpiao:programming_in_c seawolf$ date
Thu Oct  3 10:22:31 BNT 2013
escorpiao:programming_in_c seawolf$ erl
Erlang R16B01 (erts-5.10.2) [source] [64-bit] [smp:4:4] [async-threads:10] 
[hipe] [kernel-poll:false] [dtrace]

Eshell V5.10.2  (abort with ^G)
1> erlang:localtime_to_universaltime({{2013,9,28},{8,0,35}}, true).
{{2013,9,28},{0,0,35}}
2> q().
ok
escorpiao:programming_in_c seawolf$ 

How do I know for sure that I'm using the same Erlang binary as Riak is? I 
installed it via Homebrew and don't know off the top of my head how to verify 
which Erlang it's picking up (or if I even have more than one).

-- 

jeffrey k eliasen

Find and follow me on:
Blog: http://jeff.jke.net
Twitter: http://twitter.com/jeffreyeliasen
Facebook: http://facebook.com/jeffrey.eliasen

On Oct 2, 2013, at 23:44 , Luke Bakken <[email protected]> wrote:

> Hi Jeff,
> 
> Can you provide the output of the date command on the machine where Riak is 
> running as well as the one from which you're running curl? I'm assuming it's 
> the same workstation, but I'd like to be sure.
> 
> Based on the stack traces you provide, the localtime_to_universaltime 
> function is failing when called with [{{2013,9,28},{8,0,35}},true] as the 
> arguments, which really doesn't make sense.
> 
> Could you run that method via the erl command in the Erlang build used by 
> your Riak installation? I have built Riak from source so erl is in the 
> erts-5.9.1/bin directory, for instance:
> 
> lbakken ~/Projects/basho/riak_ee-1.4/dev/dev1/erts-5.9.1/bin ((riak_ee-1.4.2))
> $ ./erl
> Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:8:8] [async-threads:0] 
> [kernel-poll:false]
> 
> Eshell V5.9.1  (abort with ^G)
> 1> erlang:localtime_to_universaltime({{2013,9,28},{8,0,35}}, true).
> {{2013,9,28},{15,0,35}}
> 2> q().
> ok
> 
> --
> Luke Bakken
> CSE
> [email protected]

_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to