Database directory version (30804) is lower than current version (30900) - arangodb

I am trying to Set the password for aronogDB by executing below command in (mac).
/usr/local/opt/arangodb/sbin/arango-secure-installation
But getting above error
my arango version is 3.9, I have tried to use --database.auto-upgrade but no use

Related

'mongo' is not recognised as an internal or external command, operable program or batch file [duplicate]

I installed MongoDB community Server from this link. But when I look into C:\Program Files\MongoDB\Server\6.0\bin
, I am not able to locate mongo.exe file. I am able to see mongod.exe and mongos.exe.
Can someone help. Thank you.
legacy mongo shell (mongo) no longer ships with server binaries (for servers >= 6.0). You can download a new shell version (mongosh) from here
Answer from dododo worked for me.
Download Mongo Shell - mongosh from MongoDB Download Center
Extract the contents of the bin from the downloaded zip file to the bin file of your MongoDB folder and run mongosh instead of mongo.
To run the Mongo Shell , Download msi package from the MongoDB Community Download - https://www.mongodb.com/try/download/community
The version 6.0 do not ships with server binaries so mongo.exe file wouldn't be shown. So instead download mongo shell - https://www.mongodb.com/try/download/shell
After downloading unzip the bin directory in your Original bin directory
(You would also need to create a new directory in C: drive named data/db)
Now open the bin directory from Mongodb folder, and run mongod.exe
After that keeping Mongod.exe running in background open mongosh.exe ,
Your mongo Shell will be started.
After version 6.0.0 mongo.exe does not get installed to your bin folder so you have to manually install the new MongoDB shell which is called mongosh then you have to add its path to your system variables and then run mongosh --version to see if it got installed. Afterwards if you want to create your own databases and preform operations run "mongosh" in your terminal to connect to a MongoDB instance running on your localhost with default port 27017.
Read the mongoDB documentation for more information:
install mongosh:
https://www.mongodb.com/docs/mongodb-shell/install/
The mongosh shell vs the old mongo shell:
https://www.mongodb.com/docs/mongodb-shell/
Connect to a Deployment:
https://www.mongodb.com/docs/mongodb-shell/connect/
It should be noted, that in MongoDB version 6.0 there are two items:
The legacy mongo shell is removed from MongoDB 6.0
The MongoDB Shell (mongosh) is not installed with MongoDB Server. You need to follow the mongosh installation instructions to download and install mongosh separately. This was already announced in MongoDB version 5.0
The legacy mongo shell does not exist anymore on MongoDB version 6.0. If you desire the old mongo.exe, then you can install if from an earlier MongoDB version.
You also need to add a path variable of the bin folder where mongosh application is present (after downloading from the below link:
https://www.mongodb.com/try/download/shell ).
Then you can use mongosh command from anywhere using CMD:
STEPS TO FOLLOW AFTER DOWNLOADING SHELL FROM https://www.mongodb.com/try/download/shell
Include both your mongosh shell and mongod in environment variables.
go to your c drive and create db folder inside data folder
then run your mongosh and mongod in two different cmd windows
separately
..first run mongod
..then run mongosh
if you have check-marked run as a service at the time of download
then next time you are not required to start mongosh , it will
automatically get started.

Terraform version is giving incorrect version in windows

I noticed when I run terraform version in command prompt is not giving the correct terraform version, I just downloaded and kept in c:/terraform folder.
If you notice terraform version command in command prompt is not giving the correct terraform version, you just downloaded and kept in c:/terraform path then check these two things.
Check whether you Updated system path variable with c:/terraform
Check where terraform was installed using (get-command terraform.exe).Path in PowerShell.
Check whether you already installed terraform using chocolatey.

What is the command to check the version of the postgresql jdbc driver on Linux command line?

I am working on Linux server with PostgreSQL that is installed through the command line.
How could I check the version of the PostgreSQL JDBC Driver using Linux command line?
I use this command psql -V and it shows the PostgreSQL version psql (PostgreSQL) 9.5.24, but I need the PostgreSQL JDBC Driver version. What is the command the should I use?
When you run:
java -jar /path/to/driver.jar
it will report its version.
Obviously you need to replace /path/to/driver.jar with the correct location where you stored the driver when you downloaded it.
By default the file name itself contains the version. So if you downloaded postgresql-42.2.19.jar then it's highly likely its version is 42.2.19
As a side note: psql -V prints the version of the command line tool. That's not necessarily the same version as the server.
From Java, you can use code like this:
java.sql.Driver d = new org.postgresql.Driver();
System.out.println(d.getMajorVersion() + "." + d.getMinorVersion());
See the documentation for details.

You database files were created by PostgreSQL 9.0- could not find executables for this version

I attempted to update the version of Postgres-server on an OpenSuse server. There were a few issues and I now want to revert back to using the version of postgres-server that was installed before(9.03).
I've removed version 9.4 and I've tried starting the postgresql server but I'm getting the error:
Your database files were created by PostgreSQL version 9.0.
Could not find executables for this version.
Please install the PostgreSQL server package for version 9.0.
When I run:
rpm -qa | grep postgresql
it shows:
postgresql-docs-9.0.3-1.6.1.noarch
postgresql-server-9.0.3-1.6.1.x86_64
postgresql-contrib-9.0.3-1.6.1.x86_64
postgresql-9.0.3-1.6.1.x86_64
postgresql-devel-9.0.3-1.6.1.x86_64
So it looks like version 9.03 is already installed.
I'm not sure what to do now to get the server back to how it was and I'm panicking a bit. Can anyone suggest anything?
EDIT**
Here some more info after some useful info from Ronaldhino.
I discovered my pg_ctl file in /user/bin/pg_ctl and /data appears to be the previous data directory (I deduced this as it contain pg_hbs.conf and postgresql.conf).
As a result I've run this command as user postgres:
/usr/bin/pg_ctl start -D /data/ -l /data/pg_log/new_log.txt
I did get a message initial saying:
server starting
It appears that the server is actually running. However, the psql binary file now appears to be missing so I can't psql into the database service.
Thanks
I seems that system can not recognize where's your postgresql 9.0 location is.
You should find where's the postgresql 9.0's binary file and start Server directly.
Run command for finding where's postgresql 9.0 location
which postgres
For example:
/usr/local/pgsql/bin/
Start server
sudo /usr/local/pgsql/bin/pg_ctl start -D <<your DB dir>> -l /var/log/postgresl.log
Good luck!

arangodb 2.2.4 - foxx manager install command returning cannot write file

I have installed arangodb 2.2.4 on Ubuntu 14.04 and created new database "SampleDB" using arangodb web interface.
then executed following commands
foxx-manager --server.database SampleDB update
foxx-manager --server.database SampleDB install hello-foxx /hello
but the command is returning error "cannot write file".
I have checked the logs but could not find anything. Same error is coming if i am trying to install from arangosh.
I can confirm this problem, even with arangodb 2.2.5.
Here is what happens in the ArangoDB database:
foxx-manager simply calls arangosh
arangosh creates a temporary directory /tmp/arangodb with the current user
as owner
foxx-manager puts some stuff in there,
the dir stays
either you did not reboot or Ubuntu 14.04 does not clean /tmp on reboot,
if then another user tries to use foxx-manager, the directory is still there
and the new arangosh under the new user cannot write, which leads to the
error
Solution:
for the moment, remove /tmp/arangodb if it is in the way
I will now change arangosh such that it uses a unique name in /tmp for the temporary directory and possibly cleans that one up in the end. This should
solve the problem. I will post here which version will have the fix.

Resources