On Jan 22, 2018, at 9:08 AM, Mike Lopes <mlopes@teksavvy.ca> wrote:
The code in rlm_couchbase.c definitely processes accounting interim-update packets. So what does the debug log show when you receive such a packet?
I knew I forgot something... Here it is, I also enabled couchbase module debug output for even more details:
Sent Accounting-Request Id 163 from 0.0.0.0:60038 to 127.0.0.1:1813 length 715 (0) Received Accounting-Request Id 163 from 127.0.0.1:60038 to 127.0.0.1:1813 length 715 (0) User-Name = "noneexistent123@domain.com" (0) Acct-Status-Type = Interim-Update
That's good...
rlm_couchbase (couchbase): Reserved connection (0) (0) couchbase: EXPAND radacct_%{%{Acct-Unique-Session-Id}:-%{Acct-Session-Id}} (0) couchbase: --> radacct_51dc686492632c94c03d1346eb471bf5 109644ms [I0] {27151} [INFO] (lcbio_mgr - L:407) <10.0.2.207:11210> (HE=0x5601af6ac6f0) Found ready connection in pool. Reusing socket and not creating new connection 109644ms [I0] {27151} [DEBUG] (lcbio_mgr - L:223) <10.0.2.207:11210> (HE=0x5601af6ac6f0) Assigning R=0x5601af6b0c90 SOCKET=0x5601af6acd60 109644ms [I0] {27151} [DEBUG] (ioctx - L:101) <10.0.2.207:11210> (CTX=0x5601af8b2bc0,unknown) Pairing with SOCK=0x5601af6acd60 109644ms [I0] {27151} [DEBUG] (server - L:499) <10.0.2.207:11210> (SRV=0x5601af6b9580,IX=0) Setting initial timeout=2499ms rlm_couchbase: (get_callback) key does not exist (0) couchbase: ERROR: failed to execute get request or parse returned json object (0) couchbase: no existing document found - creating new json document rlm_couchbase: calculated start timestamp: Nov 18 2017 18:55:53 EST
That's fine.
rlm_couchbase (couchbase): Released connection (0)
That's weird. Try running "radiusd -Xx". This is one of the few times where more information may be useful. It *should* print out what attributes it's converting to json, along with the final document it's writing to couch base. Alan DeKok.