Aaron,
Sorry it was 192.168 not 192.128, I typed it in.
Here is my firewall policy:
# Generated by iptables-save v1.2.11 on Wed Dec 13 23:03:50 2006
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT DROP [3:228]
:icmp_packets - [0:0]
-A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 25 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 110 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 143 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 20 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 21 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -s 127.0.0.1 -d 127.0.0.1 -i lo -j ACCEPT
-A INPUT -p icmp -j icmp_packets
-A INPUT -p tcp -m tcp --dport 993 -j ACCEPT
-A INPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -s 127.0.0.1 -d 127.0.0.1 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 25 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 22 -j ACCEPT
-A OUTPUT -p icmp -j icmp_packets
-A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 80 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 443 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 20 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 21 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 3306 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 8080 -j ACCEPT
-A icmp_packets -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A icmp_packets -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A icmp_packets -p icmp -m icmp --icmp-type 3 -j ACCEPT
-A icmp_packets -p icmp -m icmp --icmp-type 11 -j ACCEPT
COMMIT
# Completed on Wed Dec 13 23:03:50 2006
=> Here is the reply for nslookup:
[EMAIL PROTECTED] ]# nslookup rly.rmp.com
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: rly.rmp.com
Address: 192.168.1.110
=> Here is the reply for ping:
[EMAIL PROTECTED] ]# ping rly.rmp.com
PING rly.rmp.com (192.168.1.110) 56(84) bytes of data.
64 bytes from rly.rmp.com (192.168.1.110): icmp_seq=0 ttl=64 time=0.053 ms
64 bytes from rly.rmp.com (192.168.1.110): icmp_seq=1 ttl=64 time=0.037 ms
64 bytes from rly.rmp.com (192.168.1.110): icmp_seq=2 ttl=64 time=0.026 ms
64 bytes from rly.rmp.com (192.168.1.110): icmp_seq=3 ttl=64 time=0.021 ms
64 bytes from rly.rmp.com (192.168.1.110): icmp_seq=4 ttl=64 time=0.024 ms
64 bytes from rly.rmp.com (192.168.1.110): icmp_seq=5 ttl=64 time=0.025 ms
64 bytes from rly.rmp.com (192.168.1.110): icmp_seq=6 ttl=64 time=0.030 ms
--- rly.rmp.com ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 5999ms
rtt min/avg/max/mdev = 0.021/0.030/0.053/0.012 ms, pipe 2
Regards,
Simon
On 12/14/06, Aaron Mulder <[EMAIL PROTECTED]> wrote:
So I didn't see a direct problem, but you reported that the startup
was extra-long and the shutdown tool didn't work, so I'm guessing that
there might still be a network configuration problem. It's possible
that you just have a particularly slow machine and very restrictive
firewall, but let's work through this just to make sure.
So... If you run "ifconfig" what do you get? Does it exactly match
what's in your hosts file? And if you run "nslookup rly.rmp.com" and
"ping rly.rmp.com" do they return promptly and give you what you would
expect?
In particular, it would be more common for the IP address in
/etc/hosts start with "192.168" instead of "192.128", but it just has
to match what ifconfig reports.
Thanks,
Aaron
On 12/14/06, problems mail <[EMAIL PROTECTED]> wrote:
> Aaron,
>
> Here is the reply for hostname
>
> [EMAIL PROTECTED] apacheserver]# hostname
> rly.rmp.com
>
>
> [EMAIL PROTECTED] apacheserver]# more /etc/hosts
> 127.0.0.1 localhost.localdomain localhost
> 192.128.1.110 rly.rmp.com rly
>
> Regards,
> Simon
>
>
>
> On 12/14/06, Aaron Mulder <[EMAIL PROTECTED]> wrote:
> > Most likely, there's still a problem with your /etc/hosts -- as in,
> > the machine's host name does not resolve to one of its actual IP
> > addresses. Can you provide the output of "hostname" and the contents
> > of your /etc/hosts file?
> >
> > Thanks,
> > Aaron
> >
> > On 12/14/06, problems mail <[EMAIL PROTECTED] > wrote:
> > > Hello,
> > >
> > > I have been able to successfully start Geronimo after having issues
with
> the
> > > /etc/hosts file.
> > >
> > > There are couple of issues or concerns wanted to verify, (is 1.1.1the
> right
> > > version to download ??)
> > >
> > > => I still receive errors in the log file, are these ok ? (attaching
the
> log
> > > file)
> > > => It takes over 213s (or approx. 4 minutes to start up), and
majority
> of
> > > the time it is waiting at this "Starting
geronimo/j2ee-security/1..." =>
> I
> > > cannot even shutdown the server it displays an error or stack dump
when
> I do
> > > a "Ctrl + C" on the shell window running the apache geronimo
process.
> > > => I tried to call the shutdown.jar, it is not able to connect and
> shutdown
> > > the Geronimo server
> > >
> > > Is there any setting that we need to do in the IPTables ?
> > >
> > > Are most of the users running Geronimo on Windows ? (looks like they
> dont
> > > seem to have any issues ??)
> > >
> > > Any help greatly appreciated.
> > >
> > > --
> > > Regards,
> > > Simon
> > >
> >
>
>
>
> --
> Regards,
> Simon
--
Regards,
Simon
