It looks like the log4j in Twitter4J is not correctly initialized[1]. Did
you customize the log4j in Twitter4J configuration in your system like
this[2]? By default, it's printed to standard output.


[1]
http://activemq.apache.org/log4j-warn-no-appenders-could-be-found-for-logger.html
[2] http://twitter4j.org/en/configuration.html#logger

On Tue, Oct 18, 2016 at 5:42 PM, mingda li <limingda1...@gmail.com> wrote:

> Hi,
>
> When I start 16 nodes, I found the 15th node has log file different from
> others as following.
>
> Oct 18, 2016 5:23:10 PM org.apache.hyracks.control.nc.NCDriver main
> SEVERE: Setting uncaught exception handler org.apache.hyracks.api.lifecyc
> le.LifeCycleComponentManager@73f792cf
> Oct 18, 2016 5:23:10 PM org.apache.hyracks.control.nc.
> NodeControllerService
> start
> INFO: Starting NodeControllerService
> Oct 18, 2016 5:23:10 PM
> org.apache.asterix.hyracks.bootstrap.NCApplicationEntryPoint
> start
> INFO: Starting Asterix node controller: red15
> log4j:WARN No appenders could be found for logger
> (twitter4j.TwitterStreamImpl).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
> more info.
> Oct 18, 2016 5:25:20 PM org.apache.hyracks.control.common.work.WorkQueue$
> WorkerThread auditWaitsAndBlocks
> WARNING: Work StartTasks waited 0 times (~0ms), blocked 1 times (~0ms)
> Oct 18, 2016 5:25:31 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:32 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:32 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:33 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:33 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:33 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:33 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:33 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:47 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 229376 bytes
>
> The other nodes' log files are without the problem: ( I have tried to give
> up the node, but there will be a new node with the same problem)
> Oct 18, 2016 5:23:09 PM org.apache.hyracks.control.nc.NCDriver main
> SEVERE: Setting uncaught exception handler
> org.apache.hyracks.api.lifecycle.LifeCycleComponentManager@73f792cf
> Oct 18, 2016 5:23:09 PM org.apache.hyracks.control.nc.
> NodeControllerService
> start
> INFO: Starting NodeControllerService
> Oct 18, 2016 5:23:09 PM
> org.apache.asterix.hyracks.bootstrap.NCApplicationEntryPoint start
> INFO: Starting Asterix node controller: red6
> Oct 18, 2016 5:25:31 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:32 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:32 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:32 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:32 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 229376 bytes
> Oct 18, 2016 5:25:33 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:33 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:33 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
> Oct 18, 2016 5:25:47 PM org.apache.hyracks.control.nc.Joblet close
> WARNING: Freeing leaked 131072 bytes
>
> The cluster can work well except the data feeding function on Twitter (load
> for a while but no items loaded from Twitter). The data feeding function of
> RSS can also work.
> The problem is wired. Does anyone have idea?
>
> Bests,
> Mingda
>
>
> On Tue, Oct 18, 2016 at 10:17 AM, mingda li <limingda1...@gmail.com>
> wrote:
>
> > Oh, sure. I just came back to school and could repeat the experiment on
> > our cluster today. I will try.
> >
> > Bests,
> > Mingda
> >
> > On Tue, Oct 18, 2016 at 12:25 AM, Wail Alkowaileet <wael....@gmail.com>
> > wrote:
> >
> >> Unfortunately I couldn't reproduce the issue in our tiny cluster.
> >>
> >> @Mingda if you can post the logs it might be helpful.
> >>
> >> On Sat, Oct 15, 2016 at 12:22 AM, Yingyi Bu <buyin...@gmail.com> wrote:
> >>
> >> > >> Log4J in Twitter4j doesn't initialize properly.
> >> >
> >> > Can you explain that a little bit more?
> >> > What exceptions do you hit, "class not found", or sth. else?
> >> > Thx!
> >> >
> >> > On Fri, Oct 14, 2016 at 2:20 PM, Wail Alkowaileet (JIRA) <
> >> j...@apache.org>
> >> > wrote:
> >> >
> >> > >
> >> > >     [ https://issues.apache.org/jira/browse/ASTERIXDB-1694?
> >> > > page=com.atlassian.jira.plugin.system.issuetabpanels:comment
> >> -tabpanel&
> >> > > focusedCommentId=15576516#comment-15576516 ]
> >> > >
> >> > > Wail Alkowaileet commented on ASTERIXDB-1694:
> >> > > ---------------------------------------------
> >> > >
> >> > > After a long meeting, Mingda and I located the problem. Log4J in
> >> > Twitter4j
> >> > > doesn't initialize properly.
> >> > > I don't know why that's the case. I suspect that there's something
> >> wrong
> >> > > in the deployment of AsterixDB.
> >> > >
> >> > > > Fail running Tweet Feed on Cluster of 16 nodes (while succeed on 4
> >> > nodes)
> >> > > > ------------------------------------------------------------
> >> > > -------------
> >> > > >
> >> > > >                 Key: ASTERIXDB-1694
> >> > > >                 URL: https://issues.apache.org/
> >> > > jira/browse/ASTERIXDB-1694
> >> > > >             Project: Apache AsterixDB
> >> > > >          Issue Type: Bug
> >> > > >          Components: Feeds
> >> > > >         Environment: asterix-server-0.8.9-SNAPSHOT-
> binary-assembly
> >> run
> >> > > on cluster
> >> > > >            Reporter: Mingda Li
> >> > > >            Assignee: Xikui Wang
> >> > > >   Original Estimate: 24h
> >> > > >  Remaining Estimate: 24h
> >> > > >
> >> > > > Recently, I am trying to run the data feed query on a cluster of
> 16
> >> > > nodes. All the query run well without error. But each time after I
> >> > > disconnect the feed, there is none of tweet data stored in
> dataverse.
> >> > > However, when I try to run other AQL queries, the cluster can work
> >> well.
> >> > > And I have ever used 4 nodes cluster to load Tweet data
> successfully.
> >> I
> >> > > also checked the log file and find no error there. This is wired.
> Does
> >> > > anyone know why? Has anyone ever used the data feed function on a
> >> cluster
> >> > > of 16 nodes or more?
> >> > > > I am using a asterix-server-0.8.9-SNAPSHOT-binary-assembly to
> >> > configure
> >> > > cluster compiled by myself.
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > This message was sent by Atlassian JIRA
> >> > > (v6.3.4#6332)
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >>
> >> *Regards,*
> >> Wail Alkowaileet
> >>
> >
> >
>

Reply via email to