Core Dump

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

Core Dump

Nathaniel L. Keeling III-2
I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
compile successfully by adding the parameter "-mcpu=ultrasparc" to the
"DEFS" compile time options in Makefile.defs, but when I execute
opensips, it will die with a core dump. It does thru the loading of the
modules ok but dies later. I have included part of the output from
running opensips with truss and the output from opensips.

Feb 18 13:44:56 [4447] DBG:core:find_cmd_export_t: found <xlog>(1) in
module xlog [/usr/local/opensips-1.6.1/lib64/opensips/modules/]
Feb 18 13:44:56 [4447] DBG:core:find_cmd_export_t: found <xlog>(1) in
module xlog [/usr/local/opensips-1.6.1/lib64/opensips/modules/]
Feb 18 13:44:56 [4447] DBG:core:find_cmd_export_t: found
<t_was_cancelled>(0) in module tm
[/usr/local/opensips-1.6.1/lib64/opensips/modules/]
Feb 18 13:44:56 [4447] DBG:core:socket2str: <udp:xxx.xxx.xxx.xxx:5060>
Feb 18 13:44:56 [4447] DBG:core:socket2str: <tcp:xxx.xxx.xxx.xxx:5060>
Listening on
             udp: xxxxxxxxxxxxxxxxxx.com [xxx.xxx.xxx.xxx]:5060
             tcp: xxxxxxxxxxxxxxxxxx.com [xxx.xxx.xxx.xxx]:5060
Aliases:

Feb 18 13:44:56 [4447] WARNING:core:main: no fork mode
Feb 18 13:44:56 [4447] DBG:core:fm_malloc_init: F_OPTIMIZE=16384,
/ROUNDTO=2048
Feb 18 13:44:56 [4447] DBG:core:fm_malloc_init: F_HASH_SIZE=2067,
fm_block size=16568
Feb 18 13:44:56 [4447] DBG:core:fm_malloc_init: params (fcc00000,
33554432), start=fcc00000
Feb 18 13:44:56 [4447] DBG:core:shm_mem_init_mallocs: success
Bus Error - core dumped

*Output from truss running opensips:*

4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
4327:   write(2, "   [", 2)                             = 2
4327:   write(2, " 4 3 2 7", 4)                         = 4
4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
4327:   write(2, " f i n d _ c m d _ e x p".., 17)      = 17
4327:   write(2, " :   f o u n d   <", 9)               = 9
4327:   write(2, " t _ w a s _ c a n c e l".., 15)      = 15
4327:   write(2, " > ( 0", 3)                           = 3
4327:   write(2, " )   i n   m o d u l e  ", 12)        = 12
4327:   write(2, " t m   [", 4)                         = 4
4327:   write(2, " / u s r / l o c a l / o".., 49)      = 49
4327:   write(2, " ]\n", 2)                             = 2
4327:   ioctl(3, TCGETA, 0xFFBFF46C)                    Err#25 ENOTTY
4327:   getpid()                                        = 4327 [4326]
4327:   so_socket(PF_INET, SOCK_DGRAM, IPPROTO_IP, "", SOV_DEFAULT) = 4
4327:   ioctl(4, SIOCGLIFNUM, 0xFFBFFA84)               = 0
4327:   close(4)                                        = 0
4327:   sysinfo(SI_SRPC_DOMAIN, "", 256)                = 1
4327:   open("/etc/resolv.conf", O_RDONLY|O_LARGEFILE)  = 4
4327:   fcntl(4, F_DUPFD, 0x00000100)                   Err#22 EINVAL
4327:   read(4, " d o m a i n   a k a n .".., 1024)     = 73
4327:   read(4, 0x00294A38, 1024)                       = 0
4327:   close(4)                                        = 0
4327:   so_socket(PF_INET, SOCK_DGRAM, IPPROTO_IP, "", SOV_DEFAULT) = 4
4327:   ioctl(4, SIOCGIFCONF, 0xFFBFF5B0)               = 0
4327:   ioctl(4, SIOCGIFCONF, 0xFFBFF5B0)               = 0
4327:   ioctl(4, SIOCGIFFLAGS, 0xFFBFF570)              = 0
4327:   ioctl(4, SIOCGIFFLAGS, 0xFFBFF570)              = 0
4327:   close(4)                                        = 0
4327:   brk(0x00295F60)                                 = 0
4327:   brk(0x00297F60)                                 = 0
4327:   open("/etc/netconfig", O_RDONLY|O_LARGEFILE)    = 4
4327:   fcntl(4, F_DUPFD, 0x00000100)                   Err#22 EINVAL
4327:   read(4, " # p r a g m a   i d e n".., 1024)     = 1024
4327:   read(4, " t s           t p i _ c".., 1024)     = 215
4327:   read(4, 0x00296B80, 1024)                       = 0
4327:   lseek(4, 0, SEEK_SET)                           = 0
4327:   read(4, " # p r a g m a   i d e n".., 1024)     = 1024
4327:   read(4, " t s           t p i _ c".., 1024)     = 215
4327:   read(4, 0x00296B80, 1024)                       = 0
4327:   close(4)                                        = 0
4327:   open("/dev/udp", O_RDONLY)                      = 4
4327:   ioctl(4, SIOCGLIFNUM, 0xFFBFF474)               = 0
4327:   close(4)                                        = 0
4327:   open("/dev/udp", O_RDONLY)                      = 4
4327:   ioctl(4, SIOCGLIFNUM, 0xFFBFF474)               = 0
4327:   close(4)                                        = 0
4327:   getuid()                                        = 0 [0]
4327:   getpid()                                        = 4327 [4326]
4327:   open("/proc/4327/psinfo", O_RDONLY)             = 4
4327:   read(4, "02\0\0\0\0\0\001\0\010E7".., 336)      = 336
4327:   close(4)                                        = 0
4327:   mmap(0x00010000, 65536, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEC30000
4327:   getuid()                                        = 0 [0]
4327:   getuid()                                        = 0 [0]
4327:   open64("/var/run/name_service_door", O_RDONLY)  = 4
4327:   fcntl(4, F_SETFD, 0x00000001)                   = 0
4327:   door_info(4, 0xFF1C1788)                        = 0
4327:   door_call(4, 0xFFBFF228)                        = 0
4327:   open("/etc/default/nss", O_RDONLY|O_LARGEFILE)  = 5
4327:   fcntl(5, F_DUPFD, 0x00000100)                   Err#22 EINVAL
4327:   read(5, " #   i d e n t\t " @ ( #".., 1024)     = 1024
4327:   read(5, " y   t h o s e\n # f u n".., 1024)     = 211
4327:   read(5, 0x00297100, 1024)                       = 0
4327:   close(5)                                        = 0
4327:   time()                                          = 1266479116
4327:   getpid()                                        = 4327 [4326]
4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
4327:   write(2, "   [", 2)                             = 2
4327:   write(2, " 4 3 2 7", 4)                         = 4
4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
4327:   write(2, " s o c k e t 2 s t r", 10)            = 10
4327:   write(2, " :   <", 3)                           = 3
4327:   write(2, " u d p : 2 0 9 . 2 5 2 .".., 23)      = 23
4327:   write(2, " >\n", 2)                             = 2
4327:   so_socket(PF_INET, SOCK_DGRAM, IPPROTO_IP, "", SOV_DEFAULT) = 5
4327:   ioctl(5, SIOCGIFCONF, 0xFFBFF5B0)               = 0
4327:   ioctl(5, SIOCGIFCONF, 0xFFBFF5B0)               = 0
4327:   ioctl(5, SIOCGIFFLAGS, 0xFFBFF570)              = 0
4327:   ioctl(5, SIOCGIFFLAGS, 0xFFBFF570)              = 0
4327:   close(5)                                        = 0
4327:   getuid()                                        = 0 [0]
4327:   getuid()                                        = 0 [0]
4327:   door_info(4, 0xFFBFF180)                        = 0
4327:   door_call(4, 0xFFBFF228)                        = 0
4327:   time()                                          = 1266479116
4327:   getpid()                                        = 4327 [4326]
4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
4327:   write(2, "   [", 2)                             = 2
4327:   write(2, " 4 3 2 7", 4)                         = 4
4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
4327:   write(2, " s o c k e t 2 s t r", 10)            = 10
4327:   write(2, " :   <", 3)                           = 3
4327:   write(2, " t c p : 2 0 9 . 2 5 2 .".., 23)      = 23
4327:   write(2, " >\n", 2)                             = 2
4327:   ioctl(1, TCGETA, 0xFFBFFA34)                    = 0
4327:   fstat64(1, 0xFFBFF950)                          = 0
4327:   write(1, " L i s t e n i n g   o n".., 14)      = 14
4327:   write(1, "                        ".., 70)      = 70
4327:   write(1, "                        ".., 70)      = 70
4327:   write(1, " A l i a s e s :  \n", 10)            = 10
4327:   write(1, "\n", 1)                               = 1
4327:   time()                                          = 1266479116
4327:   getpid()                                        = 4327 [4326]
4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
4327:   write(2, "   [", 2)                             = 2
4327:   write(2, " 4 3 2 7", 4)                         = 4
4327:   write(2, " ]   W A R N I N G : c o".., 15)      = 15
4327:   write(2, " m a i n", 4)                         = 4
4327:   write(2, " :   n o   f o r k   m o".., 15)      = 15
4327:   write(2, "\n", 1)                               = 1
4327:   time()                                          = 1266479116
4327:   open("/dev/zero", O_RDWR)                       = 5
4327:   mmap(0x00000000, 33554432, PROT_READ|PROT_WRITE, MAP_SHARED, 5,
0) = 0xFCC00000
4327:   close(5)                                        = 0
4327:   time()                                          = 1266479116
4327:   getpid()                                        = 4327 [4326]
4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
4327:   write(2, "   [", 2)                             = 2
4327:   write(2, " 4 3 2 7", 4)                         = 4
4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
4327:   write(2, " f m _ m a l l o c _ i n".., 14)      = 14
4327:   write(2, " :   F _ O P T I M I Z E".., 13)      = 13
4327:   write(2, " 1 6 3 8 4", 5)                       = 5
4327:   write(2, " ,   / R O U N D T O =", 11)          = 11
4327:   write(2, " 2 0 4 8", 4)                         = 4
4327:   write(2, "\n", 1)                               = 1
4327:   time()                                          = 1266479116
4327:   getpid()                                        = 4327 [4326]
4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
4327:   write(2, "   [", 2)                             = 2
4327:   write(2, " 4 3 2 7", 4)                         = 4
4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
4327:   write(2, " f m _ m a l l o c _ i n".., 14)      = 14
4327:   write(2, " :   F _ H A S H _ S I Z".., 14)      = 14
4327:   write(2, " 2 0 6 7", 4)                         = 4
4327:   write(2, " ,   f m _ b l o c k   s".., 16)      = 16
4327:   write(2, " 1 6 5 6 8", 5)                       = 5
4327:   write(2, "\n", 1)                               = 1
4327:   time()                                          = 1266479116
4327:   getpid()                                        = 4327 [4326]
4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
4327:   write(2, "   [", 2)                             = 2
4327:   write(2, " 4 3 2 7", 4)                         = 4
4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
4327:   write(2, " f m _ m a l l o c _ i n".., 14)      = 14
4327:   write(2, " :   p a r a m s   (", 10)            = 10
4327:   write(2, " f c c 0 0 0 0 0", 8)                 = 8
4327:   write(2, " ,  ", 2)                             = 2
4327:   write(2, " 3 3 5 5 4 4 3 2", 8)                 = 8
4327:   write(2, " ) ,   s t a r t =", 9)               = 9
4327:   write(2, " f c c 0 0 0 0 0", 8)                 = 8
4327:   write(2, "\n", 1)                               = 1
4327:   time()                                          = 1266479116
4327:   getpid()                                        = 4327 [4326]
4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
4327:   write(2, "   [", 2)                             = 2
4327:   write(2, " 4 3 2 7", 4)                         = 4
4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
4327:   write(2, " s h m _ m e m _ i n i t".., 20)      = 20
4327:   write(2, " :   s u c c e s s\n", 10)            = 10
4327:       Incurred fault #5, FLTACCESS  %pc = 0x00094268
4327:         siginfo: SIGBUS BUS_ADRALN addr=0xFCC040EC
4327:       Received signal #10, SIGBUS [default]
4327:         siginfo: SIGBUS BUS_ADRALN addr=0xFCC040EC

thanks

nathaniel

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

opensipslist

Hello Nathaniel,

An jeu., févr 18, 2010, Nathaniel L Keeling schrieb:
>I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
>compile successfully by adding the parameter "-mcpu=ultrasparc" to
>the "DEFS" compile time options in Makefile.defs, but when I
>execute opensips, it will die with a core dump. It does thru the
>loading of the modules ok but dies later.
>
Both Solaris 10 Sparc or Solaris 11 x86 do core dump when trying
to use OpenSIPS 1.6.1. Nobody has seem to be able to diagnose this
correctly much less repair the problem.

If you try the same build parameters to compile 1.6.0 you will
probably find that it not only compiles correctly but runs without
core dumping as well. So much for the

    'it is recommended to upgrade, as it provides important
     stability improvements'

that they write about the 1.6.1 release on the website.

Regards,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Bogdan-Andrei Iancu
In reply to this post by Nathaniel L. Keeling III-2
Hi Nathaniel,

Normally there should be no need to add any params, as opensips makefile
should detect the correct OS and arch.

So, without the mcpu you added, what is the problem? does not compile? or ?

The crash may be related to the forcing of a different CPU type - if the
compiler added some instructions which are not understood by cpu.

Regards,
Bogdan

Nathaniel L Keeling wrote:

> I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
> compile successfully by adding the parameter "-mcpu=ultrasparc" to the
> "DEFS" compile time options in Makefile.defs, but when I execute
> opensips, it will die with a core dump. It does thru the loading of the
> modules ok but dies later. I have included part of the output from
> running opensips with truss and the output from opensips.
>
> Feb 18 13:44:56 [4447] DBG:core:find_cmd_export_t: found <xlog>(1) in
> module xlog [/usr/local/opensips-1.6.1/lib64/opensips/modules/]
> Feb 18 13:44:56 [4447] DBG:core:find_cmd_export_t: found <xlog>(1) in
> module xlog [/usr/local/opensips-1.6.1/lib64/opensips/modules/]
> Feb 18 13:44:56 [4447] DBG:core:find_cmd_export_t: found
> <t_was_cancelled>(0) in module tm
> [/usr/local/opensips-1.6.1/lib64/opensips/modules/]
> Feb 18 13:44:56 [4447] DBG:core:socket2str: <udp:xxx.xxx.xxx.xxx:5060>
> Feb 18 13:44:56 [4447] DBG:core:socket2str: <tcp:xxx.xxx.xxx.xxx:5060>
> Listening on
>              udp: xxxxxxxxxxxxxxxxxx.com [xxx.xxx.xxx.xxx]:5060
>              tcp: xxxxxxxxxxxxxxxxxx.com [xxx.xxx.xxx.xxx]:5060
> Aliases:
>
> Feb 18 13:44:56 [4447] WARNING:core:main: no fork mode
> Feb 18 13:44:56 [4447] DBG:core:fm_malloc_init: F_OPTIMIZE=16384,
> /ROUNDTO=2048
> Feb 18 13:44:56 [4447] DBG:core:fm_malloc_init: F_HASH_SIZE=2067,
> fm_block size=16568
> Feb 18 13:44:56 [4447] DBG:core:fm_malloc_init: params (fcc00000,
> 33554432), start=fcc00000
> Feb 18 13:44:56 [4447] DBG:core:shm_mem_init_mallocs: success
> Bus Error - core dumped
>
> *Output from truss running opensips:*
>
> 4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
> 4327:   write(2, "   [", 2)                             = 2
> 4327:   write(2, " 4 3 2 7", 4)                         = 4
> 4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
> 4327:   write(2, " f i n d _ c m d _ e x p".., 17)      = 17
> 4327:   write(2, " :   f o u n d   <", 9)               = 9
> 4327:   write(2, " t _ w a s _ c a n c e l".., 15)      = 15
> 4327:   write(2, " > ( 0", 3)                           = 3
> 4327:   write(2, " )   i n   m o d u l e  ", 12)        = 12
> 4327:   write(2, " t m   [", 4)                         = 4
> 4327:   write(2, " / u s r / l o c a l / o".., 49)      = 49
> 4327:   write(2, " ]\n", 2)                             = 2
> 4327:   ioctl(3, TCGETA, 0xFFBFF46C)                    Err#25 ENOTTY
> 4327:   getpid()                                        = 4327 [4326]
> 4327:   so_socket(PF_INET, SOCK_DGRAM, IPPROTO_IP, "", SOV_DEFAULT) = 4
> 4327:   ioctl(4, SIOCGLIFNUM, 0xFFBFFA84)               = 0
> 4327:   close(4)                                        = 0
> 4327:   sysinfo(SI_SRPC_DOMAIN, "", 256)                = 1
> 4327:   open("/etc/resolv.conf", O_RDONLY|O_LARGEFILE)  = 4
> 4327:   fcntl(4, F_DUPFD, 0x00000100)                   Err#22 EINVAL
> 4327:   read(4, " d o m a i n   a k a n .".., 1024)     = 73
> 4327:   read(4, 0x00294A38, 1024)                       = 0
> 4327:   close(4)                                        = 0
> 4327:   so_socket(PF_INET, SOCK_DGRAM, IPPROTO_IP, "", SOV_DEFAULT) = 4
> 4327:   ioctl(4, SIOCGIFCONF, 0xFFBFF5B0)               = 0
> 4327:   ioctl(4, SIOCGIFCONF, 0xFFBFF5B0)               = 0
> 4327:   ioctl(4, SIOCGIFFLAGS, 0xFFBFF570)              = 0
> 4327:   ioctl(4, SIOCGIFFLAGS, 0xFFBFF570)              = 0
> 4327:   close(4)                                        = 0
> 4327:   brk(0x00295F60)                                 = 0
> 4327:   brk(0x00297F60)                                 = 0
> 4327:   open("/etc/netconfig", O_RDONLY|O_LARGEFILE)    = 4
> 4327:   fcntl(4, F_DUPFD, 0x00000100)                   Err#22 EINVAL
> 4327:   read(4, " # p r a g m a   i d e n".., 1024)     = 1024
> 4327:   read(4, " t s           t p i _ c".., 1024)     = 215
> 4327:   read(4, 0x00296B80, 1024)                       = 0
> 4327:   lseek(4, 0, SEEK_SET)                           = 0
> 4327:   read(4, " # p r a g m a   i d e n".., 1024)     = 1024
> 4327:   read(4, " t s           t p i _ c".., 1024)     = 215
> 4327:   read(4, 0x00296B80, 1024)                       = 0
> 4327:   close(4)                                        = 0
> 4327:   open("/dev/udp", O_RDONLY)                      = 4
> 4327:   ioctl(4, SIOCGLIFNUM, 0xFFBFF474)               = 0
> 4327:   close(4)                                        = 0
> 4327:   open("/dev/udp", O_RDONLY)                      = 4
> 4327:   ioctl(4, SIOCGLIFNUM, 0xFFBFF474)               = 0
> 4327:   close(4)                                        = 0
> 4327:   getuid()                                        = 0 [0]
> 4327:   getpid()                                        = 4327 [4326]
> 4327:   open("/proc/4327/psinfo", O_RDONLY)             = 4
> 4327:   read(4, "02\0\0\0\0\0\001\0\010E7".., 336)      = 336
> 4327:   close(4)                                        = 0
> 4327:   mmap(0x00010000, 65536, PROT_READ|PROT_WRITE|PROT_EXEC,
> MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEC30000
> 4327:   getuid()                                        = 0 [0]
> 4327:   getuid()                                        = 0 [0]
> 4327:   open64("/var/run/name_service_door", O_RDONLY)  = 4
> 4327:   fcntl(4, F_SETFD, 0x00000001)                   = 0
> 4327:   door_info(4, 0xFF1C1788)                        = 0
> 4327:   door_call(4, 0xFFBFF228)                        = 0
> 4327:   open("/etc/default/nss", O_RDONLY|O_LARGEFILE)  = 5
> 4327:   fcntl(5, F_DUPFD, 0x00000100)                   Err#22 EINVAL
> 4327:   read(5, " #   i d e n t\t " @ ( #".., 1024)     = 1024
> 4327:   read(5, " y   t h o s e\n # f u n".., 1024)     = 211
> 4327:   read(5, 0x00297100, 1024)                       = 0
> 4327:   close(5)                                        = 0
> 4327:   time()                                          = 1266479116
> 4327:   getpid()                                        = 4327 [4326]
> 4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
> 4327:   write(2, "   [", 2)                             = 2
> 4327:   write(2, " 4 3 2 7", 4)                         = 4
> 4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
> 4327:   write(2, " s o c k e t 2 s t r", 10)            = 10
> 4327:   write(2, " :   <", 3)                           = 3
> 4327:   write(2, " u d p : 2 0 9 . 2 5 2 .".., 23)      = 23
> 4327:   write(2, " >\n", 2)                             = 2
> 4327:   so_socket(PF_INET, SOCK_DGRAM, IPPROTO_IP, "", SOV_DEFAULT) = 5
> 4327:   ioctl(5, SIOCGIFCONF, 0xFFBFF5B0)               = 0
> 4327:   ioctl(5, SIOCGIFCONF, 0xFFBFF5B0)               = 0
> 4327:   ioctl(5, SIOCGIFFLAGS, 0xFFBFF570)              = 0
> 4327:   ioctl(5, SIOCGIFFLAGS, 0xFFBFF570)              = 0
> 4327:   close(5)                                        = 0
> 4327:   getuid()                                        = 0 [0]
> 4327:   getuid()                                        = 0 [0]
> 4327:   door_info(4, 0xFFBFF180)                        = 0
> 4327:   door_call(4, 0xFFBFF228)                        = 0
> 4327:   time()                                          = 1266479116
> 4327:   getpid()                                        = 4327 [4326]
> 4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
> 4327:   write(2, "   [", 2)                             = 2
> 4327:   write(2, " 4 3 2 7", 4)                         = 4
> 4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
> 4327:   write(2, " s o c k e t 2 s t r", 10)            = 10
> 4327:   write(2, " :   <", 3)                           = 3
> 4327:   write(2, " t c p : 2 0 9 . 2 5 2 .".., 23)      = 23
> 4327:   write(2, " >\n", 2)                             = 2
> 4327:   ioctl(1, TCGETA, 0xFFBFFA34)                    = 0
> 4327:   fstat64(1, 0xFFBFF950)                          = 0
> 4327:   write(1, " L i s t e n i n g   o n".., 14)      = 14
> 4327:   write(1, "                        ".., 70)      = 70
> 4327:   write(1, "                        ".., 70)      = 70
> 4327:   write(1, " A l i a s e s :  \n", 10)            = 10
> 4327:   write(1, "\n", 1)                               = 1
> 4327:   time()                                          = 1266479116
> 4327:   getpid()                                        = 4327 [4326]
> 4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
> 4327:   write(2, "   [", 2)                             = 2
> 4327:   write(2, " 4 3 2 7", 4)                         = 4
> 4327:   write(2, " ]   W A R N I N G : c o".., 15)      = 15
> 4327:   write(2, " m a i n", 4)                         = 4
> 4327:   write(2, " :   n o   f o r k   m o".., 15)      = 15
> 4327:   write(2, "\n", 1)                               = 1
> 4327:   time()                                          = 1266479116
> 4327:   open("/dev/zero", O_RDWR)                       = 5
> 4327:   mmap(0x00000000, 33554432, PROT_READ|PROT_WRITE, MAP_SHARED, 5,
> 0) = 0xFCC00000
> 4327:   close(5)                                        = 0
> 4327:   time()                                          = 1266479116
> 4327:   getpid()                                        = 4327 [4326]
> 4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
> 4327:   write(2, "   [", 2)                             = 2
> 4327:   write(2, " 4 3 2 7", 4)                         = 4
> 4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
> 4327:   write(2, " f m _ m a l l o c _ i n".., 14)      = 14
> 4327:   write(2, " :   F _ O P T I M I Z E".., 13)      = 13
> 4327:   write(2, " 1 6 3 8 4", 5)                       = 5
> 4327:   write(2, " ,   / R O U N D T O =", 11)          = 11
> 4327:   write(2, " 2 0 4 8", 4)                         = 4
> 4327:   write(2, "\n", 1)                               = 1
> 4327:   time()                                          = 1266479116
> 4327:   getpid()                                        = 4327 [4326]
> 4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
> 4327:   write(2, "   [", 2)                             = 2
> 4327:   write(2, " 4 3 2 7", 4)                         = 4
> 4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
> 4327:   write(2, " f m _ m a l l o c _ i n".., 14)      = 14
> 4327:   write(2, " :   F _ H A S H _ S I Z".., 14)      = 14
> 4327:   write(2, " 2 0 6 7", 4)                         = 4
> 4327:   write(2, " ,   f m _ b l o c k   s".., 16)      = 16
> 4327:   write(2, " 1 6 5 6 8", 5)                       = 5
> 4327:   write(2, "\n", 1)                               = 1
> 4327:   time()                                          = 1266479116
> 4327:   getpid()                                        = 4327 [4326]
> 4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
> 4327:   write(2, "   [", 2)                             = 2
> 4327:   write(2, " 4 3 2 7", 4)                         = 4
> 4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
> 4327:   write(2, " f m _ m a l l o c _ i n".., 14)      = 14
> 4327:   write(2, " :   p a r a m s   (", 10)            = 10
> 4327:   write(2, " f c c 0 0 0 0 0", 8)                 = 8
> 4327:   write(2, " ,  ", 2)                             = 2
> 4327:   write(2, " 3 3 5 5 4 4 3 2", 8)                 = 8
> 4327:   write(2, " ) ,   s t a r t =", 9)               = 9
> 4327:   write(2, " f c c 0 0 0 0 0", 8)                 = 8
> 4327:   write(2, "\n", 1)                               = 1
> 4327:   time()                                          = 1266479116
> 4327:   getpid()                                        = 4327 [4326]
> 4327:   write(2, " F e b   1 8   0 1 : 4 5".., 15)      = 15
> 4327:   write(2, "   [", 2)                             = 2
> 4327:   write(2, " 4 3 2 7", 4)                         = 4
> 4327:   write(2, " ]   D B G : c o r e :", 11)          = 11
> 4327:   write(2, " s h m _ m e m _ i n i t".., 20)      = 20
> 4327:   write(2, " :   s u c c e s s\n", 10)            = 10
> 4327:       Incurred fault #5, FLTACCESS  %pc = 0x00094268
> 4327:         siginfo: SIGBUS BUS_ADRALN addr=0xFCC040EC
> 4327:       Received signal #10, SIGBUS [default]
> 4327:         siginfo: SIGBUS BUS_ADRALN addr=0xFCC040EC
>
> thanks
>
> nathaniel
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>  


--
Bogdan-Andrei Iancu
www.voice-system.ro


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Bogdan-Andrei Iancu
In reply to this post by opensipslist
Hi Brian,

[hidden email] wrote:

> Hello Nathaniel,
>
> An jeu., févr 18, 2010, Nathaniel L Keeling schrieb:
>  
>> I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
>> compile successfully by adding the parameter "-mcpu=ultrasparc" to
>> the "DEFS" compile time options in Makefile.defs, but when I
>> execute opensips, it will die with a core dump. It does thru the
>> loading of the modules ok but dies later.
>>
>>    
> Both Solaris 10 Sparc or Solaris 11 x86 do core dump when trying
> to use OpenSIPS 1.6.1. Nobody has seem to be able to diagnose this
> correctly much less repair the problem.
>  
How comes ? I know people using 1.6 on sparc + Solaris  :P....
> If you try the same build parameters to compile 1.6.0 you will
> probably find that it not only compiles correctly but runs without
> core dumping as well. So much for the
>
>     'it is recommended to upgrade, as it provides important
>      stability improvements'
>
> that they write about the 1.6.1 release on the website.
>  
hmmm...if you see the compiling as stability, maybe you are right....

Now, getting serious....the problem is that since SF trashed the
compiled farm, we (or at least I) do not have any sparc / solaris
platform were to test the makefile options or the code....

Regards,
Bogdan

--
Bogdan-Andrei Iancu
www.voice-system.ro


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

opensipslist

Hello Bogdan,

An ven., févr 19, 2010, Bogdan-Andrei Iancu schrieb:

>[hidden email] wrote:
>> An jeu., févr 18, 2010, Nathaniel L Keeling schrieb:
>>> I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
>>> compile successfully by adding the parameter "-mcpu=ultrasparc" to
>>> the "DEFS" compile time options in Makefile.defs, but when I
>>> execute opensips, it will die with a core dump. It does thru the
>>> loading of the modules ok but dies later.
>>>
>> Both Solaris 10 Sparc or Solaris 11 x86 do core dump when trying
>> to use OpenSIPS 1.6.1. Nobody has seem to be able to diagnose this
>> correctly much less repair the problem.
>>
>How comes ? I know people using 1.6 on sparc + Solaris  :P....
>
I don't know either, but I'm sure that some builds work better
than others. This would particularly be the case if the problem
code was in a certain module or component which some builds are
missing. My build contains almost everything.

>> If you try the same build parameters to compile 1.6.0 you will
>> probably find that it not only compiles correctly but runs without
>> core dumping as well. So much for the
>>
>>     'it is recommended to upgrade, as it provides important
>>      stability improvements'
>>
>> that they write about the 1.6.1 release on the website.
>>
>hmmm... if you see the compiling as stability, maybe you are right....
>
The buildtime is not as problematic as the runtime, which only
rarely coredumps on 1.6.0 but quite often on 1.6.1. I can get
1.6.0 to coredump as well by forcing OpenSIPS to try writing
to TCP connections which don't exist. Being careful with 1.6.0
then it is possible to get a few weeks worth of usage with no
core dump, maybe more.

>Now, getting serious... the problem is that since SF trashed the
>compiled farm, we (or at least I) do not have any sparc / solaris
>platform were to test the makefile options or the code...
>
You can do a lot with a single good machine and Xen, but that
is maybe food for another thread. It's sad indeed that no Solaris
platforms are available for testing.

Regards,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Nathaniel L. Keeling III-2
In reply to this post by Bogdan-Andrei Iancu
Bogdan,

this is the error that I get when I do not add that option:

gcc  -g -O9 -funroll-loops   -Wall      -DNAME='"opensips"'
-DVERSION='"1.6.1-notls"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILE
R='"gcc 3.4.6"' -D__CPU_sparc64 -D__OS_solaris -D__SMP_yes
-DCFG_DIR='"/usr/local/opensips-1.6.1/etc/opensips/"' -DPKG_MALLOC -DSHM
_MEM  -DSHM_MMAP -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE
-DHAVE_RESOLV_RES -DSTATISTICS -DCHANGEABLE_DEBUG_LEVEL -DF_MALLO
C  -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  
-DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALL
OCA_H -DUSE_SIGACTION -D_POSIX_PTHREAD_SEMANTICS -DHAVE_DEVPOLL
-DHAVE_SELECT -c blacklists.c -o blacklists.o
*/usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 223: error: cannot use
v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 243: error: cannot use
v8plus instructions in a non-v8plus target binary*

I get the same error when compiling opensips 1.5


Thanks

Nathaniel

Bogdan-Andrei Iancu wrote:

>Hi Brian,
>
>[hidden email] wrote:
>  
>
>>Hello Nathaniel,
>>
>>An jeu., févr 18, 2010, Nathaniel L Keeling schrieb:
>>  
>>    
>>
>>>I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
>>>compile successfully by adding the parameter "-mcpu=ultrasparc" to
>>>the "DEFS" compile time options in Makefile.defs, but when I
>>>execute opensips, it will die with a core dump. It does thru the
>>>loading of the modules ok but dies later.
>>>
>>>    
>>>      
>>>
>>Both Solaris 10 Sparc or Solaris 11 x86 do core dump when trying
>>to use OpenSIPS 1.6.1. Nobody has seem to be able to diagnose this
>>correctly much less repair the problem.
>>  
>>    
>>
>How comes ? I know people using 1.6 on sparc + Solaris  :P....
>  
>
>>If you try the same build parameters to compile 1.6.0 you will
>>probably find that it not only compiles correctly but runs without
>>core dumping as well. So much for the
>>
>>    'it is recommended to upgrade, as it provides important
>>     stability improvements'
>>
>>that they write about the 1.6.1 release on the website.
>>  
>>    
>>
>hmmm...if you see the compiling as stability, maybe you are right....
>
>Now, getting serious....the problem is that since SF trashed the
>compiled farm, we (or at least I) do not have any sparc / solaris
>platform were to test the makefile options or the code....
>
>Regards,
>Bogdan
>
>  
>

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Bogdan-Andrei Iancu
In reply to this post by opensipslist
Hi Brian,

Maybe you should consider reporting the crashing you are mentioning (if
they are so many as you say), so somebody could fix them - in this case
everybody will be happier , I guess.

If it crashes or not it depends a lot of what functionalities (modules)
you are using (nobody can claim he tested all the modules in all
possible combinations).

For example I'm running opensips.org SIP service with SVN trunk and I do
not get any core dumps...and it is an almost 3K lines config...

So, again, if you get crashes, please report them.

Regards,
Bogdan

PS: if the build is bogus (like in Nathaniel), the runtime will be
unstable also - OpenSIPS has a lot of asm code that really depends on
arch, so messing the build params may lead to bogus code.



[hidden email] wrote:

> Hello Bogdan,
>
> An ven., févr 19, 2010, Bogdan-Andrei Iancu schrieb:
>  
>> [hidden email] wrote:
>>    
>>> An jeu., févr 18, 2010, Nathaniel L Keeling schrieb:
>>>      
>>>> I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
>>>> compile successfully by adding the parameter "-mcpu=ultrasparc" to
>>>> the "DEFS" compile time options in Makefile.defs, but when I
>>>> execute opensips, it will die with a core dump. It does thru the
>>>> loading of the modules ok but dies later.
>>>>
>>>>        
>>> Both Solaris 10 Sparc or Solaris 11 x86 do core dump when trying
>>> to use OpenSIPS 1.6.1. Nobody has seem to be able to diagnose this
>>> correctly much less repair the problem.
>>>
>>>      
>> How comes ? I know people using 1.6 on sparc + Solaris  :P....
>>
>>    
> I don't know either, but I'm sure that some builds work better
> than others. This would particularly be the case if the problem
> code was in a certain module or component which some builds are
> missing. My build contains almost everything.
>
>  
>>> If you try the same build parameters to compile 1.6.0 you will
>>> probably find that it not only compiles correctly but runs without
>>> core dumping as well. So much for the
>>>
>>>     'it is recommended to upgrade, as it provides important
>>>      stability improvements'
>>>
>>> that they write about the 1.6.1 release on the website.
>>>
>>>      
>> hmmm... if you see the compiling as stability, maybe you are right....
>>
>>    
> The buildtime is not as problematic as the runtime, which only
> rarely coredumps on 1.6.0 but quite often on 1.6.1. I can get
> 1.6.0 to coredump as well by forcing OpenSIPS to try writing
> to TCP connections which don't exist. Being careful with 1.6.0
> then it is possible to get a few weeks worth of usage with no
> core dump, maybe more.
>
>  
>> Now, getting serious... the problem is that since SF trashed the
>> compiled farm, we (or at least I) do not have any sparc / solaris
>> platform were to test the makefile options or the code...
>>
>>    
> You can do a lot with a single good machine and Xen, but that
> is maybe food for another thread. It's sad indeed that no Solaris
> platforms are available for testing.
>
> Regards,
> Brian
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>  


--
Bogdan-Andrei Iancu
www.voice-system.ro


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Nathaniel L. Keeling III-2
Bogdan,

Please explain what I am doing wrong. From what I am understanding, I
should be able to issue the make command and everything should compile
ok, but when I do, I get errors and a unsuccessful compile. When I add
the option "-mcpu=ultrasparc" I get a successful compile. I have
included a text file of the output from the compile.

Nathaniel

Bogdan-Andrei Iancu wrote:

>Hi Brian,
>
>Maybe you should consider reporting the crashing you are mentioning (if
>they are so many as you say), so somebody could fix them - in this case
>everybody will be happier , I guess.
>
>If it crashes or not it depends a lot of what functionalities (modules)
>you are using (nobody can claim he tested all the modules in all
>possible combinations).
>
>For example I'm running opensips.org SIP service with SVN trunk and I do
>not get any core dumps...and it is an almost 3K lines config...
>
>So, again, if you get crashes, please report them.
>
>Regards,
>Bogdan
>
>PS: if the build is bogus (like in Nathaniel), the runtime will be
>unstable also - OpenSIPS has a lot of asm code that really depends on
>arch, so messing the build params may lead to bogus code.
>
>
>
>[hidden email] wrote:
>  
>
>>Hello Bogdan,
>>
>>An ven., févr 19, 2010, Bogdan-Andrei Iancu schrieb:
>>  
>>    
>>
>>>[hidden email] wrote:
>>>    
>>>      
>>>
>>>>An jeu., févr 18, 2010, Nathaniel L Keeling schrieb:
>>>>      
>>>>        
>>>>
>>>>>I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
>>>>>compile successfully by adding the parameter "-mcpu=ultrasparc" to
>>>>>the "DEFS" compile time options in Makefile.defs, but when I
>>>>>execute opensips, it will die with a core dump. It does thru the
>>>>>loading of the modules ok but dies later.
>>>>>
>>>>>        
>>>>>          
>>>>>
>>>>Both Solaris 10 Sparc or Solaris 11 x86 do core dump when trying
>>>>to use OpenSIPS 1.6.1. Nobody has seem to be able to diagnose this
>>>>correctly much less repair the problem.
>>>>
>>>>      
>>>>        
>>>>
>>>How comes ? I know people using 1.6 on sparc + Solaris  :P....
>>>
>>>    
>>>      
>>>
>>I don't know either, but I'm sure that some builds work better
>>than others. This would particularly be the case if the problem
>>code was in a certain module or component which some builds are
>>missing. My build contains almost everything.
>>
>>  
>>    
>>
>>>>If you try the same build parameters to compile 1.6.0 you will
>>>>probably find that it not only compiles correctly but runs without
>>>>core dumping as well. So much for the
>>>>
>>>>    'it is recommended to upgrade, as it provides important
>>>>     stability improvements'
>>>>
>>>>that they write about the 1.6.1 release on the website.
>>>>
>>>>      
>>>>        
>>>>
>>>hmmm... if you see the compiling as stability, maybe you are right....
>>>
>>>    
>>>      
>>>
>>The buildtime is not as problematic as the runtime, which only
>>rarely coredumps on 1.6.0 but quite often on 1.6.1. I can get
>>1.6.0 to coredump as well by forcing OpenSIPS to try writing
>>to TCP connections which don't exist. Being careful with 1.6.0
>>then it is possible to get a few weeks worth of usage with no
>>core dump, maybe more.
>>
>>  
>>    
>>
>>>Now, getting serious... the problem is that since SF trashed the
>>>compiled farm, we (or at least I) do not have any sparc / solaris
>>>platform were to test the makefile options or the code...
>>>
>>>    
>>>      
>>>
>>You can do a lot with a single good machine and Xen, but that
>>is maybe food for another thread. It's sad indeed that no Solaris
>>platforms are available for testing.
>>
>>Regards,
>>Brian
>>
>>_______________________________________________
>>Users mailing list
>>[hidden email]
>>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>  
>>    
>>
>
>
>  
>

# make prefix=/usr/local/opensips-1.6.1 all
Compiling blacklists.c
gcc  -g -O9 -funroll-loops   -Wall      -DNAME='"opensips"' -DVERSION='"1.6.1-notls"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILER='"gcc 3.4.6"' -D__CPU_sparc64 -D__OS_solaris -D__SMP_yes -DCFG_DIR='"/usr/local/opensips-1.6.1/etc/opensips/"' -DPKG_MALLOC -DSHM_MEM  -DSHM_MMAP -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DSTATISTICS -DCHANGEABLE_DEBUG_LEVEL -DF_MALLOC  -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALLOCA_H -DUSE_SIGACTION -D_POSIX_PTHREAD_SEMANTICS -DHAVE_DEVPOLL -DHAVE_SELECT -c blacklists.c -o blacklists.o
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 223: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 243: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 267: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 298: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 318: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 340: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 371: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 391: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 414: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 455: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 475: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 497: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 594: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 612: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 635: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 667: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 685: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 721: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 753: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 771: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 796: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 868: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 888: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 910: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 1426: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 1446: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 1469: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 1528: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 1548: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 1571: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 2047: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 2067: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 2092: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 2493: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 2513: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 2536: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 2863: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 2883: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 2906: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3521: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3539: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3563: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3595: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3613: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3650: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3682: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3700: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3725: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3755: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3775: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3797: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3879: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3897: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3922: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3954: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 3972: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 4009: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 4041: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 4059: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 4084: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 4452: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 4472: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 4495: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 4690: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 4727: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 4980: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 4998: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5026: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5060: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5078: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5109: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5176: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5196: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5220: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5683: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5701: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5730: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5764: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5782: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 5815: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 6784: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 6804: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 6829: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 6887: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 6907: error: cannot use v8plus instructions in a non-v8plus target binary
/usr/ccs/bin/as: "/var/tmp//ccJ6UlSy.s", line 6936: error: cannot use v8plus instructions in a non-v8plus target binary
make: *** [blacklists.o] Error 1

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Bogdan-Andrei Iancu
In reply to this post by Nathaniel L. Keeling III-2
Please run in shell "uname -p" and "uname -m" and post here the output.

Thanks and regards,
Bogdan

Nathaniel L Keeling III wrote:

> Bogdan,
>
> this is the error that I get when I do not add that option:
>
> gcc  -g -O9 -funroll-loops   -Wall      -DNAME='"opensips"'
> -DVERSION='"1.6.1-notls"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILE
> R='"gcc 3.4.6"' -D__CPU_sparc64 -D__OS_solaris -D__SMP_yes
> -DCFG_DIR='"/usr/local/opensips-1.6.1/etc/opensips/"' -DPKG_MALLOC -DSHM
> _MEM  -DSHM_MMAP -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE
> -DHAVE_RESOLV_RES -DSTATISTICS -DCHANGEABLE_DEBUG_LEVEL -DF_MALLO
> C  -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  
> -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALL
> OCA_H -DUSE_SIGACTION -D_POSIX_PTHREAD_SEMANTICS -DHAVE_DEVPOLL
> -DHAVE_SELECT -c blacklists.c -o blacklists.o
> */usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 223: error: cannot use
> v8plus instructions in a non-v8plus target binary
> /usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 243: error: cannot use
> v8plus instructions in a non-v8plus target binary*
>
> I get the same error when compiling opensips 1.5
>
>
> Thanks
>
> Nathaniel
>
> Bogdan-Andrei Iancu wrote:
>
>  
>> Hi Brian,
>>
>> [hidden email] wrote:
>>  
>>
>>    
>>> Hello Nathaniel,
>>>
>>> An jeu., févr 18, 2010, Nathaniel L Keeling schrieb:
>>>  
>>>    
>>>
>>>      
>>>> I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
>>>> compile successfully by adding the parameter "-mcpu=ultrasparc" to
>>>> the "DEFS" compile time options in Makefile.defs, but when I
>>>> execute opensips, it will die with a core dump. It does thru the
>>>> loading of the modules ok but dies later.
>>>>
>>>>    
>>>>      
>>>>
>>>>        
>>> Both Solaris 10 Sparc or Solaris 11 x86 do core dump when trying
>>> to use OpenSIPS 1.6.1. Nobody has seem to be able to diagnose this
>>> correctly much less repair the problem.
>>>  
>>>    
>>>
>>>      
>> How comes ? I know people using 1.6 on sparc + Solaris  :P....
>>  
>>
>>    
>>> If you try the same build parameters to compile 1.6.0 you will
>>> probably find that it not only compiles correctly but runs without
>>> core dumping as well. So much for the
>>>
>>>    'it is recommended to upgrade, as it provides important
>>>     stability improvements'
>>>
>>> that they write about the 1.6.1 release on the website.
>>>  
>>>    
>>>
>>>      
>> hmmm...if you see the compiling as stability, maybe you are right....
>>
>> Now, getting serious....the problem is that since SF trashed the
>> compiled farm, we (or at least I) do not have any sparc / solaris
>> platform were to test the makefile options or the code....
>>
>> Regards,
>> Bogdan
>>
>>  
>>
>>    
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>  


--
Bogdan-Andrei Iancu
www.voice-system.ro


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Nathaniel L. Keeling III-2
Here is the output from the commands:

# uname -p
sparc
# uname -m
sun4u
#

Thanks

Nathaniel

Bogdan-Andrei Iancu wrote:

>Please run in shell "uname -p" and "uname -m" and post here the output.
>
>Thanks and regards,
>Bogdan
>
>Nathaniel L Keeling III wrote:
>  
>
>>Bogdan,
>>
>>this is the error that I get when I do not add that option:
>>
>>gcc  -g -O9 -funroll-loops   -Wall      -DNAME='"opensips"'
>>-DVERSION='"1.6.1-notls"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILE
>>R='"gcc 3.4.6"' -D__CPU_sparc64 -D__OS_solaris -D__SMP_yes
>>-DCFG_DIR='"/usr/local/opensips-1.6.1/etc/opensips/"' -DPKG_MALLOC -DSHM
>>_MEM  -DSHM_MMAP -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE
>>-DHAVE_RESOLV_RES -DSTATISTICS -DCHANGEABLE_DEBUG_LEVEL -DF_MALLO
>>C  -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  
>>-DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALL
>>OCA_H -DUSE_SIGACTION -D_POSIX_PTHREAD_SEMANTICS -DHAVE_DEVPOLL
>>-DHAVE_SELECT -c blacklists.c -o blacklists.o
>>*/usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 223: error: cannot use
>>v8plus instructions in a non-v8plus target binary
>>/usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 243: error: cannot use
>>v8plus instructions in a non-v8plus target binary*
>>
>>I get the same error when compiling opensips 1.5
>>
>>
>>Thanks
>>
>>Nathaniel
>>
>>Bogdan-Andrei Iancu wrote:
>>
>>  
>>    
>>
>>>Hi Brian,
>>>
>>>[hidden email] wrote:
>>>
>>>
>>>    
>>>      
>>>
>>>>Hello Nathaniel,
>>>>
>>>>An jeu., févr 18, 2010, Nathaniel L Keeling schrieb:
>>>>
>>>>  
>>>>
>>>>      
>>>>        
>>>>
>>>>>I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
>>>>>compile successfully by adding the parameter "-mcpu=ultrasparc" to
>>>>>the "DEFS" compile time options in Makefile.defs, but when I
>>>>>execute opensips, it will die with a core dump. It does thru the
>>>>>loading of the modules ok but dies later.
>>>>>
>>>>>  
>>>>>    
>>>>>
>>>>>        
>>>>>          
>>>>>
>>>>Both Solaris 10 Sparc or Solaris 11 x86 do core dump when trying
>>>>to use OpenSIPS 1.6.1. Nobody has seem to be able to diagnose this
>>>>correctly much less repair the problem.
>>>>
>>>>  
>>>>
>>>>      
>>>>        
>>>>
>>>How comes ? I know people using 1.6 on sparc + Solaris  :P....
>>>
>>>
>>>    
>>>      
>>>
>>>>If you try the same build parameters to compile 1.6.0 you will
>>>>probably find that it not only compiles correctly but runs without
>>>>core dumping as well. So much for the
>>>>
>>>>   'it is recommended to upgrade, as it provides important
>>>>    stability improvements'
>>>>
>>>>that they write about the 1.6.1 release on the website.
>>>>
>>>>  
>>>>
>>>>      
>>>>        
>>>>
>>>hmmm...if you see the compiling as stability, maybe you are right....
>>>
>>>Now, getting serious....the problem is that since SF trashed the
>>>compiled farm, we (or at least I) do not have any sparc / solaris
>>>platform were to test the makefile options or the code....
>>>
>>>Regards,
>>>Bogdan
>>>
>>>
>>>
>>>    
>>>      
>>>
>>_______________________________________________
>>Users mailing list
>>[hidden email]
>>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>  
>>    
>>
>
>
>  
>

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Bogdan-Andrei Iancu
Hi Nathaniel,

Ah, interesting....first reports non-64 sparc, second does :P....

Please try to comment in Makefile.defs (around line 87) the block (whole
block):
# fix sparc -> sparc64
ifeq ($(ARCH),sparc)
    ifeq ($(shell uname -m),sun4u)
        ARCH := sparc64
    endif
    ifeq ($(shell uname -m),sun4v)
        ARCH := sparc64
    endif
endif

and recompile the whole stuff.

Thanks and regards,
Bogdan

Nathaniel L Keeling III wrote:

> Here is the output from the commands:
>
> # uname -p
> sparc
> # uname -m
> sun4u
> #
>
> Thanks
>
> Nathaniel
>
> Bogdan-Andrei Iancu wrote:
>
>  
>> Please run in shell "uname -p" and "uname -m" and post here the output.
>>
>> Thanks and regards,
>> Bogdan
>>
>> Nathaniel L Keeling III wrote:
>>  
>>
>>    
>>> Bogdan,
>>>
>>> this is the error that I get when I do not add that option:
>>>
>>> gcc  -g -O9 -funroll-loops   -Wall      -DNAME='"opensips"'
>>> -DVERSION='"1.6.1-notls"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILE
>>> R='"gcc 3.4.6"' -D__CPU_sparc64 -D__OS_solaris -D__SMP_yes
>>> -DCFG_DIR='"/usr/local/opensips-1.6.1/etc/opensips/"' -DPKG_MALLOC -DSHM
>>> _MEM  -DSHM_MMAP -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE
>>> -DHAVE_RESOLV_RES -DSTATISTICS -DCHANGEABLE_DEBUG_LEVEL -DF_MALLO
>>> C  -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  
>>> -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALL
>>> OCA_H -DUSE_SIGACTION -D_POSIX_PTHREAD_SEMANTICS -DHAVE_DEVPOLL
>>> -DHAVE_SELECT -c blacklists.c -o blacklists.o
>>> */usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 223: error: cannot use
>>> v8plus instructions in a non-v8plus target binary
>>> /usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 243: error: cannot use
>>> v8plus instructions in a non-v8plus target binary*
>>>
>>> I get the same error when compiling opensips 1.5
>>>
>>>
>>> Thanks
>>>
>>> Nathaniel
>>>
>>> Bogdan-Andrei Iancu wrote:
>>>
>>>  
>>>    
>>>
>>>      
>>>> Hi Brian,
>>>>
>>>> [hidden email] wrote:
>>>>
>>>>
>>>>    
>>>>      
>>>>
>>>>        
>>>>> Hello Nathaniel,
>>>>>
>>>>> An jeu., févr 18, 2010, Nathaniel L Keeling schrieb:
>>>>>
>>>>>  
>>>>>
>>>>>      
>>>>>        
>>>>>
>>>>>          
>>>>>> I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
>>>>>> compile successfully by adding the parameter "-mcpu=ultrasparc" to
>>>>>> the "DEFS" compile time options in Makefile.defs, but when I
>>>>>> execute opensips, it will die with a core dump. It does thru the
>>>>>> loading of the modules ok but dies later.
>>>>>>
>>>>>>  
>>>>>>    
>>>>>>
>>>>>>        
>>>>>>          
>>>>>>
>>>>>>            
>>>>> Both Solaris 10 Sparc or Solaris 11 x86 do core dump when trying
>>>>> to use OpenSIPS 1.6.1. Nobody has seem to be able to diagnose this
>>>>> correctly much less repair the problem.
>>>>>
>>>>>  
>>>>>
>>>>>      
>>>>>        
>>>>>
>>>>>          
>>>> How comes ? I know people using 1.6 on sparc + Solaris  :P....
>>>>
>>>>
>>>>    
>>>>      
>>>>
>>>>        
>>>>> If you try the same build parameters to compile 1.6.0 you will
>>>>> probably find that it not only compiles correctly but runs without
>>>>> core dumping as well. So much for the
>>>>>
>>>>>   'it is recommended to upgrade, as it provides important
>>>>>    stability improvements'
>>>>>
>>>>> that they write about the 1.6.1 release on the website.
>>>>>
>>>>>  
>>>>>
>>>>>      
>>>>>        
>>>>>
>>>>>          
>>>> hmmm...if you see the compiling as stability, maybe you are right....
>>>>
>>>> Now, getting serious....the problem is that since SF trashed the
>>>> compiled farm, we (or at least I) do not have any sparc / solaris
>>>> platform were to test the makefile options or the code....
>>>>
>>>> Regards,
>>>> Bogdan
>>>>
>>>>
>>>>
>>>>    
>>>>      
>>>>
>>>>        
>>> _______________________________________________
>>> Users mailing list
>>> [hidden email]
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>  
>>>    
>>>
>>>      
>>  
>>
>>    
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>  


--
Bogdan-Andrei Iancu
www.voice-system.ro


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Nathaniel L. Keeling III-2
Hello Bogdan,

Opensips compiled ok but when I executed opensips, the modules could not
be found. The modules were expected to be in the lib64 directory and not
the lib directory of opensips. I have included a sample of the output.
# make clean
# make prefix=/usr/local/opensips-1.6.1 all
# make prefix=/usr/local/opensips-1.6.1 install

# /usr/local/opensips-1.6.1/sbin/opensips
Feb 25 01:51:21 [6370] ERROR:core:yyparse: module 'signaling.so' not
found in '/usr/local/opensips-1.6.1/lib64/opensips/modules/'
Feb 25 01:51:21 [6370] CRITICAL:core:yyerror: parse error in config
file, line 78, column 13-14: failed to load module
Feb 25 01:51:21 [6370] DBG:core:yyparse: loading module
/usr/local/opensips-1.6.1/lib64/opensips/modules/
Feb 25 01:51:21 [6370] ERROR:core:sr_load_module: could not open module
</usr/local/opensips-1.6.1/lib64/opensips/modules/>: ld.so.1: opensips:
fatal: /usr/local/opensips-1.6.1/lib64/opensips/modules/: open failed:
No such file or directory
Feb 25 01:51:21 [6370] CRITICAL:core:yyerror: parse error in config
file, line 78, column 13-14: failed to load module
Feb 25 01:51:21 [6370] ERROR:core:yyparse: module 'sl.so' not found in
'/usr/local/opensips-1.6.1/lib64/opensips/modules/'
Feb 25 01:51:21 [6370] CRITICAL:core:yyerror: parse error in config
file, line 79, column 13-14: failed to load module
Feb 25 01:51:21 [6370] DBG:core:yyparse: loading module
/usr/local/opensips-1.6.1/lib64/opensips/modules/
Feb 25 01:51:21 [6370] ERROR:core:sr_load_module: could not open module
</usr/local/opensips-1.6.1/lib64/opensips/modules/>: ld.so.1: opensips:
fatal: /usr/local/opensips-1.6.1/lib64/opensips/modules/: open failed:
No such file or directory

Feb 25 01:42:20 [6368] CRITICAL:core:yyerror: parse error in config
file, line 81, column 13-14: failed to load module
Feb 25 01:42:20 [6368] ERROR:core:yyparse: module 'maxfwd.so' not found
in '/usr/local/opensips-1.6.1/lib64/opensips/modules/'
Feb 25 01:42:20 [6368] CRITICAL:core:yyerror: parse error in config
file, line 82, column 13-14: failed to load module
Feb 25 01:42:20 [6368] DBG:core:yyparse: loading module
/usr/local/opensips-1.6.1/lib64/opensips/modules/
Feb 25 01:42:20 [6368] ERROR:core:sr_load_module: could not open module
</usr/local/opensips-1.6.1/lib64/opensips/modules/>: ld.so.1: opensips:
fatal: /usr/local/opensips-1.6.1/lib64/opensips/modules/: open failed:
No such file or directory
Feb 25 01:42:20 [6368] CRITICAL:core:yyerror: parse error in config
file, line 82, column 13-14: failed to load module
Feb 25 01:42:20 [6368] ERROR:core:yyparse: module 'textops.so' not found
in '/usr/local/opensips-1.6.1/lib64/opensips/modules/'
Feb 25 01:42:20 [6368] CRITICAL:core:yyerror: parse error in config
file, line 83, column 13-14: failed to load module
Feb 25 01:42:20 [6368] DBG:core:yyparse: loading module
/usr/local/opensips-1.6.1/lib64/opensips/modules/
Feb 25 01:42:20 [6368] ERROR:core:sr_load_module: could not open module
</usr/local/opensips-1.6.1/lib64/opensips/modules/>: ld.so.1: opensips:
fatal: /usr/local/opensips-1.6.1/lib64/opensips/modules/: open failed:
No such file or directory


Thanks

Nathaniel

Bogdan-Andrei Iancu wrote:

>Hi Nathaniel,
>
>Ah, interesting....first reports non-64 sparc, second does :P....
>
>Please try to comment in Makefile.defs (around line 87) the block (whole
>block):
># fix sparc -> sparc64
>ifeq ($(ARCH),sparc)
>    ifeq ($(shell uname -m),sun4u)
>        ARCH := sparc64
>    endif
>    ifeq ($(shell uname -m),sun4v)
>        ARCH := sparc64
>    endif
>endif
>
>and recompile the whole stuff.
>
>Thanks and regards,
>Bogdan
>
>Nathaniel L Keeling III wrote:
>  
>
>>Here is the output from the commands:
>>
>># uname -p
>>sparc
>># uname -m
>>sun4u
>>#
>>
>>Thanks
>>
>>Nathaniel
>>
>>Bogdan-Andrei Iancu wrote:
>>
>>  
>>    
>>
>>>Please run in shell "uname -p" and "uname -m" and post here the output.
>>>
>>>Thanks and regards,
>>>Bogdan
>>>
>>>Nathaniel L Keeling III wrote:
>>>
>>>
>>>    
>>>      
>>>
>>>>Bogdan,
>>>>
>>>>this is the error that I get when I do not add that option:
>>>>
>>>>gcc  -g -O9 -funroll-loops   -Wall      -DNAME='"opensips"'
>>>>-DVERSION='"1.6.1-notls"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILE
>>>>R='"gcc 3.4.6"' -D__CPU_sparc64 -D__OS_solaris -D__SMP_yes
>>>>-DCFG_DIR='"/usr/local/opensips-1.6.1/etc/opensips/"' -DPKG_MALLOC -DSHM
>>>>_MEM  -DSHM_MMAP -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE
>>>>-DHAVE_RESOLV_RES -DSTATISTICS -DCHANGEABLE_DEBUG_LEVEL -DF_MALLO
>>>>C  -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  
>>>>-DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALL
>>>>OCA_H -DUSE_SIGACTION -D_POSIX_PTHREAD_SEMANTICS -DHAVE_DEVPOLL
>>>>-DHAVE_SELECT -c blacklists.c -o blacklists.o
>>>>*/usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 223: error: cannot use
>>>>v8plus instructions in a non-v8plus target binary
>>>>/usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 243: error: cannot use
>>>>v8plus instructions in a non-v8plus target binary*
>>>>
>>>>I get the same error when compiling opensips 1.5
>>>>
>>>>
>>>>Thanks
>>>>
>>>>Nathaniel
>>>>
>>>>Bogdan-Andrei Iancu wrote:
>>>>
>>>>
>>>>  
>>>>
>>>>      
>>>>        
>>>>
>>>>>Hi Brian,
>>>>>
>>>>>[hidden email] wrote:
>>>>>
>>>>>
>>>>>  
>>>>>    
>>>>>
>>>>>        
>>>>>          
>>>>>
>>>>>>Hello Nathaniel,
>>>>>>
>>>>>>An jeu., févr 18, 2010, Nathaniel L Keeling schrieb:
>>>>>>
>>>>>>  
>>>>>>
>>>>>>    
>>>>>>      
>>>>>>
>>>>>>          
>>>>>>            
>>>>>>
>>>>>>>I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
>>>>>>>compile successfully by adding the parameter "-mcpu=ultrasparc" to
>>>>>>>the "DEFS" compile time options in Makefile.defs, but when I
>>>>>>>execute opensips, it will die with a core dump. It does thru the
>>>>>>>loading of the modules ok but dies later.
>>>>>>>
>>>>>>>  
>>>>>>>    
>>>>>>>
>>>>>>>      
>>>>>>>        
>>>>>>>
>>>>>>>            
>>>>>>>              
>>>>>>>
>>>>>>Both Solaris 10 Sparc or Solaris 11 x86 do core dump when trying
>>>>>>to use OpenSIPS 1.6.1. Nobody has seem to be able to diagnose this
>>>>>>correctly much less repair the problem.
>>>>>>
>>>>>>  
>>>>>>
>>>>>>    
>>>>>>      
>>>>>>
>>>>>>          
>>>>>>            
>>>>>>
>>>>>How comes ? I know people using 1.6 on sparc + Solaris  :P....
>>>>>
>>>>>
>>>>>  
>>>>>    
>>>>>
>>>>>        
>>>>>          
>>>>>
>>>>>>If you try the same build parameters to compile 1.6.0 you will
>>>>>>probably find that it not only compiles correctly but runs without
>>>>>>core dumping as well. So much for the
>>>>>>
>>>>>>  'it is recommended to upgrade, as it provides important
>>>>>>   stability improvements'
>>>>>>
>>>>>>that they write about the 1.6.1 release on the website.
>>>>>>
>>>>>>  
>>>>>>
>>>>>>    
>>>>>>      
>>>>>>
>>>>>>          
>>>>>>            
>>>>>>
>>>>>hmmm...if you see the compiling as stability, maybe you are right....
>>>>>
>>>>>Now, getting serious....the problem is that since SF trashed the
>>>>>compiled farm, we (or at least I) do not have any sparc / solaris
>>>>>platform were to test the makefile options or the code....
>>>>>
>>>>>Regards,
>>>>>Bogdan
>>>>>
>>>>>
>>>>>
>>>>>  
>>>>>    
>>>>>
>>>>>        
>>>>>          
>>>>>
>>>>_______________________________________________
>>>>Users mailing list
>>>>[hidden email]
>>>>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>>
>>>>  
>>>>
>>>>      
>>>>        
>>>>
>>>
>>>
>>>    
>>>      
>>>
>>_______________________________________________
>>Users mailing list
>>[hidden email]
>>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>  
>>    
>>
>
>
>  
>

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Anca Vamanu-2
Hi Nathaniel,

The path were opensips will look for modules at startup is what you set
in you configuration file - parameter "mpath". So set this to the
correct value: mpath=/usr/local/opensips-1.6.1/lib/opensips/modules/ .

Regards,

--
Anca Vamanu
www.voice-system.ro




Nathaniel L Keeling III wrote:

> Hello Bogdan,
>
> Opensips compiled ok but when I executed opensips, the modules could not
> be found. The modules were expected to be in the lib64 directory and not
> the lib directory of opensips. I have included a sample of the output.
> # make clean
> # make prefix=/usr/local/opensips-1.6.1 all
> # make prefix=/usr/local/opensips-1.6.1 install
>
> # /usr/local/opensips-1.6.1/sbin/opensips
> Feb 25 01:51:21 [6370] ERROR:core:yyparse: module 'signaling.so' not
> found in '/usr/local/opensips-1.6.1/lib64/opensips/modules/'
> Feb 25 01:51:21 [6370] CRITICAL:core:yyerror: parse error in config
> file, line 78, column 13-14: failed to load module
> Feb 25 01:51:21 [6370] DBG:core:yyparse: loading module
> /usr/local/opensips-1.6.1/lib64/opensips/modules/
> Feb 25 01:51:21 [6370] ERROR:core:sr_load_module: could not open module
> </usr/local/opensips-1.6.1/lib64/opensips/modules/>: ld.so.1: opensips:
> fatal: /usr/local/opensips-1.6.1/lib64/opensips/modules/: open failed:
> No such file or directory
> Feb 25 01:51:21 [6370] CRITICAL:core:yyerror: parse error in config
> file, line 78, column 13-14: failed to load module
> Feb 25 01:51:21 [6370] ERROR:core:yyparse: module 'sl.so' not found in
> '/usr/local/opensips-1.6.1/lib64/opensips/modules/'
> Feb 25 01:51:21 [6370] CRITICAL:core:yyerror: parse error in config
> file, line 79, column 13-14: failed to load module
> Feb 25 01:51:21 [6370] DBG:core:yyparse: loading module
> /usr/local/opensips-1.6.1/lib64/opensips/modules/
> Feb 25 01:51:21 [6370] ERROR:core:sr_load_module: could not open module
> </usr/local/opensips-1.6.1/lib64/opensips/modules/>: ld.so.1: opensips:
> fatal: /usr/local/opensips-1.6.1/lib64/opensips/modules/: open failed:
> No such file or directory
>
> Feb 25 01:42:20 [6368] CRITICAL:core:yyerror: parse error in config
> file, line 81, column 13-14: failed to load module
> Feb 25 01:42:20 [6368] ERROR:core:yyparse: module 'maxfwd.so' not found
> in '/usr/local/opensips-1.6.1/lib64/opensips/modules/'
> Feb 25 01:42:20 [6368] CRITICAL:core:yyerror: parse error in config
> file, line 82, column 13-14: failed to load module
> Feb 25 01:42:20 [6368] DBG:core:yyparse: loading module
> /usr/local/opensips-1.6.1/lib64/opensips/modules/
> Feb 25 01:42:20 [6368] ERROR:core:sr_load_module: could not open module
> </usr/local/opensips-1.6.1/lib64/opensips/modules/>: ld.so.1: opensips:
> fatal: /usr/local/opensips-1.6.1/lib64/opensips/modules/: open failed:
> No such file or directory
> Feb 25 01:42:20 [6368] CRITICAL:core:yyerror: parse error in config
> file, line 82, column 13-14: failed to load module
> Feb 25 01:42:20 [6368] ERROR:core:yyparse: module 'textops.so' not found
> in '/usr/local/opensips-1.6.1/lib64/opensips/modules/'
> Feb 25 01:42:20 [6368] CRITICAL:core:yyerror: parse error in config
> file, line 83, column 13-14: failed to load module
> Feb 25 01:42:20 [6368] DBG:core:yyparse: loading module
> /usr/local/opensips-1.6.1/lib64/opensips/modules/
> Feb 25 01:42:20 [6368] ERROR:core:sr_load_module: could not open module
> </usr/local/opensips-1.6.1/lib64/opensips/modules/>: ld.so.1: opensips:
> fatal: /usr/local/opensips-1.6.1/lib64/opensips/modules/: open failed:
> No such file or directory
>
>
> Thanks
>
> Nathaniel
>
> Bogdan-Andrei Iancu wrote:
>
>  
>> Hi Nathaniel,
>>
>> Ah, interesting....first reports non-64 sparc, second does :P....
>>
>> Please try to comment in Makefile.defs (around line 87) the block (whole
>> block):
>> # fix sparc -> sparc64
>> ifeq ($(ARCH),sparc)
>>    ifeq ($(shell uname -m),sun4u)
>>        ARCH := sparc64
>>    endif
>>    ifeq ($(shell uname -m),sun4v)
>>        ARCH := sparc64
>>    endif
>> endif
>>
>> and recompile the whole stuff.
>>
>> Thanks and regards,
>> Bogdan
>>
>> Nathaniel L Keeling III wrote:
>>  
>>
>>    
>>> Here is the output from the commands:
>>>
>>> # uname -p
>>> sparc
>>> # uname -m
>>> sun4u
>>> #
>>>
>>> Thanks
>>>
>>> Nathaniel
>>>
>>> Bogdan-Andrei Iancu wrote:
>>>
>>>  
>>>    
>>>
>>>      
>>>> Please run in shell "uname -p" and "uname -m" and post here the output.
>>>>
>>>> Thanks and regards,
>>>> Bogdan
>>>>
>>>> Nathaniel L Keeling III wrote:
>>>>
>>>>
>>>>    
>>>>      
>>>>
>>>>        
>>>>> Bogdan,
>>>>>
>>>>> this is the error that I get when I do not add that option:
>>>>>
>>>>> gcc  -g -O9 -funroll-loops   -Wall      -DNAME='"opensips"'
>>>>> -DVERSION='"1.6.1-notls"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILE
>>>>> R='"gcc 3.4.6"' -D__CPU_sparc64 -D__OS_solaris -D__SMP_yes
>>>>> -DCFG_DIR='"/usr/local/opensips-1.6.1/etc/opensips/"' -DPKG_MALLOC -DSHM
>>>>> _MEM  -DSHM_MMAP -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE
>>>>> -DHAVE_RESOLV_RES -DSTATISTICS -DCHANGEABLE_DEBUG_LEVEL -DF_MALLO
>>>>> C  -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  
>>>>> -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALL
>>>>> OCA_H -DUSE_SIGACTION -D_POSIX_PTHREAD_SEMANTICS -DHAVE_DEVPOLL
>>>>> -DHAVE_SELECT -c blacklists.c -o blacklists.o
>>>>> */usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 223: error: cannot use
>>>>> v8plus instructions in a non-v8plus target binary
>>>>> /usr/ccs/bin/as: "/var/tmp//ccww7Koi.s", line 243: error: cannot use
>>>>> v8plus instructions in a non-v8plus target binary*
>>>>>
>>>>> I get the same error when compiling opensips 1.5
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>> Nathaniel
>>>>>
>>>>> Bogdan-Andrei Iancu wrote:
>>>>>
>>>>>
>>>>>  
>>>>>
>>>>>      
>>>>>        
>>>>>
>>>>>          
>>>>>> Hi Brian,
>>>>>>
>>>>>> [hidden email] wrote:
>>>>>>
>>>>>>
>>>>>>  
>>>>>>    
>>>>>>
>>>>>>        
>>>>>>          
>>>>>>
>>>>>>            
>>>>>>> Hello Nathaniel,
>>>>>>>
>>>>>>> An jeu., févr 18, 2010, Nathaniel L Keeling schrieb:
>>>>>>>
>>>>>>>  
>>>>>>>
>>>>>>>    
>>>>>>>      
>>>>>>>
>>>>>>>          
>>>>>>>            
>>>>>>>
>>>>>>>              
>>>>>>>> I have compiled opensips 1.6.1 on Solaris Sparc 10. I was able to
>>>>>>>> compile successfully by adding the parameter "-mcpu=ultrasparc" to
>>>>>>>> the "DEFS" compile time options in Makefile.defs, but when I
>>>>>>>> execute opensips, it will die with a core dump. It does thru the
>>>>>>>> loading of the modules ok but dies later.
>>>>>>>>
>>>>>>>>  
>>>>>>>>    
>>>>>>>>
>>>>>>>>      
>>>>>>>>        
>>>>>>>>
>>>>>>>>            
>>>>>>>>              
>>>>>>>>
>>>>>>>>                
>>>>>>> Both Solaris 10 Sparc or Solaris 11 x86 do core dump when trying
>>>>>>> to use OpenSIPS 1.6.1. Nobody has seem to be able to diagnose this
>>>>>>> correctly much less repair the problem.
>>>>>>>
>>>>>>>  
>>>>>>>
>>>>>>>    
>>>>>>>      
>>>>>>>
>>>>>>>          
>>>>>>>            
>>>>>>>
>>>>>>>              
>>>>>> How comes ? I know people using 1.6 on sparc + Solaris  :P....
>>>>>>
>>>>>>
>>>>>>  
>>>>>>    
>>>>>>
>>>>>>        
>>>>>>          
>>>>>>
>>>>>>            
>>>>>>> If you try the same build parameters to compile 1.6.0 you will
>>>>>>> probably find that it not only compiles correctly but runs without
>>>>>>> core dumping as well. So much for the
>>>>>>>
>>>>>>>  'it is recommended to upgrade, as it provides important
>>>>>>>   stability improvements'
>>>>>>>
>>>>>>> that they write about the 1.6.1 release on the website.
>>>>>>>
>>>>>>>  
>>>>>>>
>>>>>>>    
>>>>>>>      
>>>>>>>
>>>>>>>          
>>>>>>>            
>>>>>>>
>>>>>>>              
>>>>>> hmmm...if you see the compiling as stability, maybe you are right....
>>>>>>
>>>>>> Now, getting serious....the problem is that since SF trashed the
>>>>>> compiled farm, we (or at least I) do not have any sparc / solaris
>>>>>> platform were to test the makefile options or the code....
>>>>>>
>>>>>> Regards,
>>>>>> Bogdan
>>>>>>
>>>>>>
>>>>>>
>>>>>>  
>>>>>>    
>>>>>>
>>>>>>        
>>>>>>          
>>>>>>
>>>>>>            
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> [hidden email]
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>>>
>>>>>  
>>>>>
>>>>>      
>>>>>        
>>>>>
>>>>>          
>>>>    
>>>>      
>>>>
>>>>        
>>> _______________________________________________
>>> Users mailing list
>>> [hidden email]
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>  
>>>    
>>>
>>>      
>>  
>>
>>    
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>  

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

opensipslist
In reply to this post by Bogdan-Andrei Iancu

Hello Bogdan,

An lun., févr 22, 2010, Bogdan-Andrei Iancu schrieb:
>Maybe you should consider reporting the crashing you are mentioning
>(if they are so many as you say), so somebody could fix them - in
>this case everybody will be happier , I guess.
>
Here's a backtrace of the OpenSIPS 1.6.1 sometime after REGISTER
request comes in:

# gdb /pfx/sbin/opensips opensips.16452.name.host.tld.core
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-pc-solaris2.11"...
(no debugging symbols found)
...
Loaded symbols for /lib/ld.so.1

Core was generated by `/pfx/sbin/opensips -P /pfx/var/opensips/opensips.pid -m 64'.
Program terminated with signal 11, Segmentation fault.
[New process 83290    ]
#0  0x0810d931 in qm_malloc ()
(gdb) bt
#0  0x0810d931 in qm_malloc ()
#1  0x0835b5a8 in mem_pool ()
#2  0x0835bf9c in mem_pool ()
#3  0x08046670 in ?? ()
#4  0xd0d55fd0 in ?? () from /pfx/lib/opensips/modules/auth_aaa.so
#5  0x0835d9b8 in mem_pool ()
#6  0x08313240 in ?? ()
#7  0x08046658 in ?? ()
#8  0xd0d51bb9 in authorize (_msg=0x20, _realm=<value optimized out>,
    _uri_user=<value optimized out>, _hftype=0) at authorize.c:126
#9  0x00000000 in ?? ()
(gdb)

>If it crashes or not it depends a lot of what functionalities
>(modules) you are using (nobody can claim he tested all the modules
>in all possible combinations).
>
Seems to me that the crash from the core dump above relates to flaws
in the AAA authorization logic. Here's the last message in the sip
trace before the crash (not sure if it's representative.)

125:1267207762:3c2d04c4da9c-95w1oc5r17eu::SIP/2.0 401 Unauthorized
Via: SIP/2.0/TLS 192.168.130.35:2291;branch=z9hG4bK-kv7jq7chf8p1;rport=2291;received=1.2.3.4
From: "My Name" <sip:[hidden email]>;tag=xlrkkswd5y
To: "My Name" <sip:[hidden email]>;tag=d170206e0ec14c1ccd1967a0f5e85cb9.9210
Call-ID: 3c2d04c4da9c-95w1oc5r17eu
CSeq: 515 REGISTER
WWW-Authenticate: Digest realm="name.host.tld", nonce="4b880e705d5b5fafcb33b4df08f7689d6850ac25", qop="auth"
Server: OpenSIPS (1.6.1-tls (i386/solaris))
Content-Length: 0
Warning: 392 name.host.tld:5061 "Noisy feedback tells:  pid=17754 req_src_ip=1.2.3.4 req_src_port=2291 in_uri=sip:name.host.tld out_uri=sip:name.host.tld via_cnt==1"

Here are the last few lines from the log before hundreds of memory
debug lines appear (because I have memory debugging on.)

<warning> opensips[12744]: WARNING:core:init_tls: disabling compression due ZLIB problems
<warning> opensips[12744]: WARNING:core:init_ssl_ctx_behavior: client verification activated. Client certificates are mandatory.
<warning> opensips[12744]: WARNING:core:init_ssl_ctx_behavior: server verification activated.
<critical> opensips[12756]: CRITICAL:core:receive_fd: EOF on 20
<warning> opensips[12748]: Memory status (pkg):
<warning> opensips[12748]: qm_status (8313260):

If you like I can send more of the memory debug log lines, but
please tell me just what to send (so I can avoid sending hundreds
of lines of log text.)

>For example I'm running opensips.org SIP service with SVN trunk
>and I do not get any core dumps... and it is an almost 3K lines
>config...
>
Building OpenSIPS 1.6.0 with the same radiusclient-ng installation
(which is up to date) results in a more stable runtime. It's usually
good for several days before crashing.

>So, again, if you get crashes, please report them.
>
Okay, but I've noticed that some crashes do not produce core dumps.

>PS: if the build is bogus (like in Nathaniel), the runtime will be
>unstable also - OpenSIPS has a lot of asm code that really depends on
>arch, so messing the build params may lead to bogus code.
>
My build is correct.

Regards,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

opensipslist
In reply to this post by Bogdan-Andrei Iancu

Hello Bogdan,

An sam., févr 27, 2010, [hidden email] schrieb:
>An lun., févr 22, 2010, Bogdan-Andrei Iancu schrieb:
>>Maybe you should consider reporting the crashing you are mentioning
>>(if they are so many as you say), so somebody could fix them - in
>>this case everybody will be happier , I guess.
>>
>Here's a backtrace of the OpenSIPS 1.6.0 sometime after INVITE
>request comes in:
>
# gdb /pfx/sbin/opensips opensips.1234.name.host.tld.core
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i386-pc-solaris2.11"...
(no debugging symbols found)
Reading symbols from /lib/ld.so.1...done.
Loaded symbols for /lib/ld.so.1

Core was generated by `/pfx/sbin/opensips -P
/pfx/var/opensips/opensips.pid -m 64'.
Program terminated with signal 6, Aborted.
[New process 67527    ]
#0  0xd11d1d75 in _lwp_kill () from /lib/libc.so.1
(gdb) bt
#0  0xd11d1d75 in _lwp_kill () from /lib/libc.so.1
#1  0xd11cb73d in thr_kill () from /lib/libc.so.1
#2  0xd1185722 in raise () from /lib/libc.so.1
#3  0xd1162c7d in abort () from /lib/libc.so.1
#4  0x0808c900 in ?? ()
#5  0x0000001a in ?? ()
#6  0x0826115c in ?? ()
#7  0x082629ac in ?? ()
#8  0xd1268ac0 in _uberdata () from /lib/libc.so.1
#9  0x00000000 in ?? ()
(gdb)

>If it crashes or not it depends a lot of what functionalities
>(modules) you are using (nobody can claim he tested all the modules
>in all possible combinations).
>
This time I don't see where the crash could have happened, maybe
the in the OpenSIPS 1.6.0 core? Here's the last message in the
sip trace before the crash (not sure if it's representative.)

INVITE:477:tls:1.2.3.4:5061:tls:4.3.2.1:1234:ck1b40kwzn:out
7070:1267304859:3c2e8013a0e7-x8fz99gffcy0::SIP/2.0 477 Send failed (477/TM)
Via: SIP/2.0/TLS 192.168.130.130:1234;branch=z9hG4bK-cuia8rmsu1z3;rport=1234;received=4.3.2.1
From: "User-Me" <sip:[hidden email]>;tag=ck1b40kwzn
To: <sip:+[hidden email];user=phone>;tag=c3f9bc8b6c0d893b80d355b0f89fbe37-0bbd
Call-ID: 3c2e8013a0e7-x8fz99gffcy0
CSeq: 1 INVITE
Server: OpenSIPS (1.6.0-tls (i386/solaris))
Content-Length: 0
Warning: 392 name.host.tld:5061 "Noisy feedback tells:  pid=2000 req_src_ip=4.3.2.1 req_src_port=1234 in_uri=sip:+[hidden email];user=phone out_uri=sips:[hidden email] via_cnt==1"

Here are the last few lines from the log before hundreds of memory
debug lines appear (because I have memory debugging on.)

Feb 27 21:44:25 name.host.tld <warning> opensips[3996]: INVITE: Noncancelled fail route [408]
Feb 27 21:44:25 name.host.tld <error> opensips[3996]: ERROR:core:warning_builder: buffer size exceeded
Feb 27 21:44:25 name.host.tld <warning> opensips[3996]: WARNING:core:build_res_buf_from_sip_req: warning skipped -- too big
Feb 27 22:07:39 name.host.tld <critical> opensips[4001]: CRITICAL:core:receive_fd: EOF on 20
Feb 27 22:07:39 name.host.tld <warning> opensips[3994]: Memory status (pkg):
Feb 27 22:07:39 name.host.tld <warning> opensips[3994]: qm_status (8311c20):

If you like I can send more of the memory debug log lines, but
please tell me just what to send (so I can avoid sending hundreds
of lines of log text.)

>For example I'm running opensips.org SIP service with SVN trunk
>and I do not get any core dumps... and it is an almost 3K lines
>config...
>
This time OpenSIPS crashed after only one day, which is unusual for
the 1.6.0 release which usually lasts longer.

>So, again, if you get crashes, please report them.
>
Okay, I'll keep doing that.

Regards,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Bogdan-Andrei Iancu
In reply to this post by opensipslist
Hi Brian,

the backtrace is completely bogus - probably the stack is corrupted
after some illegal mem ops.

Please send me privately the complete logs .

Also, can you reproduce this crash ?

Thanks and regards,
Bogdan

[hidden email] wrote:

> Hello Bogdan,
>
> An lun., févr 22, 2010, Bogdan-Andrei Iancu schrieb:
>  
>> Maybe you should consider reporting the crashing you are mentioning
>> (if they are so many as you say), so somebody could fix them - in
>> this case everybody will be happier , I guess.
>>
>>    
> Here's a backtrace of the OpenSIPS 1.6.1 sometime after REGISTER
> request comes in:
>
> # gdb /pfx/sbin/opensips opensips.16452.name.host.tld.core
> GNU gdb 6.8
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i386-pc-solaris2.11"...
> (no debugging symbols found)
> ...
> Loaded symbols for /lib/ld.so.1
>
> Core was generated by `/pfx/sbin/opensips -P /pfx/var/opensips/opensips.pid -m 64'.
> Program terminated with signal 11, Segmentation fault.
> [New process 83290    ]
> #0  0x0810d931 in qm_malloc ()
> (gdb) bt
> #0  0x0810d931 in qm_malloc ()
> #1  0x0835b5a8 in mem_pool ()
> #2  0x0835bf9c in mem_pool ()
> #3  0x08046670 in ?? ()
> #4  0xd0d55fd0 in ?? () from /pfx/lib/opensips/modules/auth_aaa.so
> #5  0x0835d9b8 in mem_pool ()
> #6  0x08313240 in ?? ()
> #7  0x08046658 in ?? ()
> #8  0xd0d51bb9 in authorize (_msg=0x20, _realm=<value optimized out>,
>     _uri_user=<value optimized out>, _hftype=0) at authorize.c:126
> #9  0x00000000 in ?? ()
> (gdb)
>
>  
>> If it crashes or not it depends a lot of what functionalities
>> (modules) you are using (nobody can claim he tested all the modules
>> in all possible combinations).
>>
>>    
> Seems to me that the crash from the core dump above relates to flaws
> in the AAA authorization logic. Here's the last message in the sip
> trace before the crash (not sure if it's representative.)
>
> 125:1267207762:3c2d04c4da9c-95w1oc5r17eu::SIP/2.0 401 Unauthorized
> Via: SIP/2.0/TLS 192.168.130.35:2291;branch=z9hG4bK-kv7jq7chf8p1;rport=2291;received=1.2.3.4
> From: "My Name" <sip:[hidden email]>;tag=xlrkkswd5y
> To: "My Name" <sip:[hidden email]>;tag=d170206e0ec14c1ccd1967a0f5e85cb9.9210
> Call-ID: 3c2d04c4da9c-95w1oc5r17eu
> CSeq: 515 REGISTER
> WWW-Authenticate: Digest realm="name.host.tld", nonce="4b880e705d5b5fafcb33b4df08f7689d6850ac25", qop="auth"
> Server: OpenSIPS (1.6.1-tls (i386/solaris))
> Content-Length: 0
> Warning: 392 name.host.tld:5061 "Noisy feedback tells:  pid=17754 req_src_ip=1.2.3.4 req_src_port=2291 in_uri=sip:name.host.tld out_uri=sip:name.host.tld via_cnt==1"
>
> Here are the last few lines from the log before hundreds of memory
> debug lines appear (because I have memory debugging on.)
>
> <warning> opensips[12744]: WARNING:core:init_tls: disabling compression due ZLIB problems
> <warning> opensips[12744]: WARNING:core:init_ssl_ctx_behavior: client verification activated. Client certificates are mandatory.
> <warning> opensips[12744]: WARNING:core:init_ssl_ctx_behavior: server verification activated.
> <critical> opensips[12756]: CRITICAL:core:receive_fd: EOF on 20
> <warning> opensips[12748]: Memory status (pkg):
> <warning> opensips[12748]: qm_status (8313260):
>
> If you like I can send more of the memory debug log lines, but
> please tell me just what to send (so I can avoid sending hundreds
> of lines of log text.)
>
>  
>> For example I'm running opensips.org SIP service with SVN trunk
>> and I do not get any core dumps... and it is an almost 3K lines
>> config...
>>
>>    
> Building OpenSIPS 1.6.0 with the same radiusclient-ng installation
> (which is up to date) results in a more stable runtime. It's usually
> good for several days before crashing.
>
>  
>> So, again, if you get crashes, please report them.
>>
>>    
> Okay, but I've noticed that some crashes do not produce core dumps.
>
>  
>> PS: if the build is bogus (like in Nathaniel), the runtime will be
>> unstable also - OpenSIPS has a lot of asm code that really depends on
>> arch, so messing the build params may lead to bogus code.
>>
>>    
> My build is correct.
>
> Regards,
> Brian
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>  


--
Bogdan-Andrei Iancu
www.voice-system.ro


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Core Dump

Bogdan-Andrei Iancu
In reply to this post by opensipslist
Hi Brian,

[hidden email] wrote:

> Here are the last few lines from the log before hundreds of memory
> debug lines appear (because I have memory debugging on.)
>
> Feb 27 21:44:25 name.host.tld <warning> opensips[3996]: INVITE: Noncancelled fail route [408]
> Feb 27 21:44:25 name.host.tld <error> opensips[3996]: ERROR:core:warning_builder: buffer size exceeded
> Feb 27 21:44:25 name.host.tld <warning> opensips[3996]: WARNING:core:build_res_buf_from_sip_req: warning skipped -- too big
> Feb 27 22:07:39 name.host.tld <critical> opensips[4001]: CRITICAL:core:receive_fd: EOF on 20
> Feb 27 22:07:39 name.host.tld <warning> opensips[3994]: Memory status (pkg):
> Feb 27 22:07:39 name.host.tld <warning> opensips[3994]: qm_status (8311c20):
>
> If you like I can send more of the memory debug log lines, but
> please tell me just what to send (so I can avoid sending hundreds
> of lines of log text.)
>  
If you could send me the full log (privately) it may help to find a hint.

Thanks and regards,
Bogdan


--
Bogdan-Andrei Iancu
www.voice-system.ro


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users