[ previous ] [ next ] [ threads ]
 
 From:  "Burkhart, John T." <JOHN dot T dot BURKHART at saic dot com>
 To:  "Burkhart, John T." <JOHN dot T dot BURKHART at saic dot com>, "'m0n0wall dash dev at lists dot m0n0 dot ch'" <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  RE: RE: [m0n0wall-dev] Unstable mini_httpd for captive portal
 Date:  Tue, 14 Jun 2005 17:14:18 -0700
-----Original Message-----
From: Burkhart, John T. 
Sent: Tuesday, June 14, 2005 5:09 PM
To: 'm0n0wall dash dev at lists dot m0n0 dot ch'
Subject: RE: [m0n0wall-dev] Unstable mini_httpd for captive portal

 

More follow-up...

 

Port 8000 had pid 120 - log file is truss.8000.log

Port 8001 had pid 123 - log file is truss.8001.log

 

There are two truss logs enclosed.

 

Noticed that at the end of the truss.8001.log there was a reference to
/usr/share/zoneinfo stuff and no files found.

 

Here is an ls 

$ ls -al /usr/share
total 144
drwxr-xr-x  2 root  wheel    512 May  8 08:03 .
drwxr-xr-x  8 root  wheel    512 Apr 23 23:04 ..
-rw-r--r--  1 root  wheel  70673 May  8 07:09 zoneinfo.tgz

I saw in section 17 of the manual that this is default behavior for space
reasons...

 

 

Then I found this entry in the archives
http://s1.m0n0.ch/wall/list/?action=show_msg
<http://s1.m0n0.ch/wall/list/?action=show_msg&actionargs%5B%5D=102&actionarg
s%5B%5D=79> &actionargs%5B%5D=102&actionargs%5B%5D=79 <<there was (at one
time) a problem with maxproc and under certain situations a failure would
occur when using SSL.>>

 

 

If there is some other troubleshooting or data you require let me know.  I'd
like to know what situations caused the failure (cited in the url above)...
I'd like to see if I could replicate the condition or something similar.  So
far I have not been able to cause the failure...I just have to wait for it
to happen...madness.

 

John