Discuss April 2014

discuss@lists.centos.org

172 participants
141 discussions

Re: [CentOS] Removing a file that starts with dashes
by benfell＠parts-unknown.org 03 Apr '14

03 Apr '14

On Wed, Apr 02, 2014 at 11:17:02PM +0200, Reindl Harald wrote: > > WTF - there is a reason the "-f" flag exists - RTFM > I don't know what manual you're reading. But -f has a specific function and *this* *isn't* *it*. -- David Benfell <benfell(a)parts-unknown.org> See https://parts-unknown.org/node/2 if you don't understand the attachment.

3 6

Setup a devel environment for perl modules
by C. L. Martinez 03 Apr '14

03 Apr '14

Hi all, This is an interesting thread: http://lists.centos.org/pipermail/centos/2014-April/141871.html about the problems you can find building perl modules for CentOS releases (new or old). I agree with John R. Pierce: cpan is very very bad tool ( in fact, I hate it) to build perl modules for CentOS systems, breaks all other perl modules. I need to use several perl modules in several servers in my dept. and after some tests, I migrate to FreeBSD due to easy install perl modules with poudriere suite. But, anyone knows if it is possible to build a confident devel environment under CentOS with some tool to build rpm's perl modules without breaking anything in CentOS systems?? Maybe, it is a good idea to create a CentOS Perl SIG :)) Thanks.

6 9

random crashes
by John R Pierce 02 Apr '14

02 Apr '14

I have a server thats been running fine for a year or two lock up a few times recently, requiring power cycling. The /var/log/messages after a lockup last night is appended to this message. hardware is a pretty typical server, Supermicro X8DTE-F motherboard, dual Xeon X5650, 48GB ECC memory, LSI SAS 2008 for the boot disks, and LSI MegaRAID SAS 9261-8i for the data volume. Lots of 3TB disks in a raid60. Primary application is BackupPC v3.3.0 (from EPEL), it also has an NFS export (also used for backup purposes). Runs CentOS 6.latest (kernel 2.6.32-431.11.2.el6.x86_64). X is not loaded (inittab level 3). selinux is permissive, iptables is not loaded. this server is on a corporate internal network, 1 Intel 82574L NIC configured with static IP, 2nd one is not in use. any clues what to try? I'm hesitant to enable irqpoll as I hear that it is a real performance sucker. (quiet for a day+ except for an nfs umount 6 hours prior to this crash) Apr 1 21:19:23 sg1 kernel: irq 70: nobody cared (try booting with the "irqpoll" option) Apr 1 21:19:23 sg1 kernel: Pid: 0, comm: swapper Not tainted 2.6.32-431.11.2.el6.x86_64 #1 Apr 1 21:19:23 sg1 kernel: Call Trace: Apr 1 21:19:23 sg1 kernel: <IRQ> [<ffffffff810e8fdb>] ? __report_bad_irq+0x2b/0xa0 Apr 1 21:19:23 sg1 kernel: [<ffffffff810e91dc>] ? note_interrupt+0x18c/0x1d0 Apr 1 21:19:23 sg1 kernel: [<ffffffff810e9825>] ? handle_edge_irq+0xf5/0x180 Apr 1 21:19:23 sg1 kernel: [<ffffffff8100faf9>] ? handle_irq+0x49/0xa0 Apr 1 21:19:23 sg1 kernel: [<ffffffff815315fc>] ? do_IRQ+0x6c/0xf0 Apr 1 21:19:23 sg1 kernel: [<ffffffff8100b9d3>] ? ret_from_intr+0x0/0x11 Apr 1 21:19:23 sg1 kernel: <EOI> [<ffffffff812e0bee>] ? intel_idle+0xde/0x170 Apr 1 21:19:23 sg1 kernel: [<ffffffff812e0bd1>] ? intel_idle+0xc1/0x170 Apr 1 21:19:23 sg1 kernel: [<ffffffff81426b67>] ? cpuidle_idle_call+0xa7/0x140 Apr 1 21:19:23 sg1 kernel: [<ffffffff81009fc6>] ? cpu_idle+0xb6/0x110 Apr 1 21:19:23 sg1 kernel: [<ffffffff8152143c>] ? start_secondary+0x2ac/0x2ef Apr 1 21:19:23 sg1 kernel: handlers: Apr 1 21:19:23 sg1 kernel: [<ffffffffa01bd260>] (e1000_msix_other+0x0/0x1f0 [e1000e]) Apr 1 21:19:23 sg1 kernel: Disabling IRQ #70 Apr 1 21:19:24 sg1 abrt-dump-oops: Reported 1 kernel oopses to Abrt Apr 1 21:19:24 sg1 abrtd: Directory 'oops-2014-04-01-21:19:24-7042-1' creation detected Apr 1 21:19:25 sg1 abrtd: Can't open file '/var/spool/abrt/oops-2014-04-01-21:19:24-7042-1/uid': No such file or directory Apr 1 21:19:30 sg1 kernel: Bridge firewalling registered Apr 1 21:22:58 sg1 kernel: INFO: task crond:11598 blocked for more than 120 seconds. Apr 1 21:22:58 sg1 kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1 Apr 1 21:22:58 sg1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 1 21:22:58 sg1 kernel: crond D 0000000000000008 0 11598 7120 0x00000080 Apr 1 21:22:58 sg1 kernel: ffff88011257bd38 0000000000000086 0000000000000000 0000000000000000 Apr 1 21:22:58 sg1 kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Apr 1 21:22:58 sg1 kernel: ffff88063208dab8 ffff88011257bfd8 000000000000fbc8 ffff88063208dab8 Apr 1 21:22:58 sg1 kernel: Call Trace: Apr 1 21:22:58 sg1 kernel: [<ffffffff81528dd5>] schedule_timeout+0x215/0x2e0 Apr 1 21:22:58 sg1 kernel: [<ffffffff81330968>] ? extract_entropy+0x108/0x1f0 Apr 1 21:22:58 sg1 kernel: [<ffffffff81528a53>] wait_for_common+0x123/0x180 Apr 1 21:22:58 sg1 kernel: [<ffffffff81065df0>] ? default_wake_function+0x0/0x20 Apr 1 21:22:58 sg1 kernel: [<ffffffff81528b6d>] wait_for_completion+0x1d/0x20 Apr 1 21:22:58 sg1 kernel: [<ffffffff81097108>] synchronize_sched+0x58/0x60 Apr 1 21:22:58 sg1 kernel: [<ffffffff81097090>] ? wakeme_after_rcu+0x0/0x20 Apr 1 21:22:58 sg1 kernel: [<ffffffff812229dc>] install_session_keyring_to_cred+0x6c/0xd0 Apr 1 21:22:58 sg1 kernel: [<ffffffff81222b73>] join_session_keyring+0x133/0x160 Apr 1 21:22:58 sg1 kernel: [<ffffffff810e2057>] ? audit_syscall_entry+0x1d7/0x200 Apr 1 21:22:58 sg1 kernel: [<ffffffff81221778>] keyctl_join_session_keyring+0x38/0x70 Apr 1 21:22:58 sg1 kernel: [<ffffffff812223a0>] sys_keyctl+0x170/0x190 Apr 1 21:22:58 sg1 kernel: [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b Apr 1 21:24:58 sg1 kernel: INFO: task crond:11598 blocked for more than 120 seconds. Apr 1 21:24:58 sg1 kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1 Apr 1 21:24:58 sg1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 1 21:24:58 sg1 kernel: crond D 0000000000000008 0 11598 7120 0x00000080 Apr 1 21:24:58 sg1 kernel: ffff88011257bd38 0000000000000086 0000000000000000 0000000000000000 Apr 1 21:24:58 sg1 kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Apr 1 21:24:58 sg1 kernel: ffff88063208dab8 ffff88011257bfd8 000000000000fbc8 ffff88063208dab8 Apr 1 21:24:58 sg1 kernel: Call Trace: Apr 1 21:24:58 sg1 kernel: [<ffffffff81528dd5>] schedule_timeout+0x215/0x2e0 Apr 1 21:24:58 sg1 kernel: [<ffffffff81330968>] ? extract_entropy+0x108/0x1f0 Apr 1 21:24:58 sg1 kernel: [<ffffffff81528a53>] wait_for_common+0x123/0x180 Apr 1 21:24:58 sg1 kernel: [<ffffffff81065df0>] ? default_wake_function+0x0/0x20 Apr 1 21:24:58 sg1 kernel: [<ffffffff81528b6d>] wait_for_completion+0x1d/0x20 Apr 1 21:24:58 sg1 kernel: [<ffffffff81097108>] synchronize_sched+0x58/0x60 Apr 1 21:24:58 sg1 kernel: [<ffffffff81097090>] ? wakeme_after_rcu+0x0/0x20 Apr 1 21:24:58 sg1 kernel: [<ffffffff812229dc>] install_session_keyring_to_cred+0x6c/0xd0 Apr 1 21:24:58 sg1 kernel: [<ffffffff81222b73>] join_session_keyring+0x133/0x160 Apr 1 21:24:58 sg1 kernel: [<ffffffff810e2057>] ? audit_syscall_entry+0x1d7/0x200 Apr 1 21:24:58 sg1 kernel: [<ffffffff81221778>] keyctl_join_session_keyring+0x38/0x70 Apr 1 21:24:58 sg1 kernel: [<ffffffff812223a0>] sys_keyctl+0x170/0x190 Apr 1 21:24:58 sg1 kernel: [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b Apr 1 21:26:58 sg1 kernel: INFO: task crond:11598 blocked for more than 120 seconds. Apr 1 21:26:58 sg1 kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1 Apr 1 21:26:58 sg1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 1 21:26:58 sg1 kernel: crond D 0000000000000008 0 11598 7120 0x00000080 Apr 1 21:26:58 sg1 kernel: ffff88011257bd38 0000000000000086 0000000000000000 0000000000000000 Apr 1 21:26:58 sg1 kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Apr 1 21:26:58 sg1 kernel: ffff88063208dab8 ffff88011257bfd8 000000000000fbc8 ffff88063208dab8 Apr 1 21:26:58 sg1 kernel: Call Trace: Apr 1 21:26:58 sg1 kernel: [<ffffffff81528dd5>] schedule_timeout+0x215/0x2e0 Apr 1 21:26:58 sg1 kernel: [<ffffffff81330968>] ? extract_entropy+0x108/0x1f0 Apr 1 21:26:58 sg1 kernel: [<ffffffff81528a53>] wait_for_common+0x123/0x180 Apr 1 21:26:58 sg1 kernel: [<ffffffff81065df0>] ? default_wake_function+0x0/0x20 Apr 1 21:26:58 sg1 kernel: [<ffffffff81528b6d>] wait_for_completion+0x1d/0x20 Apr 1 21:26:58 sg1 kernel: [<ffffffff81097108>] synchronize_sched+0x58/0x60 Apr 1 21:26:58 sg1 kernel: [<ffffffff81097090>] ? wakeme_after_rcu+0x0/0x20 Apr 1 21:26:58 sg1 kernel: [<ffffffff812229dc>] install_session_keyring_to_cred+0x6c/0xd0 Apr 1 21:26:58 sg1 kernel: [<ffffffff81222b73>] join_session_keyring+0x133/0x160 Apr 1 21:26:58 sg1 kernel: [<ffffffff810e2057>] ? audit_syscall_entry+0x1d7/0x200 Apr 1 21:26:58 sg1 kernel: [<ffffffff81221778>] keyctl_join_session_keyring+0x38/0x70 Apr 1 21:26:58 sg1 kernel: [<ffffffff812223a0>] sys_keyctl+0x170/0x190 Apr 1 21:26:58 sg1 kernel: [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b Apr 1 21:28:58 sg1 kernel: INFO: task crond:11598 blocked for more than 120 seconds. Apr 1 21:28:58 sg1 kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1 Apr 1 21:28:58 sg1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 1 21:28:58 sg1 kernel: crond D 0000000000000008 0 11598 7120 0x00000080 Apr 1 21:28:58 sg1 kernel: ffff88011257bd38 0000000000000086 0000000000000000 0000000000000000 Apr 1 21:28:58 sg1 kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Apr 1 21:28:58 sg1 kernel: ffff88063208dab8 ffff88011257bfd8 000000000000fbc8 ffff88063208dab8 Apr 1 21:28:58 sg1 kernel: Call Trace: Apr 1 21:28:58 sg1 kernel: [<ffffffff81528dd5>] schedule_timeout+0x215/0x2e0 Apr 1 21:28:58 sg1 kernel: [<ffffffff81330968>] ? extract_entropy+0x108/0x1f0 Apr 1 21:28:58 sg1 kernel: [<ffffffff81528a53>] wait_for_common+0x123/0x180 Apr 1 21:28:58 sg1 kernel: [<ffffffff81065df0>] ? default_wake_function+0x0/0x20 Apr 1 21:28:58 sg1 kernel: [<ffffffff81528b6d>] wait_for_completion+0x1d/0x20 Apr 1 21:28:58 sg1 kernel: [<ffffffff81097108>] synchronize_sched+0x58/0x60 Apr 1 21:28:58 sg1 kernel: [<ffffffff81097090>] ? wakeme_after_rcu+0x0/0x20 Apr 1 21:28:58 sg1 kernel: [<ffffffff812229dc>] install_session_keyring_to_cred+0x6c/0xd0 Apr 1 21:28:58 sg1 kernel: [<ffffffff81222b73>] join_session_keyring+0x133/0x160 Apr 1 21:28:58 sg1 kernel: [<ffffffff810e2057>] ? audit_syscall_entry+0x1d7/0x200 Apr 1 21:28:58 sg1 kernel: [<ffffffff81221778>] keyctl_join_session_keyring+0x38/0x70 Apr 1 21:28:58 sg1 kernel: [<ffffffff812223a0>] sys_keyctl+0x170/0x190 Apr 1 21:28:58 sg1 kernel: [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b Apr 1 21:30:58 sg1 kernel: INFO: task crond:11598 blocked for more than 120 seconds. Apr 1 21:30:58 sg1 kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1 Apr 1 21:30:58 sg1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 1 21:30:58 sg1 kernel: crond D 0000000000000008 0 11598 7120 0x00000080 Apr 1 21:30:58 sg1 kernel: ffff88011257bd38 0000000000000086 0000000000000000 0000000000000000 Apr 1 21:30:58 sg1 kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Apr 1 21:30:58 sg1 kernel: ffff88063208dab8 ffff88011257bfd8 000000000000fbc8 ffff88063208dab8 Apr 1 21:30:58 sg1 kernel: Call Trace: Apr 1 21:30:58 sg1 kernel: [<ffffffff81528dd5>] schedule_timeout+0x215/0x2e0 Apr 1 21:30:58 sg1 kernel: [<ffffffff81330968>] ? extract_entropy+0x108/0x1f0 Apr 1 21:30:58 sg1 kernel: [<ffffffff81528a53>] wait_for_common+0x123/0x180 Apr 1 21:30:58 sg1 kernel: [<ffffffff81065df0>] ? default_wake_function+0x0/0x20 Apr 1 21:30:58 sg1 kernel: [<ffffffff81528b6d>] wait_for_completion+0x1d/0x20 Apr 1 21:30:58 sg1 kernel: [<ffffffff81097108>] synchronize_sched+0x58/0x60 Apr 1 21:30:58 sg1 kernel: [<ffffffff81097090>] ? wakeme_after_rcu+0x0/0x20 Apr 1 21:30:58 sg1 kernel: [<ffffffff812229dc>] install_session_keyring_to_cred+0x6c/0xd0 Apr 1 21:30:58 sg1 kernel: [<ffffffff81222b73>] join_session_keyring+0x133/0x160 Apr 1 21:30:58 sg1 kernel: [<ffffffff810e2057>] ? audit_syscall_entry+0x1d7/0x200 Apr 1 21:30:58 sg1 kernel: [<ffffffff81221778>] keyctl_join_session_keyring+0x38/0x70 Apr 1 21:30:58 sg1 kernel: [<ffffffff812223a0>] sys_keyctl+0x170/0x190 Apr 1 21:30:58 sg1 kernel: [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b Apr 1 21:32:58 sg1 kernel: INFO: task crond:11598 blocked for more than 120 seconds. Apr 1 21:32:58 sg1 kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1 Apr 1 21:32:58 sg1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 1 21:32:58 sg1 kernel: crond D 0000000000000008 0 11598 7120 0x00000080 Apr 1 21:32:58 sg1 kernel: ffff88011257bd38 0000000000000086 0000000000000000 0000000000000000 Apr 1 21:32:58 sg1 kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Apr 1 21:32:58 sg1 kernel: ffff88063208dab8 ffff88011257bfd8 000000000000fbc8 ffff88063208dab8 Apr 1 21:32:58 sg1 kernel: Call Trace: Apr 1 21:32:58 sg1 kernel: [<ffffffff81528dd5>] schedule_timeout+0x215/0x2e0 Apr 1 21:32:58 sg1 kernel: [<ffffffff81330968>] ? extract_entropy+0x108/0x1f0 Apr 1 21:32:58 sg1 kernel: [<ffffffff81528a53>] wait_for_common+0x123/0x180 Apr 1 21:32:58 sg1 kernel: [<ffffffff81065df0>] ? default_wake_function+0x0/0x20 Apr 1 21:32:58 sg1 kernel: [<ffffffff81528b6d>] wait_for_completion+0x1d/0x20 Apr 1 21:32:58 sg1 kernel: [<ffffffff81097108>] synchronize_sched+0x58/0x60 Apr 1 21:32:58 sg1 kernel: [<ffffffff81097090>] ? wakeme_after_rcu+0x0/0x20 Apr 1 21:32:58 sg1 kernel: [<ffffffff812229dc>] install_session_keyring_to_cred+0x6c/0xd0 Apr 1 21:32:58 sg1 kernel: [<ffffffff81222b73>] join_session_keyring+0x133/0x160 Apr 1 21:32:58 sg1 kernel: [<ffffffff810e2057>] ? audit_syscall_entry+0x1d7/0x200 Apr 1 21:32:58 sg1 kernel: [<ffffffff81221778>] keyctl_join_session_keyring+0x38/0x70 Apr 1 21:32:58 sg1 kernel: [<ffffffff812223a0>] sys_keyctl+0x170/0x190 Apr 1 21:32:58 sg1 kernel: [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b Apr 1 21:32:58 sg1 kernel: INFO: task crond:11601 blocked for more than 120 seconds. Apr 1 21:32:58 sg1 kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1 Apr 1 21:32:58 sg1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 1 21:32:58 sg1 kernel: crond D 0000000000000008 0 11601 7120 0x00000080 Apr 1 21:32:58 sg1 kernel: ffff880102599d38 0000000000000082 0000000000000000 0000000000000000 Apr 1 21:32:58 sg1 kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Apr 1 21:32:58 sg1 kernel: ffff880633393058 ffff880102599fd8 000000000000fbc8 ffff880633393058 Apr 1 21:32:58 sg1 kernel: Call Trace: Apr 1 21:32:58 sg1 kernel: [<ffffffff81528dd5>] schedule_timeout+0x215/0x2e0 Apr 1 21:32:58 sg1 kernel: [<ffffffff81330968>] ? extract_entropy+0x108/0x1f0 Apr 1 21:32:58 sg1 kernel: [<ffffffff81528a53>] wait_for_common+0x123/0x180 Apr 1 21:32:58 sg1 kernel: [<ffffffff81065df0>] ? default_wake_function+0x0/0x20 Apr 1 21:32:58 sg1 kernel: [<ffffffff81528b6d>] wait_for_completion+0x1d/0x20 Apr 1 21:32:58 sg1 kernel: [<ffffffff81097108>] synchronize_sched+0x58/0x60 Apr 1 21:32:58 sg1 kernel: [<ffffffff81097090>] ? wakeme_after_rcu+0x0/0x20 Apr 1 21:32:58 sg1 kernel: [<ffffffff812229dc>] install_session_keyring_to_cred+0x6c/0xd0 Apr 1 21:32:58 sg1 kernel: [<ffffffff81222b73>] join_session_keyring+0x133/0x160 Apr 1 21:32:58 sg1 kernel: [<ffffffff810e2057>] ? audit_syscall_entry+0x1d7/0x200 Apr 1 21:32:58 sg1 kernel: [<ffffffff81221778>] keyctl_join_session_keyring+0x38/0x70 Apr 1 21:32:58 sg1 kernel: [<ffffffff812223a0>] sys_keyctl+0x170/0x190 Apr 1 21:32:58 sg1 kernel: [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b Apr 1 21:34:58 sg1 kernel: INFO: task crond:11598 blocked for more than 120 seconds. Apr 1 21:34:58 sg1 kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1 Apr 1 21:34:58 sg1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 1 21:34:58 sg1 kernel: crond D 0000000000000008 0 11598 7120 0x00000080 Apr 1 21:34:58 sg1 kernel: ffff88011257bd38 0000000000000086 0000000000000000 0000000000000000 Apr 1 21:34:58 sg1 kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Apr 1 21:34:58 sg1 kernel: ffff88063208dab8 ffff88011257bfd8 000000000000fbc8 ffff88063208dab8 Apr 1 21:34:58 sg1 kernel: Call Trace: Apr 1 21:34:58 sg1 kernel: [<ffffffff81528dd5>] schedule_timeout+0x215/0x2e0 Apr 1 21:34:58 sg1 kernel: [<ffffffff81330968>] ? extract_entropy+0x108/0x1f0 Apr 1 21:34:58 sg1 kernel: [<ffffffff81528a53>] wait_for_common+0x123/0x180 Apr 1 21:34:58 sg1 kernel: [<ffffffff81065df0>] ? default_wake_function+0x0/0x20 Apr 1 21:34:58 sg1 kernel: [<ffffffff81528b6d>] wait_for_completion+0x1d/0x20 Apr 1 21:34:58 sg1 kernel: [<ffffffff81097108>] synchronize_sched+0x58/0x60 Apr 1 21:34:58 sg1 kernel: [<ffffffff81097090>] ? wakeme_after_rcu+0x0/0x20 Apr 1 21:34:58 sg1 kernel: [<ffffffff812229dc>] install_session_keyring_to_cred+0x6c/0xd0 Apr 1 21:34:58 sg1 kernel: [<ffffffff81222b73>] join_session_keyring+0x133/0x160 Apr 1 21:34:58 sg1 kernel: [<ffffffff810e2057>] ? audit_syscall_entry+0x1d7/0x200 Apr 1 21:34:58 sg1 kernel: [<ffffffff81221778>] keyctl_join_session_keyring+0x38/0x70 Apr 1 21:34:58 sg1 kernel: [<ffffffff812223a0>] sys_keyctl+0x170/0x190 Apr 1 21:34:58 sg1 kernel: [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b Apr 1 21:34:58 sg1 kernel: INFO: task crond:11601 blocked for more than 120 seconds. Apr 1 21:34:58 sg1 kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1 Apr 1 21:34:58 sg1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 1 21:34:58 sg1 kernel: crond D 0000000000000008 0 11601 7120 0x00000080 Apr 1 21:34:58 sg1 kernel: ffff880102599d38 0000000000000082 0000000000000000 0000000000000000 Apr 1 21:34:58 sg1 kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Apr 1 21:34:58 sg1 kernel: ffff880633393058 ffff880102599fd8 000000000000fbc8 ffff880633393058 Apr 1 21:34:58 sg1 kernel: Call Trace: Apr 1 21:34:58 sg1 kernel: [<ffffffff81528dd5>] schedule_timeout+0x215/0x2e0 Apr 1 21:34:58 sg1 kernel: [<ffffffff81330968>] ? extract_entropy+0x108/0x1f0 Apr 1 21:34:58 sg1 kernel: [<ffffffff81528a53>] wait_for_common+0x123/0x180 Apr 1 21:34:58 sg1 kernel: [<ffffffff81065df0>] ? default_wake_function+0x0/0x20 Apr 1 21:34:58 sg1 kernel: [<ffffffff81528b6d>] wait_for_completion+0x1d/0x20 Apr 1 21:34:58 sg1 kernel: [<ffffffff81097108>] synchronize_sched+0x58/0x60 Apr 1 21:34:58 sg1 kernel: [<ffffffff81097090>] ? wakeme_after_rcu+0x0/0x20 Apr 1 21:34:58 sg1 kernel: [<ffffffff812229dc>] install_session_keyring_to_cred+0x6c/0xd0 Apr 1 21:34:58 sg1 kernel: [<ffffffff81222b73>] join_session_keyring+0x133/0x160 Apr 1 21:34:58 sg1 kernel: [<ffffffff810e2057>] ? audit_syscall_entry+0x1d7/0x200 Apr 1 21:34:58 sg1 kernel: [<ffffffff81221778>] keyctl_join_session_keyring+0x38/0x70 Apr 1 21:34:58 sg1 kernel: [<ffffffff812223a0>] sys_keyctl+0x170/0x190 Apr 1 21:34:58 sg1 kernel: [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b Apr 1 21:36:58 sg1 kernel: INFO: task crond:11598 blocked for more than 120 seconds. Apr 1 21:36:58 sg1 kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1 Apr 1 21:36:58 sg1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 1 21:36:58 sg1 kernel: crond D 0000000000000008 0 11598 7120 0x00000080 Apr 1 21:36:58 sg1 kernel: ffff88011257bd38 0000000000000086 0000000000000000 0000000000000000 Apr 1 21:36:58 sg1 kernel: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Apr 1 21:36:58 sg1 kernel: ffff88063208dab8 ffff88011257bfd8 000000000000fbc8 ffff88063208dab8 Apr 1 21:36:58 sg1 kernel: Call Trace: Apr 1 21:36:58 sg1 kernel: [<ffffffff81528dd5>] schedule_timeout+0x215/0x2e0 Apr 1 21:36:58 sg1 kernel: [<ffffffff81330968>] ? extract_entropy+0x108/0x1f0 Apr 1 21:36:58 sg1 kernel: [<ffffffff81528a53>] wait_for_common+0x123/0x180 Apr 1 21:36:58 sg1 kernel: [<ffffffff81065df0>] ? default_wake_function+0x0/0x20 Apr 1 21:36:58 sg1 kernel: [<ffffffff81528b6d>] wait_for_completion+0x1d/0x20 Apr 1 21:36:58 sg1 kernel: [<ffffffff81097108>] synchronize_sched+0x58/0x60 Apr 1 21:36:58 sg1 kernel: [<ffffffff81097090>] ? wakeme_after_rcu+0x0/0x20 Apr 1 21:36:58 sg1 kernel: [<ffffffff812229dc>] install_session_keyring_to_cred+0x6c/0xd0 Apr 1 21:36:58 sg1 kernel: [<ffffffff81222b73>] join_session_keyring+0x133/0x160 Apr 1 21:36:58 sg1 kernel: [<ffffffff810e2057>] ? audit_syscall_entry+0x1d7/0x200 Apr 1 21:36:58 sg1 kernel: [<ffffffff81221778>] keyctl_join_session_keyring+0x38/0x70 Apr 1 21:36:58 sg1 kernel: [<ffffffff812223a0>] sys_keyctl+0x170/0x190 Apr 1 21:36:58 sg1 kernel: [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b (at 10:57pm, I power cycle it) Apr 1 22:57:43 sg1 kernel: imklog 5.8.10, log source = /proc/kmsg started. Apr 1 22:57:43 sg1 rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="2232" x-info="http://www.rsyslog.com"] start Apr 1 22:57:43 sg1 kernel: Initializing cgroup subsys cpuset Apr 1 22:57:43 sg1 kernel: Initializing cgroup subsys cpu Apr 1 22:57:43 sg1 kernel: Linux version 2.6.32-431.11.2.el6.x86_64 (mockbuild(a)c6b8.bsys.dev.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-4) (GCC) ) #1 SMP Tue Mar 25 19:59:55 UTC 2014 Apr 1 22:57:43 sg1 kernel: Command line: ro root=/dev/mapper/vg_sg1-lv_root rd_NO_LUKS rd_LVM_LV=vg_sg1/lv_root rd_LVM_LV=vg_sg1/lv_swap r d_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto rhgb quiet rd_NO_DM LANG=en_US.UTF-8 ...... -- john r pierce 37N 122W somewhere on the middle of the left coast

4 6

OT: trac problems
by m.roth＠5-cent.us 02 Apr '14

02 Apr '14

I installed trac. I installed trac-agilo-plugin. Set it up (allegedly). I've made myself an admin. But: I can search in trac for agilo, I find a quick start guide... and it tells me to click the admin button on the toolbar. I don't see any. If I click the admin in the upper right, I get a file not found! I also note that the trac-agilo-plugin installs, among many other files, /usr/bin/create_agilo_project, but I don't know what it does (why would you write a manpage, I mean, really?) And no, doing a search inside of trac finds zip on that command. Clues? Clues for the poor? mark

2 2

Booting OpenBSD with pxelinux
by Paul Heinlein 02 Apr '14

02 Apr '14

I've got PXE/TFTP setup for various Linux distributions and some utilities (clonezilla, dban, etc). I'm now starting in on OpenBSD. As far as I've been able to figure out via internet searches, pxelinux (from the syslinux package) is unable to pass control of a machine directly to a BSD kernel. Instead, you have to use the BSD-supplied 'pxeboot' loader. The naming conventions enforced by pxelinux mean that pxeboot must be called pxeboot.0. Here's a simplified view of my tftpboot directory: etc/ `-- boot.conf images/openbsd/ `-- 5.4 | -- amd64 | | -- bsd | `-- pxeboot.0 `-- i386 | -- bsd `-- pxeboot.0 And here's a relevent snippet of my PXE menu file: LABEL openbsd-5.4.amd64 MENU LABEL OpenBSD 5.4 amd64 KERNEL images/openbsd/5.4/amd64/pxeboot.0 So far so good. If I boot the image listed above, I get the BSD boot loader -- but, and this is the crux of my question, afaict I have to type the location of the actual kernel manually: boot> boot images/openbsd/5.4/amd64/bsd After I type that, the OpenBSD installation kernel boots without a hitch. But manually typing the kernel path is prone to error, and it's not scriptable. It appears that you can have one (and only one!) boot.conf file from which pxeboot can get some directions. Since I want to be able to serve up at least two different images (32- and 64-bits), I can't specify a kernel in boot.conf. The best I can do is print a banner, e.g., echo ********************************************************** echo The OpenBSD pxeboot utility cannot be passed an alterative echo kernel path. So you'll have to issue one of the following echo commands manually from the boot> prompt: echo echo boot images/openbsd/5.4/amd64/bsd echo boot images/openbsd/5.4/i386/bsd echo ********************************************************** My question: Does anyone else know a better way? Can I pass an alternative kernel path or boot.conf to pxeboot? -- Paul Heinlein heinlein(a)madboa.com 45°38' N, 122°6' W

2 1

possible kernel bug?
by Fabian Zimmermann 02 Apr '14

02 Apr '14

Hello, i'm using centos 6.5. It was running fine for months. 2-3 days ago I updated the system incl. kernel, but now the system is restarting once a day caused by a panic. -- <1>BUG: unable to handle kernel paging request at 000000004d000001 <1>IP: [<ffffffff810657f3>] load_balance_fair+0x2a3/0x300 <4>PGD 0 <4>Oops: 0000 [#1] SMP <4>last sysfs file: /sys/kernel/mm/ksm/run <4>CPU 0 <4>Modules linked in: ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle autofs4 cpufreq_ondemand acpi_cpufreq freq_table mperf bridge stp llc ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 ext3 jbd vhost_net macvtap macvlan tun kvm_intel kvm ppdev parport_pc parport iTCO_wdt iTCO_vendor_support microcode r8169 mii i2c_i801 sg lpc_ich mfd_core shpchp ext4 jbd2 mbcache raid1 sd_mod crc_t10dif ahci xhci_hcd wmi i915 drm_kms_helper drm i2c_algo_bit i2c_core video output dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan] <4> <4>Pid: 23490, comm: qemu-kvm Not tainted 2.6.32-431.11.2.el6.x86_64 #1 MSI MS-7816/H87-G43 (MS-7816) <4>RIP: 0010:[<ffffffff810657f3>] [<ffffffff810657f3>] load_balance_fair+0x2a3/0x300 <4>RSP: 0018:ffff8806c0045a98 EFLAGS: 00010046 <4>RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000002 <4>RDX: ffff8806c004d440 RSI: ffff88040e872200 RDI: ffff8806c004d400 <4>RBP: ffff8806c0045b58 R08: 0000000000000000 R09: 0000000000000001 <4>R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002 <4>R13: 0000000000000000 R14: 0000000000000002 R15: ffff8806c004d400 <4>FS: 00007f6215948700(0000) GS:ffff880028200000(0000) knlGS:0000000000000000 <4>CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b <4>CR2: 000000004d000001 CR3: 00000003ee2dd000 CR4: 00000000001427e0 <4>DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 <4>DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 <4>Process qemu-kvm (pid: 23490, threadinfo ffff8806c0044000, task ffff8803ee039540) <4>Stack: <4> 0000000000000402 00000000000001fc ffff88038d4ca000 00000000000001fc <4><d> ffff880028216840 00000000000001fc 0000000100000000 000000000000002a <4><d> 0000000000000002 ffff880028316840 0000000000000000 ffff88002820fbe0 <4>Call Trace: <4> [<ffffffff81528350>] thread_return+0x46e/0x76e <4> [<ffffffffa0292db5>] kvm_vcpu_block+0x75/0xc0 [kvm] <4> [<ffffffff8109b290>] ? autoremove_wake_function+0x0/0x40 <4> [<ffffffffa02a73d7>] kvm_arch_vcpu_ioctl_run+0x627/0x10b0 [kvm] <4> [<ffffffffa028eb04>] kvm_vcpu_ioctl+0x434/0x580 [kvm] <4> [<ffffffff81060b13>] ? perf_event_task_sched_out+0x33/0x70 <4> [<ffffffff8100bb8e>] ? apic_timer_interrupt+0xe/0x20 <4> [<ffffffff8119dc12>] vfs_ioctl+0x22/0xa0 <4> [<ffffffff8119e0da>] do_vfs_ioctl+0x3aa/0x580 <4> [<ffffffff8100bb8e>] ? apic_timer_interrupt+0xe/0x20 <4> [<ffffffffa029b6ab>] ? kvm_on_user_return+0x7b/0x90 [kvm] <4> [<ffffffff8119e331>] sys_ioctl+0x81/0xa0 <4> [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b <4>Code: 8b 55 18 41 8b 45 20 3b 02 7d 02 89 02 4c 89 ff 4d 89 f4 e8 60 ee ff ff 49 89 c5 4d 85 ed 0f 85 78 ff ff ff 0f 1f 40 00 4c 89 e1 <4c> 8b b4 58 ff ff ff 4c 8b a5 50 ff ff ff 4c 8b bd 48 ff ff ff <1>RIP [<ffffffff810657f3>] load_balance_fair+0x2a3/0x300 <4> RSP <ffff8806c0045a98> <4>CR2: 000000004d000001 -- Any hints/tipps how to pin down the problem? Thanks a lot, Fabian

3 3

trouble installing Math::BigInt module
by Bennett Haselton 02 Apr '14

02 Apr '14

I had to move a perl script from an old server to a new one. Both the old and new servers are running "CentOS release 5.10 (Final)" and perl v5.8.8. (But the problem I'm running into appears to be a package management problem and not a Perl problem which is why I'm posting it to a CentOS list.) The line of code in the script that attempts to open a Net::SFTP connection, which was working fine on the old machine, no longer works on the new machine. I've tracked it down to the module Net::SSH::Perl::Key::DSA not loading correctly on the new machine. On the old one, the line: perl -e "use Net::SSH::Perl::Key::DSA;" gives no error and no output (as expected), but on the new machine, the same line gives: www:/var/www/html/circumventor# perl -e "use Net::SSH::Perl::Key::DSA;" Math::BigInt version 1.78 required--this is only version 1.77 at /usr/lib/perl5/vendor_perl/5.8.8/Crypt/DSA/KeyChain.pm line 4. BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.8.8/Crypt/DSA/KeyChain.pm line 4. Compilation failed in require at /usr/lib/perl5/vendor_perl/5.8.8/Crypt/DSA.pm line 7. BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.8.8/Crypt/DSA.pm line 7. Compilation failed in require at /usr/lib/perl5/vendor_perl/5.8.8/Net/SSH/Perl/Key/DSA.pm line 14. BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.8.8/Net/SSH/Perl/Key/DSA.pm line 14. Compilation failed in require at -e line 1. BEGIN failed--compilation aborted at -e line 1. I tried to install Math::BigInt on my new machine, by adding a file at /etc/yum.repos.d/custom.repo containing the lines: [local] name=Perl_module baseurl=http://apt.sw.be/redhat/el5/en/i386/rpmforge/ enabled=1 gpgcheck=0 and then running "yum install Math::BigInt", but it just goes through a lot of spew and then ends with this error: >>> Transaction Check Error: file /usr/share/man/man3/Math::BigFloat.3pm.gz from install of perl-Math-BigIn t-1.89-1.el5.rf.noarch conflicts with file from package perl-5.8.8-41.el5.i386 file /usr/share/man/man3/Math::BigInt.3pm.gz from install of perl-Math-BigInt- 1.89-1.el5.rf.noarch conflicts with file from package perl-5.8.8-41.el5.i386 file /usr/share/man/man3/Math::BigInt::Calc.3pm.gz from install of perl-Math-B igInt-1.89-1.el5.rf.noarch conflicts with file from package perl-5.8.8-41.el5.i3 86 file /usr/share/man/man3/Math::BigInt::CalcEmu.3pm.gz from install of perl-Mat h-BigInt-1.89-1.el5.rf.noarch conflicts with file from package perl-5.8.8-41.el5 .i386 Error Summary >>> Both servers have Math::BigInt 1.77 installed. As far as I can tell, the reason the error occurs on the new server but not on the old server, is because on the old server the place that Math::BigInt is loaded is in the file /usr/lib/perl5/vendor_perl/5.8.8/Net/IP.pm which contains the line: use Math::BigInt; whereas on the new server, Math::BigInt is loaded in the file /usr/lib/perl5/vendor_perl/5.8.8/Crypt/DSA/KeyChain.pm which contains the line: use Math::BigInt 1.78 try => 'GMP, Pari'; However, that's where my "expertise", such as it is, runs out. I have no idea why the two machines even attempt to load Math::BigInt in two different ways since I don't remember installing things differently on them. I would like to fix the problem on the new machine in the cleanest possible way (i.e., not just commenting out the "1.78" in the line "use Math::BigInt 1.78" -- I don't think that would be the "clean" solution!). Any idea what to do? Bennett

7 20

Q2ask about dual systems booting failure!
by alex43210 02 Apr '14

02 Apr '14

On my computer with dual systems(win7+centos6.4(now 6.5), after I do something, problems came out: when I plug portable hard disk into my computer, It is not mounted successfully. SO I do as the suggestions from URL 'http://wiki.centos.org/TipsAndTricks/NTFS' with the following block: _/Installing required packages/_ _//__//__//__//_ _/For /__/*CentOS-6*/__/the /__/*EPEL*/__/repository is carrying later NTFS packages. EPEL is also usable for /__/*CentOS-5*/__/. To install, after enabling the repo per the /__/Repositories <http://wiki.centos.org/Repositories>/__/page: /__//_ _/yum install ntfs-3g /__//_ _//_ _/or if you prefer to leave EPEL disabled by default /__//_ _/yum --enablerepo epel install ntfs-3g /__//_ _//__//_ _/You may also want to /__//_ _/yum install ntfsprogs ntfsprogs-gnomevfs /__//_ _//_ _/for additional functionality. /__//__//_ _/Mounting an NTFS filesystem/_ _//__//_ _/Suppose your ntfs filesystem is /__//dev/sda1/__/and you are going to mount it on /__//mymnt/win/__/, /__//__/do the following. /__//__//_ _/First, create a mount point. /__//_ _/mkdir /mymnt/win /__//_ _//_ _/Next, /__/*edit*/__//__//etc/fstab/__/as follows. To mount read-only: /__//_ _//dev/sda1 /mymnt/win ntfs-3g ro,umask=0222,defaults 0 0 /__//_ _//_ _/To mount read-write: /__//_ _//dev/sda1 /mymnt/win ntfs-3g rw,umask=0000,defaults 0 0 /__//_ _//_ _/You can now mount it by running: /__//_ _/mount /mymnt/win/_ But after doing that, the error is also reported "Unable to mount location\Error mounting: mount:unknown filesystem type 'ntfs'". So I /*mkdir*/ another */mnt/win*, */delete/* the */mymnt/win* and try again. the error is reported too! At the same time, when I reboot the computer. I can not login the Win7 system by error reported " *BOOTMGR is missing*" How can I fix these problem? By the way I use 'fdisk -l' to check my partition and shows as follows: /Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x1cc5999d Device Boot Start End Blocks Id System /dev/sda1 * 1 26 204800 7 HPFS/NTFS Partition 1 does not end on cylinder boundary. /dev/sda2 26 12927 103628800 7 HPFS/NTFS /dev/sda3 12927 117676 841393152 f W95 Ext'd (LBA) /dev/sda4 117676 121602 31534808 12 Compaq diagnostics /dev/sda5 12927 44798 256000000 7 HPFS/NTFS /dev/sda6 44798 76669 256000000 7 HPFS/NTFS /dev/sda7 76669 103440 215040000 7 HPFS/NTFS /dev/sda8 103440 103466 204800 83 Linux /dev/sda9 103466 110477 56320000 83 Linux /dev/sda10 110477 111497 8192000 82 Linux swap / Solaris /dev/sda11 111497 117676 49629184 83 Linux// //Can you help me out?/ best regards, yours alex

1 0

Adding a new disk to an existing raid 10
by Roland RoLaNd 02 Apr '14

02 Apr '14

Dear all, I'm not used to handling software raid. I've inherited a server which has raid 10 set. one of our disks failed, and it's to be replaced today. My question is; any hint how to add this new disk to the existing raid array ? first thought is :- Create identical partitions as other disks in the array i'd like to add it to.- add it to raid. Though i'm extremely worried of messing things up and wiping all my data. Any hint would be appreciated

5 5

CentOS-announce Digest, Vol 110, Issue 1
by centos-announce-request＠centos.org 01 Apr '14

01 Apr '14

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2014:0341 Moderate CentOS 5 wireshark Update (Johnny Hughes) 2. CESA-2014:0342 Moderate CentOS 6 wireshark Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 31 Mar 2014 17:51:37 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0341 Moderate CentOS 5 wireshark Update To: centos-announce(a)centos.org Message-ID: <20140331175137.GA11006(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0341 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0341.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 08c8c02b8cedb60b86ec5c10c5caadeb4549493751a112ab44367ae35825a201 wireshark-1.0.15-6.el5_10.i386.rpm 0f9a6201343210ba03cf0d218d6d1781aa3f8766c1ccdb2ad2b40d1891676f63 wireshark-gnome-1.0.15-6.el5_10.i386.rpm x86_64: 0f76ec04395bd97354cc4388ead650651d81a1ef1b2261d193f87762428cf46a wireshark-1.0.15-6.el5_10.x86_64.rpm 9c19cb783ff6c54a96da465f69c7d2ddc0391565470e1709b3071e9c0d31a07a wireshark-gnome-1.0.15-6.el5_10.x86_64.rpm Source: 0cfa8fc9cb3a5ccf88ff1fec32de647b06a42a2e6eb8e9b003f68dff867ef812 wireshark-1.0.15-6.el5_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Mon, 31 Mar 2014 18:13:23 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0342 Moderate CentOS 6 wireshark Update To: centos-announce(a)centos.org Message-ID: <20140331181323.GA63335(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0342 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0342.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e86f9c91381562e4ed24f3be923675eef44e0c6023a0cdca443c59c1c09687df wireshark-1.8.10-7.el6_5.i686.rpm 01a5149ec6028dc2be17b1118d44c0fa9054a6bee017bd55e5c7a521fafe6cd8 wireshark-devel-1.8.10-7.el6_5.i686.rpm c9fdd1f944111358f6a038a8e151b726bd626ef20dc40f1ef00b9500d3423402 wireshark-gnome-1.8.10-7.el6_5.i686.rpm x86_64: e86f9c91381562e4ed24f3be923675eef44e0c6023a0cdca443c59c1c09687df wireshark-1.8.10-7.el6_5.i686.rpm 4d85f7abcd56ab9c99156037445c5288505ba930c9d5b220a2bf3e9a7b7b5508 wireshark-1.8.10-7.el6_5.x86_64.rpm 01a5149ec6028dc2be17b1118d44c0fa9054a6bee017bd55e5c7a521fafe6cd8 wireshark-devel-1.8.10-7.el6_5.i686.rpm 798968dd1fa8b839acaa65fc32595ba22993dc217139afde6004e0f3d29ca2d6 wireshark-devel-1.8.10-7.el6_5.x86_64.rpm f1965eabc7c53b3c085555db4ac3ac6a31f5ee2dfc261ef644a6a0a767ede4b3 wireshark-gnome-1.8.10-7.el6_5.x86_64.rpm Source: 71a97a11004793b0fd19c3bfe98f65917f05690079aaa77f629eb4553bb7dfae wireshark-1.8.10-7.el6_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 110, Issue 1 ***********************************************

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss April 2014