Accumulo 1.7.3 is 3 years old this month. There are definitely newer releases available, though I do not know if they would solve your issues, since I don't know the underlying cause.
As for the "Connection refused" message, here is a good explanation of the problem in the general case: https://serverfault.com/a/725263/282759 Hadoop has a guide for this issue also: https://cwiki.apache.org/confluence/display/HADOOP2/ConnectionRefused The DEBUG message you showed says it failed to connect to localhost:9999. By default, the Accumulo master uses that port. That port is the default port that the Accumulo master server listens on. Ultimately, this means that either there is no Accumulo master listening at localhost:9999 or there is a firewall blocking it. "localhost" is a bit unexpected here, unless you're running a single-node Accumulo instance and trying to connect from that same host. If any of that is not true, then you should check your DNS configuration. It's likely the master process simply died. You can check to see what is listening on that port with `netstat -tlnp | grep :9999` (might need root/sudo to see process names, depending on your system). And, you should probably check the logs from the master process. The commons-vfs issue might be misleading. Look for some other thing in the logs that may explain why the master process may have died. On Thu, Mar 12, 2020 at 7:09 AM Maria Krommyda <[email protected]> wrote: > > Hello again, > > I am using Accumulo 1.7.3 with commons vfs2 version 2.1 > It is the default from what I could find. > > In any case, I am still wondering what might be causing the connection > refused error and why I cannot access the tables. > Any ideas about that? > > Best regards, > Maria. > > Στις Τρίτη, 10 Μαρτίου 2020, 10:34:06 μ.μ. EET, ο χρήστης Christopher > <[email protected]> έγραψε: > > > Hi Maria, > > I do not know what version of commons-vfs2 works best with Accumulo. I > know that people have tried various versions, based on their > individual needs. I do not use the vfs2 features, so I have limited > experience with it. It might help if you mentioned the version you're > using, and your version of Accumulo. You could try patching your > version of Accumulo based on the issue > https://github.com/apache/accumulo/issues/933 , but since I don't know > the underlying cause of the problem, this is merely a suggestion to > try, if you have the ability to experiment. > > On Tue, Mar 10, 2020 at 2:33 PM Maria Krommyda <[email protected]> wrote: > > > > Hello Christopher, > > > > Sorry if my initial email was not clear enough. > > > > I have an Accumulo datastore connected with my Geoserver. > > I figured the problem because Geoserver had an issue connecting to the > > datastore. > > After figuring out that there is a problem with Accumulo I noticed that the > > datastore has a problem, through different verification methods. > > > > I cannot access the tables even when using the shell or the monitor > > interface. > > Every time I try to access any information I get the connection refused > > error in the logs. > > > > I mentioned the certbot update as it led me to unistall and install > > Apache2, based on the link that you provided I am afraid that I have > > install a different version that it is causing the issue. > > > > Is there a way to verify that I have a compatible version and/or install > > the proper one? > > > > If there is additional information that I can provide to further clarify > > the issue please let me know. > > > > Best regards, > > Maria. > > > > > > > > > > Στις Τρίτη, 10 Μαρτίου 2020, 06:53:00 μ.μ. EET, ο χρήστης Christopher > > <[email protected]> έγραψε: > > > > > > Hi Maria, > > > > I'm not sure this is an Accumulo issue. Accumulo doesn't have a > > "Geoserver" service, and should not be affected by anything related to > > certbot. This might be a Geomesa-specific issue, which is not a > > project maintained by the Accumulo developers (though, there may be > > knowledgeable people on list who can help you). > > > > The one issue that indicates it might be related to Accumulo is the > > stack trace with vfs2 stuff. Accumulo does have vfs2 as a dependency, > > and I think I may have seen some similar stack traces with certain > > versions of commons-vfs2 > > (https://github.com/apache/accumulo/issues/933) but it's hard to tell > > from what you have provided, since there's no Accumulo code mentioned > > in the stack trace. > > > > On Tue, Mar 10, 2020 at 5:54 AM Maria Krommyda <[email protected]> wrote: > > > > > > Hello everyone, > > > > > > A few days ago I run a certbot update for an existing certificate that > > > caused me a few issues. > > > > > > I tried to reverse the changes made but I have not managed to run > > > Accumulo properly after that. > > > > > > My first indication that there was a problem was that the Geoserver was > > > freezing when trying to load the datastores. > > > > > > After some investigation, see attached log, I have realized that Accumulo > > > is not starting/closing properly. > > > > > > After a few tries I came across this, on start up: > > > > > > Exception in thread "Thread-2" java.lang.RuntimeException: No files-cache > > > implementation set. > > > at > > > org.apache.commons.vfs2.provider.AbstractFileSystem.getCache(AbstractFileSystem.java:209) > > > at > > > org.apache.commons.vfs2.provider.AbstractFileSystem.getFileFromCache(AbstractFileSystem.java:222) > > > at > > > org.apache.commons.vfs2.provider.AbstractFileSystem.resolveFile(AbstractFileSystem.java:332) > > > at > > > org.apache.commons.vfs2.provider.AbstractFileSystem.resolveFile(AbstractFileSystem.java:317) > > > at > > > org.apache.commons.vfs2.provider.AbstractFileObject.resolveFile(AbstractFileObject.java:2007) > > > at > > > org.apache.commons.vfs2.provider.AbstractFileObject.resolveFiles(AbstractFileObject.java:2052) > > > at > > > org.apache.commons.vfs2.provider.AbstractFileObject.getChildren(AbstractFileObject.java:1222) > > > at > > > org.apache.commons.vfs2.impl.DefaultFileMonitor$FileMonitorAgent.checkForNewChildren(DefaultFileMonitor.java:553) > > > at > > > org.apache.commons.vfs2.impl.DefaultFileMonitor$FileMonitorAgent.check(DefaultFileMonitor.java:667) > > > at > > > org.apache.commons.vfs2.impl.DefaultFileMonitor$FileMonitorAgent.access$200(DefaultFileMonitor.java:423) > > > at > > > org.apache.commons.vfs2.impl.DefaultFileMonitor.run(DefaultFileMonitor.java:376) > > > at java.lang.Thread.run(Thread.java:748) > > > > > > And I have found in the logs: > > > > > > [impl.MasterClient] DEBUG: Failed to connect to master=localhost:9999, > > > will retry... > > > org.apache.thrift.transport.TTransportException: > > > java.net.ConnectException: Connection refused (Connection refused) > > > > > > Could this be related that in my effort to reverse the changes from > > > certbot I uninstalled and installed apache2? > > > > > > Best regards, > > > Maria. > > >
