From Fedora Project Wiki
(Cleanup, remove the "wiki is slow" section :-))
(Updated)
 
(6 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 +
{{autolang|base=yes}}
 
{{header|infra}}
 
{{header|infra}}
  
Line 9: Line 10:
 
== Access Issues ==
 
== Access Issues ==
  
=== Cannot log in to cvs ===
+
=== Cannot login to fedorapeople.org ===
  
All of our cvs access requires public and private ssh keys.
+
* 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 ssh key is setup correctly.
+
* 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)
* 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.
+
* 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
 
* 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 cvs.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 26: Line 35:
 
</pre>
 
</pre>
  
If your cert has expired, remove it and get a new one from [https://admin.fedoraproject.org/accounts/user/gencert here] .
+
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:  
 +
 
 +
<pre>
 +
(openssl x509 -in ~/.fedora.cert -text; echo; openssl rsa -in ~/.fedora.cert) > fedora.cert.new; mv fedora.cert.new ~/.fedora.cert
 +
</pre>
  
 
=== Cannot request build ===
 
=== Cannot request build ===
Line 36: Line 51:
 
</pre>
 
</pre>
  
If your cert has expired, remove it and get a new one from [https://admin.fedoraproject.org/accounts/user/gencert here] .
+
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 http://fedoraproject.org/wiki/Infrastructure/SOP/Balancers
 
  
 
[[Category:Infrastructure]]
 
[[Category:Infrastructure]]

Latest revision as of 18:53, 9 March 2016

Infrastructure InfrastructureTeamN1.png


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 .