Re: kernel-2.6.32-131.2.1.el6.x86_64 Xen DomUs.
Hi Steven, On Jun 14, 2011, at 0:04, Steven Haigh wrote: In the latest batch of updates, I installed kernel-2.6.32-131.2.1.el6.x86_64 via a 'yum -y update'. It seemed all of my 5 Xen DomUs running SL6 failed to boot upon rebooting. It looks like all of these systems failed at roughly where switchroot is called. Interestingly, I could recover from this by shutting down the DomU, mounting then chrooting the DomUs filesystem and issuing: # rpm -ivh --force kernel-2.6.32-131.2.1.el6.x86_64.rpm Not sure how widespread this issue is, but I had a 100% failure rate on Xen DomUs. The one bare metal system I updated did so with no errors. no problems here on the two Xen domUs we're currently running. But then, we're still updating kernels with rpm -i rather than yum. Just a data point. Regards, Stephan -- Stephan Wiesand DESY -DV- Platanenallee 6 15738 Zeuthen, Germany
Re: kernel-2.6.32-131.2.1.el6.x86_64 Xen DomUs.
How are you booting the xen domU's, with pygrub, pvgrub, or with external kernel? Smells like either the mkinitrd failed to run at all, or ran in such a way that it didn't put some required xen block device into the ramdisk. For that matter--what hypervisor host are you using for the SL6 xen domU's--is it an SL6 guest on an SL5 hypervisor? I thought SL6 didn't support being a xen host anymore. Steve Timm On Tue, 14 Jun 2011, Stephan Wiesand wrote: Hi Steven, On Jun 14, 2011, at 0:04, Steven Haigh wrote: In the latest batch of updates, I installed kernel-2.6.32-131.2.1.el6.x86_64 via a 'yum -y update'. It seemed all of my 5 Xen DomUs running SL6 failed to boot upon rebooting. It looks like all of these systems failed at roughly where switchroot is called. Interestingly, I could recover from this by shutting down the DomU, mounting then chrooting the DomUs filesystem and issuing: # rpm -ivh --force kernel-2.6.32-131.2.1.el6.x86_64.rpm Not sure how widespread this issue is, but I had a 100% failure rate on Xen DomUs. The one bare metal system I updated did so with no errors. no problems here on the two Xen domUs we're currently running. But then, we're still updating kernels with rpm -i rather than yum. Just a data point. Regards, Stephan -- -- Steven C. Timm, Ph.D (630) 840-8525 t...@fnal.gov http://home.fnal.gov/~timm/ Fermilab Computing Division, Scientific Computing Facilities, Grid Facilities Department, FermiGrid Services Group, Group Leader. Lead of FermiCloud project.
Re: kernel-2.6.32-131.2.1.el6.x86_64 Xen DomUs.
On Tue, Jun 14, 2011 at 8:57 AM, Steven Timm t...@fnal.gov wrote: For that matter--what hypervisor host are you using for the SL6 xen domU's--is it an SL6 guest on an SL5 hypervisor? I thought SL6 didn't support being a xen host anymore. It seemed all of my 5 Xen DomUs running SL6 failed to boot upon rebooting. It looks like all of these systems failed at roughly where switchroot is called. Interestingly, I could recover from this by shutting down the DomU, mounting then chrooting the DomUs filesystem and issuing: # rpm -ivh --force kernel-2.6.32-131.2.1.el6.x86_64.rpm Not sure how widespread this issue is, but I had a 100% failure rate on Xen DomUs. The one bare metal system I updated did so with no errors. DomUs are guests. TUV and SL6 do pv-ops, so the same kernel will run baremetal or PV. -JR
qmmp and mp3 playback
I installed the QMMP. but it seemed to be lacking the mp3 support? Do i have to recompile it or i'm just missing smth obvious? i did install libmad - [code] yum info libmad.i686 Loaded plugins: aliases, changelog, downloadonly, protect-packages, refresh-packagekit Installed Packages Name : libmad Arch : i686 Version: 0.15.1b Release: 4.el6.rf Size : 133 k Repo : installed From repo : rpmforge skip yum info qmmp Loaded plugins: aliases, changelog, downloadonly, protect-packages, refresh-packagekit Installed Packages Name : qmmp Arch : i686 Version: 0.4.3 Release: 1.el6 Size : 4.3 M Repo : installed From repo : epel Summary: Qt-based multimedia player URL: http://qmmp.ylsoftware.com/index_en.html License: GPLv2+ Description: This program is an audio-player, written with help of Qt library. : The user interface is similar to winamp or xmms. : Main opportunities: : : * Winamp and xmms skins support : * plugins support : * Ogg Vorbis support : * native FLAC support : * Musepack support : * WavePack support : * ModPlug support : * PCM WAVE support : * CD Audio support : * CUE sheet support : * ALSA sound output : * JACK sound output : * OSS sound output : * PulseAudio output : * Last.fm/Libre.fm scrobbler : * D-Bus support : * Spectrum Analyzer : * sample rate conversion : * bs2b dsp effect : * streaming support : * removable device detection : * MPRIS support : * global hotkey support : * lyrics support [/code]
non-stop printer notification
I have a user who's print job was cancelled and he now gets dialog box popping up every minute telling him so and suggesting he find out why. And little else. Sound familiar? Is there a simple way of shutting up the machine short of shutting it down?
Re: non-stop printer notification
On 11-06-14 11:59 AM, Ken Teh wrote: I have a user who's print job was cancelled and he now gets dialog box popping up every minute telling him so and suggesting he find out why. And little else. Sound familiar? Is there a simple way of shutting up the machine short of shutting it down? You can try clearing the printer queue... Perhaps it's continually trying to print and failing? Or, try restarting CUPS: /etc/init.d/cups restart -Chris
Re: non-stop printer notification
I found 500 of these in the queue on the print server, cancelled all of them. They are no longer listed but it still pops up on the client machine. Ken On 06/14/2011 02:10 PM, Chris Tooley wrote: On 11-06-14 11:59 AM, Ken Teh wrote: I have a user who's print job was cancelled and he now gets dialog box popping up every minute telling him so and suggesting he find out why. And little else. Sound familiar? Is there a simple way of shutting up the machine short of shutting it down? You can try clearing the printer queue... Perhaps it's continually trying to print and failing? Or, try restarting CUPS: /etc/init.d/cups restart -Chris
Re: non-stop printer notification
On Tue, 14 Jun 2011, Ken Teh wrote: I have a user who's print job was cancelled and he now gets dialog box popping up every minute telling him so and suggesting he find out why. And little else. Sound familiar? Is there a simple way of shutting up the machine short of shutting it down? Is the job still in a printer queue *on the client machine* ? -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge a.c.aitchi...@dpmms.cam.ac.uk http://www.dpmms.cam.ac.uk/~werdna
Re: Problem with cut
On Tue, 14 Jun 2011, Chetan Tiwari wrote: Greetings, I was having trouble using the cut command and wasn't sure if anyone else on this list faced a similar problem. Perhaps I am doing something wrong and any help will be much appreciated. I am using SL6 and the version of cut installed is cut (GNU coreutils) 8.4. I have a text file with the following line: abcdefghijklmnopqrstuvwxyz When I execute the following statement: cut -c1-3,24- test.txt, I get the correct output: abcxyz. When I run the same command, but with a --output-delimiter flag (i.e. cut -c1-3,24- test.txt --output-delimiter=|), I get the exact same output as before: abcxyz. The delimiter (I - pipe symbol) is missing. What is LANG/LC_ALL enveronment in your shell? If it is something with .UTF-8 try to set it without suffix. LANG=C cut --output-delimiter=| -c 1-3,24- test.txt should do the trick. When I run the exact same commands on a machine running Ubuntu with cut (GNU coreutils) 7.4, I get the desired output: abc|xyz. The same problem occurs with larger data files that I was trying to manipulate as well. Thanks, Chetan -- Best regards, Valery Mitsyn
Re: kernel-2.6.32-131.2.1.el6.x86_64 Xen DomUs.
On 14/06/2011 11:57 PM, Steven Timm wrote: How are you booting the xen domU's, with pygrub, pvgrub, or with external kernel? Smells like either the mkinitrd failed to run at all, or ran in such a way that it didn't put some required xen block device into the ramdisk. I'm using pygrub. This way each system has its own kernel. I believe the ramdisk failed - either in including a module, or through a silent error. Either way, it failed. For that matter--what hypervisor host are you using for the SL6 xen domU's--is it an SL6 guest on an SL5 hypervisor? I thought SL6 didn't support being a xen host anymore. I use a self-compiled Xen 4.1.0 with a self-compiled 2.6.32.40 kernel. I'm looking at making them all into RPMs and hosting a Xen repo for kernel + xen - but I'm not that experienced in creating RPMs as yet. In time, I'll get around to it. -- Steven Haigh Email: net...@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 Fax: (03) 8338 0299
