[pgpool-general: 9341] WARNING: failed to lock semaphore

[Maria Nieva]

Hello,

We recently upgraded pgpool from 4.1.1 to 4.4.6.  We noticed that we are
getting this

2025-02-08 01:39:33.724 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % WARNING:  failed to lock semaphore
2025-02-08 01:39:33.725 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % DETAIL:  Invalid argument
2025-02-08 01:39:33.725 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % LOCATION:  pool_sema.c:129
2025-02-08 01:39:33.725 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % WARNING:  failed to unlock semaphore
2025-02-08 01:39:33.725 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % DETAIL:  Invalid argument
2025-02-08 01:39:33.725 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % LOCATION:  pool_sema.c:202
2025-02-08 01:39:33.763 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % WARNING:  failed to lock semaphore
2025-02-08 01:39:33.763 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % DETAIL:  Invalid argument
2025-02-08 01:39:33.763 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % LOCATION:  pool_sema.c:129
2025-02-08 01:39:33.764 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % WARNING:  failed to unlock semaphore
2025-02-08 01:39:33.764 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % DETAIL:  Invalid argument
2025-02-08 01:39:33.764 PROCESS: WORKER DB: [No Connection] USER: [No
Connection] APPL: sr_check_worker % LOCATION:  pool_sema.c:202

This doesn't show much

ipcs -s

------ Semaphore Arrays --------
key        semid      owner      perms      nsems


This is in our *pgpool.conf *
backend_clustering_mode = 'streaming_replication'
num_init_children = 250
min_spare_children = 25
max_spare_children = 50
max_pool = 2
child_life_time = 300
child_max_connections = 2
connection_life_time = 300
client_idle_limit = 300

Can you please help us understand why we see the warning?  What is it?  How
do we resolve this?


Thank you very much.  Any help would be appreciated

Maria Nieva   Senior Database Administrator

T 416*.*596*.*6370

*Points  *|  More together.

Connect with us: Points <https://company.points.com/> | Twitter
<https://twitter.com/PointsLoyalty> | Instagram
<https://www.instagram.com/pointsloyalty/?hl=en> | LinkedIn
<https://www.linkedin.com/company/points/> | Careers
<https://company.points.com/careers/current-openings/>

TSX: PTS <https://web.tmxmoney.com/quote.php?qm_symbol=pts>; NASDAQ: PCOM
<https://www.nasdaq.com/symbol/pcom/>

111 Richmond St. W., Suite 700, Toronto, ON, M5H 2G4, Canada
[image: Points logo]        [image: Great Place to Work: Best Workplaces
2015 Canada]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20250210/58ae0ca0/attachment-0001.htm>