Iptables causes Alfresco not to start up

tfrasch — Sun, 02 Mar 2008 00:10:20 GMT

Hey,I have a problem with Alfresco Community 2.9B Tomcat Bundle on Debian. I get following the error:23:19:09,503 Userystem WARN [remoting.rmi.RmiServiceExporter] Could not detect RMI registry - creating new one23:19:09,509 Userystem INFO [quartz.core.QuartzScheduler] Scheduler DefaultSchedule

Re: Iptables causes Alfresco not to start up

tfrasch — Thu, 06 Mar 2008 00:44:30 GMT

I tracked down that error to my firewall. If I shut down iptables everything works. But with iptables running, no chance.

This is my configuration:

Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     0    –  127.0.0.1            127.0.0.1
DROP       0    -f  0.0.0.0/0            0.0.0.0/0
tcpfilter  tcp  –  0.0.0.0/0            0.0.0.0/0           tcp flags:0x17/0x04 limit: avg 10/sec burst 5
icmpfilter icmp –  0.0.0.0/0            0.0.0.0/0
udpfilter  udp  –  0.0.0.0/0            0.0.0.0/0
tcpfilter  tcp  –  0.0.0.0/0            0.0.0.0/0

Chain FORWARD (policy DROP)
target     prot opt source               destination
icmpfilter icmp –  0.0.0.0/0            0.0.0.0/0
udpfilter  udp  –  0.0.0.0/0            0.0.0.0/0

Chain OUTPUT (policy DROP)
target     prot opt source               destination
ACCEPT     0    –  127.0.0.1            127.0.0.1
icmpfilter icmp –  0.0.0.0/0            0.0.0.0/0
udpfilter  udp  –  0.0.0.0/0            0.0.0.0/0
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           state NEW,ESTABLISHED
ACCEPT     0    –  0.0.0.0/0            0.0.0.0/0

Chain icmpfilter (3 references)
target     prot opt source               destination
ACCEPT     0    –  0.0.0.0/0            0.0.0.0/0

Chain tcpfilter (2 references)
target     prot opt source               destination
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:20
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:21
           tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:22 state NEW recent: SET name: DEFAULT side: source
DROP       tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:22 state NEW recent: UPDATE seconds: 600 hit_count: 4 name: DEFAULT side: source
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:22
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:53
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:80
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:443
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:25
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:587
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:110
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:995
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:143
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:8080
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:50500
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:135
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:139
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:445
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:1137
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:1139
ACCEPT     tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:1145
DROP       tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:1433
DROP       tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:2967
DROP       tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:2968
DROP       tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:5900
DROP       tcp  –  0.0.0.0/0            0.0.0.0/0           tcp dpt:10000
ACCEPT     0    –  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED
ACCEPT     0    –  0.0.0.0/0            0.0.0.0/0           state NEW
DROP       0    –  0.0.0.0/0            0.0.0.0/0

Chain udpfilter (3 references)
target     prot opt source               destination
ACCEPT     udp  –  0.0.0.0/0            0.0.0.0/0           udp dpt:53
ACCEPT     udp  –  0.0.0.0/0            0.0.0.0/0           udp dpt:137
ACCEPT     udp  –  0.0.0.0/0            0.0.0.0/0           udp dpt:138
ACCEPT     udp  –  0.0.0.0/0            0.0.0.0/0           udp dpt:1138
ACCEPT     udp  –  0.0.0.0/0            0.0.0.0/0           udp dpt:50500
ACCEPT     0    –  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED
ACCEPT     0    –  0.0.0.0/0            0.0.0.0/0           state NEW
DROP       0    –  0.0.0.0/0            0.0.0.0/0‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I configured the RMI service to run on port 50500. I put this into "tomcat/shared/classes/alfresco/extension/custom-remote-services-context.xml"

<beans>

        <bean id="avmRemoteService" class="org.springframework.remoting.rmi.RmiServiceExporter">
          <property name="service">
                  <ref bean="avmRemoteTransport"/>
        </property>
          <property name="serviceInterface">
                  <value>org.alfresco.service.cmr.remote.AVMRemoteTransport</value>
        </property>
          <property name="serviceName">
                  <value>avm</value>
        </property>
          <property name="registryPort">
                <value>${alfresco.rmi.services.port}</value>
          </property>
          <property name="servicePort">
                <value>50500</value>
          </property>
  </bean>

</beans>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Any suggestions?

Re: Iptables causes Alfresco not to start up

msporled — Fri, 06 Jun 2008 15:01:21 GMT

Have you made any progress on this? I'm tracking down issues with alfresco and ports and found that it opens a lot of stuff, mostly hard-wired to listen on localhost or all interfaces. There doesn't seem to be an easy way to change either of these settings.

You will also find parts of alfresco that open a few random ports on startup, so good luck.

Re: Iptables causes Alfresco not to start up

greendevil — Fri, 22 Aug 2008 03:02:33 GMT

I was getting the exact same (port 50500 in use) error when trying to install the labs 3a war file into an existing tomcat 5.5 instance that contained Liferay 5.1. I found that the avm service was also listening on the same port. If I did a full install of the labs 3a, there was no problem.

i.e. <bean id="avmSyncServiceTransport" class="org.springframework.remoting.rmi.RmiProxyFactoryBean">
        <property name="serviceUrl">
            <value>rmi://localhost:50500/avmsync</value>
        </property>

I changed the rmi entry in alfresco-shared.properties to 40500 and the issue went away. At least it now runs.

Re: Iptables causes Alfresco not to start up

syslack — Tue, 04 May 2010 09:17:09 GMT

I don't know if it's a good solution, but it worked for me:

iptables -A INPUT -s 127.0.0.1 -j ACCEPT

topic Iptables causes Alfresco not to start up in Alfresco Archive

Iptables causes Alfresco not to start up

Re: Iptables causes Alfresco not to start up

Re: Iptables causes Alfresco not to start up

Re: Iptables causes Alfresco not to start up

Re: Iptables causes Alfresco not to start up