Problems with backup and restore using Datastax OpsCenter - datastax-enterprise

Can someone helps on this issue? I have a scheduled backup and this morning I got this message: “Snapshot of all keyspaces on node {ip address} failed: java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: org.apache.cassandra.io.FSWriteError (no security manager: RMI class loader disabled)“. I believe nothing was changed before that and now I can backup the database. Any clue?

Solve the issue with this command:
sudo chmod -R 777 /var/lib/cassandra/data/

Related

Upgrading Neo4j data fails on "logs contains entries with prefix 2"

I'm running a database on Neo4j v3.5.11 CE via Docker volume on AWS. I want to upgrade to 4.4.9, so I created a tar of ./graph.db and brought it back to my dev box. I extracted to /var/lib/neo4j/data/databases. I mounted it to a neo4j v3.5.11 container and it starts fine. I can see all the data via localhost:7474.
Next I try mounting to neo4j v4.4.0 via:
docker run -d -p 7474:7474 -p 7687:7687 -v /var/lib/neo4j/data:/var/lib/neo4j/data -v /var/lib/neo4j/plugins:/plugins -v /var/lib/neo4j/logs:/var/log/neo4j -e NEO4J_AUTH=none -e NEO4J_dbms_allow__upgrade=true --name neo4j neo4j:4.0.0
Neo4j fails: "Transaction logs contains entries with prefix 2, and the highest supported prefix is 1. This indicates that the log files originates from a newer version of neo4j." This is odd because it was upgraded from 3.5.5 and has been running on 3.5.11--never touched by a newer version.
docker logs neo4j-apoc
Fetching versions.json for Plugin 'apoc' from https://neo4j-contrib.github.io/neo4j-apoc-procedures/versions.json
Installing Plugin 'apoc' from https://github.com/neo4j-contrib/neo4j-apoc-procedures/releases/download/4.0.0.7/apoc-4.0.0.7-all.jar to /plugins/apoc.jar
Applying default values for plugin apoc to neo4j.conf
Skipping dbms.security.procedures.unrestricted for plugin apoc because it is already set
Directories in use:
home: /var/lib/neo4j
config: /var/lib/neo4j/conf
logs: /logs
plugins: /plugins
import: /var/lib/neo4j/import
data: /var/lib/neo4j/data
certificates: /var/lib/neo4j/certificates
run: /var/lib/neo4j/run
Starting Neo4j.
2022-09-10 14:18:32.888+0000 WARN Unrecognized setting. No declared setting with name: apoc.export.file.enabled
2022-09-10 14:18:32.892+0000 WARN Unrecognized setting. No declared setting with name: apoc.import.file.enabled
2022-09-10 14:18:32.893+0000 WARN Unrecognized setting. No declared setting with name: apoc.import.file.use_neo4j_config
2022-09-10 14:18:32.921+0000 INFO ======== Neo4j 4.0.0 ========
2022-09-10 14:18:32.934+0000 INFO Starting...
2022-09-10 14:18:48.713+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabaseService#123d7057' was successfully initialized, but failed to start. Please see the attached cause exception "Transaction logs contains entries with prefix 2, and the highest supported prefix is 1. This indicates that the log files originates from a newer version of neo4j.". Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabaseService#123d7057' was successfully initialized, but failed to start. Please see the attached cause exception "Transaction logs contains entries with prefix 2, and the highest supported prefix is 1. This indicates that the log files originates from a newer version of neo4j.".
I tried a couple things:
1.) Deleting the transaction logs: sudo rm graph.db/neostore.transaction.db.* It throws the same exact transaction log error, even though there are no transaction logs in the directory;
2.) Tried a database recovery by adding this to the run command: -e NEO4J_unsupported_dbms_tx__log_fail__on__corrupted__log__files=false This fails with "Unknown store version 'SF4.3.0'":
2022-09-10 15:39:48.458+0000 INFO Starting...
2022-09-10 15:40:34.529+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabaseService#2a39aa2b' was successfully initialized, but failed to start. Please see the attached cause exception "Unknown store version 'SF4.3.0'". Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabaseService#2a39aa2b' was successfully initialized, but failed to start. Please see the attached cause exception "Unknown store version 'SF4.3.0'".
org.neo4j.server.ServerStartupException: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabaseService#2a39aa2b' was successfully initialized, but failed to start. Please see the attached cause exception "Unknown store version 'SF4.3.0'".
Any ideas appreciated! Thanks!
Deleting transaction logs is never a good idea. What you want to do is add an environment variable:
dbms.allow_upgrade=true
Then it should work as the docs states that you can update the latest 3.5 to 4.0.0 Neo4j version.

Neo4j - unable to get routing for database neo4j - unavailable after system upgrade

I have been running a neo4j database for a while without problem.
Yesterday our server OS was update from centos-8 to centos-stream, and since this upgrade our neo4j database does not start anymore.
The service is listed as running but on every query it says: Unable to get a routing table for database 'neo4j' because this database is unavailable.
I cannot log in to the cypher shell because it shuts down with the same error.
I'm not sure what I can do here, I would like to not reset the database as we need the information in there.
The versions I'm running are as follows:
neo4j-4.3.6-1.noarch
neo4j-java11-adapter-1-1.noarch
I had similar issue, so I checked the logs and found the below error in the logs.
Caused by: java.nio.file.AccessDeniedException:
/var/lib/neo4j/data/databases/neo4j/neostore
The fix for the above issue is to change the ownership of noe4j databases folders and files.
cd /var/lib/neo4j/data
sudo chown -R neo4j:neo4j databases/
sudo chown -R neo4j:neo4j transactions/
Restart the neo4j service
sudo systemctl restart neo4j.service

Rails Error: Unable to access log file

I suddenly got this error at my app which ran without problems for more than two years:
Rails Error: Unable to access log file. Please ensure that .../production.log exists...
WARN -- : Errno::EACCES: Permission denied # rb_sysopen .../log/newrelic_agent.log
The result of this error is that my mongoDB is killed. After I restarted the app everything works again until scheduled tasks are called which lead to that behaviour.
The error message says that i have to chmod to 0664, but this is still the case. For the deployment I use capistrano.
Any ideas?
Make log directory writable for other users:
chmod -R 777 specify_app_path_here/log
Now I know the reason for that strange behaviour: Hard Disk Failure !!!
Even both Disks were dead at the same time (RAID1) :(

Reinstalling rabbitmq causing a permission issue

I'm getting the following issue when I do
rabbitmq-server
I'm running on mac os x. rabbitmq version 3.5.4.
I tried to uninstall and reinstall rabbitmq without issues with brew, but end up here with the following error every time. Guidance is appreciated.
Thanks for the help!
BOOT FAILED
===========
Error description:
{could_not_back_up_mnesia_dir,{"/usr/local/var/lib/rabbitmq/mnesia/rabbit#localhost",
"/usr/local/var/lib/rabbitmq/mnesia/rabbit#localhost-upgrade-backup",
eacces}}
Log files (may contain more information):
/usr/local/var/log/rabbitmq/rabbit#localhost.log
/usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
Stack trace:
[{rabbit_upgrade,take_backup,0,
[{file,"src/rabbit_upgrade.erl"},{line,111}]},
{rabbit_upgrade,ensure_backup_taken,0,
[{file,"src/rabbit_upgrade.erl"},{line,100}]},
{rabbit_upgrade,maybe_upgrade_mnesia,0,
[{file,"src/rabbit_upgrade.erl"},{line,142}]},
{rabbit,'-boot/0-fun-0-',0,[{file,"src/rabbit.erl"},{line,328}]},
{rabbit,start_it,1,[{file,"src/rabbit.erl"},{line,353}]},
{init,start_it,1,[]},
{init,start_em,1,[]}]
{"init terminating in do_boot",{could_not_back_up_mnesia_dir,{"/usr/local/var/lib/rabbitmq/mnesia/rabbit#localhost","/usr/local/var/lib/rabbitmq/mnesia/rabbit#localhost-upgrade-backup",eacces}}}
init terminating in do_boot ()
eacces is a permission problem.
Try to execute it using sudo rabbitmq-server
Edit
RabbitMQ does not need the sudo rights.
The default folders where RMQ writes (in this case) need the sudo rights.
But you can overload the default folders reading the documentation.
I usually override this:
export RABBITMQ_PID_FILE=/Users/gabriele/programs/rabbitmq_server-3.5.4/data/rmq.pid
export RABBITMQ_BASE=/Users/gabriele/programs/rabbitmq_server-3.5.4
export RABBITMQ_LOG_BASE=/Users/gabriele/programs/rabbitmq_server-3.5.4/data/logs
export RABBITMQ_MNESIA_BASE=/Users/gabriele/programs/rabbitmq_server-3.5.4/data/db
export RABBITMQ_PLUGINS_DIR=/Users/gabriele/programs/rabbitmq_server-3.5.4/plugins
export RABBITMQ_PLUGINS_EXPAND_DIR=/Users/gabriele/programs/rabbitmq_server-3.5.4/plugins/expands
export RABBITMQ_ENABLED_PLUGINS_FILE=/Users/gabriele/programs/rabbitmq_server-3.5.4/enabled_plugin
and I don't need to use sudo
Please read this https://www.rabbitmq.com/relocate.html for more info about.

how to setup appium for iOS simulator?

I was trying to setup appium for iOS automated testing, but I keep getting this error while running ./reset.sh
does anyone know how to fix the issue?
Running "setConfigVer:ios" (setConfigVer) task
Config file exists, updating it
{"git-sha":"1c004673dcc4a2af7357aff4be72a2da7f9f86bc","ios":{"version":"1.2.3"}}
Done, without errors.
* Installing ios-sim-locale
cp: build/ios-sim-locale: Permission denied
---- FAILURE: reset.sh exited with status 1 ----
Because it is a "Permission denied" error,
try: sudo ./reset.sh --ios ?
I found the issue, for some reason the build folder inside my repo, had the wrong permissions. I simply removed it (it's an empty folder) and mkdir a new one with the same name.

Resources