Hello list,
I'm new to this place, and actually new to the world of SIP and VoIP, but I'm starting to like it after I've seen what it can do.
I tried to install ser myself on my machine running NetBSD 2.0 on the amd64 architecture.
Starting from scratch, I tried to install the current releases, but they fail mostly on modules. So I deciced to give CVS a try.
After compiling, I ended up with a sip_router dir, and it compiled ok from what I could see. It had a few warnings but I figured that it couldn't hurt much.
The main configfile didn't leave much to change, so I set debug on and fork off, and started off:
bash-2.05b# ./ser Listening on udp: 10.0.0.30 [10.0.0.30]:5060 udp: 130.89.169.133 [130.89.169.133]:5060 udp: 127.0.0.1 [127.0.0.1]:5060 tcp: 10.0.0.30 [10.0.0.30]:5060 tcp: 130.89.169.133 [130.89.169.133]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 Aliases: tcp: localhost.:5060 tcp: localhost:5060 tcp: ascwin.student.utwente.nl:5060 tcp: mobiel30.crib:5060 udp: localhost.:5060 udp: localhost:5060 udp: ascwin.student.utwente.nl:5060 udp: mobiel30.crib:5060
WARNING: no fork mode and more than one listen address found(will use only the the first one) stateless - initializing textops - initializing ERROR: error -478 while trying to fix configuration
In the /var/log/messages, it shows:
Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 55, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 54, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 53, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 52, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 51, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 50, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 49, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 48, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 47, 0700) failed: No space left on device
This is the case running as both root and as user.
Any tips/directions? I googled around for the error and couldn't find anything matching.
Thanks in advance!
Wouter Schoot
Hello again list,
Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 48, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 47, 0700) failed: No space left on device
Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/wd0a 969 87 833 9% / /dev/wd0f 1939 4 1837 0% /var /dev/wd0e 77556 1600 72078 2% /usr /dev/wd0g 83160 17 78985 0% /home /dev/wd0h 19388 0 18419 0% /shells kernfs 0 0 0 100% /kern procfs 0 0 0 100% /proc kernfs 0 0 0 100% /kern
Forgot to mention, that the disc really isn't full yet :)
Wouter
Do you have these options compiled into your kernel?
options SYSVMSG # System V-like message queues options SYSVSEM # System V-like semaphores #options SEMMNI=10 # number of semaphore identifiers #options SEMMNS=60 # number of semaphores in system #options SEMUME=10 # max number of undo entries per process #options SEMMNU=30 # number of undo structures in system options SYSVSHM # System V-like memory sharing #options SHMMAXPGS=2048 # 2048 pages is the default
What's the output of ipcs?
-- Xten Networks Inc. www.xten.com
-----Original Message-----
From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Wouter
Schoot
Sent: December 10, 2004 7:29 AM To: serusers@lists.iptel.org Subject: [Serusers] Ser (CVS) on NetBSD 2.0/amd64
Hello list,
I'm new to this place, and actually new to the world of
SIP
and VoIP, but I'm starting to like it after I've seen what
it can do.
I tried to install ser myself on my machine running NetBSD
2.0 on the
amd64 architecture.
Starting from scratch, I tried to install the current releases, but they fail mostly on modules. So I deciced to
give CVS a try.
After compiling, I ended up with a sip_router dir, and it compiled ok from what I could see. It had a few warnings
but
I figured that it couldn't hurt much.
The main configfile didn't leave much to change, so I set debug on and fork off, and started off:
bash-2.05b# ./ser Listening on udp: 10.0.0.30 [10.0.0.30]:5060 udp: 130.89.169.133 [130.89.169.133]:5060 udp: 127.0.0.1 [127.0.0.1]:5060 tcp: 10.0.0.30 [10.0.0.30]:5060 tcp: 130.89.169.133 [130.89.169.133]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 Aliases: tcp: localhost.:5060 tcp: localhost:5060 tcp: ascwin.student.utwente.nl:5060 tcp: mobiel30.crib:5060 udp: localhost.:5060 udp: localhost:5060 udp: ascwin.student.utwente.nl:5060 udp: mobiel30.crib:5060
WARNING: no fork mode and more than one listen address found(will use only the the first one) stateless - initializing textops - initializing ERROR: error -478 while trying to fix configuration
In the /var/log/messages, it shows:
Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 55, 0700) failed: No space left on device Dec
10
16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 54, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 53, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 52, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 51, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 50, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 49, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 48, 0700) failed: No space left on device Dec 10 16:16:36 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 47, 0700) failed: No space left on device
This is the case running as both root and as user.
Any tips/directions? I googled around for the error and couldn't find anything matching.
Thanks in advance!
Wouter Schoot
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Gregory McGarry wrote:
options SYSVMSG # System V-like message options SYSVSEM # System V-like semaphores options SYSVSHM # System V-like memory
Yup, got 'em all three (They are in GENERIC..)
What's the output of ipcs?
[ascent@ascent /home/ascent]$ ipcs Message Queues: T ID KEY MODE OWNER GROUP
Shared Memory: T ID KEY MODE OWNER GROUP m 65536 5432001 --rw------- pgsql pgsql
Semaphores: T ID KEY MODE OWNER GROUP s 65536 5432001 --rw------- pgsql pgsql s 65537 5432002 --rw------- pgsql pgsql s 65538 5432003 --rw------- pgsql pgsql
Wouter
Hi list,
Tried today's CVS again:
Dec 14 09:12:14 ascent ser: WARNING: fix_socket_list: could not rev. resolve 10.0.0.1 Dec 14 09:12:14 ascent ser: WARNING: fix_socket_list: could not rev. resolve 10.0.0.1 Dec 14 09:12:14 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 16, 0700) failed: No space left on device Dec 14 09:12:14 ascent ser: ERROR: lock_set_init (SYSV): semget (..., 15, 0700) failed: No space left on device Dec 14 09:12:14 ascent ser: ERROR: mod_init: initializing hash_table failed Dec 14 09:12:14 ascent ser: init_mod(): Error while initializing module tm Dec 14 09:12:14 ascent ser: BUG: qm_free: freeing already freed pointer, first free: h_table.c: free_hash_table(309) - aborting
That dumps a core too, don't know if anyone's interested?
Wouter
-
Gregory McGarry -
Wouter Schoot