falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raghav Kumar Gautam <raghavgau...@gmail.com>
Subject Re: Not able to start falcon in distributed mode
Date Mon, 30 Sep 2013 10:50:36 GMT
I don't see any errors. I tried the same thing again and saw the following
from application.log:

2013-09-30 03:40:28,667 INFO  - [main:] ~ Started
SocketConnector@0.0.0.0:15000 (log:67)
2013-09-30 03:45:05,101 INFO  - [Thread-10:] ~ config.location is set,
using:
/usr/local/lib/falcon-server-0.4-incubating-SNAPSHOT/conf/runtime.properties
(ApplicationProperties:106)
2013-09-30 03:45:05,101 INFO  - [Thread-10:] ~ Initializing properties with
domain prism (ApplicationProperties:141)
2013-09-30 03:45:05,101 DEBUG - [Thread-10:] ~
log.cleanup.frequency.hours.retention=minutes(1) (ApplicationProperties:146)
2013-09-30 03:45:05,101 DEBUG - [Thread-10:] ~
log.cleanup.frequency.months.retention=months(3) (ApplicationProperties:146)
2013-09-30 03:45:05,101 DEBUG - [Thread-10:] ~
log.cleanup.frequency.minutes.retention=hours(6) (ApplicationProperties:146)
2013-09-30 03:45:05,101 DEBUG - [Thread-10:] ~ domain=prism
(ApplicationProperties:146)
2013-09-30 03:45:05,102 DEBUG - [Thread-10:] ~
log.cleanup.frequency.days.retention=days(7) (ApplicationProperties:146)
2013-09-30 03:45:36,240 INFO  - [847830880@qtp-1122993107-0:] ~ Logging in
root (CurrentUser:53)
2013-09-30 03:45:36,267 INFO  -
[847830880@qtp-1122993107-0:root:POST//entities/submit/cluster
0e05eb95-8a3e-4d5e-9249-bfb139a1cee4] ~ Request from user: root,
path=/entities/submit/cluster, query=null (BasicAuthFilter:86)

And following in falcon.out:
[root@devbox falcon-server-0.4-incubating-SNAPSHOT]# cat
logs/falcon.out.2013093003391380537581
nohup: appending output to `nohup.out'
Sep 30, 2013 3:40:19 AM
com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
INFO: Initiating Jersey application, version 'Jersey: 1.8 06/24/2011 12:17
PM'
Sep 30, 2013 3:40:26 AM
com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
INFO: Initiating Jersey application, version 'Jersey: 1.8 06/24/2011 12:17
PM'


Thanks,
Raghav.



Raghav Kumar Gautam
http://www.linkedin.com/in/raghavg


On Sat, Sep 28, 2013 at 7:01 AM, Shwetha GS <shwetha.gs@inmobi.com> wrote:

> Do you see any error in logs/application.log?
>
>
>
> > On 27-Sep-2013, at 11:08 pm, Raghav Kumar Gautam <raghavgautam@gmail.com>
> wrote:
> >
> > I am starting out with falcon's distributed mode. I am using the falcon's
> > master branch and am getting the following error (this was working with
> > 0.3-incubating).
> >
> > bin/falcon entity -type cluster -submit -file ~/primary-cluster.xml
> > Sep 27, 2013 10:25:34 AM com.sun.jersey.api.client.ClientResponse
> getEntity
> > SEVERE: A message body reader for Java class
> > org.apache.falcon.resource.APIResult, and Java type class
> > org.apache.falcon.resource.APIResult, and MIME media type text/html;
> > charset=iso-8859-1 was not found
> > Sep 27, 2013 10:25:34 AM com.sun.jersey.api.client.ClientResponse
> getEntity
> > SEVERE: The registered message body readers compatible with the MIME
> media
> > type are:
> > */* ->
> >  com.sun.jersey.core.impl.provider.entity.FormProvider
> >  com.sun.jersey.core.impl.provider.entity.StringProvider
> >  com.sun.jersey.core.impl.provider.entity.ByteArrayProvider
> >  com.sun.jersey.core.impl.provider.entity.FileProvider
> >  com.sun.jersey.core.impl.provider.entity.InputStreamProvider
> >  com.sun.jersey.core.impl.provider.entity.DataSourceProvider
> >  com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General
> >  com.sun.jersey.core.impl.provider.entity.ReaderProvider
> >  com.sun.jersey.core.impl.provider.entity.DocumentProvider
> >
>  com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader
> >  com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader
> >  com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader
> >  com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General
> >  com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General
> >  com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General
> >  com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General
> >  com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General
> >  com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General
> >  com.sun.jersey.core.impl.provider.entity.EntityHolderReader
> >  com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General
> >  com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General
> >
> > Unable to connect to Falcon server, please check if the URL is correct
> and
> > Falcon server is up and running
> > A message body reader for Java class
> org.apache.falcon.resource.APIResult,
> > and Java type class org.apache.falcon.resource.APIResult, and MIME media
> > type text/html; charset=iso-8859-1 was not found
> >
> >
> >
> > Jetty is actually up at 15000 (telent connects).
> > Content of logs/falcon.out.2013092710241380302689:
> >
> > nohup: appending output to `nohup.out'
> > Sep 27, 2013 10:24:54 AM
> > com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
> > INFO: Initiating Jersey application, version 'Jersey: 1.8 06/24/2011
> 12:17
> > PM'
> > Sep 27, 2013 10:24:55 AM
> > com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
> > INFO: Initiating Jersey application, version 'Jersey: 1.8 06/24/2011
> 12:17
> > PM'
> >
> > I am following steps from
> > http://falcon.incubator.apache.org/docs/InstallationSteps.html. Am I
> > missing something ?
> >
> > Thanks,
> > Raghav.
>
> --
> _____________________________________________________________
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete transmission
> of the information contained in this communication nor for any delay in its
> receipt.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message