Hi, I created new SOP for retrace server (see attachemnt). I tried to git-push it, but got: $ git push Counting objects: 6, done. Delta compression using up to 8 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 2.02 KiB | 0 bytes/s, done. Total 6 (delta 3), reused 0 (delta 0) remote: error: insufficient permission for adding an object to repository database ./objects remote: fatal: failed to write object error: remote unpack failed: unpack-objects abnormal exit Killed by signal 1. To ssh://lockbox01.phx2.fedoraproject.org/git/infra-docs ! [remote rejected] master -> master (unpacker error) error: failed to push some refs to 'ssh://lockbox01.phx2.fedoraproject.org/git/infra-docs' This worked in past for me. Did I lost some access? Can I get it back please or can someone apply the patch? -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
>From d524e7cae19eec440a4ad14467ec31a219e11a85 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miroslav=20Such=C3=BD?= <msuchy@xxxxxxxxxx> Date: Wed, 17 May 2017 11:09:16 +0200 Subject: [PATCH] added retrace SOP --- docs/sysadmin-guide/sops/retrace.rst | 127 +++++++++++++++++++++++++++++++++++ 1 file changed, 127 insertions(+) create mode 100644 docs/sysadmin-guide/sops/retrace.rst diff --git a/docs/sysadmin-guide/sops/retrace.rst b/docs/sysadmin-guide/sops/retrace.rst new file mode 100644 index 0000000..bef3dc9 --- /dev/null +++ b/docs/sysadmin-guide/sops/retrace.rst @@ -0,0 +1,127 @@ +.. title: Retrace SOP +.. slug: infra-retrace +.. date: 2017-15-17 +.. taxonomy: Contributors/Infrastructure + +========== +retrace SOP +========== + + Retrace server - provides complete tracebacks for unhandled crashes and + show aggregated information for developers + +Contact Information +------------------- + +Owner: + Fedora QA Devel, Fedora Infrastructure Team, ABRT team +Contact: + #abrt, #fedora-admin, #fedora-noc +Servers: + retrace*, faf* + +Purpose: + Provides complete tracebacks for unhandled crashes and + show aggregated information for developers. + +Description +----------- + +The physical server runs two main servers: retrace-server and FAF. + +Retrace-server +============== + +The upstream for retrace server lives at: + + https://github.com/abrt/retrace-server + +When user has ABRT client installed and some software crash with unhandled +exception (traceback or core dump). User can send the request to retrace-server, +which will install the same set of package plus debuginfo and return to user +traceback where instead of plain pointers are names of functions. This is more +useful for further debugging. + +Retrace-server can allow uploading of user coredump via WebUI, but this has been +disabled in Fedora instance. + +FAF +=== + +When user decide that he want to report his crash then problem is sent to FAF. +ABRT can be also configured to send microreports automatically without user +intervention. +FAF can agreggate the data and similar reports group into one entity (called +Problems). FAF provides nice WebUI for developers who can see crashes in their +packages. It lives at: + + https://retrace.fedoraproject.org/faf/ + +Playbook +-------- + +Playbook is splitted into several roles. There are two main roles + + * abrt/faf + * abrt/retrace + +These are copy from upstream. You should never update it directly. +The new version can be fetched from upstram using: + + # cd ansible/abrt + # rm -rf faf retrace + # ansible-galaxy install -f -r requirements.yml --ignore-errors -p ./ + +You should review the new differences and commit and push. + +Then there are some roles, which are local for our instance: + + * abrt/faf-local - This is run *before* abrt/faf. + * abrt/retrace-local - This is run *after* abrt/retrace. + * abrt/retrace-local-pre - This is run *before* abrt/retrace. + +Services +-------- + +FAF and retrace-server are web applications. So you just need httpd running. + +Cron +---- + +Both FAF and retrace-server has bunch of cron tasks. They are *not* under +/etc/cron*, but are user crons. They are under users: faf and retrace. + +You can list those crons using: + + * sudo -u faf crontab -l + * sudo -u retrace crontab -l + +All cronjobs should be Ansible managed. Just make sure if you delete some +cron from Ansible that it does not remain on the server. (not always possible +with state=absent) + +Directories +----------- + +- /srv/ssd - fast disk, used for PostgreSQL storage +- /srv - big fat disk, used for storing packages. Mainly: + - /srv/faf/lob + - /srv/retrace +- /srv/faf/db-backup/ - Daily backups of DB. No rotating yet. Needs to be + manually deleted occasionally. +- /srv/faf/lob/InvalidUReport/ - Invalid reports, can be pretty big. + No automatic removal too. Need to be purged manually occasionally. + +Front-page +---------- + +The main web page is handled by package abrt-server-info-page, which can be +controlled using: + /usr/lib/python2.7/site-packages/abrt-server-info-page/config.py + +DB +-- + +Only FAF use DB. We use our own instance of PostgreSQL. You can connect to it +using: + sudo -u faf psql faf -- 2.13.0
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
