Please copy the list.
Strange, could you please post all the information about what you have done, your hardware configuration, your config, and the error trace to serdev? g-)
Barton Fisher wrote:
Same results. I tried to compile after removing DSHM_MMAP from Makefile.defs - no luck there either That was only change I made after hello world test
Bart
Greger V. Teigre wrote:
Hm, try a minimum (hello world) ser.cfg to see if you get the same error. PTR is not required. I assume you have not done any makefile changes. g-)
Barton Fisher wrote:
Greger V. Teigre wrote:
What is confusing? The message is pretty clear. But maybe the reason is unknown? What kind of system is this? Hardware? How much memory, etc etc? g-)
Barton Fisher wrote:
A bit confused by startup message:
0(16102) ERROR: shm_mem_init: could not attach shared memory segment: No space left on device 0(16102) could not initialize shared memory pool, exiting... Too much shared memory demanded: 33554432
I found prior message to upgrade Kernel to 2.4 - currently I'm on 2.6.8-022stab076.1-enterprise At another place it said to recompile ser with SYSV shm instead of mmap (remove -DSHM_MMAP from Makefile.defs) <= This I'm not sure exactly how / what to change in Makefile.def. And yet another regarding no PTR <= I've contracted ISP regarding this, but was hoping to bypass - I was hoping there was some temporary fix for this until they act?
I'm running SER 0.9.6
Thanks for any assistance.
Bart
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I have never seen PC, but here's what I know about it: Processors = 4 Model = Intel(R) XEON(TM) CPU 1.80GHz Speed = 1.8GHz Kernel Version = 2.6.8-022stab076.1-enterprise (SMP) Distro Name = CentOS release 4.4 (Final) Physical Memory = 3.89G Me thinks issue is there is no PTR record as I see something like this before it errors out:
... lots of junk ahead of this.... 0(13373) if ( 0(13373) NOT( 0(13373) OR( 0(13373) uri 0(13373) =~ 0(13373) "1 83" 0(13373) , 0(13373) uri 0(13373) =~ 0(13373) "200" 0(13373) ) 0(13373) ) 0(13373) ) { 0(13373) drop( 0(13373) type<0> 0(13373) ); 0(13373) } else { 0(13 373) }; 0(13373) external_module_call( 0(13373) f_ptr<0x40573860> 0(13373) , " FA" 0(13373) ); 0(13373) external_module_call( 0(13373) f_ptr<0x40573860> 0(13 373) , "FA" 0(13373) ); 0(13373)
If it is PTR record checking, can I disable this checking? Bart
__________ NOD32 2096 (20070305) Information __________
This message was checked by NOD32 antivirus system. http://www.eset.com
-
Greger V. Teigre