Infrastructure/CommonProblems

From FedoraProject

Jump to: navigation, search
Infrastructure InfrastructureTeamN1.png


Contents

Common Problems

General

This page contains a list of common and known issues in our environment. If you've run into an issue a lot please add it to this page or update relevant documentation. If this page does not contain a fix for your issue please Report it.

Access Issues

Cannot log in to cvs

All of our cvs access requires public and private ssh keys.

  • Make sure your ssh key is setup correctly.
  • Our accounts sync at the top of every hour. After you have been sponsored for access it should take no longer than 2 hours for your access to propagate.
  • Ensure you are using the correct username
  • Verify you can log in to https://admin.fedoraproject.org/accounts/home (mention this in reporting the issue)
  • Verify you have network access to the box with "traceroute -T -p 22 cvs.fedoraproject.org"

Cannot upload source

The most common problem with uploading source is a bad cert. Verify that .fedora.cert exists and it has not expired with:

grep After ~/.fedora.cert

If your cert has expired, remove it and get a new one from here .

Cannot request build

The most common problem with requesting builds is a bad cert. Verify that .fedora.cert exists and it has not expired with:

grep After ~/.fedora.cert

If your cert has expired, remove it and get a new one from here .

The web apps

Pages only partially load / every other page load is different

We are in a load balanced environment for most of our apps. Unfortunately our balancer is very dumb (we are working to correct this). Please contact someone in #fedora-admin and notify them of the error and send them to http://fedoraproject.org/wiki/Infrastructure/SOP/Balancers