Re: [CentOS-es] POWERFAIL EN CENTOS 7
De nada, acabo de mirar en 3 máquinas CentOS 6.6 y ninguna tiene esa entrada en inittab. Es posible que tuvieses instalado NUT (perl-UPS-Nut.noarch) http://www.networkupstools.org eso requiere una entrada pf en inittab (posiblemente la cree al instalarse, pero no lo se) El 6/4/15 a las 22:07, Jesus Rudas Simmonds escribió: Gracias por responder. No tenía ningún software que hacia runlevel pf esto lo hacían los centos anteriores en el archivo /etc/inittab, lo que no se es si coloco esas líneas en ese mismo archivo en esa versión con esa estructura funcione -Mensaje original- De: centos-es-boun...@centos.org [mailto:centos-es-boun...@centos.org] En nombre de José María Terry Jiménez Enviado el: lunes, 06 de abril de 2015 02:57 p.m. Para: centos-es@centos.org Asunto: Re: [CentOS-es] POWERFAIL EN CENTOS 7 Posiblemente tendrías un software que hacía runlevel pf al recibir el corte de energía (monitorizando el puerto del UPS (o un socket o algo)). Tendrías que instalar ese software y hacer que arranque, por ejemplo si es antiguo y funcionaba sysvinit, posiblemente tengas que crearle una entrada para que systemd lo pueda iniciar (si el software es compatible). Por ejemplo en equipos APC este software es PowerChute y corre en Java. El 6/4/15 a las 21:31, Jesus Rudas Simmonds escribió: Buenas tardes. Siempre he tenido centos instalado en mi servidor el cual esta protegido por una UPS y le configuraba que cuando la UPS entraba en funcionamiento y y antes de descargarse enviaba una señal al centos que en /etc/inittab le decía que hacer. ME ha pasado a Centos 7 y no es lo mismo. Como puedo configurar mi centos 7 para que reciba la señal de la ups y se apage. El comando que tenia antes en /etc/inittab es: pf::powerfail:/sbin/shutdown -f -h +2 Power Failure; System Shutting Down Gracias Jesus Rudas Simmonds ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es
[CentOS-es] POWERFAIL EN CENTOS 7
Buenas tardes. Siempre he tenido centos instalado en mi servidor el cual esta protegido por una UPS y le configuraba que cuando la UPS entraba en funcionamiento y y antes de descargarse enviaba una señal al centos que en /etc/inittab le decía que hacer. ME ha pasado a Centos 7 y no es lo mismo. Como puedo configurar mi centos 7 para que reciba la señal de la ups y se apage. El comando que tenia antes en /etc/inittab es: pf::powerfail:/sbin/shutdown -f -h +2 Power Failure; System Shutting Down Gracias Jesus Rudas Simmonds ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es
Re: [CentOS-es] POWERFAIL EN CENTOS 7
Gracias por responder. No tenía ningún software que hacia runlevel pf esto lo hacían los centos anteriores en el archivo /etc/inittab, lo que no se es si coloco esas líneas en ese mismo archivo en esa versión con esa estructura funcione -Mensaje original- De: centos-es-boun...@centos.org [mailto:centos-es-boun...@centos.org] En nombre de José María Terry Jiménez Enviado el: lunes, 06 de abril de 2015 02:57 p.m. Para: centos-es@centos.org Asunto: Re: [CentOS-es] POWERFAIL EN CENTOS 7 Posiblemente tendrías un software que hacía runlevel pf al recibir el corte de energía (monitorizando el puerto del UPS (o un socket o algo)). Tendrías que instalar ese software y hacer que arranque, por ejemplo si es antiguo y funcionaba sysvinit, posiblemente tengas que crearle una entrada para que systemd lo pueda iniciar (si el software es compatible). Por ejemplo en equipos APC este software es PowerChute y corre en Java. El 6/4/15 a las 21:31, Jesus Rudas Simmonds escribió: Buenas tardes. Siempre he tenido centos instalado en mi servidor el cual esta protegido por una UPS y le configuraba que cuando la UPS entraba en funcionamiento y y antes de descargarse enviaba una señal al centos que en /etc/inittab le decía que hacer. ME ha pasado a Centos 7 y no es lo mismo. Como puedo configurar mi centos 7 para que reciba la señal de la ups y se apage. El comando que tenia antes en /etc/inittab es: pf::powerfail:/sbin/shutdown -f -h +2 Power Failure; System Shutting Down Gracias Jesus Rudas Simmonds ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es
[CentOS] filesystem corruption?
Got an older server here, running CentOS 6.6 (64-bit). Suddenly, at 0-dark-30 yesterday morning, we had failures to connect. After several tries to reboot and get working, I tried yum update, and that failed, complaining of an python krb5 error. With more investigation, I discovered that logins were failing as there was a problem with pam; this turned out to be it couldn't open /lib64/security/pam_permit.so. The reason for that was that it was a broken symlink, pointing to a file in the same directory, that actually existed in the /lib64. Checking other systems, I found it should, in fact, be a file, not a symlink. At this point, the system was considered suspect. I brought the system down, replaced the root drive, and rebuilt. I was not able to build it as CentOS 7, as something in the older hardware broke the install. CentOS 6 built successfully, and the server was returned to service. I then loaded the drive in another server, and examined it. fsck reported both / and /boot were clean, but when I redid this with fask -c, to check for bad blocks, it found many multiply-claimed blocks. First question: anyone have an idea why it showed as clean, until I checked for bad blocks? Would that just be because I'd gracefully shut down the original server, and it mounted ok on the other server? Mounting it on /mnt, I found no driver errors being reported in the logs, nor anything happening, including logons, before an automated contact from another server, which failed. AND I checked our loghost, and nothing odd shows there, neither in message nor in secure. At this point, I *think* it's filesystem corruption, rather than a compromised system, but I'd really like to hear anyone's thoughts on this. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Import Nautilus file notes from C6 Gnome to C7 Mate
On Wed, 1 Apr 2015 14:04:34 -0600 Frank Cox wrote: With C6 Gnome and C7 Mate you can right-click on a file icon, select Properties, select Notes, and write notes about your file. Does anyone know if those notes can be directly transferred between C6 Gnome and C7 Mate? Can I just copy that home file into the new C7 Mate desktop and have the file notes move in automatically, or do I have to somehow extract the notes and re-import them? To answer my own question here, I just created a new user on a Centos 7 machine and copied that user's home directory from Centos 6 to the Centos 7 machine with rsync. Logged in as that username and the file notes were present under C7 caja just like they were under C6 nautilus. So there is no extracting or importing required. It just works. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Satellite sync (spacewalk) of configuration channels?
Hello all. I have inter-Satellite sync set up and working on two Satellite servers downstream from a development Satellite server. Channels sync up fine, but I would like to sync up system groups and configuration channel content as well. Any ideas? Thanks, Chris ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] The future of centos
Le 04/04/2015 18:57, Bill Maltby (C4B) a écrit : Been UNIX (programming and user) since 1978, Linux since some early Slackware distributions, CentOS since 4.x. Will now be looking for something staying truer to the original UNIX concepts but full-featured and stable - may not be available, but I've got to at least look. I'm using Slackware and CentOS, and I'm happy with both. The former may be just what you are looking for. The bone-headed installer hasn't changed much since the early versions, building software from source is dead easy (without tossing a monkey wrench in the package manager), and everything JustWorks(tm). I have a few production servers and many desktop clients running Slackware, and I'm quite happy with it. I'm using CentOS for stuff that Slackware can't do (FreeIPA, etc.) Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] filesystem corruption?
On Mon, April 6, 2015 4:37 pm, m.r...@5-cent.us wrote: Got an older server here, running CentOS 6.6 (64-bit). Suddenly, at 0-dark-30 yesterday morning, we had failures to connect. After several tries to reboot and get working, I tried yum update, and that failed, complaining of an python krb5 error. With more investigation, I discovered that logins were failing as there was a problem with pam; this turned out to be it couldn't open /lib64/security/pam_permit.so. The reason for that was that it was a broken symlink, pointing to a file in the same directory, that actually existed in the /lib64. Checking other systems, I found it should, in fact, be a file, not a symlink. At this point, the system was considered suspect. I brought the system down, replaced the root drive, and rebuilt. I was not able to build it as CentOS 7, as something in the older hardware broke the install. CentOS 6 built successfully, and the server was returned to service. I then loaded the drive in another server, and examined it. fsck reported both / and /boot were clean, but when I redid this with fask -c, to check for bad blocks, it found many multiply-claimed blocks. First question: anyone have an idea why it showed as clean, until I checked for bad blocks? Would that just be because I'd gracefully shut down the original server, and it mounted ok on the other server? Mounting it on /mnt, I found no driver errors being reported in the logs, nor anything happening, including logons, before an automated contact from another server, which failed. AND I checked our loghost, and nothing odd shows there, neither in message nor in secure. At this point, I *think* it's filesystem corruption, rather than a compromised system, but I'd really like to hear anyone's thoughts on this. mark Someone has suggested to reformat disk. Before doing that you may want to make an image of the whole drive as it is now: dd the whole device into file (somewhere on huge filesystem). I definitely would do that before even running fsck or badblocks (BTW, badblocks has non-destructive mode) - too late to mention now. You may need this image for future forensics. The best would be to have some system integrity suite installed before bad event, then you will be able to tell what exactly changed (and approximately when). Alas, you don't seem to have that option. You should be able to use backup as a sort of replacement for that: (hopefully you back up system area as well). I would restore all on the closest date before event, compare all you had with what you see on mounted image(s) of your drive (I would definitely play with copy of copy of image, leaving original intact). I definitely would mount them read only with no journal. Take a look in logs what kind of events you find there. Check that logs were not tampered with (chkrootkit may be your friend). Take a look who logged when for how long (and from where!), see if there is correlation with some segfaults or kernel oopses, or if some kernel modules were loaded (should they be loaded all of a sudden?). Anyway, take some forensics guide if you don't do forensics often, and follow it. May take a couple of weeks depending on how busy you are in general. Good luck with that. Hardware (drive) hypothesis. It is very attractive. I would kick myself so wishful thinking will not take over. But if you indeed noticed bad blocks detected, this quite likely is your case. Again, logs must have records as drive will report its hardware events. I also would check SMART status of drive. Try to get some information from drive (hdparm comes to my mind, careful, you don't want to change anything which mostly hdparm is used for, just collect info). After everything else tried I would run hard drive fitness test (vendors have downloadable utility). BTW, what is model/manufacturer of the drive? [There is one more possibility which unlikely is your case: bad memory, or just just small memory error but in really bad place that cased big consequences. Reboot would resolve trouble, so it is unlikely your case. But if this hits specific place in RAM, it can cause corruption of filesystem as well...] Good luck! Let us know what you find out. Valeri Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] filesystem corruption?
On 2015-04-07, Valeri Galtsev galt...@kicp.uchicago.edu wrote: before even running fsck or badblocks (BTW, badblocks has non-destructive mode) - too late to mention now. You may need this image for future forensics. e2fsck -c will run badblocks in read-only mode, so it may not be too late. --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] filesystem corruption?
On 04/06/2015 02:37 PM, m.r...@5-cent.us wrote: I then loaded the drive in another server, and examined it. fsck reported both / and /boot were clean, but when I redid this with fask -c, to check for bad blocks, it found many multiply-claimed blocks. Just running fsck with no arguments will not do anything unless the filesystem is unclean or the time interval between checks has expired. I suspect that fsck -f would have found problems as well. Time will tell if there is a hardware problem with the system, but I would probably run some hardware diagnostics on the server including memory and IO tests if you wanted to be on the safe side. You could also reformat the disk and run some write/readback diagnostics if you wanted to find out if the disk is bad. Nataraj First question: anyone have an idea why it showed as clean, until I checked for bad blocks? Would that just be because I'd gracefully shut down the original server, and it mounted ok on the other server? Mounting it on /mnt, I found no driver errors being reported in the logs, nor anything happening, including logons, before an automated contact from another server, which failed. AND I checked our loghost, and nothing odd shows there, neither in message nor in secure. At this point, I *think* it's filesystem corruption, rather than a compromised system, but I'd really like to hear anyone's thoughts on this. mark ___ 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] NFS Stale file handle drives me crazy (Centos 6)
Have you tried exporting with options insecure,fsid=1? Cheers, Barbara On 06/04/15 06:00, Ted Miller wrote: On 04/02/2015 09:03 AM, Götz Reinicke - IT Koordinator wrote: Hi folks, I have a Centos 6 NFS server, which dirves me crazy. The directory I try to export cant be accessed by different clients. I tried a centos 7, centos 6 and a pool of vmware esxi 5.5 systems. At the client side I get errors like: mount.nfs: Stale file handle or Sysinfo set operation VSI_MODULE_NODE_mount failed with the tatus Unable to query remote mount point's attributes. On the server I get messages in the log like svc: 172.17.252.35, port=851: unknown version (0 for prog 13, nfsd) rpc.mountd[1927]: authenticated mount request from A good place to start on an issue like this would be to include your entire smb.conf file. Since you tried across three different Centos versions, It is likely either the configuration or the clients that are the problem. The curious thing is, that other directories exported on the same filesysten can be exported. Can they be used by the same clients that are trying to use the /home/stuff directories, or are the clients for the two directories different? so /home/stuff works /home/students fails. chmode 777 is set, /etc/exports is double checked. nfs/rpc/etc is up and running. selinux firewall for debugging off. I use xfs on all shared filesystems. Googling for VMWARE and native NFS suggestions did not help so far :-/ Any hint or suggestion is very very welcome! Regard thanks . Götz Ted Miller Elkhart, IN, USA ___ 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] vncserver on centos 7
On 04/06/2015 04:56 AM, Jerry Geis wrote: Is there a way to make vncserver on centos 7 to be read only? I want to allow someone to connect and see the screen- but not change it of course. Thanks, jerry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Add -AcceptPointerEvents=0 and -AcceptKeyEvents=0 to the vncserver commandline in vncserver@:#.service file, or on the Xvnc command line. Emmett ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] vncserver on centos 7
Is there a way to make vncserver on centos 7 to be read only? I want to allow someone to connect and see the screen- but not change it of course. Thanks, jerry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS-virt] upstream packages rebuilt for EL7
Hi, You can find some upstream packages I've built for EL7. My testing purposes are only about KVM and Ceph but there is also a Xen package you feel free to play with. https://copr.fedoraproject.org/coprs/jmliger/virt7-upstream/ Regards, Jean-Marc ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS] Firewall-config NetworkManager Problem (Centos-7( 1))
Hello I installed the Firewall-config on a new system and have bad Errors The firewall-config brake with a error line 53 can't load NetworkManager and on a reboot I have this Message. ABRT hat 1 Fehler festgestellt. (Für weitere Informationen: abrt-cli list -- since 1428305986) [root@ipa1 ~]# abrt-cli list --since 1428305986 id 659c6c2d4ec4cc75b8e2156b5be69375e551b82a reason: firewall-config:34:module:ImportError: cannot import name NetworkManager time: Mo 06 Apr 2015 09:19:58 CEST cmdline:/usr/bin/python -Es /usr/bin/firewall-config package:firewall-config-0.3.9-11.el7 uid:0 (root) count: 2 Directory: /var/tmp/abrt/Python-2015-04-06-09:19:58-3224 Have any a Hint? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
