[AOLSERVER] AOLserver 4.5.1 - running but unable to load pages on browser

[Thorpe Mayes]

Hi,

My guess is that this is simple, but it eludes me.

I have AOLserver 4.5.1 running. Here is the log:

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: nsmain: AOLserver/4.5.1 starting

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: nsmain: security info: uid=502, euid=502, gid=503, egid=503

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: nsmain: max files: FD_SETSIZE = 1024, rl_cur = 1024, rl_max = 1024

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: encoding: loaded: utf-8

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: fastpath[server1]: mapped GET /

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: fastpath[server1]: mapped HEAD /

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: fastpath[server1]: mapped POST /

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: adp[server1]: mapped GET /*.adp

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: adp[server1]: mapped HEAD /*.adp

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: adp[server1]: mapped POST /*.adp

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: adp[server1]: mapped GET /*.html

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: adp[server1]: mapped HEAD /*.html

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: adp[server1]: mapped POST /*.html

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: modload: loading '/usr/local/aolserver/bin/nssock.so'

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: modload: loading '/usr/local/aolserver/bin/nslog.so'

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: nslog: opened '/usr/local/aolserver/servers/server1/access.log'

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: modload: loading '/usr/local/aolserver/bin/nsperm.so'

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: modload: loading '/usr/local/aolserver/bin/nsdb.so'

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: modload: loading '/usr/local/aolserver/bin/nspostgres.so'

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: PostgreSQL loaded.

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: conf: [ns/server/server1]enabletclpages = 1

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: tcl: enabling .tcl pages

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: default thread pool: minthreads 5 maxthreads 5 idle 0 current 0 maxconns 5 queued 0 timeout 120 spread 20

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: nsmain: AOLserver/4.5.1 running

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: nsmain: security info: uid=502, euid=502, gid=503, egid=503

[19/Jul/2012:13:55:06][2047.3067435888][-sched-] Notice: sched: starting

[19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: driver: starting: nssock

[19/Jul/2012:13:55:06][2047.3060759408][-default:2-] Notice: random: generating 1 seed

[19/Jul/2012:13:55:06][2047.3049257840][-nssock:driver-] Notice: starting

[19/Jul/2012:13:55:06][2047.3049257840][-nssock:driver-] Notice: nssock: listening on 64.58.34.215:80

Sure enough, it is listening on 64.58.34.215:

netstat -tulpn

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name   

tcp        0      0 64.58.34.215:80             0.0.0.0:*                   LISTEN      2047/nsd      

I can ping it:

--- 64.58.34.215 ping statistics ---

18 packets transmitted, 18 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 41.027/42.837/45.061/1.362 ms

There is a file to serve in the pages directory. 

Yet, when I try to load that file (http://64.58.34.215) in a browser I get:

Oops! Google Chrome could not connect to 64.58.34.215

What am I missing here? 

Thanks,

Thorpe

[Jeff Rogers]

First thought, do you have a firewall that might be blocking incoming
network traffic on that port?

Can you connect from a non-web browser (e.g., telnet or nc)? Maybe
chrome is doing something odd.

-J

Thorpe Mayes wrote:
> Hi,
>
> My guess is that this is simple, but it eludes me.
>
> I have AOLserver 4.5.1 running. Here is the log:

> [19/Jul/2012:13:55:06][2047.3049257840][-nssock:driver-] Notice: starting
> [19/Jul/2012:13:55:06][2047.3049257840][-nssock:driver-] Notice: nssock:
> listening on 64.58.34.215:80
>
>
> Sure enough, it is listening on 64.58.34.215:
>
> netstat -tulpn
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
> tcp 0 0 64.58.34.215:80 0.0.0.0:* LISTEN 2047/nsd
>
>
> I can ping it:
>
> --- 64.58.34.215 ping statistics ---
> 18 packets transmitted, 18 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 41.027/42.837/45.061/1.362 ms
>
>
> There is a file to serve in the pages directory.
>
>
>
> Yet, when I try to load that file (http://64.58.34.215) in a browser I get:
>
> Oops! Google Chrome could not connect to 64.58.34.215
>
>
> What am I missing here?
>
> Thanks,
>
> Thorpe
>

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
aolserver-talk mailing list
aolserv...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk

[Ayan George]

On 07/19/2012 03:58 PM, Thorpe Mayes wrote:
>
> [19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: nsmain: AOLserver/4.5.1 starting
> [19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: nsmain: security info: uid=502, euid=502, gid=503, egid=503
> [19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: nsmain: max files: FD_SETSIZE = 1024, rl_cur = 1024, rl_max = 1024
> [19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: encoding: loaded: utf-8
> [19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: fastpath[server1]: mapped GET /
> [19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: fastpath[server1]: mapped HEAD /
> [19/Jul/2012:13:55:06][2047.3077928640][-main-] Notice: fastpath[server1]: mapped POST /

Can you telnet to it from the machine that the server is running on?

Are you trying to connect from another machine? If so, do you think you
might have any filters that might prevent outside access to 64.58.34.215:80?

-ayan

[Dave Bauer]

What do your access logs and error logs say when you attempt to connect. This should help track it down. 

Could there be some firewall or something blocking port 80 access?

Dave

 

[Haig Didizian]

Hey Thorpe,

Could it be a firewall config issue?

Best,
Haig

On Thu, Jul 19, 2012 at 3:58 PM, Thorpe Mayes <tma...@ecognizant.net> wrote:

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
aolserver-talk mailing list
aolserv...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk

--

Haig Didizian - Chief Technology Officer

ha...@wineaccess.com | www.wineaccess.com
O: (610) 642-1255 x120 | F: (610) 642-1277 | C: (610) 457-1748

wineaccess ®
direct from the source

[Bernhard van Woerden]

Change the config to listen to port 80 on all interfaces using the address 0.0.0.0

http://panoptic.com/wiki/aolserver/Conf/Server/Module/nssock/Address

Use -b 0.0.0.0:80 in the command to start nsd.

http://panoptic.com/wiki/aolserver/Command_Line_Reference

Then check on the host running AOLserver

$ telnet 127.0.0.1 80
then type

GET /

See http://www.jmarshall.com/easy/http/

Then check the IP  64.58.34.215 using telnet

$ telnet 64.58.34.215 80

Do this from the localhost and from a remote host.

If you can connect locally but the remote host fails to connect to 64.58.34.215 on port 80 then it may be a firewall issue.

- Bernhard

[Thorpe Mayes]

Haig,

Thanks for your help with this.

It was a firewall issue. I modifed the iptables file and that fixed the problem.

Thanks,

Thorpe

[Thorpe Mayes]

Bernard,

Thank you for your help with this. I appreciate it.

I modified the iptables file and that fixed the problem. 

Thanks,

Thorpe

Thorpe Mayes

tma...@ecognizant.com

405.514.9753