[CentOS] MySQL stale socket
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have a server with a faulty power supply that resets the server every 4/5 hours. While I wait for the supplier to change the PS, I am facing an issue with MySQL. When the system comes back on, mysqld script starts the daemon, but the connections via /var/lib/mysql/mysql.sock don't work because MySQL doesn't delete and recreate the stale socket. Apart from editing /etc/init.d/mysqld to force the deletion of a stale socket are there any other way to solve this issue? Thank you un advance. Ciao, luigi - -- / +--[Luigi Rosa]-- \ Microsoft may issue tablets by Christmas. No word yet on whether they'll contain potassium cyanide or saxitoxin. --fark.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKuzTMACgkQ3kWu7Tfl6ZRW6gCfaU56Jcayg7TfZU9b0vTkTJXs m7EAoM7ROhaRk+x+3C0+ygi/Xk+2PKke =BWy2 -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] MySQL stale socket
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have a server with a faulty power supply that resets the server every 4/5 hours. While I wait for the supplier to change the PS, I am facing an issue with MySQL. When the system comes back on, mysqld script starts the daemon, but the connections via /var/lib/mysql/mysql.sock don't work because MySQL doesn't delete and recreate the stale socket. Apart from editing /etc/init.d/mysqld to force the deletion of a stale socket are there any other way to solve this issue? Thank you un advance. Ciao, luigi - -- / +--[Luigi Rosa]-- \ Microsoft may issue tablets by Christmas. No word yet on whether they'll contain potassium cyanide or saxitoxin. --fark.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKuzTUACgkQ3kWu7Tfl6ZTV8wCfdFrw937bBokoy3MPcIRy3Qd+ fWMAn1/fEyC6LBZp/0kHHzByqg8nFRP3 =jV5r -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MySQL stale socket
On Mon, 16 Dec 2013 10:51:54 +0100 Luigi Rosa wrote: > > I have a server with a faulty power supply that resets the server > every 4/5 hours. > > While I wait for the supplier to change the PS, I am facing an issue > with MySQL. > > When the system comes back on, mysqld script starts the daemon, but > the connections via /var/lib/mysql/mysql.sock don't work because > MySQL doesn't delete and recreate the stale socket. > > Apart from editing /etc/init.d/mysqld to force the deletion of a > stale socket are there any other way to solve this issue? > > > Thank you un advance. > > > Ciao, > luigi > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos Hi, As a *temporary* solution you could do the following: # chkconfig mysqld off # nano /etc/rc.local Add at bottom: rm /var/lib/mysql/mysql.sock service mysqld start Now Save. Next time the machine boots it should remove the sock file, and then start mysqld. Once your PSU is fixed, remove those lines and run: # chkconfig mysqld on Job done! :-D Hope this helps. Kind Regards, Jake Shipton (JakeMS) GPG Key: 0xE3C31D8F GPG Fingerprint: 7515 CC63 19BD 06F9 400A DE8A 1D0B A5CF E3C3 1D8F ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL 7 Beta is now public
On 12/15/2013 10:23 PM, Keith Keller wrote: >> >> CentOS *IS* RHEL rebuilt without branding and offered without support >> contracts. So saying the needs of the user differ is specious. > > I disagree. The people RH may be targetting for purchasing RHEL7 may > very well be different from the people hoping to use CentOS 7. If not > enough paying RHEL customers complain about this issue, they're not > likely to change their policy; upset CentOS users probably won't bother > upstream enough. therefore, if enough people sign up to help and do the work, we can make the resources available within the project to facilitate this. the people doing the work in centos for the distro base do not have the bandwidth to add this additional task - so its going to need people to stay up and offer to do the work. I'm happy and very willing to help bootstrap the process. Also worth keeping in mind is that this would be a 'derevative' of the core CentOS Linux and it wont just be CentOS Linux 7/i686. That gives us a few easy wins : we dont need to port the entire package set, and we can selectively make changes to things like the installer ( to work around the xfs issue, however looking at the code briefly, we dont / wont have the xfs issue anyway, the installer is smart enough to work around on i686 ). There would also be implications on how we do the release work, but the main issue at hand, that needs to be solved before we even consider this as a group : who's stepping up to do the work involved. Off the top of my head, this is going to need a team of 5 to 8 people doing stuff 'in odd hours' or a couple of people working on this as their primary focus. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL 7 Beta is now public
I meant the actual implementation, I knew it would be GNOME Classic. This beta release is awful. I lost count of how many devel packages were missing now, I think I had to rebuild over 20 of their source rpms to get them while I was toying with Cairo Dock. Not to mention that desktop, 4 ways to close an app - that's awesome! (not) Meh, this really should be labeled an alpha it has so many problems but I guess it's easy enough to bootstrap their sources to spit out all of the missing dependencies. On Wed, Dec 11, 2013 at 11:51 AM, Alain Péan wrote: > Le 11/12/2013 18:26, Andrew Wyatt a écrit : > > Thanks for this, looking forward to kicking the tires to see what they > did > > with GNOME 3. > > From the release notes : > "Red Hat Enterprise Linux 7.0 Beta features the next major version of > the GNOME Desktop, GNOME 3. The user experience of GNOME 3 is largely > defined by GNOME Shell, which replaces the GNOME 2 desktop shell. Apart > from window management, GNOME Shell provides the top bar on the screen, > which hosts the 'system status' area in the top right, a clock, and a > hot corner that switches to |Activities Overview|, which provides easy > access to applications and windows. > > The default GNOME Shell interface in Red Hat Enterprise Linux 7.0 Beta > is GNOME Classic which features a window list at the bottom of the > screen and traditional *Applications* and *Places* menus." > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] duplicate packages on connection reset
From: Adrian Sevcenco > if i try to remove them, yum tries to uninstall all > system (447 packages 1.4 gb)!! What about a simple "rpm -e PKG" ? JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] LVM recovery after pvcreate
Hi all, I had centos 5.9 installed with one of its volumes (non-root) on LVM: ... /dev/vgapps/lvapps /opt/apps ext3defaults1 2 ... Then installed centos 6.4 on this servers but without exporting this volume (I wanted to reuse it). After that instead importing it I did: # pvcreate /dev/sddlmac # vgcreate vgapps /dev/sddlmac And then realised that I should have import it instead of pvcreate/vgcreate. Can I restore previous state and data from this volume ? I have files from /etc/lvm/backup (taken before reinstallation) with its old definition. Regards P. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] What is eating up Swap
From: Stephen Harris > Having pages in swap is not indicative of a problem; what's more > important is the level of swap _activity_. See "vmstat" output, for > example, to determine how much swap activity is occuring. If that's > zero then you're not throwing new pages out to swap. Maybe unrelated but we ran into some NUMA memory allocation per cpu problem with our mysql servers. The swap would be used (up to 100%) while there was plenty of free RAM. Prefixing mysqld with "numactl --interleave all" seemed to fix it... JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] 7.0 largely estimated release date...
Hey, I have a new laptop for which CentOS 6.5 says hardware not supported, but it still seems to work. So I was happy to hear about the beta and naively planning to wait until 7.0 to install it... But, seeing that RHEL 6 beta->stable took around 6 months, and add to that the CentOS hard work... Do you think we are talking about an autumn 2014 release? Thx, JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LVM recovery after pvcreate
To give additional data - currently I have the following: # pvs File descriptor 7 (pipe:[76957]) leaked on pvs invocation. Parent PID 15357: bash PVVG Fmt Attr PSize PFree /dev/sddlmab2 vg01 lvm2 a-- 14.47g 480.00m /dev/sddlmac vgapps lvm2 a-- 50.00g 50.00g But vgapps has been created "manually" after reinstallation (pvcreate + vgcreate) Is that correct approach if I pvremove it and then pvcreate previous volume using /etc/lvm/backup files ? Regards P. Od: przemol...@poczta.fm Do: centos@centos.org; Wysłane: 16:22 Poniedziałek 2013-12-16 Temat: [CentOS] LVM recovery after pvcreate > > Hi all, > > I had centos 5.9 installed with one of its volumes (non-root) on LVM: > ... > /dev/vgapps/lvapps /opt/apps ext3defaults1 2 > ... > Then installed centos 6.4 on this servers but without exporting this volume > (I wanted to reuse it). > After that instead importing it I did: > # pvcreate /dev/sddlmac > # vgcreate vgapps /dev/sddlmac > > And then realised that I should have import it instead of pvcreate/vgcreate. > Can I restore previous state and data from this volume ? > I have files from /etc/lvm/backup (taken before reinstallation) with its old > definition. > > Regards > P. > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] duplicate packages on connection reset
On Mon, Dec 16, 2013 at 12:55 AM, Adrian Sevcenco wrote: > >> Running 'yum-complete-transaction' will usually fix things up. If >> you don't have it you should be able to 'yum install yum-utils' >> without affecting the old incomplete transaction. > both > 1. yum-complete-transaction and > 2. yum-complete-transaction --skip-broken > > fails with : > 1. > Error: Package: mesa-dri-drivers-9.2-0.5.el6_5.2.x86_64 (updates) >Requires: mesa-dri1-drivers >= 7.11-6 >Removing: mesa-dri1-drivers-7.11-8.el6.x86_64 (@base) >mesa-dri1-drivers = 7.11-8.el6 > Error: Package: dracut-004-336.el6_5.2.noarch (updates) >Requires: plymouth >= 0.8.0-0.2009.29.09.19.1 >Removing: plymouth-0.8.3-27.el6.centos.x86_64 (@base) >plymouth = 0.8.3-27.el6.centos > Error: Package: xorg-x11-server-Xorg-1.13.0-23.el6.centos.x86_64 (base) >Requires: fedora-setup-keyboard >Removing: system-setup-keyboard-0.7-4.el6.x86_64 > (@anaconda-base-201211270324.x86_64/6.1.0) >fedora-setup-keyboard = 0.7-4.el6 > You could try using --skip-broken to work around the problem > > 2. Error: Trying to remove "yum", which is protected > ** Found 159 pre-existing rpmdb problem(s), 'yum check' output follows: > Try a 'yum update yum' to make sure you have the newest, then 'rpm -e' the older duplicate package using the full package name. Repeat for other specific errors until the yum-complete transaction works. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] thunderbird-24.2.0-2.el5 is borked
> Try to export your calendars and import them on a fresh install, see if > the problem persists. Don't think I can do that with Exchange calendars. Anyway, the CentOS6 version works fine, even coming from a 17.x profile, so there definitely is a problem with the CentOS5 version. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] thunderbird-24.2.0-2.el5 is borked
Am 16.12.2013 um 17:21 schrieb Lars Hecking : > >> Try to export your calendars and import them on a fresh install, see if >> the problem persists. > > Don't think I can do that with Exchange calendars. > > Anyway, the CentOS6 version works fine, even coming from a 17.x profile, so > there definitely is a problem with the CentOS5 version. just report it to http://bugzilla.redhat.com -- LF ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On Sun, 15 Dec 2013, Darr247 wrote: > I see 2 components in ps4.jpg that look like they've ruptured. > > One in the mid/foreground with the yellow hot glue on it (the shorter The one with the visible VENT and 105 printing? > one, between the inductor and the caps), and one hiding under the > harness that exits the supply... to the upper-right of the green cap, > near the PS housing. And to the right of the pink padlocky thing. To me it looks too fuzzy to tell. I'm sure that is partly the dust. VENT105 does look like it's bulging a bit. I'll take another look to make sure it isn't a camera thing. -- Michael henne...@web.cs.ndsu.nodak.edu "SCSI is NOT magic. There are *fundamental technical reasons* why it is necessary to sacrifice a young goat to your SCSI chain now and then." -- John Woods ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On Sat, 14 Dec 2013, John R Pierce wrote: > me, if I had any reason to suspect a power supply, I would just get a > new one, basic PC power supplies in reasonable wattage ratings are quite > cheap. examples: > http://www.newegg.com/Product/Product.aspx?Item=N82E16817152032 > http://www.newegg.com/Product/Product.aspx?Item=N82E16817371003 >From this, I infer that 20-pin ATX's are sufficiently standardized that I do not need to be model- or brand-specific. -- Michael henne...@web.cs.ndsu.nodak.edu "SCSI is NOT magic. There are *fundamental technical reasons* why it is necessary to sacrifice a young goat to your SCSI chain now and then." -- John Woods ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 12/13/2013 16:35, Michael Hennebry wrote: > I note the absence of PAE for CentOS. > I've read that PAE can be important. Only if you're trying to address more than 4 GB of RAM on a 32-bit system. Even then, most software doesn't take advantage of it. PAE is an old hack Intel invented in the mid 90's to ease the transition to 64-bit computing. Now that 64-bit is really, finally here, it's time to start forgetting that PAE ever existed. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 12/15/2013 16:21, Michael Hennebry wrote: > > the yellow stuff looks suspicious. It's a kind of strain relief. Without that flexible glue, dropping the computer could snap those caps off at their base. Since this is the sort of thing that occasionally happens to computers in shipping, computer manufacturers try to make sure their machines can withstand a few of these sharp shocks. After all, damage in shipping is damage during the warranty period, and the shipping companies are a PITA to get insurance money out of. > The darkness near the smaller yellow spot indicates my inability > to position both the camera and the light the way I wanted them. That's why I mentioned reflectors and bounce cards among my photo advice. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On Mon, Dec 16, 2013 at 11:28 AM, Warren Young wrote: > On 12/13/2013 16:35, Michael Hennebry wrote: >> I note the absence of PAE for CentOS. >> I've read that PAE can be important. > > Only if you're trying to address more than 4 GB of RAM on a 32-bit > system. Even then, most software doesn't take advantage of it. > > PAE is an old hack Intel invented in the mid 90's to ease the transition > to 64-bit computing. Now that 64-bit is really, finally here, it's time > to start forgetting that PAE ever existed. I think PAE is a required default in CentOS6 instead of an option. CentOS5 had separate kernel versions. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 12/15/2013 16:49, Michael Hennebry wrote: > > Looks like I'll need to see whether I still have my multimeter. That's not likely to tell you much. About the only thing I'd trust a typical DMM to tell me about a PSU is whether its rails are within voltage spec. You must do that test under load, and you need a fairly accurate DMM to get a result you can trust. If the PSU passes the voltage test, it could still be bad. The only way to tell, short of just swapping it, is to do an ESR test[*], which requires an LCR meter. (It also requires removing the PSU board from the box, which exposes you to the dangers of AC wiring and charged caps.) I don't think I've ever seen a DMM with an integrated ESR function. If such a thing does exist, the DMM would end up being pretty expensive if it gave results you could trust for this, since we're talking about measurements under 1 ohm. Decent LCR meters start at about $200 and go way up from there. Cheaper to just gamble on a PSU swap. [*] https://en.wikipedia.org/wiki/Equivalent_series_resistance ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 12/16/2013 09:53, Michael Hennebry wrote: > > The one with the visible VENT and 105 printing? "Vent" just calls out that there is a vent on the top of the cap, which it obvious without the label. It's the scoring in the metal, which allows the top of the cap to break open in a controlled way if the pressure inside gets too high. Without the vent, a failing cap holds the pressure in until it explodes like a firecracker. The other label is actually 105℃, meaning that it's rated for a certain number of hours of use at 105℃. That means it's probably a fairly high quality cap. If you have to replace this cap, you'd want to match that temperature rating as well as the capacitance and voltage rating. You'll probably find that *all* of the caps are 105℃ rated, so they'll have that marking on them somewhere. (You think things are complicated already? Wait until you start shopping for caps!) > And to the right of the pink padlocky thing. ?? Do you mean the chokes, which have yellow cores and red and orange lacquered wire? Or perhaps the dark gray cored inductors, with red wire? Or do you mean the pink resistors(?) near the board edge? > To me it looks too fuzzy to tell. > I'm sure that is partly the dust. Yes. You should have blown the dust out before taking the pics. It needs to be blown out regardless. > VENT105 does look like it's bulging a bit. It doesn't look like it to me. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 12/16/2013 8:56 AM, Michael Hennebry wrote: > >From this, I infer that 20-pin ATX's are sufficiently standardized > that I do not need to be model- or brand-specific. well, ATX 1.x stuff had more 5V and less 12V, while ATX 2.x boosts the 12V output capacity and has less 5V... I'm pretty sure even a AGP/PCI P4 is ATX 2.0, but I suppose I could be wrong.We're stirring some mighty old neurons here. I ejunked all my P4's some time ago. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 12/16/2013 10:03 AM, John R Pierce wrote: > On 12/16/2013 8:56 AM, Michael Hennebry wrote: >> >>From this, I infer that 20-pin ATX's are sufficiently standardized >> >that I do not need to be model- or brand-specific. > well, ATX 1.x stuff had more 5V and less 12V, while ATX 2.x boosts the > 12V output capacity and has less 5V... I'm pretty sure even a AGP/PCI > P4 is ATX 2.0, but I suppose I could be wrong.We're stirring some > mighty old neurons here. I ejunked all my P4's some time ago. ok, I googled it, the manual for your motherboard says "ATX12V", which is close enough the 2.x spec that it should work. I do see a suggestion that you use a somewhat higher 'wattage' ATX12V 2.x PSU to compensate for the differences. btw, here's the technical product manual for your mainboard http://downloadmirror.intel.com/15207/eng/D865GBF_D865GLC_ProductGuide02_English.pdf -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
At 10:27 AM 12/16/2013, you wrote: >On 12/16/2013 10:03 AM, John R Pierce wrote: > > On 12/16/2013 8:56 AM, Michael Hennebry wrote: > >> >>From this, I infer that 20-pin ATX's are sufficiently standardized > >> >that I do not need to be model- or brand-specific. > > well, ATX 1.x stuff had more 5V and less 12V, while ATX 2.x boosts the > > 12V output capacity and has less 5V... I'm pretty sure even a AGP/PCI > > P4 is ATX 2.0, but I suppose I could be wrong.We're stirring some > > mighty old neurons here. I ejunked all my P4's some time ago. > >ok, I googled it, the manual for your motherboard says "ATX12V", which >is close enough the 2.x spec that it should work. I do see a suggestion >that you use a somewhat higher 'wattage' ATX12V 2.x PSU to compensate >for the differences. > >btw, here's the technical product manual for your mainboard >http://downloadmirror.intel.com/15207/eng/D865GBF_D865GLC_ProductGuide02_English.pdf > > >-- >john r pierce 37N 122W >somewhere on the middle of the left coast > >_ Is there some reason that this conversation is in the public channel? I'm not sure that power connectors to ATX boards is really relevant to the forum's topic. David Kurn ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Open more then one connection with RDP client
I'm using CentOS 6.5 and have one connection open to a system in my student doing a software install. I set up a second RDP connection (Applications -> Internet -> Terminal Server Client), but when I double click on it, it will not run. Is there a way to have more than one running? -wes ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Open more then one connection with RDP client
On Mon, Dec 16, 2013 at 12:37 PM, Wes James wrote: > I'm using CentOS 6.5 and have one connection open to a system in my > student doing a software install. I set up a second RDP connection > (Applications -> Internet -> Terminal Server Client), but when I double > click on it, it will not run. Is there a way to have more than one running? > > Never mind I created a new rdp connection and that worked. The one that didn't seem to be working was an export then import. But I double-clicked on it again, and now it works. I guess I'm not double-clicking on the icon good enough. -wes ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 16 December 2013 @16:53 zulu, Michael Hennebry wrote: > On Sun, 15 Dec 2013, Darr247 wrote: > >> I see 2 components in ps4.jpg that look like they've ruptured. >> >> One in the mid/foreground with the yellow hot glue on it (the shorter > The one with the visible VENT and 105 printing? No. The short one (in 'front' of the electrolytic capacitor with the markings you mention) that appears to have an output choke (inductor), wound around the component and likely terminated to each lead. The other one is to the right of the pink resistor, yes... it *also* appears to have an output choke wound around it. Those are quite unusual, in my experience. I just took apart 3 dead power supplies here in the recycle bin and found swollen caps in all of them, but no chokes wound around components like that. Typically, inductor coils are wound around a piece of ferrous metal to intensify the flux, amplifying their filtering effect. On one hand you'd think it's a design flaw that extra chokes would need to be added like that to specific components; on the other hand it would point to extra engineering having been done to actually fix a specific problem instead of just pushing them out the door. Then again - as others have mentioned - maybe it's just clumps of dust... and I'm imagining things. :) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On Mon, 16 Dec 2013, John R Pierce wrote: > On 12/16/2013 10:03 AM, John R Pierce wrote: >> On 12/16/2013 8:56 AM, Michael Hennebry wrote: > From this, I infer that 20-pin ATX's are sufficiently standardized that I do not need to be model- or brand-specific. >> well, ATX 1.x stuff had more 5V and less 12V, while ATX 2.x boosts the >> 12V output capacity and has less 5V... I'm pretty sure even a AGP/PCI >> P4 is ATX 2.0, but I suppose I could be wrong.We're stirring some >> mighty old neurons here. I ejunked all my P4's some time ago. > > ok, I googled it, the manual for your motherboard says "ATX12V", which > is close enough the 2.x spec that it should work. I do see a suggestion > that you use a somewhat higher 'wattage' ATX12V 2.x PSU to compensate > for the differences. > > btw, here's the technical product manual for your mainboard > http://downloadmirror.intel.com/15207/eng/D865GBF_D865GLC_ProductGuide02_English.pdf That is where I got the 20-pin ATX stuff. It just occured to me that I might want geometric as well as electrical compatibility. -- Michael henne...@web.cs.ndsu.nodak.edu "SCSI is NOT magic. There are *fundamental technical reasons* why it is necessary to sacrifice a young goat to your SCSI chain now and then." -- John Woods ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] died again
On 12/16/2013 08:28 PM, Michael Hennebry wrote: >> btw, here's the technical product manual for your mainboard >> http://downloadmirror.intel.com/15207/eng/D865GBF_D865GLC_ProductGuide02_English.pdf > > That is where I got the 20-pin ATX stuff. > It just occured to me that I might want > geometric as well as electrical compatibility. > I wonder if its time to start considering a social list again; very little of the conversation in this thread is really CentOS specific now. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] 6.5 minimal kickstart bug?
I am new to kickstart file, but my understanding of the process is that I am supposed to be able to take the anaconda-ks-cfg file from the /root directory, copy it to an accessible location, and point the install disk to it, and it should reproduce the install I did originally. I used the 6.5 minimal install ISO, copied and renamed the ks.cfg. It is seen as a kickstart file, but it refuses to complete the install with the error message: - Unable to read package metadata. This may be due to a missing repodata directory. Please ensure that your install tree has been correctly generated. Cannot find a valid baseurl for repo: CentOS -- I read the kickstart file and found the Centos reference in the "repo" line, which the docs say is optional. I commented out that line, and the file works fine. I am guessing that this may be a capitalization mismatch? Or is there something I don't know? Do I need to do a bugzilla on this? Ted Miller Elkhart, IN, USA ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 6.5 minimal kickstart bug?
On 12/16/2013 10:52 PM, Ted Miller wrote: > > I read the kickstart file and found the Centos reference in the "repo" > line, which the docs say is optional. I commented out that line, and the > file works fine. its possible the url the --repo line was pointing at was either invalid or not accessible from the location you were doing the install from. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 6.5 minimal kickstart bug?
On 12/16/2013 07:53 PM, Karanbir Singh wrote: > On 12/16/2013 10:52 PM, Ted Miller wrote: >> >> I read the kickstart file and found the Centos reference in the "repo" >> line, which the docs say is optional. I commented out that line, and the >> file works fine. > > its possible the url the --repo line was pointing at was either invalid > or not accessible from the location you were doing the install from. > It is pointing at the CDROM. It was mointed. The line is: repo --name="CentOS" --baseurl=cdrom:sr0 --cost=100 Ted Miller ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] grub color on C6 (not)
I have tried more than half a dozen different combinations of the "color" command in my grub.conf file, and see nothing but black and white. Is there * a problem with the Centos grub command? * a problem with grub figuring out how to do color on my hardware? * a true-false day, when everything is either true or false, no in between grays, and no color? scratching my head, Ted Miller Elkhart, IN, USA ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Virtual Machine converted from physical : Kernel Panic at boot .
Hi. I used VMware Standalone converter 5.5 to convert a CentOS 5.3 machine from a Physical server to a Virtaul Machine on ESXi 5.1 . Thus far with every attempt to convert this machine I get a "Kernel panic" mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc failed: No such file or directory setuproot: error mounting /sys failed: No such file or directory switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!-22 I have follows the VMware provided solution for this situation but the results are the same http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002402 http://blog.edgoad.com/2010/03/vmware-no-volume-groups-found.html I have re-installed the CentOS kernel but that didn't make any difference. I have tried installing disk labels but that didn't make any difference. I have installed a clean install of 5.3 into a new vm , I even did a custom disk configuration to match that created by VMware Converter and that worked fine with most of the configuration being the same with the exception that it used disk labels. I'm at a loss at this point , I'm open to suggestions. Here are my configs as shown when using a rescue disk and chroot into /mnt/sysimage [root@localhost /]# cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 console=ttyS0,9600n8 console=tty0 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 #splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu # (removed by Converter) title Memtest86+ (1.65) # (removed by Converter)root (hd0,0) # (removed by Converter)kernel /memtest86+-1.65 ro root=/dev/VolGroup00/LogVol00 rhgb quiet title CentOS (2.6.18-128.7.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-128.7.1.el5 ro root=/dev/sdb1 rhgb quiet # kernel /vmlinuz-2.6.18-128.7.1.el5 ro root=LABEL=/ initrd /initrd-2.6.18-128.7.1.el5.img #title CustomKernel (2.6.18-128.7.1.el5) # root (hd0,0) # kernel /vmlinuz-2.6.18-128.7.1.el5 ro root=/dev/sdb1 rhgb quiet # initrd /initrd-2.6.18-128.7.1.el5.img [root@localhost /]# [root@localhost /]# cat /boot/grub/device.map (hd0) /dev/sda (hd1) /dev/sdb [root@localhost /]# [root@localhost /]# cat /etc/fstab /dev/sdb1 / ext3defaults,noatime1 2 #LABEL=// ext3defaults,noatime1 2 LABEL=/boot /boot ext3defaults1 2 tmpfs /dev/shmtmpfs defaults0 0 devpts /dev/ptsdevpts gid=5,mode=620 0 0 sysfs /syssysfs defaults0 0 proc/proc procdefaults0 0 [root@localhost /]# [root@localhost /]# fdisk -l /dev/sda Disk /dev/sda: 108 MB, 108134400 bytes 4 heads, 32 sectors/track, 1650 cylinders Units = cylinders of 128 * 512 = 65536 bytes Device Boot Start End Blocks Id System /dev/sda1 * 21633 104448 83 Linux [root@localhost /]# fdisk -l /dev/sdb Disk /dev/sdb: 159.9 GB, 159921602560 bytes 143 heads, 28 sectors/track, 78008 cylinders Units = cylinders of 4004 * 512 = 2050048 bytes Device Boot Start End Blocks Id System /dev/sdb1 1 78009 156172288 83 Linux [root@localhost /]# [root@localhost /]# mount /dev/sdb1 on / type ext3 (rw,noatime) /dev/sda1 on /boot type ext3 (rw) devpts on /dev/pts type devpts (rw) tmpfs on /dev/shm type tmpfs (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) [root@localhost /]# Thank you. G ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Virtual Machine converted from physical : Kernel Panic at boot .
On Tue, 17 Dec 2013, Gregory Machin wrote: > Hi. > > I used VMware Standalone converter 5.5 to convert a CentOS 5.3 machine from > a Physical server to a Virtaul Machine on ESXi 5.1 . Thus far with every > attempt to convert this machine I get a "Kernel panic" > > mount: could not find filesystem '/dev/root' > setuproot: moving /dev failed: No such file or directory > setuproot: error mounting /proc failed: No such file or directory > setuproot: error mounting /sys failed: No such file or directory > switchroot: mount failed: No such file or directory > Kernel panic - not syncing: Attempted to kill init!-22 I'm not following all of what is on the machine here, but here are some general things to try: 1. From what I can tell, your grub.conf expects /boot to be on its own partition, which appears to be sda1 .. is that the case? 2. Verify your /etc/fstab looks right for the new virtual HW you set up. 3. If that is correct, try using "grub-install /dev/sda" to reinstall your bootloader. 4. You might trying using the older/compatible versions of hardware, specifically the SCSI controller in case that is an issue. 5. In the event that it really can't find /proc or /sys mount in a chrooted rescue environment run "mkdir /proc /sys ; chmod 555 /proc ; chmod 755 /sys" Good luck! Barry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
