You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@accumulo.apache.org by David Medinets <da...@gmail.com> on 2012/07/13 03:28:03 UTC

monitor.Monitor - Unable to contact the garbage collector - connection refused

I am seeing the following output in my monitor_lasho.log file. Would
it be possible to display the host and port that is being displayed as
a DEBUG level message?

13 01:25:50,760 [monitor.Monitor] WARN :  Unable to contact the
garbage collector
org.apache.thrift.transport.TTransportException:
java.net.ConnectException: Connection refused
        at org.apache.accumulo.core.client.impl.ThriftTransportPool.createNewTransport(ThriftTransportPool.java:475)
        at org.apache.accumulo.core.client.impl.ThriftTransportPool.getTransport(ThriftTransportPool.java:464)
        at org.apache.accumulo.core.client.impl.ThriftTransportPool.getTransport(ThriftTransportPool.java:441)
        at org.apache.accumulo.core.client.impl.ThriftTransportPool.getTransportWithDefaultTimeout(ThriftTransportPool.java:366)
        at org.apache.accumulo.core.util.ThriftUtil.getClient(ThriftUtil.java:54)
        at org.apache.accumulo.server.monitor.Monitor.fetchGcStatus(Monitor.java:432)
        at org.apache.accumulo.server.monitor.Monitor.fetchData(Monitor.java:299)
        at org.apache.accumulo.server.monitor.Monitor$2.run(Monitor.java:502)
        at org.apache.accumulo.core.util.LoggingRunnable.run(LoggingRunnable.java:34)
        at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.ConnectException: Connection refused
        at sun.nio.ch.Net.connect0(Native Method)
        at sun.nio.ch.Net.connect(Net.java:364)
        at sun.nio.ch.Net.connect(Net.java:356)
        at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:623)
        at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:92)
        at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:76)
        at org.apache.accumulo.core.util.TTimeoutTransport.create(TTimeoutTransport.java:39)
        at org.apache.accumulo.core.client.impl.ThriftTransportPool.createNewTransport(ThriftTransportPool.java:473)

Re: monitor.Monitor - Unable to contact the garbage collector - connection refused

Posted by David Medinets <da...@gmail.com>.

I would hope that Accumulo developers aspire to a higher level of
security awareness. :)

On Thu, Jul 12, 2012 at 9:50 PM, Corey Nolet <cn...@texeltek.com> wrote:
> Hadoop & Zookeeper put that information at the INFO level the their logs don't they?
>
> On Jul 12, 2012, at 9:41 PM, David Medinets wrote:
>
>> I was thinking that someone might not want hostname and port
>> information in log files for security reasons. By putting the
>> 'sensitive' information in a DEBUG message instead of an WARNING
>> message the level of exposure can be controlled by log4j. Perhaps a
>> non-issue, but with these days of consolidating log files into one
>> location for analysis using two messages does provide a bit of cover
>> when talking security.
>>
>> On Thu, Jul 12, 2012 at 9:34 PM, Adam Fuchs <af...@apache.org> wrote:
>>> Sounds like a good upgrade to me. Could even be done as part of that warning
>>> message.
>>>
>>> On Thu, Jul 12, 2012 at 9:28 PM, David Medinets <da...@gmail.com>
>>> wrote:
>>>>
>>>> I am seeing the following output in my monitor_lasho.log file. Would
>>>> it be possible to display the host and port that is being displayed as
>>>> a DEBUG level message?
>

Re: monitor.Monitor - Unable to contact the garbage collector - connection refused

Posted by Corey Nolet <cn...@texeltek.com>.

Hadoop & Zookeeper put that information at the INFO level the their logs don't they?

On Jul 12, 2012, at 9:41 PM, David Medinets wrote:

> I was thinking that someone might not want hostname and port
> information in log files for security reasons. By putting the
> 'sensitive' information in a DEBUG message instead of an WARNING
> message the level of exposure can be controlled by log4j. Perhaps a
> non-issue, but with these days of consolidating log files into one
> location for analysis using two messages does provide a bit of cover
> when talking security.
> 
> On Thu, Jul 12, 2012 at 9:34 PM, Adam Fuchs <af...@apache.org> wrote:
>> Sounds like a good upgrade to me. Could even be done as part of that warning
>> message.
>> 
>> On Thu, Jul 12, 2012 at 9:28 PM, David Medinets <da...@gmail.com>
>> wrote:
>>> 
>>> I am seeing the following output in my monitor_lasho.log file. Would
>>> it be possible to display the host and port that is being displayed as
>>> a DEBUG level message?

Re: monitor.Monitor - Unable to contact the garbage collector - connection refused

Posted by David Medinets <da...@gmail.com>.

I was thinking that someone might not want hostname and port
information in log files for security reasons. By putting the
'sensitive' information in a DEBUG message instead of an WARNING
message the level of exposure can be controlled by log4j. Perhaps a
non-issue, but with these days of consolidating log files into one
location for analysis using two messages does provide a bit of cover
when talking security.

On Thu, Jul 12, 2012 at 9:34 PM, Adam Fuchs <af...@apache.org> wrote:
> Sounds like a good upgrade to me. Could even be done as part of that warning
> message.
>
> On Thu, Jul 12, 2012 at 9:28 PM, David Medinets <da...@gmail.com>
> wrote:
>>
>> I am seeing the following output in my monitor_lasho.log file. Would
>> it be possible to display the host and port that is being displayed as
>> a DEBUG level message?

Re: monitor.Monitor - Unable to contact the garbage collector - connection refused

Posted by Adam Fuchs <af...@apache.org>.

Sounds like a good upgrade to me. Could even be done as part of that
warning message.

Adam


On Thu, Jul 12, 2012 at 9:28 PM, David Medinets <da...@gmail.com>wrote:

> I am seeing the following output in my monitor_lasho.log file. Would
> it be possible to display the host and port that is being displayed as
> a DEBUG level message?
>
> 13 01:25:50,760 [monitor.Monitor] WARN :  Unable to contact the
> garbage collector
> org.apache.thrift.transport.TTransportException:
> java.net.ConnectException: Connection refused
>         at
> org.apache.accumulo.core.client.impl.ThriftTransportPool.createNewTransport(ThriftTransportPool.java:475)
>         at
> org.apache.accumulo.core.client.impl.ThriftTransportPool.getTransport(ThriftTransportPool.java:464)
>         at
> org.apache.accumulo.core.client.impl.ThriftTransportPool.getTransport(ThriftTransportPool.java:441)
>         at
> org.apache.accumulo.core.client.impl.ThriftTransportPool.getTransportWithDefaultTimeout(ThriftTransportPool.java:366)
>         at
> org.apache.accumulo.core.util.ThriftUtil.getClient(ThriftUtil.java:54)
>         at
> org.apache.accumulo.server.monitor.Monitor.fetchGcStatus(Monitor.java:432)
>         at
> org.apache.accumulo.server.monitor.Monitor.fetchData(Monitor.java:299)
>         at
> org.apache.accumulo.server.monitor.Monitor$2.run(Monitor.java:502)
>         at
> org.apache.accumulo.core.util.LoggingRunnable.run(LoggingRunnable.java:34)
>         at java.lang.Thread.run(Thread.java:722)
> Caused by: java.net.ConnectException: Connection refused
>         at sun.nio.ch.Net.connect0(Native Method)
>         at sun.nio.ch.Net.connect(Net.java:364)
>         at sun.nio.ch.Net.connect(Net.java:356)
>         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:623)
>         at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:92)
>         at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:76)
>         at
> org.apache.accumulo.core.util.TTimeoutTransport.create(TTimeoutTransport.java:39)
>         at
> org.apache.accumulo.core.client.impl.ThriftTransportPool.createNewTransport(ThriftTransportPool.java:473)
>