Thanks James for helping
On Mon, May 18, 2020 at 9:14 PM Robert Snakard
wrote:
> Solved.
>
> The user command `free` is not installed by default on the debian docker
> images. Running `apt-get install procps` installs the `free` command. This
> fixes the issue.
>
> Unsure what changed within
Solved.
The user command `free` is not installed by default on the debian docker
images. Running `apt-get install procps` installs the `free` command. This
fixes the issue.
Unsure what changed within the last month to break this. Do I submit a
request to add procps to the list of Cassandra
Manually ran the start-stop-daemon without the quiet flag. Got some output
# start-stop-daemon -S -c cassandra -a /usr/sbin/cassandra -p
/run/cassandra/cassandra.pid -- -p /run/cassandra/cassandra.pid -H
/var/log/cassandra/java_.hprof -E /var/log/cassandra/hs_err_.log
=>
Apologies for the hyperlink
On Mon, May 18, 2020 at 8:47 PM Robert Snakard
wrote:
> for dir in $(find / -name cassandra -type d); do
> find $dir -type f
> done
>
>
> =>
>
> /usr/share/doc/cassandra/copyright
>
>
>
> /usr/share/cassandra/cassandra.in.sh
>
>
>
> /usr/share/cassandra/*.jar
>
>
for dir in $(find / -name cassandra -type d); do
find $dir -type f
done
=>
/usr/share/doc/cassandra/copyright
/usr/share/cassandra/cassandra.in.sh
/usr/share/cassandra/*.jar
/etc/cassandra/triggers/README.txt
/etc/cassandra/jvm.options
/etc/cassandra/hotspot_compiler
go to configure directory, i.e. /var/lib/cassandra/conf, look logback.xml,
whether configured logs in other directory? Also, do you see output.log,
debug.log in /var/log/cassandra/?
or you may use linux find command to search.
On Mon, May 18, 2020 at 10:51 PM Robert Snakard
wrote:
> docker
docker logs just outputs stderr and stdout. It doesn't show anything more
than what I put in top email
On Mon, May 18, 2020 at 7:42 PM James Shaw wrote:
> docker logs ... see any error in docker/container logs ?
>
> On Mon, May 18, 2020 at 10:27 PM Robert Snakard
> wrote:
>
>> # cat
docker logs ... see any error in docker/container logs ?
On Mon, May 18, 2020 at 10:27 PM Robert Snakard
wrote:
> # cat /var/log/cassandra/system.log
> => cat: system.log: No such file or directory
>
> I've also checked other possible locations. Since this is occurring before
> startup no logs
Do you mean that you want to fix sstable table corrupt error and don't mind
the testing data ? You may run nodetool scrub
or nodetool upgradesstable -a( -a is
re-write to current version).
Thanks,
James
On Mon, May 18, 2020 at 12:54 PM Leena Ghatpande
wrote:
> Running cassandra 3.7
>
# cat /var/log/cassandra/system.log
=> cat: system.log: No such file or directory
I've also checked other possible locations. Since this is occurring before
startup no logs are created
On Mon, May 18, 2020 at 7:03 PM Erick Ramirez
wrote:
> Can you inspect the C* system.log? It might give
On face value, it looks to me that your recovery approach is sound (but of
course, the devil is in the details). If you're getting inconsistent
results, try running the same query in cqlsh with CONSISTENCY ALL (to force
a read-repair from both replicas). If you get the expected result, that
would
Can you inspect the C* system.log? It might give clues for the startup or
it might point to another problem. Cheers!
Cassandra is failing to start with the error
[FAIL] could not access pidfile for Cassandra ... failed!
Steps to reproduce
$ docker run -it debian: bash
# apt-get update && apt-get install wget gnupg
# echo "deb http://www.apache.org/dist/cassandra/debian 311x main" >
Running cassandra 3.7
our TEST cluster has 6 nodes, 3 in each data center
replication factor 2 for keyspaces.
we added 1 new node in each data center for testing making it 8 node cluster.
We decided to remove the 2 new nodes from cluster, but instead of decommission,
the admin just deleted the
You can use `DataModel.objects.using().create()` or use another model for
this purpose. See the ContextQuery utility:
https://docs.datastax.com/en/developer/python-driver/3.23/cqlengine/connections/#context-manager
Hey,
Apologies for the late reply João.
We really, really appreciate your interest and likewise we could not reproduce
this issue anywhere else but in production where it occurred, which is slightly
undesirable. As we could not afford to keep the DC in this state we have
removed it from our
16 matches
Mail list logo
