On Mon, Oct 12, 2015 at 08:02:11AM +0300, Liviu Daia wrote:
>
> I get something similar without nagios:
>
> $ grep syscall /var/log/messages
> Oct 10 07:50:26 router /bsd: tty(2446): syscall 54
> Oct 10 07:50:33 router /bsd: tty(29826): syscall 54
> Oct 10 07:54:15 router /bsd: tty(10733):
On 12.10.2015 09:41, Sebastien Marie wrote:
On Mon, Oct 12, 2015 at 08:02:11AM +0300, Liviu Daia wrote:
I get something similar without nagios:
$ grep syscall /var/log/messages
Oct 10 07:50:26 router /bsd: tty(2446): syscall 54
Oct 10 07:50:33 router /bsd: tty(29826): syscall 54
Oct 10
On 12 October 2015, Sebastien Marie wrote:
> On Mon, Oct 12, 2015 at 08:02:11AM +0300, Liviu Daia wrote:
> >
> > I get something similar without nagios:
> >
> > $ grep syscall /var/log/messages
> > Oct 10 07:50:26 router /bsd: tty(2446): syscall 54
> > Oct 10 07:50:33
Hi,
I got *who(X): syscall 54* in the last few snapshots.
If you need more info just ask.
~$ ktrace -i who
~$ kdump
16759 who RET read 2819/0xb03
16759 who CALL close(4)
16759 who RET close 0
16759 who CALL kbind
On Sun, Oct 11, 2015 at 11:53:10AM +0300, Atanas Vladimirov wrote:
> Hi,
> I got *who(XXXXX): syscall 54* in the last few snapshots.
> If you need more info just ask.
syscall 54 is for ioctl syscall.
> ~$ ktrace -i who
> ~$ kdump
> ...
On 11.10.2015 18:54, Sebastien Marie wrote:
On Sun, Oct 11, 2015 at 11:53:10AM +0300, Atanas Vladimirov wrote:
Hi,
I got *who(X): syscall 54* in the last few snapshots.
If you need more info just ask.
syscall 54 is for ioctl syscall.
~$ ktrace -i who
~$ kdump
> I rebuild who(1) with DEBUG and add 'abort' in all pledge calls.
> Also I changed kern.nosuidcoredump=3 and made /var/crash/who but I can't
> find who.core.
> Meanwhile I got syscall 54 every 5 min. Is it possible another
> process/daemon to generate this errors?
> How can I find it?
>
> ~$
On 11.10.2015 21:18, Theo de Raadt wrote:
I rebuild who(1) with DEBUG and add 'abort' in all pledge calls.
Also I changed kern.nosuidcoredump=3 and made /var/crash/who but I
can't
find who.core.
Meanwhile I got syscall 54 every 5 min. Is it possible another
process/daemon to generate this
Atanas Vladimirov wrote:
I think that I found it - Nagios. Now the question is how to debug it further?
lsof?
--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.well.com/~jax # thinking, a way of skeptically interrogating the universe
www.softwoehr.com # with a
On Mon, Oct 12, 2015 at 12:44:08AM +0300, Atanas Vladimirov wrote:
> On 11.10.2015 21:18, Theo de Raadt wrote:
> >>I rebuild who(1) with DEBUG and add 'abort' in all pledge calls.
> >>Also I changed kern.nosuidcoredump=3 and made /var/crash/who but I can't
> >>find who.core.
> >>Meanwhile I got
On 12 October 2015, Atanas Vladimirov wrote:
> On 11.10.2015 21:18, Theo de Raadt wrote:
> >> I rebuild who(1) with DEBUG and add 'abort' in all pledge calls.
> >> Also I changed kern.nosuidcoredump=3 and made /var/crash/who but I
> >> can't
> >> find who.core.
> >> Meanwhile I
11 matches
Mail list logo