Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failover stopped working #4032

Open
amisk opened this issue Dec 12, 2019 · 1 comment
Open

failover stopped working #4032

amisk opened this issue Dec 12, 2019 · 1 comment

Comments

@amisk
Copy link

amisk commented Dec 12, 2019

Expected behavior

changing server

Actual behavior

Not changing server, queueing

Environment

  • rsyslog version: 8.1911.0
  • platform: Cent OS 8

So, I posted here before that the failover did not work. The solution was to not have queues within the actions, but rather for the ruleset.
It did work. But now it stopped. And I don't get it.

I even reinstalled rsyslog to have a clean version.

Here is the ruleset:

ruleset(name="fwd" queue.type="disk" queue.filename="fwdq"){
	action(type="omfwd"
		target="10.0.2.15"
		port="514"
		protocol="tcp"
	)

	action(type="omfwd"
		target="10.0.2.10"
		port="514"
		protocol="tcp"
		action.execOnlyWhenPreviousIsSuspended="on"
	)
}

*.* call fwd

if the first server is up, everything runs. If I disconnect it, it will not switch, but happily queues the messages.

service rsyslog status does not show that there is no connection.

It's as if the sending rsyslog does not notice that the first receiver is gone.

Something wrong with that?

edit: also not working with relp.

edit2: I just noticed, that if I do not disable the network interface (Its a VM) on the first receiver, but rather shut it down, the sender immediately switches over.

edit3: It also works if I shut down the rsyslog service on the first receiver. But still not if I disconnect the virtual ethernet connection.

Where is there a difference?

@amisk amisk changed the title failove stopped working failover stopped working Dec 12, 2019
@rgerhards
Copy link
Member

Please create a debug log. Instructions: https://www.rsyslog.com/doc/v8-stable/troubleshooting/howtodebug.html

Be sure that the problem in question occurs at least once during the debug run. Once this is done, please post the debug log (e.g. via pastbin or github). After that, we can review the contents and check how exactly rsyslog processing worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants