Fedora 12 clean install with some issues

andyofne · #1 10th February 2010, 01:24 AM

After performing a clean install of F12 on a Dell Optiplex GX280 (Pentium IV 3.2ghz w/hyperthreading enabled, 3.5GB of DDR2 RAM, two 1TB SATA hard drives and an IDE DVD drive) I can get logged in and most everything works normally; however, I can't create SAMBA users, I can't launch the HTTP server configuration GUI and I get some unusual errors in the log file.

I googled the errors and couldn't find much to help. I also searched these forums but can't seem to find a thread that reports the same sort of issues.

Previously, i was running Fedora 9 on the same box and it ran fine. I some times think I should just leave things as they are.

mbratch · #2 10th February 2010, 04:07 AM

Quote:

Originally Posted by andyofne

After performing a clean install of F12 on a Dell Optiplex GX280 (Pentium IV 3.2ghz w/hyperthreading enabled, 3.5GB of DDR2 RAM, two 1TB SATA hard drives and an IDE DVD drive) I can get logged in and most everything works normally; however, I can't create SAMBA users, I can't launch the HTTP server configuration GUI and I get some unusual errors in the log file.

I googled the errors and couldn't find much to help. I also searched these forums but can't seem to find a thread that reports the same sort of issues.

Maybe you could share the error messages with us?

Quote:

Originally Posted by andyofne

Previously, i was running Fedora 9 on the same box and it ran fine. I some times think I should just leave things as they are.

But that would be no fun.

Seriously, I know exactly what you mean. I did something similar: I had a relative comfortable Fedora 8 running and decided to do a clean install of Fedora 12. For a few days I was cursing the day I decided to do that. But then I had a couple of simple breakthroughs and I'm happy now that I'm here. I'm sure it's something simple, it just needs to be pinpointed.

andyofne · #3 10th February 2010, 04:28 AM

Yeah, I was posting that from my windows 7 box while performing a clean reinstall on this computer.

Here is what I see in 'messages' after trying to launch the 'system > administration > server > http':

Feb 9 22:06:57 localhost abrtd: Directory 'ccpp-1265774817-1911' creation detected
Feb 9 22:06:57 localhost abrtd: Lock file '/var/cache/abrt/ccpp-1265774817-1911.lock' is locked by process 1912
Feb 9 22:06:57 localhost abrt: saved core dump of pid 1911 to /var/cache/abrt/ccpp-1265774817-1911/coredump
Feb 9 22:06:58 localhost abrtd: Getting local universal unique identification...
Feb 9 22:06:58 localhost abrtd: New crash, saving...

When I try to set up SAMBA, most of the functions work until I try to add a SAMBA user:

The system seems to freeze for a minute or three, then (this time) i got an SELinux error when trying to add the SAMBA user account:

Summary:

SELinux is preventing /usr/bin/abrt-pyhook-helper "search" access on abrt.

Detailed Description:

SELinux denied access requested by abrt-pyhook-hel. It is not expected that this
access is required by abrt-pyhook-hel and this access may signal an intrusion
attempt. It is also possible that the specific version or configuration of the
application is causing it to require additional access.

Allowing Access:

You can generate a local policy module to allow this access - see FAQ
(http://fedora.redhat.com/docs/selinu...fc5/#id2961385) Please file a bug
report.

Additional Information:

Source Context system_u:system_r:sambagui_t:s0-s0:c0.c1023
Target Context system_u:object_r:abrt_var_cache_t:s0
Target Objects abrt [ dir ]
Source abrt-pyhook-hel
Source Path /usr/bin/abrt-pyhook-helper
Port <Unknown>
Host fedora
Source RPM Packages abrt-addon-python-0.0.11-1.fc12
Target RPM Packages
Policy RPM selinux-policy-3.6.32-41.fc12
Selinux Enabled True
Policy Type targeted
MLS Enabled True
Enforcing Mode Enforcing
Plugin Name catchall
Host Name fedora
Platform Linux fedora 2.6.31.5-127.fc12.i686.PAE #1 SMP Sat
Nov 7 21:25:57 EST 2009 i686 i686
Alert Count 2
First Seen Tue 09 Feb 2010 10:13:51 PM CST
Last Seen Tue 09 Feb 2010 10:13:51 PM CST
Local ID e4768636-3b7d-4cb6-88df-23e6d4481941
Line Numbers

Raw Audit Messages

node=fedora type=AVC msg=audit(1265775231.661:42041): avc: denied { search } for pid=2251 comm="abrt-pyhook-hel" name="abrt" dev=dm-0 ino=2269188 scontext=system_u:system_r:sambagui_t:s0-s0:c0.c1023 tcontext=system_u:object_r:abrt_var_cache_t:s0 tclass=dir

node=fedora type=SYSCALL msg=audit(1265775231.661:42041): arch=40000003 syscall=83 success=no exit=-13 a0=bfe3837e a1=82410cc a2=586890 a3=bfe3836e items=0 ppid=2144 pid=2251 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="abrt-pyhook-hel" exe="/usr/bin/abrt-pyhook-helper" subj=system_u:system_r:sambagui_t:s0-s0:c0.c1023 key=(null)

I can create a SAMBA user from the command line.

---------- Post added at 10:28 PM CST ---------- Previous post was at 10:17 PM CST ----------

Also, I can't apply system updates:

Error Type: <class 'yum.Errors.RepoError'>
Error Value: Error getting repository data for installed, repository not found
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3125, in <module>
main()
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3122, in main
backend.dispatcher(sys.argv[1:])
File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 710, in dispatcher
self.dispatch_command(args[0], args[1:])
File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 657, in dispatch_command
self.update_packages(only_trusted, package_ids)
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1948, in update_packages
signed = self._is_package_repo_signed(pkg)
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1437, in _is_package_repo_signed
repo = self.yumbase.repos.getRepo(pkg.repoid)
File : /usr/lib/python2.6/site-packages/yum/repos.py, line 121, in getRepo
'Error getting repository data for $s, repository not found' $ (repoid)

GoinEasy9 · #4 10th February 2010, 05:34 AM

You could try disabling SELinux, or, if you feel you need the extra security, read up on how to configure it so it allows you to setup functions without throwing off errors. The SELinux Troubleshooter also is a helpful app located in System Tools. There is a great SELinux manual in Fedora Docs. http://docs.fedoraproject.org/selinu...2/html-single/

PackageKit is having problems, try doing yum update as root in terminal. That should get you through System Updates.

andyofne · #5 10th February 2010, 02:58 PM

Quote:

Originally Posted by GoinEasy9

You could try disabling SELinux, or, if you feel you need the extra security, read up on how to configure it so it allows you to setup functions without throwing off errors. The SELinux Troubleshooter also is a helpful app located in System Tools. There is a great SELinux manual in Fedora Docs. http://docs.fedoraproject.org/selinu...2/html-single/

PackageKit is having problems, try doing yum update as root in terminal. That should get you through System Updates.

Thanks, I'll check that when I get home.

I did disable SELINUX on the first install. It made no difference.

I set it to permissive after the second install and it didn't make any difference.

**AdamW** · #6 10th February 2010, 07:33 PM

It must make some difference, because the selinux denial you get for setting up a SAMBA user account can only possibly happen with SELinux active in enforcing mode. It may still not work with selinux disabled, but there must be some other kind of error.

'system > administration > server > http' is crashing on startup. Try running it from a console and see if you get a more useful error message there.

System updates - the error message you pasted isn't quite the right one, we need to know what repository it's having trouble contacting. Someone in another thread seemed to be having trouble reaching the RPM Fusion repo, it may be the same for you; if you have Fusion repos enabled, try disabling them.

andyofne · #7 11th February 2010, 06:27 AM

Well, attempt #5...

Clean install, added the updates.

The system starts booting. The white and blue bar starts going across the screen. Eventually "FEdora 12" shows at the end.

I hit F8 and watch the start up sequence. It goes through to "starting atd". Then the screen flashes a few times and nothing else seems to happen. After a couple of minutes a half cursor starts blinking at the upper left corner of the screen and just continues to blink.

I've been running RedHat since 5.1 and virtually every version of Fedora through F10. I used to think I knew what I was doing but I'm beginning to realize that I don't.

EDIT

Booting to single user mode I get an error right off the bat about the Radeon video drivers. Nice.

---------- Post added 2010-02-11 at 12:27 AM CST ---------- Previous post was 2010-02-10 at 11:43 PM CST ----------

Removing the PCIe video card, a Radeon X700, resolved the loading issue.

Disabling SELINUX still makes no difference. I cannot launch the HTTP server GUI config tool nor can I add SAMBA users.

I think I'm going to give up on F12 and install Win7 on the box. This is far too much work just to get things up and running.

Thanks for the help.

andyofne · #8 12th February 2010, 01:58 AM

I haven't quite given up yet. This seems to be an SELinux issue and I can't figure out what to do about it.

It's possible that this bug is related: https://bugzilla.redhat.com/show_bug.cgi?id=499183

How do I apply the patch?

---------- Post added at 07:58 PM CST ---------- Previous post was at 07:40 PM CST ----------

The latest errors when tryping to launch the server config . http gui

Code:

Feb 11 19:51:36 localhost setroubleshoot: SELinux not enabled, setroubleshootd exiting...
Feb 11 19:51:39 localhost pulseaudio[1605]: ratelimit.c: 3 events suppressed
Feb 11 19:53:18 localhost abrtd: Directory 'ccpp-1265939598-2805' creation detected
Feb 11 19:53:18 localhost abrtd: Lock file '/var/cache/abrt/ccpp-1265939598-2805.lock' is locked by process 2806
Feb 11 19:53:18 localhost abrt[2806]: saved core dump of pid 2805 (/usr/bin/python) to /var/cache/abrt/ccpp-1265939598-2805/coredump 
(9527296 bytes)
Feb 11 19:53:19 localhost abrtd: Getting local universal unique identification...
Feb 11 19:53:19 localhost abrtd: Crash is in database already
Feb 11 19:53:19 localhost abrtd: Already saved crash, just sending dbus signal
Feb 11 19:54:44 localhost abrtd: Directory 'ccpp-1265939684-2821' creation detected
Feb 11 19:54:44 localhost abrtd: Lock file '/var/cache/abrt/ccpp-1265939684-2821.lock' is locked by process 2822
Feb 11 19:54:45 localhost abrt[2822]: saved core dump of pid 2821 (/usr/bin/python) to /var/cache/abrt/ccpp-1265939684-2821/coredump 
(9527296 bytes)
Feb 11 19:54:46 localhost abrtd: Getting local universal unique identification...
Feb 11 19:54:46 localhost abrtd: Crash is in database already
Feb 11 19:54:46 localhost abrtd: Already saved crash, just sending dbus signal

And this comes from trying to add a SAMBA user.

Code:

Feb 11 19:56:26 localhost python: abrt: detected unhandled Python exception in /usr/share/system-config-samba/system-config-samba-mec
hanism.py
Feb 11 19:56:26 localhost abrtd: Directory 'pyhook-1265939786-2887' creation detected
Feb 11 19:56:26 localhost abrtd: Lock file '/var/cache/abrt/pyhook-1265939786-2887.lock' is locked by process 2898
Feb 11 19:56:26 localhost abrt[2898]: saved python crash dump of pid 2887 to /var/cache/abrt/pyhook-1265939786-2887
Feb 11 19:56:28 localhost abrtd: Crash is in database already
Feb 11 19:56:28 localhost abrtd: Already saved crash, just sending dbus signal

andyofne · #9 12th February 2010, 07:48 PM

Please disregard this thread. I can't seem to find a solution in a timely fashion and I'd like to get the machine back in action so I'm abandoning the effort to run Fedora 12 on this particular computer.

I'll either go back to F9, which worked flawlessly on this system, or try CentOS.

Thanks again for the replies.

**AdamW** · #10 12th February 2010, 11:34 PM

Both of those just look like straight crashes in the tools. In both cases abrt kicked in, so it should have popped up a tray icon to notify you of the crash and offer to send a bug report. Filling that in would be the way forward.

andyofne · #11 13th February 2010, 04:55 AM

Quote:

Originally Posted by AdamW

Both of those just look like straight crashes in the tools. In both cases abrt kicked in, so it should have popped up a tray icon to notify you of the crash and offer to send a bug report. Filling that in would be the way forward.

It crashes every time but doesn't notify me of the crash or the bug report.

Someone suggested I may have a hardware problem. I just don't know. I did burn a new DVD ISO of 12 and I might try that before trying CentOS.

Alternatively, and less to my liking, I have another machine I can use. It's a little older and slower but it has SATA ports so I can use the 2 1TB drives.

---------- Post added at 10:55 PM CST ---------- Previous post was at 05:37 PM CST ----------

I tried a different Fedora 12 DVD ISO burned on my work computer but it failed, too.

I backed down to Fedora 10, installed with all the updates selected, and it's working perfectly.

Everything seems to be fine. I'm happy but I'm still curious why F12 wouldn't run properly.