similar to: CentOS 7, 327 kernel still crashing

> -----Original Message----- > From: Wes James [mailto:comptekki at me.com] > Sent: Wednesday, January 27, 2016 7:04 PM > To: CentOS mailing list > Subject: Re: [CentOS] CentOS 7, 327 kernel still crashing > > > > On Jan 27, 2016, at 1:47 PM, m.roth at 5-cent.us wrote: > > > > I've just added the following to the CentOS bugtracker for CentOS-7 > >

This is happening on anything other than plain vanilla Dell servers. One R730, with dual Tesla cards, one R420, with a fibre card for a RAID device, it never switches root. All these systems have Xeons, not AMD CPUs. We've had this with every one of the 327 kernels. In addition, it seems to happen also with the 229.20.1; the 229.14.1 has no such problem. >From the rdsosreport: starting

On Thu, 18 Feb 2016, m.roth at 5-cent.us wrote: > This is happening on anything other than plain vanilla Dell servers. One > R730, with dual Tesla cards, one R420, with a fibre card for a RAID > device, it never switches root. All these systems have Xeons, not AMD > CPUs. > > We've had this with every one of the 327 kernels. In addition, it seems to > happen also with the

Paul Heinlein wrote: > On Thu, 18 Feb 2016, m.roth at 5-cent.us wrote: > >> This is happening on anything other than plain vanilla Dell servers. One >> R730, with dual Tesla cards, one R420, with a fibre card for a RAID >> device, it never switches root. All these systems have Xeons, not AMD >> CPUs. >> >> We've had this with every one of the 327

> On Jan 27, 2016, at 1:47 PM, m.roth at 5-cent.us wrote: > > I've just added the following to the CentOS bugtracker for CentOS-7 > 0009860. I admit to not being sure if it's the same issue, or a separate > one, but this and other Dell servers - I *think* they're all R420's, but I > could be wrong, just all do the same thing on boot. > ***************** >

I am trying to create a CF card that boots 686 CentOS 6.3 On boot I get a message about /dev/disk/by-label/\x2f where \x2f is "/" cannot be found. Adding rdshell to the boot line and booting up sure enough the /dev/disk directory does not exist. What "creates" that early on in the boot process? My CF card was changed from UUID to LABEL. So I edited grub.conf and make

Hello together. I''ve tried to register an onFailure behavior for all my Ajax.Requests and .Updaters to handle a session-based timout system. On each server request via Ajax there is a check whether the user hasn''t made something for the last x minutes, and if he hasn''t, the php page throws an 403 forbidden header (via header("HTTP/1.1 403 Forbidden")). I am

All, I'm trying to use PAM to replicate the authorized user functionality in commercial ssh. In the past, I've patched openssh to do this, but I think that solution is fairly ugly (and requires me to patch with each new release of openssh which is really bad). I want to do this: 0. use openssh for all communication with this machine. 1. check a user's identity using their

All, I''m having a weird issue with posted parameters in Rails 3.1.0. This is only happening in production and not in development. I have confirmed that when making a post, parameters are passed to the server as: utf8=%E2%9C %93&authenticity_token=jOn16Uw3oUBPQfX02nt1IN8muZf150nTt24Ic4JgPvY %3D&alert%5Btitle%5D=http%3A%2F%2Fwww&alert%5Bheadline%5D=%26headline Which looks

Hellos, Yes, I did some tests with "OnFailure" attribute, but the result was the same: system didn't sent any mail. Daemon and script files were: * crond.service: * [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target OnFailure=crond-notify-email.service [Service] EnvironmentFile=/etc/sysconfig/crond

Hi everyone, The onSuccess callback gets fired when HTTP status code is 200, and onComplete gets fired AFTER onSuccess/onFailure when the browser has finished handling the request, i.e. when the DOM is ready, right? So my question is where to put code that MUST ONLY be executed if HTTP status code is 200 AND Ajax.Request was called with option ''evalScripts: true''. The code in

Working on the Dell R420 today, got most of it working, even the broadcom ethernet cards! However, I get the following when I reboot the system: Syncing disks, vnodes remaining...4 Sleeping thread (tid 100107, pid 9) owns a non-sleepable lock KDB: stack backtrace of thread 100107: sched_switch() at sched_switch+0x19f mi_switch() at mi_switch+0x208 sleepq_switch() at sleepq_switch+0xfc

Hi all, I have this code: new Ajax.Request(''non_existant.file'', { onSuccess:function(){alert("yay");}, onFailure:function(){alert("boo");} }); Why does the onFailure alert never get called? It works fine if I use a real file (onSuccess gets called). Thanks, Douglas

Team I have a Dell PowerEdge R720xd, with the Broadcom NetXtreme bcm5720. I found the following thread: http://forums.freebsd.org/showthread.php?t=31769 I find I am unable to use the NIC's (there are 4 on the server). When we put a cable into it we get a "watchdog timeout -- resetting" error, and the machine will pause for 5 or so seconds. IP may or may not come up randomly.

Hello All, I''m trying to capture the exception message that my server application is providing in response to my Ajax.Request. However, I''m confused as to when onFailure is fired vs. onException. The onException handler has access to the javascript exception object and I''d understood that it was only called when the dispatch fails. Not sure what exactly that means

Hi, I am working on a page that updates a calendar via Ajax.Request when the previous (''? <http://luther.edu/new/?cur_month=2005-09>'') or next (''? <http://luther.edu/new/?cur_month=2005-11>'') month links are clicked . http://luther.edu/new/ It seems to work fine if I don''t call anything onLoading. http://luther.edu/new/noonloading.php

Gesti? Servidors wrote: > > Hello, > > I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: > # /etc/systemd/system/crond.service > [Unit] > Description=Command Scheduler > After=auditd.service systemd-user-sessions.service time-sync.target >

Update: I found a workaround to prevent entering emergency shell during boot for no reason. I've simply cleared the `OnFailure=` option for initrd-parse-etc.service (which was previously set to `OnFailure=emergency.target`). Now the server boots successfully without dropping into an emergency shell. This is a total hack, and I'm a little embarrassed that it's the only solution that

I am trying to catch failed Ajax requests, but I''m talking about requests that receive no response from the server (server is down), not responses that result in a 500. The latter can be handled with the onException or onFailure callback, but I am not able to handle the former. To reproduce/test: 1) Start your server 2) Create a page that does this:

Hello SpinDoctors, I am fairly new to prototype js framework. I love it. Have various Ajax -get calls... which work wonderful... Suddenly, realised that in one case I have to use ''post'' to overcome the limitation on URL length... Have changed the parameters to suit to ''post'' request, but nothing happens... need your help... function getOptionalGroups(key){