AB-Solution - The Ad Blocking Solution

[thelonelycoder]

@MarioCaires you can also enter this right after reboot:

netstat -tuln | grep :80

Without ps running, this is a standard return:

user@RT-AC1900P:/tmp/home/root# netstat -tuln | grep :80
tcp        0      0 127.0.0.1:80            0.0.0.0:*               LISTEN
tcp        0      0 172.20.0.1:80           0.0.0.0:*               LISTEN

This is with ps running:

user@RT-AC1900P:/tmp/home/root# netstat -tuln | grep :80
tcp        0      0 172.20.0.254:80          0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:80            0.0.0.0:*               LISTEN
tcp        0      0 172.20.0.1:80          0.0.0.0:*               LISTEN

172.20.0.254 is that router's ps IP.

 

[MarioCaires]

The wan-start looks the same before run AB...

#!/bin/sh

# DO NOT EDIT this part of the file #
# generated by AB-Solution 3.8
psState=on
if [ $psState == "on" ];then
    ifconfig br0:pixelserv 192.168.1.10 up
    logger "AB-Solution created br0:pixelserv 192.168.1.10 via $0"
fi
# end of DO NOT EDIT #

When running "netstat -tuln | grep :80" I get the expected behaviour return (ps not running):

ac87@RT-AC87U-ED60:/tmp/home/root# netstat -tuln | grep :80
tcp        0      0 127.0.0.1:80            0.0.0.0:*               LISTEN
tcp        0      0 192.168.1.1:80          0.0.0.0:*               LISTEN

When you say there is a service running on port 80, you mean on the router level or device level, or any?

EDIT: Further checking the log, I found this:

kernel: EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended

Not sure if is normal...

 

[thelonelycoder]

kernel: EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended

Then do the check on the WebUI start page by clicking on the device icon.

I have another suspicion, the WAN might take some time to come up. Until then, wan-start is not run and therefore the virtual ps IP is not up for ps to use.
In the meantime, all the other scripts run, including the Entware start scripts that start ps.

Let me think about what can be tweaked to overcome this.

 

[thelonelycoder]

@MarioCaires You have indeed a WAN up problem, I just tested it and get the same error message:

Jul 20 17:23:56 pixelserv[1065]: Abort: Cannot assign requested address - :172.20.0.254:80

How long does it take for your WAN to be up?
On this router, WAN is up at 23 Seconds:

Aug  1 02:00:23 WAN(0)_Connection: WAN was restored.

A second or two later, the mounting of the USB devices starts and then at 35 seconds post-mount runs, starting ps through Entware:

Aug  1 02:00:35 custom_script: Running /jffs/scripts/post-mount (args: /tmp/mnt/entware)

The ps start is aborted later, after the correct time is set at Jul 20 17:23:56.

 

[MarioCaires]

On mine it takes 45 seconds...

 

[thelonelycoder]

On mine it takes 45 seconds...

That's a long time.
Try this, bearing in mind that this file is replaced any time you make changes in the ps menu.

Modify your /opt/etc/init.d/S80pixelserv-tls like this, the part above the DO NOT EDIT warning is new, do not change below that.
Change PS_IP= to your ps IP, while the WAIT_TIMEOUT= is in seconds, this loop runs that long until giving up.
When rebooting the router, you will see these entries in the Syslog, giving you an idea how high to set the timeout:
pixelserv-tls IP is not up, waiting 1 second until timeout in 8 second

#!/bin/sh

WAIT_TIMEOUT=15
PS_IP=172.20.0.254

while [ $WAIT_TIMEOUT -ne 0 ];do

   ping -c 1 -W 1 "$PS_IP" >/dev/null
   rc=$?

   if [ $rc -eq 0 ];then
       WAIT_TIMEOUT=0
   else
       WAIT_TIMEOUT=$(($WAIT_TIMEOUT - 1))
       logger "pixelserv-tls IP is not up, waiting 1 second until timeout in $WAIT_TIMEOUT seconds"
       sleep 1
   fi

done

# DO NOT EDIT this part of the file #
# generated by AB-Solution 3.9
export TZ=$(cat /etc/TZ)
ENABLED=yes
PROCS=pixelserv-tls
ARGS="172.20.0.254 "
PREARGS=""
PRECMD="ulimit -s 64"
DESC="$PROCS (AB-Solution)"
PATH=/opt/sbin:/opt/bin:/opt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
. /opt/etc/init.d/rc.func
# end of DO NOT EDIT #

 

[MarioCaires]

Adding your code to the file, ps started successfully at 39 seconds and the WAN at 44.

Regarding the usb drive error, when I run the scan utility it says the drive is being used, how can I terminate the processes in the drive and run the scan?

Thank you @thelonelycoder for your patience and help!

 

[thelonelycoder]

Adding your code to the file, ps started successfully at 39 seconds and the WAN at 44.

Regarding the usb drive error, when I run the scan utility it says the drive is being used, how can I terminate the processes in the drive and run the scan?

Thank you @thelonelycoder for your patience and help!

Beside AB, you have more scripts running on your router.

The only way to successfully do that would be to rename the /jffs/scripts/ folder, to, say scripts_not so you have /jffs/scripts_not/

Then reboot the router.
No scripts will start this time and you can do the device scan.
Once done successfully, un-mount the device in the UI, remove it, rename the /jffs/scripts_not/ back to /jffs/scripts/ and then plug your device back in (all while the router still runs).
AB and all the other scripts will start again.

 

[MarioCaires]

The scan result was this...

SanDisk: Adding dirhash hint to filesystem.

SanDisk was not cleanly unmounted, check forced.
SanDisk: The bad block inode looks invalid.  

SanDisk: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    (i.e., without -a or -p options)

Not a good signal I suppose...

 

[thelonelycoder]

The scan result was this...

SanDisk: Adding dirhash hint to filesystem.

SanDisk was not cleanly unmounted, check forced.
SanDisk: The bad block inode looks invalid. 

SanDisk: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    (i.e., without -a or -p options)

Not a good signal I suppose...

Nothing is lost, just run the fsck, the drive needs to be unmounted to do this.

 

[MarioCaires]

Oh well, I have reformatted the drive and after a few reboots, the warning is showing again in the log! Think will just leave as it is and see how it goes...

Regarding pixelserv, I have set the timeout to 6 seconds and looks like it can still be reduced to around 4, however to avoid issues will leave at 6!
Thank you once again @thelonelycoder!

 

[thelonelycoder]

Oh well, I have reformatted the drive and after a few reboots, the warning is showing again in the log! Think will just leave as it is and see how it goes...

Regarding pixelserv, I have set the timeout to 6 seconds and looks like it can still be reduced to around 4, however to avoid issues will leave at 6!
Thank you once again @thelonelycoder!

The timeout is just a maximum tries until it runs the rest of the file anyway.
And of course it stops looping as soon as the IP is available. So best leave it at a reasonable 10 seconds.
I might actually add this by default into the ps start script.
If the WAN is up, it runs through it with practically no delay, if not, it serves a good purpose.

 

[thelonelycoder]

@MarioCaires I care (caires)!
S80pixelserv-tls will now include the delay loop by default in the upcoming release.
It is a stripped down version of the code posted above.
The timeout is a hardcoded 15 secs, but is jumped over immediately when the ps IP is up.

 

[|ZeuS|]

Hello, lonelycoder and whoever person in the future happens to read this post because they encountered the same problem with pixelserv installation in their ab-solution.
Here is a short description of the issue:
I am on an ASUS RT N66U router running Merlin 380.67 and the ab-solution 3.8.1

Since Merlin 380.67 beta2 or so I have the problem of not being able to install successfully the pixelserv. I kept postponing the troubleshooting due to lazyness but today I did try to figure out what is going on, and at the moment I am at a loss.
When I say cannot successfully install the pixelserv I mean that at some point I reach the

-------------------------------------------
Starting pixelserv-tls (AB-Solution)... done.
checking if 192.168.1.2 responds
192.168.1.2 responded, continuing
--------------------------------------------

part of the installation and then the entire process comes to a halt for some time (significant time... like say 10 minutes) and after that pause I am presented with the AB-S menu and the message
--------------------------------------------
Error: pixelserv-tls is not running.
Check System Log in router WebUI for clues
--------------------------------------------

So first I will dumb here a bunch of the output from my putty console and then I will briefly describe what I have already done.
In fact I will split the post in two due to the 10k character post limit, so ignore the word briefly above

.................putty output below somewhat truncated (if you do not want to check this skip untill you see dots like these>... again ...........


What do you want to do? ps
__________________________________________________


Install pixelserv-tls info:
This will guide through the complete installation
of Entware and pixelserv-tls on this router.

But before we start,
we need to check your system.
-------------------------------------------------

Continue? [1=Yes e=Exit] 1

AB-Solution 3.8.1: pixelserv-tls install

checking your system

testing firmware capability: LAN IP port 80
router listens only on LAN IP port 80, continuing

testing if 'ifconfig br0 up' works on your system
this might take a few seconds to complete...

this appears to be working, continuing

checking port 443 availability
port 443 is available, continuing

- Entware is not installed
-------------------------------------------------

Based on the check above, this will

Install Entware and pixelserv-tls on a
compatible device.
-------------------------------------------------

Continue? [1=Yes e=Exit] 1

AB-Solution 3.8.1: pixelserv-tls install

Listing compatible device(s) to use or
install Entware on.
Only ext2|ext3 formatted devices are supported:

1. /tmp/mnt/usbs62mb

Select device [1=Device(s) e=Exit] 1

testing device /tmp/mnt/usbs62mb
device test passed, continuing...

checking for device label for
/tmp/mnt/usbs62mb:
Device has a label and is not named by system
using device: /tmp/mnt/usbs62mb
-------------------------------------------------

Continue? [1=Yes e=Exit] 1

AB-Solution 3.8.1: pixelserv-tls install

Before we start installing, you need to reserve
one IP addresses for use
with pixelserv-tls.

-------------------------------------------------

DO THIS NOW:

blah blah

Continue? [1=Yes e=Exit] 1

AB-Solution 3.8.1: pixelserv-tls install

preparing system for Entware install

installing Entware, using external script
-------------------------------------------------

Info: Creating folders...
Info: Deploying opkg package manager...
Downloading /opt/bin/opkg... success!
Downloading /opt/etc/opkg.conf... success!
Downloading /opt/etc/profile... success!
Downloading /opt/etc/init.d/rc.func... success!
Downloading /opt/etc/init.d/rc.unslung... success!
Info: Basic packages installation...
Downloading http://pkg.entware.net/binaries/mipsel/Packages.gz
Updated list of available packages in /opt/var/opkg-lists/entware-ng
Installing ldconfig (1.0.17-1) to root...
Downloading http://pkg.entware.net/binaries/mipsel/ldconfig_1.0.17-1_mipselsf.ipk
Installing findutils (4.6.0-1) to root...
Downloading http://pkg.entware.net/binaries/mipsel/findutils_4.6.0-1_mipselsf.ipk
Installing libc (1.0.17-1) to root...
Downloading http://pkg.entware.net/binaries/mipsel/libc_1.0.17-1_mipselsf.ipk
Installing libgcc (5.4.0-1) to root...
Downloading http://pkg.entware.net/binaries/mipsel/libgcc_5.4.0-1_mipselsf.ipk
Installing libssp (5.4.0-1) to root...
Downloading http://pkg.entware.net/binaries/mipsel/libssp_5.4.0-1_mipselsf.ipk
Configuring ldconfig.
Configuring libgcc.
Configuring libc.
Configuring libssp.
Configuring findutils.

Congratulations! If there are no errors above then Entware-ng is successfully initialized.

Found a Bug? Please report at https://github.com/Entware-ng/Entware-ng/issues

Type 'opkg install <pkg_name>' to install necessary package.
-------------------------------------------------

Entware sucessfully installed
checking the scripts in /jffs/scripts

jffs file check, replace:
/jffs/scripts/services-start

jffs file check, replace:
/jffs/scripts/services-stop

jffs file check, passed:
/jffs/scripts/post-mount
appending /jffs/scripts/post-mount
with Entware entries
-------------------------------------------------

installing pixelserv-tls

Installing pixelserv-tls (V35.HZ12.Kj-1) to root...
Downloading http://pkg.entware.net/binaries/mipsel/pixelserv-tls_V35.HZ12.Kj-1_ mipselsf.ipk
Installing libopenssl (1.0.2k-1) to root...
Downloading http://pkg.entware.net/binaries/mipsel/libopenssl_1.0.2k-1_mipselsf .ipk
Installing zlib (1.2.11-1) to root...
Downloading http://pkg.entware.net/binaries/mipsel/zlib_1.2.11-1_mipselsf.ipk
Place ca.crt and ca.key to /opt/var/cache/pixelserv before starting HTTPS mode.
Start options can be adjusted via /opt/etc/init.d/S80pixelserv-tls.

See 'pixelserv-tls -h' for details
Configuring zlib.
Configuring libopenssl.
Configuring pixelserv-tls.

pixelserv-tls installed

AB-Solution 3.8.1: pixelserv-tls install

starting post-install configuration
for pixelserv-tls
checking your router's IP settings
-------------------------------------------------

This is where you enter the
IP address you reserved earlier.

It must be:
higher than 192.168.1.1
and lower than 192.168.1.3

-------------------------------------------------

Set a new pixelserv-tls IP address


Enter IPv4 Address: 192.168.1.2

You entered: 192.168.1.2

Is this correct? [1=Yes 2=No] 1

192.168.1.2 is a valid IP address

checking if 192.168.1.2 is available to use

pixelserv-tls IP address set to 192.168.1.2

jffs file check, replace:
/jffs/scripts/wan-start
appending /jffs/scripts/post-mount
with Entware entries

AB-Solution 3.8.1: pixelserv-tls install

checking certificates for pixelserv-tls

creating the certificates for pixelserv-tls

Generating RSA private key, 1024 bit long modulus
blah b;la
certificates for pixelserv-tls created

AB-Solution 3.8.1: pixelserv-tls install


writing the pixelserv-tls startup script
restarting pixelserv-tls to apply changes
Starting pixelserv-tls (AB-Solution)... done.
checking if 192.168.1.2 responds
192.168.1.2 responded, continuing
.......................................putty output paused................................................
=================
(LONG PAUSE)
(then cont...)
=================

 

[|ZeuS|]

.......................................putty output continues............................................


A B - S O L U T I O N A D - B L O C K I N G

AB-Solution 3.8 by thelonelycoder
--------------------------------------------------
RT-N66U (mips) fw-380.67 @ 192.168.1.1 IPv6
--------------------------------------------------
18,519 blocked domains 5 hosts files in use
(logging off, no stats available)
--------------------------------------------------

i AB-Solution [/tmp/mnt/usbs62mb]
cu check for updates

a ad-blocking [on]
l logging [off]
rs router stats [off]

cb custom block IP [off] (0.0.0.0)
ps install pixelserv-tls

b blocking file [AB-Maximum] [Fri @ 2:00]
u update blocking file
el edit white or black list

f follow the logfile
ac update ads counter

e exit AB-Solution sm sub menu
__________________________________________________

Error: pixelserv-tls is not running. <---------------- oops
Check System Log in router WebUI for clues <---------------- pixelserv from ab solutions seems to be running (check output below later)

What do you want to do? ps <---------------- repeat for the heck of it...
__________________________________________________


writing the pixelserv-tls startup script
restarting pixelserv-tls to apply changes
Shutting down pixelserv-tls... done.
Starting pixelserv-tls (AB-Solution)... done.
checking if 192.168.1.2 responds
192.168.1.2 responded, continuing
Error: pixelserv-tls is not running.
Check System Log in router WebUI for clues

A B - S O L U T I O N A D - B L O C K I N G

AB-Solution 3.8 by thelonelycoder
--------------------------------------------------
RT-N66U (mips) fw-380.67 @ 192.168.1.1 IPv6
--------------------------------------------------
18,519 blocked domains 5 hosts files in use
(logging off, no stats available)
--------------------------------------------------

i AB-Solution [/tmp/mnt/usbs62mb]
cu check for updates

a ad-blocking [on]
l logging [off]
rs router stats [off]

cb custom block IP [off] (0.0.0.0)
ps install pixelserv-tls

b blocking file [AB-Maximum] [Fri @ 2:00]
u update blocking file
el edit white or black list

f follow the logfile
ac update ads counter

e exit AB-Solution sm sub menu
__________________________________________________

Error: pixelserv-tls is not running.
Check System Log in router WebUI for clues


.......................................putty output ends.................................................................................................................................................................


So here is what I have tried:

1) ssh into the router, unmount the micro ssd, partition it again, format it again (was and remained ext2) and delete the stuff in various places in the jffs where there were relevant file, e.g. the start stop scripts in the jffs scripts.
2) format jffs
3) do 1 and 2 at the same time
4) changed micro sd (even though I had this one working fine with ab-solution and pixelserv in the past)
5) used ext2 formatted and labeled USB flash drive and did the whole thing there.

also here is some other relevant putty output of things I have checked :
/tmp/mnt/usbs62mb/entware/etc/init.d# ls
S80pixelserv-tls rc.func rc.unslung <-----only one S80pixelserv-tls so that is good.

./S80pixelserv-tls check
Checking pixelserv-tls (AB-Solution)... alive.


opkg list-installed
findutils - 4.6.0-1
ldconfig - 1.0.17-1
libc - 1.0.17-1
libgcc - 5.4.0-1
libopenssl - 1.0.2k-1
libssp - 5.4.0-1
pixelserv-tls - V35.HZ12.Kj-1
zlib - 1.2.11-1

relevant logs from the webUI :=================================================================================
Jul 21 19:26:48 pixelserv[6056]: 311 uts, 0 log, 0 req, 0 avg, 0 rmx, 0 tav, 0 tmx, 0 slh, 0 slm, 0 sle, 0 slu, 0 nfe, 0 gif, 0 ico, 0 txt, 0 jpg, 0 png, 0 swf, 0 sta, 0 stt, 0 ufe, 0 rdr, 0 nou, 0 pth, 0 204, 0 pst, 0 hed, 0 bad, 0 err, 0 tmo, 0 cls
Jul 21 19:26:48 pixelserv[6056]: exit on SIGTERM

Jul 21 19:26:48 pixelserv[6365]: pixelserv-tls version: v35.HZ12.Kj compiled: May 31 2017 04:30:23 options: 192.168.1.2
Jul 21 19:26:48 pixelserv[6365]: Listening on :192.168.1.2:80
Jul 21 19:26:48 pixelserv[6365]: Listening on :192.168.1.2:443
Jul 21 19:26:48 nonofyourbusinesswhatmyloginis: Started pixelserv-tls (AB-Solution) from /tmp/mnt/usbs62mb/adblocking/addon/pixelserv-tls.add.
Jul 21 19:26:53 nonofyourbusinesswhatmyloginis: AB-Solution created 192.168.1.2 for pixelserv during install
---irrelevant stuff----
Jul 21 19:34:19 pixelserv[6936]: pixelserv-tls version: v35.HZ12.Kj compiled: May 31 2017 04:30:23 options: <none> (this is from the second attempt to install it I suppose)
Jul 21 19:34:19 pixelserv[6936]: Abort: Address already in use - :*:80
---irrelevant stuff---
Jul 21 19:57:07 pixelserv[6365]: 1819 uts, 0 log, 0 req, 0 avg, 0 rmx, 0 tav, 0 tmx, 0 slh, 0 slm, 0 sle, 0 slu, 0 nfe, 0 gif, 0 ico, 0 txt, 0 jpg, 0 png, 0 swf, 0 sta, 0 stt, 0 ufe, 0 rdr, 0 nou, 0 pth, 0 204, 0 pst, 0 hed, 0 bad, 0 err, 0 tmo, 0 cls
Jul 21 19:57:07 pixelserv[6365]: exit on SIGTERM
Jul 21 19:57:08 pixelserv[8055]: pixelserv-tls version: v35.HZ12.Kj compiled: May 31 2017 04:30:23 options: 192.168.1.2
Jul 21 19:57:08 pixelserv[8055]: Listening on :192.168.1.2:80
Jul 21 19:57:08 pixelserv[8055]: Listening on :192.168.1.2:443
Jul 21 19:57:08 nonofyourbusinesswhatmyloginis: Started pixelserv-tls (AB-Solution) from /tmp/mnt/usbs62mb/adblocking/addon/pixelserv-tls.add.
Jul 21 19:57:13 nonofyourbusinesswhatmyloginis: AB-Solution created 192.168.1.2 for pixelserv during install.
relevant logs from the webUI end: ================================================================================


So any idea of what is going on?

 

[thelonelycoder]

So any idea of what is going on?

You do not need to format or reinstall AB-Solution or pixelserv-tls again to get this resolved.
Enter these two commands in SSH and post the output:

wget --tries=6 --retry-connrefused -O /tmp/servstats.txt 192.168.1.2/servstats.txt

What happens now is relevant to your problem, because that's where the ps install fails.

If you see no return from the above command, enter this:

cat /tmp/servstats.txt

The latter should now show the pixelserv-tls stats, please post it.

 

[thelonelycoder]

@|ZeuS| If the above fails, you might want to wait for the release of the next version of AB-Solution.
I have built in some options for a case like yours.
This release will be available sometime today.

 

[|ZeuS|]

@thelonelycoder here is what happens:

rootusmaximus@RT-N66U-87F0:/tmp/home/root# wget --tries=6 --retry-connrefused -O
/tmp/servstats.txt 192.168.1.2/servstats.txt
--2017-07-22 08:05:59--  http://192.168.1.2/servstats.txt
Connecting to 192.168.1.2:80... failed: Connection timed out.
Retrying.

--2017-07-22 08:06:45--  (try: 2)  http://192.168.1.2/servstats.txt
Connecting to 192.168.1.2:80... failed: Connection timed out.
Retrying.

--2017-07-22 08:07:32--  (try: 3)  http://192.168.1.2/servstats.txt
Connecting to 192.168.1.2:80... failed: Connection timed out.
Retrying.

--2017-07-22 08:08:20--  (try: 4)  http://192.168.1.2/servstats.txt
Connecting to 192.168.1.2:80... failed: Connection timed out.
Retrying.

--2017-07-22 08:09:09--  (try: 5)  http://192.168.1.2/servstats.txt
Connecting to 192.168.1.2:80... failed: Connection timed out.
Retrying.

--2017-07-22 08:09:59--  (try: 6)  http://192.168.1.2/servstats.txt
Connecting to 192.168.1.2:80... failed: Connection timed out.
Giving up.

rootusmegus@RT-N66U-87F0:/tmp/home/root# cat /tmp/servstats.txt
rootusultimus@RT-N66U-87F0:/tmp/home/root#

So cat displays nothing... :/
Of course, I can wait for the next release today or whenever it will be. However, the case here is curious.
I had no problem installing pixelserv in the past. I thought that it may be Merlin's latest firmware but it is not. The problem persists even if I repeat everything I did but on an older firmware in which I had been using ab-solution with pixelserv in the past. Besides, Merlin's new firmware breaking entware and/or pixelserv specifically and there is no widespread freaking out is far fetched.
Thus, we have a case of something that was installed on Merlin's version X and works fine.... then for completely irrelevant reasons and while working fine on Merlin's version Y it gets uninstalled (for truly irrelevant reasons) and when a reinstall is attempted like 1 day later on Merlin's Y we get this imbroglio.

The question then is, do you have any idea what could possibly be the reason for this observed change of behavior? Even if for example the cause is understood to be due to some timing issue (pixelserv starting too late or too fast)... still the what exactly changed and caused this timing issue during a simple uninstall/install of the ab-solution should be understood.

Thank you for your help by the way and for one of the coolest pieces of software available for free

 

[|ZeuS|]

I forgot to mention that if I use chrome to go to http://192.168.1.2/servstats then I get stats just fine.
take a look:

pixelserv-tls version: v35.HZ12.Kj compiled: May 31 2017 04:30:23 options: 192.168.1.2

uts    0d 03:37    pixelserv uptime
log    0    logging access to syslog (0=disabled 1=enabled)
req    9    total # of requests (HTTP, HTTPS, success, failure etc)
avg    0 bytes    average length of request URL
rmx    0 bytes    maximum length of request URL
tav    0 ms    average processing time (per request)
tmx    0 ms    maximum processing time (per request)
slh    0    # of accepted HTTPS requests
slm    0    # of rejected HTTPS requests (missing certificate)
sle    0    # of rejected HTTPS requests (certificate available but bad)
slu    0    # of dropped HTTPS requests (unknown error)
nfe    0    # of GET requests for server-side scripting
gif    0    # of GET requests for GIF
ico    0    # of GET requests for ICO
txt    0    # of GET requests for Javascripts
jpg    0    # of GET requests for JPG
png    0    # of GET requests for PNG
swf    0    # of GET requests for SWF
sta    1    # of GET requests for HTML stats
stt    0    # of GET requests for plain text stats
ufe    0    # of GET requests /w unknown file extension
rdr    0    # of GET requests resulted in REDIRECT response
nou    0    # of GET requests /w empty URL
pth    0    # of GET requests /w malformed URL
204    0    # of GET requests (HTTP 204 response)
pst    0    # of POST requests (HTTP 501 response)
hed    0    # of HEAD requests (HTTP 501 response)
bad    0    # of unknown HTTP requests (HTTP 501 response)
err    0    # of dropped requests (failed to accept client connection)
tmo    0    # of dropped requests (client timeout before connection accepted)
cls    0    # of dropped requests (client disconnect before connection accepted)

 

[thelonelycoder]

AB-Solution 3.9 is now available
See post#1 or ab-solution.info for what's new.