[erlang-questions] erlang-questions Digest, Vol 135, Issue 4

Thu Oct 17 14:07:12 CEST 2013

Can erlang read xlsx file (excel file)?

------------------ Original ------------------
From:  "erlang-questions-request";<erlang-questions-request@REDACTED>;
Date:  Thu, Oct 17, 2013 06:00 PM
To:  "erlang-questions"<erlang-questions@REDACTED>; 

Subject:  erlang-questions Digest, Vol 135, Issue 4

Send erlang-questions mailing list submissions to
	erlang-questions@REDACTED

To subscribe or unsubscribe via the World Wide Web, visit
	http://erlang.org/mailman/listinfo/erlang-questions
or, via email, send a message with subject or body 'help' to
	erlang-questions-request@REDACTED

You can reach the person managing the list at
	erlang-questions-owner@REDACTED

When replying, please edit your Subject line so it is more specific
than "Re: Contents of erlang-questions digest..."

Today's Topics:

   1. Re:  A (hopefully simple) diameter relay question
      (Anders Svensson)
   2. Re:  A (hopefully simple) diameter relay question (Tim Watson)
   3.  memsup errors on Mac OS X 10.8.4 (Max Lapshin)

----------------------------------------------------------------------

Message: 1
Date: Wed, 16 Oct 2013 12:22:04 +0200
From: Anders Svensson <anders.otp@REDACTED>
To: Tim Watson <watson.timothy@REDACTED>
Cc: "erlang-questions@REDACTED Questions"
	<erlang-questions@REDACTED>
Subject: Re: [erlang-questions] A (hopefully simple) diameter relay
	question
Message-ID:
	<CADho9oeUcfZtVRcqmJca83zDaGUs3=na0CnQGvLeSLtgmVEEQg@REDACTED>
Content-Type: text/plain; charset=UTF-8

Hi Tim.

On Tue, Oct 15, 2013 at 5:32 PM, Tim Watson <watson.timothy@REDACTED> wrote:
> Putting the list back on cc...
>
> So actually, having read through someone else's adventure -
> http://erlang.org/pipermail/erlang-questions/2013-March/072918.html - I see
> that if you have multiple 'Auth-Application-Id' entries, you seem to need
> and {application, Config} tuple for each entry with the relevant dictionary.
> That's not at all what I want. I wish to 'snoop' on the AVPs and relay all
> traffic to the real diameter server. I had hoped that by just setting up
>
> {'Auth-Application-Id', [?DIAMETER_APP_ID_RELAY]}, {application, [....,
> {dictionary, ?DIAMETER_DICT_RELAY}]}
>
> that I could avoid all of that.

Yes, this is the right thing to do.

> But unless I set the same list of values in 'Auth-Application-Id' on the
> erlang relay as I do on the server, the capabilities exchange seems to fail.

How do the CER/CEA messages look when it fails?

/Anders, Erlang/OTP

> Is it in fact possible to be a transparent relay/proxy in this fashion? I've
> spent the best part of 24 hours fiddling around with auth-app-ids in the
> test client / server and that's fair enough - but now the test client and
> server will happily talk directly to each other, but once the erlang relay
> gets in the middle it all falls apart. There must be some rules about how to
> configure a relay agent that I'm missing.
>
> Cheers,
> Tim
>
> On 15 Oct 2013, at 10:32, Ferenc Holzhauser wrote:
>
> Hi Tim,
>
> AFAIK the restrict_connections and use_shared_peers options are internal to
> the diameter app for the case it is distributed when connections may be
> handled on different erlang nodes.
>
> Typically if pick peer doesn't give you anything to pick from (assuming that
> peers are connected) then the remote end didn't announce support for the app
> id you're trying to send to (and/or tell that he is a jolly joker relay
> accepting anything). You being relay is not doing a lot when sending IMO.
> What did your seagull announce when connecting?
>
> BR,
> Ferenc
>
>
>
>
> On 14 October 2013 17:43, QDev <watson.timothy@REDACTED> wrote:
>>
>> Hi folks,
>>
>> Hopefully I'm being a bit dense and missing some obvious configuration
>> here, but how do I get the OTP application to relay diameter messages to
>> another (externally hosted) diameter server? I start my service with
>> {'Auth-Application-Id', [?DIAMETER_APP_ID_RELAY]}, {restrict_connections,
>> false} and {use_shared_peers, true}, and then start a listener and a relay
>> to the upstream using the example peer module:
>>
>> peer:connect(?MODULE, {tcp, loopback, 13868}),
>> peer:listen(?MODULE, tcp),
>>
>> However whilst my callback module's handle_request gets called fine, when
>> it returns {relay, [{extra, [relayed]}]}, in the corresponding pick_peer/5
>> callback there are no remote (or local) peers to select from! Do I need to
>> add additional service configuration in order to relay to another diameter
>> server? The server I am trying to "forward" traffic to is *not* an
>> Erlang/OTP server btw, but some other diameter server (or as it happens in
>> this particular case, a diameter test bed server running on seagull).
>>
>> Cheers,
>> Tim
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>
>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>

------------------------------

Message: 2
Date: Wed, 16 Oct 2013 11:39:42 +0100
From: Tim Watson <watson.timothy@REDACTED>
To: Anders Svensson <anders.otp@REDACTED>
Cc: "erlang-questions@REDACTED Questions"
	<erlang-questions@REDACTED>
Subject: Re: [erlang-questions] A (hopefully simple) diameter relay
	question
Message-ID: <C1BFC706-59F4-4891-A471-7E2CB2827DB1@REDACTED>
Content-Type: text/plain; charset=us-ascii

Hi Anders,

On 16 Oct 2013, at 11:22, Anders Svensson wrote:
> On Tue, Oct 15, 2013 at 5:32 PM, Tim Watson <watson.timothy@REDACTED> wrote:
>> I had hoped that by just setting up
>> 
>> {'Auth-Application-Id', [?DIAMETER_APP_ID_RELAY]}, {application, [....,
>> {dictionary, ?DIAMETER_DICT_RELAY}]}
>> 
>> that I could avoid all of that.
> 
> Yes, this is the right thing to do.
> 

Ah, good to know.

>> But unless I set the same list of values in 'Auth-Application-Id' on the
>> erlang relay as I do on the server, the capabilities exchange seems to fail.
> 
> How do the CER/CEA messages look when it fails?
> 

I'm not in front of it right now, but as soon as I am, I'll look through the wireshark traces and post back.

Thanks!

Tim

------------------------------

Message: 3
Date: Thu, 17 Oct 2013 13:49:32 +0400
From: Max Lapshin <max.lapshin@REDACTED>
To: Erlang-Questions Questions <erlang-questions@REDACTED>
Subject: [erlang-questions] memsup errors on Mac OS X 10.8.4
Message-ID:
	<CAMxVRxDw6bx=tEcRzgO2zF0PAVi-F_M7s3nCxyn12iarZVQeiA@REDACTED>
Content-Type: text/plain; charset="utf-8"

(flussonic@REDACTED)49> 13:02:03.502 emulator Error in process <0.16248.3>
on node 'flussonic@REDACTED' with exit value: {{case_clause,{more,"Pages
free:~d.",0,[]}},[{memsup,fread_value,2,[{file,"memsup.erl"},{line,760}]},{memsup,get_memory_usage,1,[{file,"memsup.erl"},{line,730}]},{memsup,'-handle_call/3-fun-1-',2,[{file,"memsup.erl"},{line,285}]}]}

Looks like something two years ago:
http://erlang.org/pipermail/erlang-bugs/2009-October/001559.html

Currently my vm_stat shows:

$ vm_stat
Mach Virtual Memory Statistics: (page size of 4096 bytes)
Pages free:                         979676.
Pages active:                       603451.
Pages inactive:                      74428.
Pages speculative:                  162379.
Pages wired down:                   243971.
"Translation faults":            244013412.
Pages copy-on-write:              15480794.
Pages zero filled:               211325884.
Pages reactivated:                  428830.
Pageins:                          22645518.
Pageouts:                                0.
Object cache: 14 hits of 372888 lookups (0% hit rate)

Can I provide any other information about this failure?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20131017/0aeda644/attachment-0001.html>

------------------------------

_______________________________________________
erlang-questions mailing list
erlang-questions@REDACTED
http://erlang.org/mailman/listinfo/erlang-questions

End of erlang-questions Digest, Vol 135, Issue 4
************************************************
.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20131017/ee3c8ceb/attachment.htm>