Thanks, I should've caught that...
/tmp/truss -o /tmp/truss.log -p 2739 &
ps auxww showed 2739 as /usr/local/sbin/mini_httpd -S -a -M 0 -E
/var/etc/cert-portal.pem -u root -maxproc 16 -p 8001 -i
/var/run/mini_httpd.cps.pid
This happened after pid 2739 died...after the process died a new one
appeared....pid 3106.
$ cat /tmp/truss.log
(null)() = 1 (0x1)
accept(0x4,{ AF_INET 192.168.1.254:1389 },0xbfbff804) = 6 (0x6)
fork() = 2942 (0xb7e)
close(6) = 0 (0x0)
SIGNAL 20
SIGNAL 20
SIGNAL 20
select(0x5,0xbfbff890,0x0,0x0,0x0) ERR#4 'Interrupted system
call'
sigaction(SIGCHLD,0xbfbff5cc,0xbfbff5b4) = 0 (0x0)
wait4(0xffffffff,0xbfbff610,0x1,0x0) = 2942 (0xb7e)
wait4(0xffffffff,0xbfbff610,0x1,0x0) ERR#10 'No child processes'
sigreturn(0xbfbff630) ERR#4 'Interrupted system
call'
select(0x5,0xbfbff890,0x0,0x0,0x0) = 1 (0x1)
accept(0x4,{ AF_INET 192.168.1.254:1391 },0xbfbff804) = 6 (0x6)
fork() = 2951 (0xb87)
close(6) = 0 (0x0)
select(0x5,0xbfbff890,0x0,0x0,0x0) = 1 (0x1)
accept(0x4,{ AF_INET 192.168.1.254:1392 },0xbfbff804) = 6 (0x6)
fork() = 2952 (0xb88)
close(6) = 0 (0x0)
SIGNAL 20
SIGNAL 20
SIGNAL 20
select(0x5,0xbfbff890,0x0,0x0,0x0) ERR#4 'Interrupted system
call'
sigaction(SIGCHLD,0xbfbff5cc,0xbfbff5b4) = 0 (0x0)
wait4(0xffffffff,0xbfbff610,0x1,0x0) = 2952 (0xb88)
wait4(0xffffffff,0xbfbff610,0x1,0x0) = 0 (0x0)
sigreturn(0xbfbff630) ERR#4 'Interrupted system
call'
SIGNAL 20
SIGNAL 20
SIGNAL 20
select(0x5,0xbfbff890,0x0,0x0,0x0) ERR#4 'Interrupted system
call'
sigaction(SIGCHLD,0xbfbff5cc,0xbfbff5b4) = 0 (0x0)
wait4(0xffffffff,0xbfbff610,0x1,0x0) = 2951 (0xb87)
wait4(0xffffffff,0xbfbff610,0x1,0x0) ERR#10 'No child processes'
sigreturn(0xbfbff630) ERR#4 'Interrupted system
call'
select(0x5,0xbfbff890,0x0,0x0,0x0) = 1 (0x1)
accept(0x4,{ AF_INET 192.168.1.254:1393 },0xbfbff804) = 6 (0x6)
fork() = 2961 (0xb91)
close(6) = 0 (0x0)
SIGNAL 20
SIGNAL 20
SIGNAL 20
select(0x5,0xbfbff890,0x0,0x0,0x0) ERR#4 'Interrupted system
call'
sigaction(SIGCHLD,0xbfbff5cc,0xbfbff5b4) = 0 (0x0)
wait4(0xffffffff,0xbfbff610,0x1,0x0) = 2961 (0xb91)
wait4(0xffffffff,0xbfbff610,0x1,0x0) ERR#10 'No child processes'
sigreturn(0xbfbff630) ERR#4 'Interrupted system
call'
SIGNAL 15
SIGNAL 15
SIGNAL 15
select(0x5,0xbfbff890,0x0,0x0,0x0) ERR#4 'Interrupted system
call'
close(3) = 0 (0x0)
exit(0x1) process exit, rval = 256
-----Original Message-----
From: Jonathan De Graeve
To: Burkhart, John T.
Cc: m0n0wall dash dev at lists dot m0n0 dot ch
Sent: 6/9/2005 1:26 PM
Subject: Re: [m0n0wall-dev] Unstable mini_httpd for captive portal
Upload some version of truss compiled for FreeBSD 4.x (e.g.
http://m0n0.ch/wall/downloads/truss) through exec.php, mark it as
executable and run it on the PID of the captive portal mini_httpd
process (i.e. /path/to/truss -o /tmp/truss.log -p <mini_httpd-pid> &).
Another thing to try would be to kill the captive portal mini_httpd,
upload the mini_httpd that comes with 1.2b3 (pull it out of
rootfs-1.2b3, usr/local/bin/mini_httpd), rename the existing
mini_httpd to something else, copy the uploaded mini_httpd to the
original location (/usr/local/bin/mini_httpd), make sure it's marked
as executable, and hit "save" on the captive portal page to make it
start again.
--
Jonathan De Graeve
System/Network Administrator
Imelda vzw
Informatica Dienst
015/50.52.98
jonathan dot de dot graeve at imelda dot be
----- Original Message -----
From: "Burkhart, John T." <JOHN dot T dot BURKHART at saic dot com>
To: <mk at neon1 dot net>
Cc: <m0n0wall dash dev at lists dot m0n0 dot ch>; <jonathan dot de dot graeve at imelda dot be>
Sent: Thursday, June 09, 2005 10:16 PM
Subject: RE: [m0n0wall-dev] Unstable mini_httpd for captive portal
>
>
>
> -----Original Message-----
> From: Burkhart, John T.
> To: 'mk at neon1 dot net '
> Cc: 'm0n0wall dash dev at lists dot m0n0 dot ch '; 'jonathan dot de dot graeve at imelda dot be '
> Sent: 6/9/2005 1:11 PM
> Subject: RE: [m0n0wall-dev] Unstable mini_httpd for captive portal
>
> Sorry but there is not a truss binary available on the cd iso
rendering
> and there appears to be no error checking for this.
>
> So, I took a look at the processes running on the system (notes and
> outputs are enclosed). <speculation> I suspect that the system is
> getting confused because of port 8000 still being on? </speculation>
> Also, I have not seen this behavior in the HTTP login mode.
>
> The only other speculation I have is that this may be happening after
an
> authentication TIMEOUT. I may be way off base and will go down that
> path if I need to.
>
> Do you have truss hidden in a directory somewhere or a renamed binary?
>
> Respectfully,
> John
>
>
>
>
>
|
