Re: InitDB: Bad system call

Hello,

>> ... The simplest explanation
>> I can think of is that it's *only* shmctl that is malfunctioning, not
>> the other SysV shared memory calls. Which is even weirder, and
>> definitely seems to move the problem into the category of kernel bug
>> rather than configuration mistake.
>
> Hmmm ... Google turned up the information that FreeBSD migrated from int
> to size_t variables for shared memory size between 7.0 and 8.0, and in
> particular that the size of the struct used by shmctl() changed in
> 8.0. So I'm now wondering if what you're dealing with is some sort of
> version skew problem. Could it be that you built Postgres against
> system header files that don't match your kernel version? I'm not
> exactly sure how that would manifest as this particular signal,
> but it seems worth checking.

I have the correct header files, but that brings me to an interesting
notice and a workaround.

Before i had build the new jail, i checked out the newest sources for
FreeBSD 7.0 and recompile the world. With the new "world" i build the
jail and the problems occurs.
Meanwhile there are two running jails with postgresql in at the same
server. And IPC-problems seems unfamiliar to me, because the
error-messages normally looks very different and other instances running
without problems;)

What i've done now, was disableing an old jail and copy it to an new
location. After some reconfiguration i use the copy as new jail and
install postgresql. And it works.

That fortify your assumption, that the problem must lie in FreeBSD. But
this will be hard to debug, because the last "make world" was 3 years
ago of the machine. I will discribe the problem to the FreeBSD-Community.

Thanks for all your help and time,
Torsten