Poppy (ftp upload server) dies without explanation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Tom Haddon |
Bug Description
Poppy has suddenly died more frequently that we would like and there is currently no way to find out why, since its log output is not stored. The only thing we can tell is that the claimed PID was not present anymore.
For improving the response on failures we could set up nagios to probe the pid file (/var/run/
On the code front, we may need to be more verbose about upload events an their durations and incoming IP (but AFAICS this is already available).
The last occurrence of this problem was reported in https:/
Changed in soyuz: | |
assignee: | nobody → cprov |
importance: | Undecided → High |
milestone: | none → 2.2.1 |
status: | New → Triaged |
Changed in soyuz: | |
milestone: | 2.2.1 → 2.2.2 |
Changed in soyuz: | |
milestone: | 2.2.2 → 2.2.3 |
Changed in soyuz: | |
assignee: | cprov → mthaddon |
We can easily store the log by appending '-v --log-file=<FILE>' command line used in /etc/init.d/poppy on PPA and ubuntu machines.
Bonus if we can setup logrotate for this file (PPA already has it set for /srv/production -logs, but unfortunately lp_upload can't write on it)
The log is very poor, it only logs ftp start/end sessions with the corresponding incoming IP address. I'm not entirely sure random events will get logged, but we have to try.