panic during work with jailed postgresql8.4
oleg.lomaka at gmail.com
Fri Apr 2 12:16:09 UTC 2010
On Apr 2, 2010, at 3:02 PM, Bjoern A. Zeeb wrote:
> On Thu, 1 Apr 2010, Oleg Lomaka wrote:
>> I have a kernel panic when connect to postgresql8.4 server installed in one of jails from another jail. It's 100% reproducible.
>> Also I have tried to connect from host machine to jailed pg server. That way it works fine without crash.
>> Server configuration uses geli and zfs. Four disks encrypted using geli. And raidz2 is using ad8.eli, ad10.eli, ad12.eli, ad14.eli providers. All jails located at this raidz2 pool.
>> Also I use ezjail for jails management. And it uses NFS to mount directories with base system.
>> atal double fault
>> rip = 0xffffffff8063510a
>> rsp = 0xffffff80eaec5f50
>> rbp = 0xffffff80eaec6040
>> cpuid = 1; apic id = 02
>> panic: double fault
>> cpuid = 1
>> Uptime: 7m11s
>> Physical memory: 8169 MB
>> uname -a
>> FreeBSD cerberus.regredi.com 8.0-STABLE FreeBSD 8.0-STABLE #7 r206031: Thu Apr 1 13:43:57 EEST 2010 root at cerberus.regredi.com:/usr/obj/usr/src/sys/GENERIC amd64
>> Link to dmesg.boot:
>> Link to kernel core backtrace:
>> Can I help to spot this trouble by providing additional info?
> Looking at the info I doubt it's related to jails or Pg in first
> place. Have you been running that same setup already before your Apr
> 1st, r206031, kernel? If so, from when was your last kernel?
Yes, this configuration works on another server fine (8.0-STABLE FreeBSD 8.0-STABLE #3 r205202)
Made few more tests. All tests I make using psql command (as it is 100% reproducible, may be now try spot it using telnet/netcat, without involving pg). psql accomplish login operation fine, panic appears after i run any command like \d, so I think it depends on packet size.
Current picture is:
1. When connect from host machine - works fine.
2. When I connect from other server - works fine.
3. When connect from another jail on the same box as db's jail (tried from few jails) - kernel fault.
Also tried security.jail.allow_raw_sockets on/off - nothing changes.
More information about the freebsd-stable