topic Re: One Address is not reachable for a forwarder, all address become unreachable! in Getting Data In

One Address is not reachable for a forwarder, all address become unreachable!

robertlynch2020 — Wed, 05 Apr 2017 15:05:50 GMT

I had the following issues, i had two address on two different machines configured on one forwarder. I access via /net/.

One machine was shut down hp589srv(so not accessible anymore), but both HOST stopped forwarding data dell439srv as well.
I got no errors, but just spent the day figuring this out.

Is there a way to tell the forwarder that if an address it not reachable ignore it and move on.

[monitor:///net/hp589srv/hp589srv3/apps/TX_ORA_3691008//logs/monitoring/db_rowcounts/*]
disabled = false
host = TX_TST_ndjelveh
index = mlc_live
sourcetype = row_counts
initCrcLength = 4096


[monitor:///net/dell439srv/data1/apps/__COLLAT_BENCH//mlc/timings/*]
disabled = false
host = COLLAT-COMPL-PAC_tkoch
index = mlc_live
sourcetype = lts_timings
whitelist = timings.csv$

Cheers for any help on this 🙂

Re: One Address is not reachable for a forwarder, all address become unreachable!

woodcock — Mon, 21 Jan 2019 19:51:22 GMT

This is a SAN, isn't it? Forwarding from SANs is fraught with these kind of problems.

Re: One Address is not reachable for a forwarder, all address become unreachable!

robertlynch2020 — Fri, 01 Feb 2019 10:40:56 GMT

Hi - Yes it was

We changed the architecture from each forwarder pulling/pushing from one machine not 2.
So if one goes down it does not affect the other.

Rob

Re: One Address is not reachable for a forwarder, all address become unreachable!

robertlynch2020 — Fri, 01 Feb 2019 10:41:03 GMT

Hi - Yes it was

We changed the architecture from each forwarder pulling/pushing from one machine not 2.
So if one goes down it does not affect the other.

Rob