similar to: CentOS 5.10 - turn off sosreport?

On Sunday, I did a "yum update" which installed kernel 2.6.32-573.3.1.el6.i686 on half a dozen virtual machines running CentOS 6.7. Since then, two of them have gone into "meltdown", and started spewing "ABRT Daemon" emails: one on Tuesday, and one tonight. The machines have a very light workload -- one runs "trac", and a handful of development systems,

On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth at 5-cent.us wrote: > Fred Smith wrote: > > On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote: > >> On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote: > >> > On Mon, Jun 20, 2016 at 01:34:30PM +0300, ????????? ???????? wrote: > >> > > >Can anyone of you provide further hints on what

On Fri, December 18, 2015 10:27 am, Jonathan Billings wrote: > On Fri, Dec 18, 2015 at 09:55:39AM -0600, Valeri Galtsev wrote: >> <sarcasm> >> I guess we all are divided into two categories >> >> 1. If google [something] doesn't work on the operating system of my >> choice, the hell with that crap (and google itself). >> >> 2. If google

Current kernel, and I just booted, and dmesg shows, of the 32 cores, 0, 2, 4 and 6 ok, and *all* other show "is now offline. What's happening here? mark

Our environment has several "classes" of servers, such as "development", "production", "qa", "utility", etc. Then we have all our users. There's no obvious mapping between users and server class. Some users may have access to only one class, some may span multiple classes, etc. And for maximum complexity, some classes of machines use local

We've just started seeing this. Anyone else? reason: BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8 component: kernel count: 1 analyzer: vmcore architecture: x86_64 event_log: kernel: 3.10.0-327.18.2.el7.x86_64 last_occurrence: 1484067452 os_release: CentOS Linux release 7.3.1611 (Core) runlevel: N 3 time:

Here's a thought I just thunk, folks: some scum, apparently in eastern Europe, has harvested my email, and is using it in the Reply-To: in its spamming efforts. Now, I realize that some mails go out from noreply, but other than that, is there a good reason why a mailserver would not be configured to send delivery failure to *both* Reply-To and From? mark

All, I have a user who has a Dell Precision 7520 laptop, and we're running CentOS 7, latest kernel. This morning he had two lockup incidents. Nothing in /var/log/messages stands out so far, but did get this information when running 'abrt-cli list --since 1560891312': id c48278a875c27dd4369d971bcfc7db4267766c6d reason: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:356

Anyone else around using apcupsd? I seem to be seeing a problem, and I'd like someone to check me on it: I edit /etc/apcupsd/apccontrol to replace the value of SHUTDOWN from /sbin/shutdown to /bin/false (we don't want 3 or 6 servers shutting down over a 2 second or so blip, which it really wants to do). What's happened is that a machine shut down the other day, and looking at it, I

Send CentOS-announce mailing list submissions to centos-announce at 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 at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Anybody familiar with it, or what it's needed for? I've got at least one user (it's *very* noticeable with her) whose system is spamming /var/log/messages, to the effect of "Another agent is running...\nFailed to allocate the agent. Exitting" (complete with misspelled exiting). In googling, I've seen someone just removing the package. What, if anything, would that break?

John R Pierce wrote: > On 11/17/2017 7:16 AM, m.roth at 5-cent.us wrote: >> I can't seem to find apcupsd for C 6. Just went to epel's website, and >> not >> visible. Anyone have a clue? >> > > suggestion, use NUT instead, the Network UPS Tools....? works for all > sorts of UPS's, not just APC, and supports a master/slave sort of > network control

Kenneth Porter wrote: > On 6/7/2017 8:31 AM, m.roth at 5-cent.us wrote: >> Not sure what you mean when you say "jacked up filesystem". Here's >> fstab: > > In systemd fstab takes care of only rudimentary mounting. Most mounting > is done through *.mount unit files. Type "mount" and you'll see a bunch > of other mounts that were implemented

Chris Murphy wrote: > firewall-cmd --add-service=rsyncd > firewall-cmd --add-service=rsyncd Error: INVALID_SERVICE: rsyncd Is there another place that there needs to be an rsyncd service file, whatever it's supposed to be named, *other* than where systemd wants it? mark > To make it permanent, do the above and this: > firewall-cmd --permanent --add-service=rsyncd > >

Someone else got the 7 pxe install going, and one thing that's annoying is that NetworkMangler appears to be regularly trying to fire up the wifi. On a workstation, in a wired environment. I just want to tell NM to knock it off....It's Monday, and my searching isn't going too well. Clues for the poor? mark

Valeri Galtsev wrote: > > On Fri, March 25, 2016 9:55 am, m.roth at 5-cent.us wrote: >> I don't think I've seen this with CentOS 6 or 5, but I had to repair an >> external RAID box this morning. The server, running CentOS 7, has an >> LSI HBA card in it, and it's presented to the system as /dev/sdb. >> I shut off the RAID controller, powered it off, >

On Mon, Jun 20, 2016 at 05:02:32PM -0400, m.roth at 5-cent.us wrote: > Fred Smith wrote: > > On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth at 5-cent.us wrote: > >> Fred Smith wrote: > >> > On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote: > >> >> On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote: > >> >> > On

Ok, we used to get this occasionally on cluster nodes, and we just got it on a fileserver (very bad). The system is discovered to be unresponsive: it doesn't ping, and plugging a console in, you can see that it's not dead, but there nothing at all on the screen, nor does it respond to even <ctrl-alt-del>. The only answer is to power cycle it; it comes up fine. Nothing in

I hadn't paid attention when one or two folks recently posted this, but it's hit us, also: $ sealert -l d1655210-f43c-4737-98dc-86b6aac82bb6 Entity: line 53: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0x99 0x3C 0x2F 0x74 <tpath>`</tpath> ^ failed to connect to server: xmlParseDoc() failed I tried reinstalling

We've just started getting this. We're running 5.10, kernel 2.6.32-358.18.1.el6.x86_64. Anyone else seen anything like this, or have any ideas? mark Nov 1 14:34:21 <server> kernel: WARNING: at block/ll_rw_blk.c:543 blk_do_ordered() Nov 1 14:34:21 <server> kernel: Nov 1 14:34:21 <server> kernel: Call Trace: Nov 1 14:34:22 <server> kernel: