I have installed couchDB 1.0.1 on my linux 12.04. But as I ran the test suite, the replication section failed. The failure information is as follows:
Exception raised: {"error":"not_found"}
Another failed test include "rev_stemming". The rest of the items have passed the test. Database replication is vital to multi-master scenarios like couchDB, so could you help me? Thanks in advance.
The true and only recommendation is to get upgrade your CouchDB up to the latest release (1.6.1). CouchDB 1.0.1 recently had celebrated 4-th happy birthday - it's ancient, unsupported and obliviously didn't and will not receive any bugfixes. More over it's vulnerable to several CVE issues which were partially fixed with 1.0.4 release, but not at all. It's strongly recommended you to upgrade your CouchDB.
Related
Symfony 2.8 requires PHP version to be at least 5.3.9, however nothing is mentioned regarding Apache and MySQL versions in the documentation. What are the minimal requirements for them?
Apache and MySQL version are not exactly relevant there: Apache acts merely as a caller to PHP (in the most common mod_php stack), so it does not interact directly with Symfony. Plus Apache release cycles tend to be longer (2.2 from 2005 is still around).
Regarding MySQL, it concerns Doctrine exactly, especially the DBAL - Database Abstraction Layer. Doctrine platforms documentation does not state much about it, we can infer it supports MySQL 5.0+.
Of course, the higher you can go is the better. PHP 5.3 is not supported anymore, nor PHP 5.4 or PHP 5.5 (security bugs supports stopped last week). Apache 2.2 you need the very last "patch" version. MySQL dramatically improved in 5.5+.
If nothing is mentionned in the documentation,then it means any version can be used most of the time.
I think you should simple use the latest version available in your distributions's repository.
I have two couchbase servers, one is 2.5.1 and one is 3.0.3. I can easkily backup all buckets in the 2.5.1 server, but I cannot restore them into the 3.0.3 server. Is this even possible? I read in the documentation here that if you're upgrading, the install will automatically detect the format and convert it, is there such a standalone tool that I could use on my own? I certainly don't see one that seems glaring in my couchbase/bin directory.
cbtransfer tool can do this or you could use XDCR to go between clusters as well.
Just because I am curious, what error do you get when you do a cbrestore into the 3.0.3 cluster with the backups from the 2.5.1 cluster? this should work in theory.
I got problems while running Neoclipse with the Neo4j community edition 2.0.0.
On a Linux machine, after connecting, Only the first node (id=1) appears, with no relationships.
I set the deep level to 4 but nothing happens.
I also see the different relationship types on the windows but cannot navigate.
On a windows machine the situation is worse: I got an 'error reading as json' when I try to connect with the DB. (Neoclipse version is 1.9.5).
Can anyone help please?
Thank you
Paolo
Neoclipse' source repo contains already some commits regarding Neo4j 2.0 - however there seems not to have happened a release since then. So you might checkout the sources from https://github.com/neo4j-contrib/neoclipse and build it locally?
I'm trying to develop fully stand-alone server that would be able to upgrade themselves without any human intervention. To be more acute, here are the requirements :
- Every nights the server checks for updates on a specified server :
- When a upgrade is available, it downloads a new configuration file or something
- Then the server proceeds its upgrade but if anything goes wrong (internet connection is lost or something is badly downloaded) the server rolls back to its previous configuration.
In fact we don't really care if the server isn't up to date but we want to be sure that its still running (even in a old version). I've looked for configuration management system and found fancy tools like Puppet. But, for instance, if puppet can't download a new debian package, the update will failed and there's a risk that the server can't fullfil it's task.
So i was wondering, do I have to check if every packages are correctly downloaded before launching the upgrade or is there any fancy tools that can do it for me and rollback if needed ?
One point is very important, once a server is deploy, we can't have any access to it. That's why it's better to have it running in an older version than to have it not running.
I hope that you'll understand my issue, sorry for my english
Julian
I've got a bit of an obscure problem and I'm hoping someone here can give me some pointers regarding it, I've exhausted everythign I can think of...
At the moment, I have a two node cluster setup (sql server 2008). I have patched this, as per the microsoft guidlines, to service pack 1. The issue is, when I connect to each node individually, I can see the version is 10.1.xxxx, but, when I connect to the cluster by it's name, it reports 10.0.xxxx (the pre-service-pack installation version).
I've tried restarting the cluster services, and also re-applying the patch (which is impossible, because the service pack installer reports the cluster is at 10.1.xxxx - sp1).
Any help/advice/ideas welcome.
Dave
I opened a microsoft support ticket for this, and had the issue corrected by an extremely helpful MS support engineer - sadly, I'm not sure of the details of the fix.
Dave