Re: [Radiusplugin-users] OpenVPN & Radius Plugin

[Ralf Lübben]

Hi,

it seems that the interprocess communication between the plugin processes 
causes the crash. From the past messages it seems that the process crashes 
after a read or write to internal sockets. 

So far it's clear to me why. 

If you increase the "verb" option to 7, the plugin will create some debug 
output. I think it is also forwarded to syslog.  Can you try to send the 
output to me? The plugin output has always a "RADIUS-PLUGIN" as prefix. 

Regards
Ralf




Am Sonntag, 31. Oktober 2010, um 19:09:05 schrieben Sie:
> Dear Ralf,
> 
> Same thing happen with Radius Plugin Version 2.1
> 
> #0  0x0000003f3f8c6240 in __read_nocancel () from /lib64/libc.so.6
> #1  0x00002ae6c5cbee6b in IpcSocket::recvInt() () from
> /etc/openvpn-ssl/radiusplugin.so
> #2  0x00002ae6c5cc8c71 in
> AuthenticationProcess::Authentication(PluginContext*) () from
> /etc/openvpn-ssl/radiusplugin.so
> #3  0x00002ae6c5cc71fa in openvpn_plugin_open_v2 () from
> /etc/openvpn-ssl/radiusplugin.so
> #4  0x0000000000441971 in ASN1_BIT_STRING_get_bit ()
> #5  0x0000000000415477 in ASN1_BIT_STRING_get_bit ()
> #6  0x000000000041834d in ASN1_BIT_STRING_get_bit ()
> #7  0x0000000000418b9d in ASN1_BIT_STRING_get_bit ()
> #8  0x0000000000425d8c in ASN1_BIT_STRING_get_bit ()
> #9  0x000000000042f203 in ASN1_BIT_STRING_get_bit ()
> #10 0x0000003f3f81d994 in __libc_start_main () from /lib64/libc.so.6
> #11 0x00000000004064d9 in ASN1_BIT_STRING_get_bit ()
> #12 0x00007fff7207a588 in ?? ()
> #13 0x0000000000000000 in ?? ()
> 
> Best Regards.
> 
> On Sun, Oct 31, 2010 at 6:17 PM, Farrukh Ahmed <address@hidden> wrote:
> > Dear Ralf,
> > 
> > I am using syslog logging for OpenVPN and which does not logged Radius
> > Plugin Logs. Today i found that we again got crashed.
> > 
> > FYI,
> > 
> > #0  0x0000003f3f8c6240 in __read_nocancel () from /lib64/libc.so.6
> > #1  0x00002b27a7ebce6b in std::_Rb_tree<std::basic_string<char,
> > std::char_traits<char>, std::allocator<char> >,
> > std::pair<std::basic_string<char, std::char_traits<char>,
> > std::allocator<char> > const, UserAcct>,
> > std::_Select1st<std::pair<std::basic_string<char, std::char_traits<char>,
> > std::allocator<char> > const, UserAcct> >,
> > std::less<std::basic_string<char, std::char_traits<char>,
> > std::allocator<char> > >,
> > std::allocator<std::pair<std::basic_string<char, std::char_traits<char>,
> > std::allocator<char> > const, UserAcct> >
> > 
> > >::_M_insert(std::_Rb_tree_node_base*, std::_Rb_tree_node_base*,
> > 
> > std::pair<std::basic_string<char, std::char_traits<char>,
> > std::allocator<char> > const, UserAcct> const&) () from
> > /etc/openvpn/radiusplugin.so
> > #2  0x00002b27a7ec6c71 in
> > AuthenticationProcess::Authentication(PluginContext*) () from
> > /etc/openvpn/radiusplugin.so
> > #3  0x00002b27a7ec51fa in User::User(User const&) () from
> > /etc/openvpn/radiusplugin.so
> > #4  0x0000000000441971 in ASN1_BIT_STRING_get_bit ()
> > #5  0x0000000000415477 in ASN1_BIT_STRING_get_bit ()
> > #6  0x000000000041834d in ASN1_BIT_STRING_get_bit ()
> > #7  0x0000000000418b9d in ASN1_BIT_STRING_get_bit ()
> > #8  0x0000000000426e07 in ASN1_BIT_STRING_get_bit ()
> > #9  0x000000000042f203 in ASN1_BIT_STRING_get_bit ()
> > #10 0x0000003f3f81d994 in __libc_start_main () from /lib64/libc.so.6
> > #11 0x00000000004064d9 in ASN1_BIT_STRING_get_bit ()
> > #12 0x00007fff46ebb6d8 in ?? ()
> > #13 0x0000000000000000 in ?? ()
> > 
> > I will try 2.1 and let you know if there will be no issue.
> > 
> > Best Regards.
> > 
> > On Sun, Oct 31, 2010 at 2:37 PM, Ralf Lübben <address@hidden> wrote:
> >> Hello,
> >> 
> >> can you also try the version 2.1 from
> >> http://www.nongnu.org/radiusplugin/?
> >> 
> >> The new beta mainly includes a "accounting only feature" and "non fatal
> >> accouting" and bugfixes related to BSD.
> >> 
> >> Some changes are in the function AccoutingProcess which seems to crash,
> >> to find
> >> the code where the plugin crashes I would need the end (~100 lines) of
> >> the OpenVPN log file, maybe it gives a hint.
> >> 
> >> Can you identify the event when the plugin crashes, e.g. a user
> >> connects, disconnects, etc?
> >> 
> >> Regards,
> >> Ralf
> >> 
> >> Am Samstag, 30. Oktober 2010, um 14:03:49 schrieb Farrukh Ahmed:
> >> > Dear Ralf,
> >> > 
> >> > can you provide me some more information:
> >> > > - Which version of the plugin do you use?
> >> > 
> >> > I have used this v2.1a_beta1 and from CVS head.
> >> > 
> >> > > - Which operating system? Is it 64 bit os?
> >> > 
> >> > Yes, its CentOS 64 bit os.
> >> > 
> >> > > - The plugin configuration.
> >> > 
> >> > NAS-Identifier=OpenVPN-NL-01
> >> > Service-Type=5
> >> > Framed-Protocol=1
> >> > NAS-Port-Type=5
> >> > NAS-IP-Address=83.170.87.238
> >> > OpenVPNConfig=/etc/openvpn/server.conf
> >> > subnet=255.255.255.0
> >> > overwriteccfiles=false
> >> > 
> >> > server
> >> > {
> >> > 
> >> >         acctport=1813
> >> >         authport=1812
> >> >         name=83.170.87.238
> >> >         retry=1
> >> >         wait=1
> >> >         sharedsecret=testing123
> >> > 
> >> > }
> >> > 
> >> > > - And can you also increase the verbosity in OpenVPN to 7 and send
> >> > > me
> >> 
> >> the
> >> 
> >> > > OpenVPN log file? The plugin will write some debug information to
> >> > > it.
> >> > 
> >> > I have seen log file its very huge i can not send it to you right now.
> >> > 
> >> > Best Regards.
> > 
> > --
> > Färrükh Ähmëd