Error 503 SERVICE_UNAVAILABLE

asai · May 17, 2008, 4:53am

Hi Guys,

So, trying to get Red5 Plugin working. I have Red5 Server .7 already installed on server and bound to a second IP address on the server, but it’s shut down at the moment. Got the plugin installed into Openfire, but when I go to myserver:9090/red5/index.html I get

HTTP ERROR: 503

SERVICE_UNAVAILABLE

RequestURI=/red5/index.html

I know there are some with similar problems…has anyone been able to solve this one? Or are there any insights as to a possible solution?

Thanks.

Dele_Olajide · May 17, 2008, 5:06pm

You have not read the readme document me have you

http://www.igniterealtime.org/community/docs/DOC-1520

http://www.igniterealtime.org/community/docs/DOC-1518

it is myserver:7070/red5/index.html or whatever you http-bind port is

-dele-

asai · May 17, 2008, 5:15pm

Hi Dele,

Thanks for the reply.

I changed the HTTP Bind Port to 9090, thinking maybe it was still listening on that port and changed the admin port to 9000. Still no dice.

Any other thoughts on this?

asai · May 17, 2008, 5:19pm

Here’s a shot of the Warn log from last night, I don’t know if it’s relevant:

2008.05.16 21:39:52 Committed before 404 null2008.05.16 21:39:52 /red5/index.html

java.lang.IllegalStateException: Committed at org.mortbay.jetty.Response.resetBuffer(Response.java:995) at org.mortbay.jetty.Response.sendError(Response.java:240) at org.mortbay.jetty.Response.sendError(Response.java:340) at org.mortbay.jetty.servlet.ServletHandler.notFound(ServletHandler.java:995) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollect ion.java:206) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.j ava:828) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)

asai · May 17, 2008, 7:01pm

I found this in checking out the red5.log

java.net.BindException: Address already in use

So. I have Flash Media Server already running on this machine. Is there any way of binding Openfire or the Red5 plugin to the other IP address available on the server?

asai · May 18, 2008, 7:59pm

Dele,

I’ve been able to trace it down to java.net.BindException: Address already in use.

Can I ask, what port is the Red5 plugin listening on? When I restart Openfire, that’s the exception I get in the red5.log. So perhaps if I could get more info on what port the plugin is listening on, maybe I could track down the IP/port conflict.

Thanks for all your efforts here.

-asai

asai · May 19, 2008, 1:01am

Ok,

Looks like I’m narrowing in on the problem…the port in question is 1935. Since I already have Flash Media Server running on the same server, it’s causing a port conflict. The problem here is that the Red5 plugin seems to want to bind to all available addresses, and not just the IP address of the Openfire server. I have Openfire bound to the second IP address of my server, and Flash Media Server running on the first, with FMS binding only to the first. This doesn’t dause conflcts with the full version of Red5 running, as I can have both running side by side because I can bind Red5 to a single IP.

So Dele, is there any way of changing the plugin so that it will bind only to the IP of the Openfire server? Otherwise, can I modify the source and build?

asai · May 19, 2008, 1:21am

Ok. I figured it out. In /opt/openfire/plugins/red5/WEB-INF/classes there’s a file called red5-core.xml.

In that file I found where you can change the IP binding. It’s under the RTMP Mina Transport section.

Red5 plugin activated. Problem solved.

Dele_Olajide · May 19, 2008, 10:20am

Thanks for the feedback. I am sure some else will find that very useful

-dele

111 · June 3, 2008, 1:49pm

when I compile openfire_src_3_5_1.zip on Win XP, I hava got the information in Console View of eclipse as follows:

Openfire 3.6.0 Alpha

Admin console listening at http://127.0.0.1:9090

but when I input “http://127.0.0.1:9090/” in WEB explorer,I got the Error as follow for every time.

HTTP ERROR: 503SERVICE_UNAVAILABLE

RequestURI=/

Powered by jetty://

Though, I tried to compile openfire_src_2008-06-03.zip ,openfire_src_2008-06-02.zip and so on,but I come across the same ERROR as abovle.

can anybody could help me,Thank you.

john_li · July 9, 2008, 6:44am

My red5.log like this: Please help

2008-07-10 02:36:24,919 INFO org.red5.server.jmx.JMXAgent - JMX HTML adapter was not enabled

2008-07-10 02:36:24,926 INFO org.red5.server.jmx.JMXAgent - JMX RMI adapter was not enabled

2008-07-10 02:36:25,623 INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP Mina Transport Settings

2008-07-10 02:36:25,625 INFO o.r.s.net.rtmp.RTMPMinaTransport - IO Threads: 2

2008-07-10 02:36:25,625 INFO o.r.s.net.rtmp.RTMPMinaTransport - Event Threads - core: 4, max: 8, queue: -1, keepalive: 60

2008-07-10 02:36:25,658 INFO o.r.s.net.rtmp.RTMPMinaTransport - TCP No Delay: true

2008-07-10 02:36:25,658 INFO o.r.s.net.rtmp.RTMPMinaTransport - Receive Buffer Size: 65536

2008-07-10 02:36:25,659 INFO o.r.s.net.rtmp.RTMPMinaTransport - Send Buffer Size: 271360

2008-07-10 02:36:25,665 INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP Mina Transport bound to /127.0.0.1:1935

2008-07-10 02:36:25,665 INFO org.red5.server.jmx.JMXFactory - Object name: org.red5.server:type=RTMPMinaTransport,address=127.0.0.1,port=1935

2008-07-10 02:36:25,677 INFO org.red5.server.jmx.JMXFactory - Object name: org.red5.server:type=IoServiceManager,address=127.0.0.1,port=1935

2008-07-10 02:36:27,012 INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP Mina Transport unbind

2008-07-10 02:36:27,038 ERROR o.red5.server.war.WarLoaderServlet -

org.springframework.beans.factory.access.BootstrapException: Unable to initialize group definition. Group resource name , factory key http://default.context; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘default.context’ defined in URL jar:file:/opt/openfire/plugins/red5/WEB-INF/lib/red5Plugin.jar!/beanRefContext.x ml: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class http://org.springframework.context.support.ClassPathXmlApplicationContext: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘rtmpt.server’ defined in class path resource http://red5-core.xml: Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘Server’ defined in class path resource http://red5-rtmpt.xml: Invocation of init method failed; nested exception is java.net.BindException: Address already in use

at org.springframework.beans.factory.access.SingletonBeanFactoryLocator.useBeanFac tory(SingletonBeanFactoryLocator.java:387)

at org.springframework.web.context.ContextLoader.loadParentContext(ContextLoader.j ava:317)

at org.springframework.web.context.ContextLoader.initWebApplicationContext(Context Loader.java:185)

at org.red5.server.war.WarLoaderServlet.contextInitialized(WarLoaderServlet.java:1 14)

at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:540)

at org.mortbay.jetty.servlet.Context.startContext(Context.java:135)

at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1220)

at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:510)

at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)

at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)

at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollec tion.java:156)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)

at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)

at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)

at org.mortbay.jetty.Server.doStart(Server.java:222)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)

at org.jivesoftware.openfire.http.HttpBindManager.changeHttpBindPorts(HttpBindMana ger.java:246)

at org.jivesoftware.openfire.http.HttpBindManager.setHttpBindPorts(HttpBindManager .java:210)

at org.jivesoftware.openfire.admin.http_002dbind_jsp.handleUpdate(http_002dbind_js p.java:28)

at org.jivesoftware.openfire.admin.http_002dbind_jsp._jspService(http_002dbind_jsp .java:104)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.ja va:1093)

at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:11 8)

at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)