Infrastructure/CommonProblems

From FedoraProject

< Infrastructure(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
m
(5 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<!-- Do not remove
+
{{autolang|base=yes}}
-->
+
{{header|infra}}
<!-- StartHeader
+
-->
+
<pre>#!html
+
<div style="height:66px; width:100%; background-color:#002867;">
+
<a href = "http://fedoraproject.org/wiki/Infrastructure"> <img style="float:right;padding-top:3px;" src="http://fedoraproject.org/wiki/Infrastructure?action=AttachFile&do=get&target=InfrastructureTeamN1.png" /></a>
+
</div>
+
  
<HR style="height:2px; background-color:#00578E;" />
 
</pre>
 
<!-- EndHeader
 
-->
 
 
<!-- page was renamed from CommonProblems
 
-->
 
 
= Common Problems =
 
= Common Problems =
 
 
  
 
== General ==
 
== General ==
Line 25: Line 10:
 
== Access Issues ==
 
== Access Issues ==
  
=== Cannot log in to cvs ===
+
=== Cannot ssh to a host ===
  
All of our cvs access requires public and private ssh keys.
+
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:
 +
 
 +
<pre>
 +
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.
 
* Make sure your ssh key is setup correctly.
 
* 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.
 
* 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
 
* 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 pkgs01.fedoraproject.org"
  
 
=== Cannot upload source ===
 
=== Cannot upload source ===
Line 42: Line 37:
 
</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:  
 +
 
 +
openssl x509 -in ~/.fedora.cert -text; echo; openssl rsa -in ~/.fedora.cert) > fedora.cert.new; mv fedora.cert.new ~/.fedora.cert
  
 
=== Cannot request build ===
 
=== Cannot request build ===
Line 52: 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 ==
 
== The web apps ==
 
=== Wiki Page Saves are Slow ===
 
 
Unfortunately our version of Moin does not scale very well.  The main problem with page saves are because Moin has to iterate over every user to determine who is watching the page.  With thousands of users this takes a long time.  Average page save times should be between 20 and 45 seconds.
 
 
Another issue is with categories.  Please avoid using categories when possible, they put a great strain on the server.
 
  
 
=== Pages only partially load / every other page load is different ===
 
=== 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
+
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]]

Revision as of 08:36, 5 January 2012

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 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.
  • 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 pkgs01.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 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 .

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