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 ssh to a host

We run denyhosts on all of our externally facing servers. If you fail to log in 15 times in a row, the IP you're coming from (found at http://www.whatismyip.com/) will get flagged as bad for a period of 4 weeks. If you need it removed stop by irc.freenode.net in #fedora-admin and ping an admin with your I Paddress. The most common error message is:

ssh_exchange_identification: Connection closed by remote host

To best avoid complications from denyhosts know that changes made in fas can take an hour to sync to other servers, also ensure you're including your user info correctly, often times people just "ssh fedorapeople.org" for example. If you are logged in to your workstation as 'superman' but your user name is 'wuzzy', you'll want "ssh wuzzy@fedorapeople.org"

Cannot log in to pkgs

All of our git pkgs 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.

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 fedora-cert -n .

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 Infrastructure/SOP/Balancers