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

Ignoring unknown application_name/node #230

Closed
RajasekarArumugam28 opened this issue May 1, 2024 · 2 comments
Closed

Ignoring unknown application_name/node #230

RajasekarArumugam28 opened this issue May 1, 2024 · 2 comments

Comments

@RajasekarArumugam28
Copy link

Hi Team, I have recently upgraded the node to Postgres 15 and I could see the below INFO in pacemaker log. I have verified in barman side and found no issues there and how to stop this Info message and why am I getting this.

tail -f pacemaker.log
pgsqlms(pgsqld)[3729375]: May 01 09:56:56 INFO: Ignoring unknown application_name/node "barman_receive_wal"
pgsqlms(pgsqld)[3729375]: May 01 09:56:56 INFO: Ignoring unknown application_name/node "barman_receive_wal"
pgsqlms(pgsqld)[3729517]: May 01 09:57:12 INFO: Ignoring unknown application_name/node "barman_receive_wal"
pgsqlms(pgsqld)[3729517]: May 01 09:57:12 INFO: Ignoring unknown application_name/node "barman_receive_wal"

pcs status
Cluster name: pg_cluster
Cluster Summary:

  • Stack: corosync
  • Current DC: pg2 (version 2.0.3-4b1f869f0f) - partition with quorum
  • Last updated: Wed May 1 10:00:07 2024
  • Last change: Wed May 1 09:11:35 2024 by root via cibadmin on pg0
  • 3 nodes configured
  • 6 resource instances configured (1 BLOCKED from further action due to failure)

Node List:

  • Online: [ pg0 pg1 pg2 ]

Full List of Resources:

  • MASTER (ocf::pacemaker:Dummy): Started pg0
  • vip (ocf::heartbeat:IPaddr2): Started pg0
  • mgmt_vip (ocf::heartbeat:IPaddr2): Started pg0
  • Clone Set: pgsql-ha [pgsqld] (promotable):
    • pgsqld (ocf::heartbeat:pgsqlms): FAILED pg1 (blocked)
    • Masters: [ pg0 ]
    • Slaves: [ pg2 ]

Failed Resource Actions:

  • pgsqld_stop_0 on pg1 'error' (1): call=75, status='complete', exitreason='Unexpected state for instance "pgsqld" (returned 9)', last-rc-change='2024-05-01 09:21:45Z', queued=0ms, exec=251ms

Daemon Status:
corosync: active/disabled
pacemaker: active/disabled
pcsd: active/enabled

@ioguix
Copy link
Member

ioguix commented May 1, 2024

Hi,

Yes, this is expected if you have something else replicating from the primary that is not a known node from pacemaker perspective. Issue #178 exists about these flooding messages. I'm not sure how to deal with them though.

If you have some idea about how to deal with that, do not hesitate to discuss them in #178.

Thanks,

@ioguix ioguix closed this as completed May 1, 2024
@RajasekarArumugam28
Copy link
Author

got it , will let you know if anything comes up. thanks

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