Displaying 3 results from an estimated 3 matches for "norwell".
Did you mean:
orwell
2013 May 01
1
Latest winbind creating fault
All,
Yesterday morning, I updated samba from samba3-3.6.13-45 to
samba3-3.6.14-45 (obtained from sernet) on a couple of
CentOS 5.9 boxes. As soon as users started access these
boxes, one of my sensors detected a winbind error, as in:
Apr 30 08:19:36 norwell winbindd[13283]: ? INTERNAL ERROR:
Signal 11 in pid 13283 (3.6.14)
Here's what appears in syslog:
Apr 30 08:19:36 norwell winbindd[8938]: [2013/04/30
08:19:36.667710, 0] lib/fault.c:47(fault_report)
Apr 30 08:19:36 norwell winbindd[8938]:
===============================================...
2006 Jul 13
3
Winbind dies
...'re good again. However, as
this is a very active server that is accessed 18 hours a day, 7 days
a week, I'm called at home during those few hours I spend there to
restart winbind on this particular machine.
Here's the relevant syslog output (sorry for the length):
Jul 12 18:26:06 norwell winbindd[23775]: [2006/07/12 18:26:06, 0]
lib/fault.c:fault_report(41)
Jul 12 18:26:06 norwell winbindd[23775]:
===============================================================
Jul 12 18:26:06 norwell winbindd[23775]: [2006/07/12 18:26:06, 0]
lib/fault.c:fault_report(42)
Jul 12 18:26:06 norwell...
2006 Jul 14
0
Re: (Samba) Winbind dies
...ing those few hours I spend
> > there to restart winbind on this particular machine.
>
> The is the second report of winbindd crash in the krb5 libs.
> The other was an FC5 box.
>
> > INTERNAL ERROR: Signal 6 in pid 23775 (3.0.23)
>
> ...
>
> > Jul 12 18:26:06 norwell winbindd[23775]: ? BACKTRACE: 28 stack
> > frames: #0 winbindd(log_stack_trace+0x2d) [0x5f5add]
> > #1 ?winbindd(smb_panic+0x75) [0x5f5985]
> > #2 winbindd [0x5e10d6]
> > #3 /lib/tls/libc.so.6 [0x1b70d8]
> > #4 /lib/tls/libc.so.6 (abort+0x1d5) [0x1b8705]
> > #5 w...