[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#701533: marked as done (project: UDD can not access PET database on wagner.debian.org)

Your message dated Tue, 26 Feb 2013 17:41:19 +0100
with message-id <20130226164119.GA31755@an3as.eu>
and subject line Bug should have not been send to project but rather qa - will reopen with better wording
has caused the Debian Bug report #701533,
regarding project: UDD can not access PET database on wagner.debian.org
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
701533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701533
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: project
Severity: normal

Hi,

since PET moved from a private machine to wagner.debian.org.  This had
the side effect that the UDD job was not able to access the PET database
any more.  A solution was proposed on the Debian QA mailing list[1]
which should be an entry into pg_hba.conf:

# access as guest to pet from udd.debian.org
host    pet             guest           206.12.19.141/32        trust
host    pet             guest           2607:f8f0:610:4000:6564:a62:ce0c:138d/128 trust

Several weeks ago I contacted alioth admins on IRC and they explained
that this solution will not work because of some firewall admin
implemented by some hoster.  Alioth admins were unable / unwilling to
give some honest / helpful time estimation when this can be solved.

It might make sense to consider different means to inject PET data into
UDD than relying on the direct postgresql connection (some intermediate
data file copied via rsync comes to mind.)

I just intend to record this issue here in BTS to enable reasonable
handling of the problem.

Kind regards

        Andreas.

[1] http://lists.debian.org/debian-qa/2012/10/msg00048.html

-- System Information:
Debian Release: 6.0.6
Architecture: i386 (i686)

Kernel: Linux 2.6.36-xenU-4814-i386 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
Hi,

due to a typo (18 instead of 19) this bug was reported to a wrong
address.  I will open a new bug after having received some hints about
better wording.

Sorry for the noise

      Andreas.

-- 
http://fam-tille.de

--- End Message ---
Reply to: