>>> "Ulrich Windl" schrieb am 08.10.2021 um
08:01 in Nachricht <615fdec902a100044...@gwsmtp.uni-regensburg.de>:
> test is running, but where the test was sussessul.
Ouch: s/sussessul/successful/ Time for the week-end... ;-)
___
Manage your subscri
>>> Ken Gaillot schrieb am 07.10.2021 um 22:53 in
Nachricht
<8bec6dc04c52d4ac5c2a8055eb7bae455f5a449d.ca...@redhat.com>:
> Hi all,
>
> We're looking ahead to the next Pacemaker release already. Even though
> we had a recent release for a regression fix, I want to get back to the
> goal of having
>>> Marek Marcola schrieb am 07.10.2021 um 18:55 in
Nachricht :
> Hello,
>
> > Oct 05 20:13:25 h19 kernel: NETDEV WATCHDOG: p4p1 (bnxt_en): transmit
> queue 2 timed out
> I have seen this error few times on HP DL360 with centos7 and on HP ML350
> with esxi6.
>
> Disabling offloading on networ
>>> Ken Gaillot schrieb am 07.10.2021 um 22:28 in
Nachricht
<597cd05761a31365b34c6b349539478a5a8b8ced.ca...@redhat.com>:
> On Thu, 2021-10-07 at 12:18 +, Ian Diddams wrote:
>> I trying to find out exactly what the impact/point of such cluster
>> error messages as from running “pcs status”
>>
>>> martin doc schrieb am 07.10.2021 um 17:45 in
Nachricht
:
> Hi,
>
> I've been trying to work out if it is possible to leave a resource on the
> cluster node that it is on and only move it to another node if a dependent
> resource is started. This is all using Red Hat's presentation in RHEL.
Hi all,
We're looking ahead to the next Pacemaker release already. Even though
we had a recent release for a regression fix, I want to get back to the
goal of having a release before the holidays.
The new release will have a couple of enhancements to fencing
configuration options.
The existing p
On Thu, 2021-10-07 at 15:45 +, martin doc wrote:
> Hi,
>
> I've been trying to work out if it is possible to leave a resource on
> the cluster node that it is on and only move it to another node if a
> dependent resource is started. This is all using Red Hat's
> presentation in RHEL...
>
> Ok
On Thu, 2021-10-07 at 12:18 +, Ian Diddams wrote:
> I trying to find out exactly what the impact/point of such cluster
> error messages as from running “pcs status”
>
>
> mysql_VIP01_monitor_3 on wp-vldyn-rafeiro 'unknown error' (1):
> call=467, status=Timed Out, exitreason='',
> last-rc-
Hello,
> Oct 05 20:13:25 h19 kernel: NETDEV WATCHDOG: p4p1 (bnxt_en): transmit queue 2
timed out
I have seen this error few times on HP DL360 with centos7 and on HP ML350 with
esxi6.
Disabling offloading on network card on centos7 seems to solve problem for me:
- RX/TX Checksumming:
# eth
I trying to find out exactly what the impact/point of such cluster error
messages as from running "pcs status"
mysql_VIP01_monitor_3 on wp-vldyn-rafeiro 'unknown error' (1): call=467,
status=Timed Out, exitreason='',
last-rc-change='Mon Oct 4 17:04:07 2021', queued=0ms, exec=0ms
This error
Hi,
I've been trying to work out if it is possible to leave a resource on the
cluster node that it is on and only move it to another node if a dependent
resource is started. This is all using Red Hat's presentation in RHEL...
Ok, that might sound gibberish...
The cluster config I'm trying to b
Hi!
This is not strictly a cluster question, but the problem occurred while the
cluster was live-migrating Xen PVMs.
We have a cluster of three Dell PowerEdge R7415 servers featuring the following
hardware (and running SLES15 SP2):
* Two "Broadcom BCM57412 NetXtreme-E 10Gb RDMA Ethernet Control
12 matches
Mail list logo
