Discuss

discuss@lists.centos.org

34753 discussions

Re: [CentOS] Removing a file that starts with dashes
by James B. Byrne 03 Apr '14

03 Apr '14

On Wed, April 2, 2014 20:56, John R. Dennison wrote: > On Wed, Apr 02, 2014 at 03:59:26PM -0700, benfell(a)parts-unknown.org wrote: >> On Wed, Apr 02, 2014 at 11:17:02PM +0200, Reindl Harald wrote: >> > >> > WTF - there is a reason the "-f" flag exists - RTFM >> > > > Please ignore and do not respond to this person; he's not a member of > the list and is using nefarious methods to post to it. > Background: https://lists.fedoraproject.org/pipermail/advisory-board/2013-May/011982.ht… -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

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

03 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:0348 Important CentOS 5 xalan-j2 Update (Johnny Hughes) 2. CESA-2014:0348 Important CentOS 6 xalan-j2 Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 2 Apr 2014 12:17:13 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0348 Important CentOS 5 xalan-j2 Update To: centos-announce(a)centos.org Message-ID: <20140402121713.GA31311(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0348 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0348.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0a93cd521aa9197ef5e08abbc130eddae7b0d7d7bdc8de2e3e417e0ceb72789b xalan-j2-2.7.0-6jpp.2.i386.rpm 99f6ad2ccf7ca1ff180360510279a1a274c3af0bbe8f46f51d453f1b5636bfff xalan-j2-demo-2.7.0-6jpp.2.i386.rpm e1abce5dcc6bb72fca6c482e48fd7aa8ddfaacec946ce538ead8044057621003 xalan-j2-javadoc-2.7.0-6jpp.2.i386.rpm d6d235e7331ed50701061db86eb5636435f791d951fd2ca0f5da40ab19fc114b xalan-j2-manual-2.7.0-6jpp.2.i386.rpm 25b19b09a04c414ca19de5ae8776779dff35b2d7f07ea14845c58d1ebf74d12a xalan-j2-xsltc-2.7.0-6jpp.2.i386.rpm x86_64: 20b4cb7dffa6c9e487f000ed856ea236519123c31d37b272cfc5b4a549c03ca0 xalan-j2-2.7.0-6jpp.2.x86_64.rpm 060bb167461297e137975dfa5ce53025320650068ad83ccb7feed626fde9020b xalan-j2-demo-2.7.0-6jpp.2.x86_64.rpm a2e6b04ad6432bfcc87d771ae0c1c07ac8e762babbbb65ab39a81ad2f6a60f57 xalan-j2-javadoc-2.7.0-6jpp.2.x86_64.rpm debebcbc1a2e58d4ce02ffed019716455c5aeb70df0acb60dcd3e4b258394c80 xalan-j2-manual-2.7.0-6jpp.2.x86_64.rpm 7e3c0e52f39a41745c5ef5c9b18f18f2f250badb9b3931db862a43270980f38b xalan-j2-xsltc-2.7.0-6jpp.2.x86_64.rpm Source: 3c7587838c8f200c574eef290aef47c9b95e1d86e4a2eb2030d5ddd056cf0338 xalan-j2-2.7.0-6jpp.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 2 Apr 2014 12:22:27 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0348 Important CentOS 6 xalan-j2 Update To: centos-announce(a)centos.org Message-ID: <20140402122227.GA34356(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0348 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0348.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 4791c5a062d2fafdbc3281552de6770ffcfb2e678913af78a76e8160e7398343 xalan-j2-2.7.0-9.9.el6_5.noarch.rpm 315a5642f01614a5ea9ad520bab9969169c35a5d07622f99003d97aa00c455ee xalan-j2-demo-2.7.0-9.9.el6_5.noarch.rpm 876b3aa82be8b979368b06121e038e01bbb768e91dbf65e4cbd84475b17fb94f xalan-j2-javadoc-2.7.0-9.9.el6_5.noarch.rpm 5c87ed68e12853a34ebb9cfbe4910e1ac5b42092a467fab7980e97a77753a94f xalan-j2-manual-2.7.0-9.9.el6_5.noarch.rpm 439b1a8b03fec9837f0149a3540e79482795ba3359762372fd59c3eb859bc2b8 xalan-j2-xsltc-2.7.0-9.9.el6_5.noarch.rpm x86_64: 4791c5a062d2fafdbc3281552de6770ffcfb2e678913af78a76e8160e7398343 xalan-j2-2.7.0-9.9.el6_5.noarch.rpm 315a5642f01614a5ea9ad520bab9969169c35a5d07622f99003d97aa00c455ee xalan-j2-demo-2.7.0-9.9.el6_5.noarch.rpm 876b3aa82be8b979368b06121e038e01bbb768e91dbf65e4cbd84475b17fb94f xalan-j2-javadoc-2.7.0-9.9.el6_5.noarch.rpm 5c87ed68e12853a34ebb9cfbe4910e1ac5b42092a467fab7980e97a77753a94f xalan-j2-manual-2.7.0-9.9.el6_5.noarch.rpm 439b1a8b03fec9837f0149a3540e79482795ba3359762372fd59c3eb859bc2b8 xalan-j2-xsltc-2.7.0-9.9.el6_5.noarch.rpm Source: a0c023cc26c02efc826a66cbe7e87e0c4808d456a3016a81e0dd1b24b83bf202 xalan-j2-2.7.0-9.9.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 2 ***********************************************

1 0

write barrier support in CentOS 6
by Tom Robinson 03 Apr '14

03 Apr '14

Hi, I've been looking for an answer to this question and can't find anything concrete that says full support for write barriers has been backported to the stock kernel. I've read that: "There is incomplete write barrier support in kernel versions 2.6.32 and earlier (2.6.31 has some support, while 2.6.33 works for all types of device target) - RHEL 6 uses 2.6.32." Now, I understand that Red Hat (and therefore CentOS) backport many upstream features into the stock kernel so how can I be sure that kernel 2.6.32-431.11.2.el6 has write barrier support? Any clues, anyone? Kind regards, Tom -- Tom Robinson IT Manager/System Administrator MoTeC Pty Ltd 121 Merrindale Drive Croydon South 3136 Victoria Australia T: +61 3 9761 5050 F: +61 3 9761 5051 E: tom.robinson(a)motec.com.au

3 7

Removing a file that starts with dashes
by Frank M. Ramaekers 03 Apr '14

03 Apr '14

How can I remove this file? -rw-r--r-- 1 root root 28707 Mar 31 12:31 --backup=numbered I've tried a few different methods, but most attempts interprets the file name as a switch (which it doesn't understand). TIA, Frank M. Ramaekers Jr. | Systems Programmer | Information Technology | American Income Life Insurance Company | 254-761-6649

9 14

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss