INN version for me...

[Przemysław Maciuszko]

On Wed, Jun 30, 2004 at 08:23:45PM +0200, Przemysław Maciuszko wrote:

> Ok. We'll see in just few minutes...

Innbind is working fine on Solaris now.
However - something is still broken with shared memory.

When starting INN I did get the following in news.notice:

Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 0 semap 0
addr -e40000 size 32768
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 1 semap 1
addr -e50000 size 32768
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 2 semap 2
addr -f90000 size 32768
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 3 semap 3
addr -fa0000 size 32768
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 4 semap 4
addr -fb0000 size 32768
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 5 semap 5
addr -1090000 size 32768
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 6 semap 6
addr -10a0000 size 32768
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 7 semap 7
addr -10b0000 size 32768
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 8 semap 8
addr -10c0000 size 32768
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 9 semap 9
addr -10d0000 size 32768
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 10 semap
10 addr -10e0000 size 32768
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] created shmid 11 semap
11 addr -10f0000 size 32768

Jun 30 22:41:01 inews innd: [ID 349736 news.warning] SERVER descriptors 4096
Jun 30 22:41:01 inews innd: [ID 355441 news.warning] SERVER outgoing 4083
Jun 30 22:41:01 inews innd: [ID 213933 news.warning] SERVER ccsetup
control:24
Jun 30 22:41:01 inews innd: [ID 213933 news.warning] SERVER ccsetup
control:24
Jun 30 22:41:01 inews innd: [ID 432620 news.warning] SERVER lcsetup
localconn:26
Jun 30 22:41:01 inews innd: [ID 702911 news.notice] SERVER rcsetup
remconn:29
Jun 30 22:41:08 inews innd: [ID 907491 news.warning] innfeed! spawned
innfeed!:31:proc:16994
Jun 30 22:41:08 inews innfeed[16994]: [ID 702911 news.notice] ME starting
innfeed 2.5.0 (20040630 prerelease) at Wed Jun 30 22:4
1:08 2004

Then after few seconds when readers started to connect i get the errors in
news.notice:

Jun 30 22:41:28 inews nnrpd[17091]: [ID 801593 news.warning] semop failed to
getSharedLock: No space left on device
Jun 30 22:41:28 inews nnrpd[17091]: [ID 801593 news.warning] semop failed to
release shared lock: Resource temporarily unavailab
le
Jun 30 22:41:28 inews nnrpd[17091]: [ID 801593 news.warning] semop failed to
getSharedLock: No space left on device
Jun 30 22:41:28 inews nnrpd[17091]: [ID 801593 news.warning] semop failed to
release shared lock: Resource temporarily unavailab
le


And so on.

I've got following settings in my /etc/system:

set maxpgio=1024
set noexec_user_stack=1
set noexec_user_stack_log=1
set rlim_fd_cur=4096
set rlim_fd_max=20480
set shmsys:shminfo_shmmax=3221225472
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmni=100
set semsys:seminfo_semmsl=1000
set semsys:seminfo_semmns=2000
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767

set autoup=10
set tune_t_fsflushr=2


Any ideas? It's broken for few months as for now :(


-- 
Przemysław Maciuszko
Agora SA