Description of problem: When I try from a remote computer to copy data to my computer (with scp and rsync) selinux on my local computer freezes the local computer. Steps to Reproduce: S = Server (in my case an ubuntu 9.04 machine) C = Client (in my case a fedora 12 machine) - Login on a computer S - Give the command "scp foldername C-ip:/folderpath" - Wait a few seconds and C will freeze For rsync, simply substitute the scp command to the appropriate rsync command Additional info: I'm sorry to not be able to bring you any kind of log, but I haven't found them :( (I asked in IRC and a guy suggested my a log file that I actually do not have on my system :\)
Are you sure SELinux is the problem? Have you tried to setenforce 0 and see if the machine hangs? The log file you should have is /var/log/audit/audit.log, if you do not have this file the messages should be in /var/log/messages. If you run audit2allow -la It should look for all messages in both locations and generate a list of allow rules.
--- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Ok, I made some tests. These are the results: - seLinux is not the problem (with setenforce 0 the problem is still there) - the audit2allow command returns me only two white lines (maybe no logging actived?) - even if I'm on computer C and try to rsync/scp from the computer S to C the problem appear.
(In reply to comment #3) > Ok, I made some tests. These are the results: > - seLinux is not the problem (with setenforce 0 the problem is still there) > - the audit2allow command returns me only two white lines (maybe no logging > actived?) From the MAN page : This utility scans the logs for messages logged when the system denied permission for operations, and generates a snippet of policy rules which, if loaded into policy, might have allowed those operations to succeed. So i would assume it's a expected result if you don't run into any config. problem ? > - even if I'm on computer C and try to rsync/scp from the computer S to C the > problem appear. You should take a look @ /var/log/messages or messages-2010xxxx to see if you can find further information, if it's logged there... --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Reassigning to rsync. You might be better off asking on users.org if this is not a bug
In /var/log/messages only appears those lines for the moment in which everything happened: Jan 14 21:12:39 localhost ntpd[1406]: Listening on interface #5 wlan0, 192.168.1.102#123 Enabled Jan 14 21:14:59 localhost dbus: avc: received setenforce notice (enforcing=0) Jan 14 21:14:59 localhost dbus: avc: received setenforce notice (enforcing=0) Jan 14 21:14:59 localhost dbus: Can't send to audit system: USER_AVC avc: received setenforce notice (enforcing=0)#012: exe="?" sauid=81 hostname=? addr=? terminal=? Jan 14 21:17:09 localhost ntpd[1406]: synchronized to 193.109.40.18, stratum 2 Jan 14 21:17:09 localhost ntpd[1406]: kernel time sync status change 2001 Jan 14 21:20:22 localhost kernel: imklog 4.4.2, log source = /proc/kmsg started. Jan 14 21:20:22 localhost kernel: Initializing cgroup subsys cpuset Jan 14 21:20:22 localhost kernel: Initializing cgroup subsys cpu Jan 14 21:20:22 localhost kernel: Linux version 2.6.31.9-174.fc12.i686 (mockbuild.fedoraproject.org) (gcc version 4.4.2 20091027 (Red Hat 4.4.2-7) (GCC) ) #1 SMP Mon Dec 21 06:24:20 UTC 2009 I disabled selinux and after I gived the command 'rsync 192.168.1.150:/home/fale/dati .' but I don't see any trace of this command :(. After a few seconds I had to reboot keeping pushed the button.
I'm sorry, but I didn't manage to reproduce the issue. I suspect there is something wrong with ssh, since not only rsync, but also scp freezes for you. I'm reassigning this to openssh.
There is something seriously broken with your computer and I do not think the ssh/rsync or SELinux is the problem. This looks much more like a broken hardware or a bug in the driver of your network card in the kernel.
On the same computer, using ubuntu 9.10 the problem is not present. I don't think is an hardware issue.
Today I tested again closing amarok... and the error does not occur. Is possible that amarok is creating some conflict?
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I ran into this yesterday in Fedora 14. Both 64 & 32 bit versions have the problem. Ubuntu 10.04 x86_64 on the same hardware does not have the problem. I haven't figured out how to capture useful information about what is causing the problem. I am able to transfer smaller files sometimes (1-10MB), but it always happens with larger files (8GB). I don't know if it is related, but the copy stalls periodically and for no apparent reason restarts until the machine hangs (caps/num lock LEDs won't change) until it is rebooted. I have tried turning off apci & irqbalance with no change in behavior. This is a large problem for me, but I'm not sure if I should adjust the priority of the bug.
Reverting the bug back to Fedora 12 - just discovered that my problem was due to this issue: https://bugzilla.redhat.com/show_bug.cgi?id=538920
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.