Re: Kyum: /var/log/yum.log, could not be opened for reading.
by ron
On Mon, 2006-07-03 at 12:18 -0400, ron wrote:
But I still get:
"/var/log/yum.log could not be opened for reading."
I removed kyum, erased all remaining files, reinstalled kyum,
and set
SELinux to permissive.
But still no luck.
On Mon, 03 Jul 2006 19:16:20 +0100, Paul wrote:
You are running it as root, right?
On Tue, 04 Jul 2006 05:50:00 -0400, ron wrote:
Yes, I'm running as root.
Package management works ok.
Permissions are:
-rw------- 1 root root 25262 Jul 3 13:05 yum.log
-rw-r--r-- 1 root root 30898 May 8 17:13 yum.log.1
On Tue, 04 Jul 2006 11:36:30 +0100, Paul wrote:
Does it work if you change the permissions to 644?
On Tue, 4 Jul 2006 07:37:52 -0400, ron wrote:
No.
On Tue, 04 Jul 2006 14:01:51 +0100, Paul wrote:
OK, how about the parent directory permissions?
# ls -ldZ / /var /var/log
Paul,
the parent directory permissions are:
drwxr-xr-x root root system_u:object_r:root_t /
drwxr-xr-x root root system_u:object_r:var_t /var
drwxr-xr-x root root system_u:object_r:var_log_t /var/log
-ron-
17 years, 11 months
Ping Dave Jones: Serious issues with kernel-2.6.17
by Keith G. Robertson-Turner
Lots of sweeping changes in 2.6.17 that I've read about on kernel dev,
and a few seem to be badly broken.
I realize that this is +UPSTREAM, but regardless, any progress/comments?
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=196556
Also a few networking issues posted on this list.
I'm only anxious for a kernel upgrade in the hope it will solve an issue
with 2.6.16 ACPI poweroff - which it doesn't on my system, currently,
but given the state of 2.6.17, I think I might hold out for the next
major kernel release, before going anywhere near it.
--
K.
http://slated.org - Slated, Rated & Blogged
Fedora Core release 5 (Bordeaux) on sky, running kernel 2.6.16-1.2133_FC5
01:23:01 up 13 days, 1:39, 2 users, load average: 2.80, 2.96, 2.98
17 years, 11 months
httpd, NAT/SUA, router and DynDNS
by Deepak
Hi
I am trying to setup a home web for me to access files from other
locations. I don't know if this is fedora related problems or not.
Anyway my problem is like this:
I am running httpd in my fedora 5 locally in LAN , which I have given
the static address (private 192.168.1.2) for this web server. I am
using ZyXEL Prestige 600 Series DSL Modem Router. I thave already
forward the port 80 and 443 in my router as instructed at
http://www.portforward.com/english/routers/port_forwarding/ZyXEL/Prestige...
But when I try to access my site, it goes to the router's web
configuration page instead of showing the page from my fedora machine.
Do I need to set up anything else? By the way I have already set the
http as trusted service in Selinux setting. Anybody have idea how to
make this thing work?
Thanks
17 years, 11 months
suspend fails the second time
by Louis Garcia
Updated FC5 box suspend fails the second time after reboot. I get this
in log. What is khubd?
kernel: Stopping tasks:
===========================================================================================
Jul 4 22:29:47 soncomputer kernel: stopping tasks timed out after 20
seconds (1 tasks remaining):
Jul 4 22:29:47 soncomputer kernel: khubd
Jul 4 22:29:47 soncomputer kernel: Restarting tasks...<6> Strange,
khubd not stopped
Jul 4 22:29:47 soncomputer kernel: done
17 years, 11 months
FC5 SELinux prevents php from connecting to postgresql
by Clodoaldo Pinto
FC5 SELinux prevents php from connecting to postgresql.
I had a hard time trying to figure out why I could not connect from
php to postgres locally in a new and patched FC5 box, although I could
connect to that same postgres server and with the same user from
another box (FC3).
>From /var/log/messages:
kernel: audit(1151945653.900:39): avc: denied { name_connect } for
pid=17167 comm="httpd" dest=5432 scontext=user_u:system_r:httpd_t:s0
tcontext=system_u:object_r:postgresql_port_t:s0 tclass=tcp_socket
Regards, Clodoaldo Pinto
17 years, 11 months
/dev/root kernel panic: Possible mkinitrd bug?
by Brian Wright
I've experienced the /dev/root kernel panic that a lot of folks have
experienced. I get the following during my boot process:
Trying to resume from /dev/hdc1
No suspend signature on swap, not resuming.
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesustems.
Setting up new foor fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to ew root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: No such file or directory
[<c011a32e>] panic+0x3e/0x170 [<c011cede>] do_exit+0x71/0x6c8
[<c011d5b9>] sys_exit_group+0x0/0xd [<c0102bc1>] syscall_call+0x7/0xb
I'm not using LVMs on my linux drive. It's a 320 gig Western Digital
drive with an 8 gig swap partition and the rest is the root file system.
I'm using lilo v 22.6 on Fedora Core 5 and I've not switched to grub
only because I'm trying to figure out how to migrate from lilo to grub.
My current lilo.conf file:
boot = /dev/hda
timeout = 50
prompt
default = linux
vga = 0x318
read-only
map=/boot/map
install=/boot/boot.b
image = /boot/vmlinuz-2.6.17-1.2139_FC5
label=2.6.17-1.2139_F
append="mem=1024M"
initrd=/boot/initrd-2.6.17-1.2139_FC5.img
root=/dev/hdc2
image = /boot/vmlinuz-2.6.17.3
label=linux
append="mem=1024M"
initrd=/boot/initrd-2.6.17.3.img
root=/dev/hdc2
image = /boot/vmlinuz-2.6.16.19
label=linux-prev
append="mem=1024M"
initrd=/boot/initrd-2.6.16.19.img
root=/dev/hdc2
other = /dev/hda1
label = Windows
Here's my /etc/fstab. /dev/hda is another 320 gig Western Digital hard
drive running Windows XP on VFAT:
/dev/hdc2 / ext3 defaults 1 1
/dev/fd0 mnt/floppy auto user,exec,dev,suid,rw,noauto 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
none /dev/pts devpts gid=5,mode=620 0 0
/dev/hdc1 swap swap defaults
none /sys sysfs defaults 0 0
I did find a solution for it at Linuxquestions.org (see
http://www.linuxquestions.org/questions/showthread.php?t=433048) and I
noticed that in the init file that mkinitrd produces there's a
"mount /sysroot" line that seems to be the source of the problem. It
should be "mount -o defaults --ro -t ext3 /dev/hdc2 /sysroot" but this
doesn't get written out by default. It's trying to mount /dev/root
to /sysroot and /dev/root is apparently deprecated in FC5.
As per the LinuxQuestions thread I've done the following steps:
1) Boot with the rescue CD
2) Type 'chroot /mnt/sysimage' (wherever it mounts the Fedora 5
partition)
3) 'cd /boot'
4) 'mkdir newinit'
5) 'cd newinit'
6) 'gunzip -c ../initrd-2.6.15-1.2054_FC5.img | cpio -idmv'
7) 'vi init'
8) Find 'mount /sysroot' (near the end of the file)
9) Delete or comment this out
10) Replace with 'mount -o defaults --ro -t
ext3 /dev/VolGroup00/LogVol00 /sysroot' where /dev/VolGroup00/LogVol00
is the mount point for /
11) ':wq' out of vi
12) 'find . | cpio --quiet -c -o >../newinitrd'
13) 'cd ..' - you are now in /boot
14) 'mv initrd-2.6.15-1.2054_FC5.img initrd-2.6.15-1.2054_FC5.bak' -
backup current initrd img file (just in case)
15) 'gzip -9 < newinitrd > initrd-2.6.15-1.2054_FC5.img'
16) Reboot the computer without the CD
My init file that's in the initrd image looks like this:
mount -t proc /proc /proc
setquiet
echo Mounting proc filesystem
echo Mounting sysfs filesystem
mount -t sysfs /sys /sys
echo Creating /dev
mount -o mode=0755 -t tmpfs /dev /dev
mkdir /dev/pts
mount -t devpts -o gid=5,mode=620 /dev/pts /dev/pts
mkdir /dev/shm
mkdir /dev/mapper
echo Creating initial device nodes
mknod /dev/null c 1 3
mknod /dev/zero c 1 5
mknod /dev/systty c 4 0
mknod /dev/tty c 5 0
mknod /dev/console c 5 1
mknod /dev/ptmx c 5 2
mknod /dev/rtc c 10 135
mknod /dev/tty0 c 4 0
mknod /dev/tty1 c 4 1
mknod /dev/tty2 c 4 2
mknod /dev/tty3 c 4 3
mknod /dev/tty4 c 4 4
mknod /dev/tty5 c 4 5
mknod /dev/tty6 c 4 6
mknod /dev/tty7 c 4 7
mknod /dev/tty8 c 4 8
mknod /dev/tty9 c 4 9
mknod /dev/tty10 c 4 10
mknod /dev/tty11 c 4 11
mknod /dev/tty12 c 4 12
mknod /dev/ttyS0 c 4 64
mknod /dev/ttyS1 c 4 65
mknod /dev/ttyS2 c 4 66
mknod /dev/ttyS3 c 4 67
echo Setting up hotplug.
hotplug
echo Creating block device nodes.
mkblkdevs
echo "Loading advansys.ko module"
insmod /lib/advansys.ko
mkblkdevs
resume /dev/hdc1
echo Creating root device.
mkrootdev -t ext3 -o defaults,ro /dev/hdc2
echo Mounting root filesystem.
# mount /sysroot
mount -o defaults --ro -t ext3 /dev/hdc2 /sysroot
echo Setting up other filesystems.
setuproot
echo Switching to new root and running init.
switchroot
I'm suspecting that this is caused by a bug in mkinitrd because I first
noticed this when building a custom kernel and when I booted into the
new kernel I got the kernel panic. I have to do the above procedure
every time I build a new kernel and even the kernel RPMs from the Fedora
Core 5 Updates repository will do the same thing.
If there's something that I'm doing wrong I'm still trying to figure out
what it is if mkinitrd is not the issue.
Thanks!,
Brian
17 years, 11 months
yum dumb? Re-installes rpms you specifically remove
by Paul Johnson
My Dell laptop hates the new kernel-2.6.17, so I remove it with yum
remove kernel-2.6....
Then I go about my business and find that the yum cron job has run and
re-downloaded and re-installed that kernel. Goddam.
Then I can put exclude=kernel-2.6.17* in /etc/yum.conf, but the
problem just starts there. When yum runs, it finds updates for kernel
modules on atrpms (for ipw3945 wireless) and livna (video card), and
yum then fails because it cannot install those modules because it
cannot install the new kernel. So I have to go back into
/etc/yum.conf and exclude some specific versions of those modules.
What a hassle.
Seems to me that if a person manually removes something in yum, the
system should respect that.
pj
--
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas
17 years, 11 months
file-copy corruption
by Terry Horsnell
I'm in the process of moving stuff from our Alpha fileserver
onto A linux replacement. I've been using gnu-tar to copy filesystems
from the Alpha to to the Linux NFS-exported disks over a 1Gbit LAN,
followed by diff -r to check that they have copied correctly (I wish
diff had an option to not follow symlinks..). I've so far transferred
about 3 TiB of data (spread over several weeks) and am concerned
that during this process, 3 files were mis-copied without any
apparent hardware-errors being flagged. There was nothing unusual
about these files, and re-copying them (with cp) fixed the problem.
Are occasional undetected errors like this to be expected?
I thought there were sufficient stages of checksumming/parity
(both boxes have ECC memory) etc to render the probability
of this to be vanishingly small.
On all 3 files, multiple retries of the diff still resulted
in a compare error, which was then fixed by a re-copy. This
suggests that the problem occurs during the 'gtar' phase, rather
than the 'diff -r' phase.
Does anyone know of a network-exercise utility I can use
to check the LAN component of the data-path?
Cheers,
Terry.
17 years, 11 months
What is a soft lockup?
by Zac Tolley
I'm running a fc5 box, with a bunch of disks and opennms, which puts
a high workload on the disks. Not running raid.
In /var/logl/messages i get and error like this repeatedl. The box is
a dual xeon and it seems like each cpu in turn shows this error.
what does it mean?
Jul 2 04:00:21 opennms kernel: BUG: soft lockup detected on CPU#2!
Jul 2 04:00:21 opennms kernel: CPU 2:
Jul 2 04:00:21 opennms kernel: Modules linked in: loop ipv6 ppdev
autofs4 hidp rfcomm l2cap bluetooth sunrpc ip_conntrack_netbios_ns
ipt_REJECT xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter
ip_tables x_tables video button battery ac lp parport_pc parport
floppy nvram uhci_hcd ehci_hcd e1000 tg3 hw_random e752x_edac edac_mc
dm_snapshot dm_zero dm_mirror dm_mod ext3 jbd cciss mptspi mptscsih
sd_mod scsi_mod mptbase
Jul 2 04:00:21 opennms kernel: Pid: 27, comm: kblockd/2 Not tainted
2.6.15-1.2054_FC5 #1
Jul 2 04:00:21 opennms kernel: RIP: 0010:[<ffffffff8033b86a>]
<ffffffff8033b86a>{_spin_unlock_irqrestore+11}
Jul 2 04:00:21 opennms kernel: RSP: 0018:ffff81015b435e08 EFLAGS:
00000247
Jul 2 04:00:21 opennms kernel: RAX: 0000000000000002 RBX:
0000000000000247 RCX: ffff81015a4d2850
Jul 2 04:00:21 opennms kernel: RDX: 0000000000000002 RSI:
0000000000000247 RDI: ffff81015a40b3d8
Jul 2 04:00:21 opennms kernel: RBP: ffff81015a4d2938 R08:
ffff81015a4d28a0 R09: ffff81015a4d2800
Jul 2 04:00:21 opennms kernel: R10: 00000000dffe0000 R11:
ffff81015a40b000 R12: ffff81015b4118c0
Jul 2 04:00:21 opennms kernel: R13: 0000000000000247 R14:
ffff81015b028ce8 R15: ffffffff801fd5c7
Jul 2 04:00:21 opennms kernel: FS: 0000000000000000(0000)
GS:ffff81015bf256c0(0000) knlGS:0000000000000000
Jul 2 04:00:21 opennms kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
000000008005003b
Jul 2 04:00:21 opennms kernel: CR2: 00002b78d369f000 CR3:
0000000000101000 CR4: 00000000000006e0
Jul 2 04:00:21 opennms kernel:
Jul 2 04:00:21 opennms kernel: Call Trace: <ffffffff801425e1>
{run_workqueue+159} <ffffffff80142c7a>{worker_thread+0}
Jul 2 04:00:21 opennms kernel: <ffffffff80145ca3>
{keventd_create_kthread+0} <ffffffff80142d83>{worker_thread+265}
Jul 2 04:00:21 opennms kernel: <ffffffff8012959c>
{__wake_up_common+62} <ffffffff8012ad74>{default_wake_function+0}
Jul 2 04:00:21 opennms kernel: <ffffffff80145ca3>
{keventd_create_kthread+0} <ffffffff80145fb6>{kthread+254}
Jul 2 04:00:21 opennms kernel: <ffffffff8010b8e6>{child_rip
+8} <ffffffff80145ca3>{keventd_create_kthread+0}
Jul 2 04:00:21 opennms kernel: <ffffffff80339fce>
{thread_return+0} <ffffffff80145eb8>{kthread+0}
Jul 2 04:00:21 opennms kernel: <ffffffff8010b8de>{child_rip+0}
17 years, 11 months