poppy-sftp service has its gpg conf reaped
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Critical
|
Unassigned |
Bug Description
Uploading vdr_1.7.
07:20 < lifeless> sinzui: we did, poppy died and poppy-sftp now listens on ftp as well
07:20 < lifeless> sinzui: this is the issue - valid GPG signature: Verification failed 3 times: ['General error', 'General error', 'General error'] :
07:21 < lifeless> sinzui: the poppy-sftp service *also* tries to verify gpg sigs while the client is connected
07:21 < lifeless> sinzui: it uses GPGHandler
07:21 < lifeless> sinzui: which uses a /tmp dir
07:21 < lifeless> sinzui: which the /tmp reaper deletes old files from
07:21 < lifeless> sinzui: so this means that the gpg.conf for the running poppy-sftp on ppa.launchpad.net has been deleted and needs to be recreated.
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → Critical |
tags: | added: regression |
Sinzui: Does the fix for this entail preventing reaping or automatic recreation?
lifeless: long term is a code change to either stop using one long gpghandler or put it somewhere else. The problem isn't that its in /tmp, its that its written at daemon startup and untouched for 5 days or 4 days or whatever the reaper config is
/me ponders a hack to touch the file every 12 hours.
I do not see an issue with putting it somewhere else, but I think creating a new gpghandler every n hours is the better way to solve this.