From Fedora Project Wiki
(Fix rhel6 fedora.cert fix command)
(Updated)
 
Line 10: Line 10:
== Access Issues ==
== Access Issues ==


=== Cannot ssh to a host ===
=== Cannot login to fedorapeople.org ===


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:
* Make sure you are in one NON cla group. If you are just in cla_done and cla_fpca, you do not yet have a fedorapeople account.
* Make sure your _public_ ssh key is uploaded to your account in the Fedora Account System. (wait 10-20min after uploading for key to sync)
* Make sure your private key is loaded into your local ssh agent (ssh-add -L should show it).
* Ensure you are using the correct username


<pre>
=== Cannot commit to pkgs ===
ssh_exchange_identification: Connection closed by remote host
</pre>
 
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.
All of our git pkgs access requires public and private ssh keys.
* Make sure your ssh key is setup correctly.
* Make sure your ssh key is setup correctly and the public part is uploaded to the Fedora Account System.
* 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.
* After you have been sponsored for access it should take no longer than 10-20minutes for your access to propagate.
* Ensure you are using the correct username
* 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 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 pkgs01.fedoraproject.org"
* Verify you have network access to the box with "traceroute -T -p 22 pkgs.fedoraproject.org"
* Verify you can login to fedorapeople.org


=== Cannot upload source ===
=== Cannot upload source ===
Line 54: Line 52:


If your cert has expired, remove it and get a new one from fedora-cert -n .
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]]


[[Category:Infrastructure]]
[[Category:Infrastructure]]

Latest revision as of 18:53, 9 March 2016

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 login to fedorapeople.org

  • Make sure you are in one NON cla group. If you are just in cla_done and cla_fpca, you do not yet have a fedorapeople account.
  • Make sure your _public_ ssh key is uploaded to your account in the Fedora Account System. (wait 10-20min after uploading for key to sync)
  • Make sure your private key is loaded into your local ssh agent (ssh-add -L should show it).
  • Ensure you are using the correct username

Cannot commit to pkgs

All of our git pkgs access requires public and private ssh keys.

  • Make sure your ssh key is setup correctly and the public part is uploaded to the Fedora Account System.
  • After you have been sponsored for access it should take no longer than 10-20minutes 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 pkgs.fedoraproject.org"
  • Verify you can login to fedorapeople.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 by calling 'fedora-cert -n'

If you are running rhel6, you will need to modify the cert: 

(openssl x509 -in ~/.fedora.cert -text; echo; openssl rsa -in ~/.fedora.cert) > fedora.cert.new; mv fedora.cert.new ~/.fedora.cert

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 .

Retrieved from "https://fedoraproject.org/w/index.php?title=Infrastructure/CommonProblems&oldid=438336"