[Bamboo-Users] The following errors come out when "Run-java" is started.
Olaf Görlitz
goerlitz at uni-koblenz.de
Wed Apr 30 10:21:12 UTC 2008
Hello Mike,
that continuing output is normal. It comes from the log4j logging
facility. You can switch it off by creating a file 'log4j.properties' in
the base directory and setting the LOG LEVEL to WARN or ERROR for bamboo.
My 'log4j.properties' looks like this:
-------------------------------------
log4j.rootLogger = WARN, CONSOLE
log4j.logger.bamboo = ERROR
log4j.appender.CONSOLE = org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout = org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern = %-5p [%t] %4r %c %x: %m%n
-------------------------------------
Cheers,
Olaf
On 30.04.2008 12:07, Mike wrote:
> Dear Olaf
>
> This is Mike.
> Thank you for your advise .
>
> Because the operation of
> "put and get" has been achieved,
> "run-java"and "gateway.cfg" might be normal as you say.
>
> However, after "Sandstorm: Ready" and "Tapestry: ready" is displayed ,
> the following message kept being endlessly displayed many times many times
> (forever),
> it did doubting the operation situation.
>
> ■Error message
> ----------------------------------------------
> "bamboo.lss.ASyncCoreImpl: watchdog awakened"
>
> Thank you for advice of this time.
>
>
>
>
>
>
>
> 2008/4/30, Olaf Görlitz <goerlitz at uni-koblenz.de>:
>
> On 30.04.2008 09:51, Mike wrote:
> > Hello Olaf
> >
> > This is Mike.
> > Thank you for your help .
> >
> > It made it to the same content as the content in the user guide.
> > (http://bamboo-dht.org/gateway.cfg)
> >
> > Afterwards, another error message has come out.
> > The good idea is not found
> > though some plans of restoration were examined.
> > I'm sorry many times.
> > It is very welcome that it can be advice of something.
> >
> >
---------------------------------------------------------------------
> > ■Hereafter, it is a content of the error message.
>
>
> Looks fine to me.
> That is the usual program output - only INFO no ERROR.
> Or is there another Exception?
>
> Olaf
>
>
> >
> >
> > Sandstorm: Ready
> > 2008-04-30 1:41:06,646 INFO bamboo.router.Router: Joined through
> gateway
> > 127.0.0.1:3630
> > Tapestry: ready
> > 2008-04-30 1:41:16,639 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:41:26,639 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:41:36,639 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:41:46,639 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:41:56,640 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:42:06,640 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:42:16,640 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:42:20,298 INFO bamboo.db.StorageManager: starting
> checkpoint
> > 2008-04-30 1:42:20,298 INFO bamboo.db.StorageManager:
checkpoint done
> > 2008-04-30 1:42:26,640 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:42:36,641 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:42:46,641 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:42:56,641 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:43:06,641 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:43:16,641 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:43:26,642 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:43:36,642 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:43:46,642 INFO bamboo.lss.ASyncCoreImpl: watchdog
> awakened
> > 2008-04-30 1:43:47,905 INFO bamboo.db.StorageManager: starting
> checkpoint
> > 2008-04-30 1:43:47,905 INFO bamboo.db.StorageManager:
checkpoint done
> >
> >
> > Olaf Go"rlitz <goerlitz at uni-koblenz.de> wrote:
> >> Hello Mike,
> >>
> >> the port number of your gateway in the Router stage must be exactly
> the
> >> same as defined in the global node_id. You are also missing the RPC
> and
> >> the StorageManager stage. Better use the original gateway.cfg from
> the
> >> user guide. (http://bamboo-dht.org/gateway.cfg)
> >>
> >> Olaf
> >>
> >>
> >> On 30.04.2008 06:00, Mike wrote:
> >>> Hello everyone.
> >>>
> >>> I am a beginner user for bambooDHT ,
> >>> and I hope to know the recovery method
> >>> from the following errors.
> >>>
> >>> Your hellp will be greatly appreciated !
> >>> Best regard
> >>>
> >>> The following errors come out when "Run-java" is started.
> >>>
> >>>
> >>> [root at hostname tmp]# /home/username/bamboo/bin/run-java
> >> bamboo.lss.DustDevil
> >>> /tmp/gateway.
> >>> cfg
> >>> /home/username/bamboo/bin/run-java
> >>> Sandstorm: Ready
> >>> 2008-04-30 12:49:28,691 FATAL bamboo.lss.DustDevil: uncaught
> exception
> >>> java.lang.NullPointerException
> >>> at bamboo.router.Router$13.run(Router.java:1299)
> >>> at
> bamboo.lss.ASyncCoreImpl.asyncMain(ASyncCoreImpl.java:357)
> >>> at bamboo.lss.ASyncCore.async_main(ASyncCore.java:129)
> >>> at bamboo.lss.DustDevil.main(DustDevil.java:343)
> >>>
> >>>
> >>>
> ---------------------------------------------------------------------
> >>> ■Hereafter, the content is gateway.cfg
> >>>
> >>>
> >>> <sandstorm>
> >>> <global>
> >>> <initargs>
> >>> node_id localhost:3631
> >>> </initargs>
> >>> </global>
> >>>
> >>> <stages>
> >>> <Network>
> >>> class bamboo.network.Network
> >>> </Network>
> >>>
> >>> <Router>
> >>> class bamboo.router.Router
> >>> <initargs>
> >>> gateway localhost:3630
> >>> digit_values 16
> >>> </initargs>
> >>> </Router>
> >>>
> >>> <Vivaldi>
> >>> class bamboo.vivaldi.Vivaldi
> >>> <initargs>
> >>> vc_type 2.5d
> >>> generate_pings true
> >>> eavesdrop_pings false
> >>> use_reverse_ping true
> >>> ping_period 10000
> >>> version 1
> >>> </initargs>
> >>> </Vivaldi>
> >>> </stages>
> >>> </sandstorm>
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------
> >>>
> >>> _______________________________________________
> >>> Bamboo-Users mailing list
> >>> Bamboo-Users at bamboo-dht.org
> >>> http://bamboo-dht.org/cgi-bin/mailman/listinfo/bamboo-users
> >>
> >
More information about the Bamboo-Users
mailing list