After upgrading from 15.1.0 to 15.1.1 of Octopus im seeing this error for
dashboard:
cluster:
id: c5233cbc-e9c2-4db3-85e1-423737a95a8c
health: HEALTH_ERR
Module 'dashboard' has failed: ('pwdUpdateRequired',)
Also executing any command result in:
Error EIO:
Hi Gencer,
On 2020-03-22 09:37, Gencer W. Genç wrote:
> After upgrading from 15.1.0 to 15.1.1 of Octopus im seeing this error for
> dashboard:
>
> cluster:
>
> id: c5233cbc-e9c2-4db3-85e1-423737a95a8c
>
> health: HEALTH_ERR
>
> Module 'dashboard' has failed: ('pwdUpd
hi folks. I seem to have gotten myself into a situation where my monitor
directory filled itself up entirely while I wasn't looking, and now my monitor
is unresponsive. (this is in a 3-node cluster). it grew a whole lot right
after I added a number of OSDs and it started rebalancing. how can I
Hello Samuel,
we from croit.io don't use NFS to boot up Servers. We copy the OS directly
into the RAM (approximately 0.5-1GB). Think of it like a container, you
start it and throw it away when you no longer need it.
This way we can save the slots of OS harddisks to add more storage per node
and re
Hello,
While testing our ceph cluster setup, I noticed a possible issue with the
cluster/public network configuration being ignored for TCP session
initiation.
Looks like the daemons (mon/mgr/mds/osd) are all listening on the right IP
address but are initiating TCP sessions from the wrong interfa
So, I thought I’d post with what I learned re: what to do with this problem.
This system is a 3-node Proxmox cluster, and each node had:
1 x 1TB NVMe
2 x 512GB HDD
I had maybe 100GB of data in this system total. Then I added:
2 x 256GB SSD
1 x 1TB HDD
To each system, and let it start rebalanci
Liviu,
I've found that for Linux systems with multiple NICs the default kernel
settings allow the behavior you're seeing. To prevent this I always add
the following to my /etc/sysctl settings, usually in
/etc/sysctl.d/rp_filter.conf:
net.ipv4.conf.default.rp_filter=1
net.ipv4.conf.all.
Hi Dave,
Thank you for the answer.
Unfortunately the issue is that ceph uses the wrong source IP address, and
sends the traffic on the wrong interface anyway.
Would be good if ceph could actually set the source IP address to the
cluster/public IP when initiating a TCP connection.
I managed to co
On Sun, Mar 22, 2020 at 8:21 AM Dungan, Scott A. wrote:
>
> Zitat, thanks for the tips.
>
> I tried appending the key directly in the mount command
> (secret=) and that produced the same error.
>
> I took a look at the thread you suggested and I ran the commands that Paul at
> Croit suggested ev
