StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9865979
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-26T02:40:26.143
FavoriteCount
0
LastActivityDate
2012-03-26T02:40:26.143
LastEditDate
LastEditorUserId
0
OwnerUserId
920136
ParentId
8154963
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
I finally found the answer (at least for my situation)! The problem was SELinux. I turned off SELinux, and it worked with no problem. If you interested in all of the gory details, you can read about it on <a href="http://linuxsagas.digitaleagle.net/2012/03/23/troubleshooting-ssh-connections-and-using-syslog/">my blog</a>, but let me detail the pertinent facts here... On the remote machine, I used dmesg to view the logging messages: <pre><code>dmesg | tail </code></pre> I found a number of messages like this: <pre><code>type=1400 audit(1332520527.110:51337): avc: denied { read } for pid=25240 comm="sshd" name="authorized_keys" dev=dm-5 ino=167 scontext=unconfined_u:system_r:sshd_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:home_root_t:s0 tclass=file </code></pre> You can check the status of SELinux with this command: <pre><code>$ sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode: permissive Mode from config file: permissive Policy version: 24 Policy from config file: targeted </code></pre> You can turn it to permissive mode with this command: <pre><code>setenforce 0 </code></pre> For more information on SELinux, I found <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Security-Enhanced_Linux/index.html">Red Hat's guide helpful</a>. Also, for other SSH issues, I found <a href="http://dissectionbydavid.wordpress.com/2010/06/24/ssh-log-file-making-one-new-location/">David's blog</a> helpful for getting logging to help. For me, after that, my X11 forwarding started working with no problem. SELinux was preventing several other different things. It could not create the necessary files to make key authentication work. I also found it blocking ssh-keygen from creating keys in the home directory.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POssh X11 forwarding won't work
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USdigitaleagle
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.