View Issue Details

IDProjectCategoryView StatusLast Update
0000312My infrastructureGeneralpublic2025-11-13 18:37
Reporterdvl Assigned Todvl  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Summary0000312: Should /usr/local/etc/freshports/config.pm contain listening creds?
DescriptionIt may be that FreshPorts::Config::user_listening & FreshPorts::Config::password_listening are required only by the fp-listen daemon which runs only on webserver nodes, not ingress nodes.

This was noticed on r720-02-ingress01
TagsNo tags attached.

Activities

dvl

2025-11-12 12:57

manager   ~0000488

This uncommitted change awaits testing:

[12:50 ansible root /usr/local/etc/ansible] # svn di  roles/freshports-configuration-ingress/templates/config.pm.j2
Index: roles/freshports-configuration-ingress/templates/config.pm.j2
===================================================================
--- roles/freshports-configuration-ingress/templates/config.pm.j2	(revision 2940)
+++ roles/freshports-configuration-ingress/templates/config.pm.j2	(working copy)
@@ -38,10 +38,6 @@
 $FreshPorts::Config::user                       = '{{ fp_pg_user_commits }}';
 $FreshPorts::Config::password                   = '{{ fp_pg_user_commits_password }}';
 
-# For the fp-listen daemon
-$FreshPorts::Config::user_listening             = '{{ fp_pg_user_listening }}';
-$FreshPorts::Config::password_listening         = '{{ fp_pg_user_listening_password }}';
-
 # For readonly connections
 $FreshPorts::Config::user_readonly              = '{{ fp_pg_user_readonly }}';
 $FreshPorts::Config::password_readonly          = '{{ fp_pg_user_readonly_password }}';

dvl

2025-11-12 12:57

manager   ~0000489

change deployed to dvl-ingress01 for testing.

dvl

2025-11-12 12:59

manager   ~0000490

All green on Nagios.

dvl

2025-11-12 13:01

manager   ~0000491

Now deployed to all hosts except aws-1-ingress01

dvl

2025-11-13 18:37

manager   ~0000493

Done on all hosts. So far, so good.

Issue History

Date Modified Username Field Change
2025-08-30 13:06 dvl New Issue
2025-08-30 13:06 dvl Description Updated
2025-11-12 12:42 dvl Assigned To => dvl
2025-11-12 12:42 dvl Status new => assigned
2025-11-12 12:57 dvl Note Added: 0000488
2025-11-12 12:57 dvl Note Added: 0000489
2025-11-12 12:59 dvl Note Added: 0000490
2025-11-12 13:01 dvl Note Added: 0000491
2025-11-13 18:37 dvl Status assigned => resolved
2025-11-13 18:37 dvl Resolution open => fixed
2025-11-13 18:37 dvl Note Added: 0000493