From Fedora Project Wiki

Bodhi Backend Tasks

# get the errors
sudo journalctl --since=yesterday -o short -u fedmsg-hub > error.out
awk '/E[Rr][Rr]/' error.out
egrep 'ERROR|Errno' error.out


# reset the fedmsg-hub service
sudo systemctl restart fedmsg-hub
# start the bodhi push
cd /var/cache/sigul
yes 'no' | sudo -u masher -S bodhi-push --releases '23 22 21 5 6 7' --username parasense
# sign the push
for i in 23 22 21 ; do NSS_HASH_ALG_SUPPORT=+MD5 ~/releng/scripts/sigulsign_unsigned.py fedora-$i -v --write-all --sigul-batch-size=25 $(cat /var/cache/sigul/{Stable,Testing}-F${i})    ; done
for i in  7  6  5 ; do NSS_HASH_ALG_SUPPORT=+MD5 ~/releng/scripts/sigulsign_unsigned.py epel-$i   -v --write-all --sigul-batch-size=25 $(cat /var/cache/sigul/{Stable,Testing}-*EL-${i}) ; done


# Inspect the repo cache areas (optional)
# Areas to verify empty ?
/mnt/fedora_koji/koji/mash/updates/dist-5E-epel{,-testing}.repocache/repodata/
/mnt/fedora_koji/koji/mash/updates/dist-6E-epel{,-testing}.repocache/repodata/
/mnt/fedora_koji/koji/mash/updates/epel7{,-testing}.repocache/repodata
/mnt/fedora_koji/koji/mash/updates/f21-updates{,-testing}.repocache/repodata
/mnt/fedora_koji/koji/mash/updates/f22-updates{,-testing}.repocache/repodata
/mnt/fedora_koji/koji/mash/updates/f23-updates{,-testing}.repocache/repodata
# Check for existing masher locks of currently running push, or failed previous push
ls -l /mnt/koji/mash/updates/MASHING-*
# check for currently running push/mash
pgrep -f masher.py


# resume the push
sudo -u masher bodhi-push --resume --username parasense


Sign Bridge Tasks

# monitor the signing on bridge for potential stalls from bodhi-backend
ssh -v -o'ControlPath=none' sign-bridge01 'tail -f /var/log/sigul_bridge.log'
# Verify the bridge is running or not
sudo pgrep -af bridge.py

# kill the bridge if necessary 
sudo pkill -f -9 bridge.py

# Initialize the bridge with verbose debugging output
sudo NSS_HASH_ALG_SUPPORT=+MD5 sigul_bridge -d -v -v

# Review the bridge.py output
tail -f /var/log/sigul_bridge.log