On Thu, May 10, 2012 at 08:19:58PM -0300, Rafael Zalamena wrote: > While I was configuring a new ALIX to my MPLS setup a panic ocurred > while starting LDPd daemon. > > Steps: > 1. Configure all interfaces using /etc/hostname.*, then run 'sh > /etc/netstart' > 2. Configure ospfd.conf, then start it: ospfd -dv & > 3. Configure ldpd.conf, then start it: ldpd -dv > 4. Panic > > I'll send the ospfd.conf and ldpd.conf next mail. I'm using OpenBSD > 5.1-release on all 3 ALIX now, it happened while I was setting up the > last ALIX connected to the other two. > > p.s. note the scrambled print output of LDPd before dying. >
> Panic log > === > # ldpd -dv > startup > kernel add routeuvm_fault(0xd54e5bf4, 0x0, 0, 1) -> e > 0.0.0.0/0 > kernkel add route 10.e0.3.0/24 > kernelr add route 10.0.n4.0/24 > kernel aedd route 10.0.10l.3/32 > kernel ad:d route 192.168. 3.0/24 > page fault trap, code=0 > Stopped at ifaof_ifpforaddr+0x26: movl 0x14(%edx),%edx > ddb> trace > ifaof_ifpforaddr(d11884d8,0,0,d03e6afd,d09e1220) at ifaof_ifpforaddr+0x26 > ifa_ifwithroute(140003,d11884d8,d11884e8,0,d09e1220) at ifa_ifwithroute+0x61 > rt_getifa(d8c9acfc,0,d1188a0c,2,0) at rt_getifa+0xe2 > rtrequest1(1,d8c9acfc,8,d8c9ad54,0) at rtrequest1+0x5f7 > route_output(d54ebb00,d5358008,d54ebb00,0,0) at route_output+0xe29 > route_usrreq(d5358008,9,d54ebb00,0,0) at route_usrreq+0x65 > sosend(d5358008,0,d8c9aec0,d54ebb00,0) at sosend+0x456 > soo_write(d54d2370,d54d238c,d8c9aec0,d54f23c0,d54e44c8) at soo_write+0x3b > dofilewritev(d54df680,4,d54d2370,cfbf3f40,3) at dofilewritev+0x131 > sys_writev(d54df680,d8c9af64,d8c9af84,d0576b0a,d54df680) at sys_writev+0x7c > syscall() at syscall+0x26a > --- syscall (number 0) --- > 0x2: > ddb> The ifp passed to ifaof_ifpforaddr() is NULL. How that can happen is unclear to me, it seems like the found ifa is not valid anymore. Is this crash easy to trigger? Can I get you're hostname.* files, ospfd.conf and ldpd.conf for all three boxes? -- :wq Claudio
