Re: [CentOS] ][SOLVED] suddenly X gives black screen with small clock cursor
On Fri, Oct 11, 2013 at 02:06:19PM -0400, Fred Smith wrote: > On Fri, Oct 11, 2013 at 09:41:08AM -0400, Fred Smith wrote: > > On Fri, Oct 11, 2013 at 02:50:14AM -0700, John Doe wrote: > > > From: Fred Smith > > > > > > > I rebooted a while ago (and in between the down and up, I installed > > > > Fedora > > > > 20 Beta on a USB hard drive, making sure it wouldn't mess with my > > > > Centos system). The install went fine, but afterwards, when I reboot > > > > Centos, it > > > > comes up with a black screen and a clock as the mouse cursor (small > > > > clock). > > > > > > > > chmod a+rw /dev/null > > > > chmod a+rw /dev/urandom > > > > chmod a+rw /dev/zero > > > > chmod a+rw /dev/full > > > > chmod a+rw /dev/random > > > > > > > > Can anyone suggest an accurate way to have the system fix all the > > > > permissions > > > > in /dev? some arcane options on rpm, perhaps? > > > > > > Nothing at all in the logs...? > > > > Nothing I can see in the logs looks particularly damning. > > > > > Global check: rpm -qVa > > running that right now, will post again if anything interesting turns up. > > > > > Maybe check udev confs...? > > I was thinking of that, but the amount I know aobut udev wouldn't cover > > the head of a pin. Open to suggestions, though. > > Looking in /lib/udev/rules.d/50-udev-default.rules I see: > > KERNEL=="ptmx", GROUP="tty", MODE="0666" > KERNEL=="null|zero|full|random|urandom", MODE="0666" > > so if I understand them right, /dev/ptmx, /dev/null, /dev/zero, /dev/full, > /dev/random, and /dev/urandom should all come up as 'rw' for all users > after a system boot, but they don't. I reboot and they all come up as > 0644, crw-rw. grepping for "null" in /lib/udev finds only that > single entry in all of the files, as does "ptmx". > > So, I wonder if something is preventing this file from being run (which > seems unlikely, given that it contains a ton of rules which would all > be skipped). I note that /etc/udev/rules.d contains a rules file with > exactly the same name (which sets up some firewire stuff) and wonder if > that's a problem,... anyone know? sigh. the problem, had this been a car, could have been diagnosed as: "There's a loose nut behind the wheel." I.e., me. it's exactly due to the duplicate udev rules filenames, one in /etc/udev/rules.d and the other in lib/udev/rules.d. Self-inflicted damage. PROBLEM SOLVED. -- Fred Smith -- fre...@fcshome.stoneham.ma.us - The eyes of the Lord are everywhere, keeping watch on the wicked and the good. - Proverbs 15:3 (niv) - ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VNC
Humm, Could windows machine be blocking the port going out? If your using putty as a ssh client you could try to port forward (5901, 5901) through the ssh session and then try to connect using localhost:5901 or localhost:5902 on the windows machine and see if you can connect. It can be done with other ssh clients but I've only used putty, so I know it can be done with it. You might also compare some of the settings to this page http://wiki.centos.org/HowTos/VNC-Server You could try stopping the servers and running the vncserver in the console to see if there are connections or errors - but I'm not sure with the configuration your using if that is possible. I'm not sure what else to offer. -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Larry Martell Sent: Friday, October 11, 2013 7:13 PM To: CentOS mailing list Subject: Re: [CentOS] VNC On Fri, Oct 11, 2013 at 4:45 PM, Terre Porter wrote: > You can specify the port with the IP by using the colon with the ip. > > x.x.x.x:5901 or x.x.x.x:5902 > Those both give me connection refused (as opposed to without the port, where I get connection timed out) > > > -Original Message- > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > Behalf Of Larry Martell > Sent: Friday, October 11, 2013 6:35 PM > To: CentOS mailing list > Subject: Re: [CentOS] VNC > > On Fri, Oct 11, 2013 at 4:26 PM, Terre Porter > wrote: > > > The instructions out linked to has a type-o at the end says to > > connect to > > ip:5801 should be 5901. > > > > If your using a vnc client uvnc, tightvnc.. try using just the ip > > without the :port part or :1 for the 5901. > > > > I am unfortunately connecting from a windows box that I do not have > admin rights on. I have to use the client provided, which is RealVNC > Viewer. All I can do is give the ip. > > > > Try lsof -i -P | grep -i "listen" > > > > To see what ports are listening... > > > > > [root@10 sysconfig]# lsof -i -P | grep -i "listen" | grep vnc > Xvnc 22052 motor4u IPv4 527366 0t0 TCP > localhost.localdomain:5901 (LISTEN) > Xvnc 22286 motor4u IPv4 530145 0t0 TCP > localhost.localdomain:5902 (LISTEN) > > > > > > -Original Message- > > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] > > On Behalf Of Larry Martell > > Sent: Friday, October 11, 2013 6:05 PM > > To: CentOS mailing list > > Subject: Re: [CentOS] VNC > > > > On Fri, Oct 11, 2013 at 3:42 PM, Terre Porter > > wrote: > > > > > Try this, iptables dump from my fresh install, with ssh allow and > > > the vnc you referenced. > > > > > > Terre > > > > > > # Generated by iptables-save v1.4.7 on Fri Oct 11 17:39:52 2013 > > > *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT > > > [45:7091] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT > > > -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p > > > tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -m > > > state --state NEW -m tcp -p tcp -m multiport --dports > > > 5901:5903,6001:6003 -j ACCEPT > > > -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD > > > -j REJECT --reject-with icmp-host-prohibited COMMIT # Completed on > > > Fri Oct 11 17:39:52 2013 > > > > > > > > OK, with this file I'm getting connection timed out - before I was > > getting connection refused so I guess that's some progress. > > > > > > > > > > > -Original Message- > > > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] > > > On Behalf Of Larry Martell > > > Sent: Friday, October 11, 2013 5:36 PM > > > To: CentOS mailing list > > > Subject: Re: [CentOS] VNC > > > > > > On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez > > > > > >wrote: > > > > > > > > > > > On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote: > > > > > I'm trying to set up a VNC server using the instructions at > > > > > > > > > http://www.techrepublic.com/blog/linux-and-open-source/linux-101 > > > > -e > > > > as > > > > y- > > > > vnc-server-setup/ > > > > > . > > > > > > > > > > I am up to step 6: > > > > > > > > > > Step 6: Edit iptables > > > > > > > > > > In order for the VNC connections to get through, you must > > > > > allow them with iptables. To do this, open up the file > > > > > /etc/sysconfig/iptables and add > > > > the > > > > > line: > > > > > > > > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport > > > > > --dports > > > > > 5901:5903,6001:6003 -j ACCEPT > > > > > > > > > > Save the file and restart iptables with the command: > > > > > > > > > > service iptables restart > > > > > > > > > > When I issue the restart command I get: > > > > > > > > > > iptables: Applying firewall rules: iptables-restore: line 1 > > > > > failed > > > > > > > > > > [FAILED] > > > > > > > > > > Note that I did not have an iptables file before but there is > > > > > an iptables-config file. > > > > > > > > > > Can someon
Re: [CentOS] VNC
On Fri, Oct 11, 2013 at 4:45 PM, Terre Porter wrote: > You can specify the port with the IP by using the colon with the ip. > > x.x.x.x:5901 or x.x.x.x:5902 > Those both give me connection refused (as opposed to without the port, where I get connection timed out) > > > -Original Message- > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > Behalf > Of Larry Martell > Sent: Friday, October 11, 2013 6:35 PM > To: CentOS mailing list > Subject: Re: [CentOS] VNC > > On Fri, Oct 11, 2013 at 4:26 PM, Terre Porter > wrote: > > > The instructions out linked to has a type-o at the end says to connect > > to > > ip:5801 should be 5901. > > > > If your using a vnc client uvnc, tightvnc.. try using just the ip > > without the :port part or :1 for the 5901. > > > > I am unfortunately connecting from a windows box that I do not have admin > rights on. I have to use the client provided, which is RealVNC Viewer. All > I can do is give the ip. > > > > Try lsof -i -P | grep -i "listen" > > > > To see what ports are listening... > > > > > [root@10 sysconfig]# lsof -i -P | grep -i "listen" | grep vnc > Xvnc 22052 motor4u IPv4 527366 0t0 TCP > localhost.localdomain:5901 (LISTEN) > Xvnc 22286 motor4u IPv4 530145 0t0 TCP > localhost.localdomain:5902 (LISTEN) > > > > > > -Original Message- > > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > > Behalf Of Larry Martell > > Sent: Friday, October 11, 2013 6:05 PM > > To: CentOS mailing list > > Subject: Re: [CentOS] VNC > > > > On Fri, Oct 11, 2013 at 3:42 PM, Terre Porter > > wrote: > > > > > Try this, iptables dump from my fresh install, with ssh allow and > > > the vnc you referenced. > > > > > > Terre > > > > > > # Generated by iptables-save v1.4.7 on Fri Oct 11 17:39:52 2013 > > > *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT > > > [45:7091] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A > > > INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m > > > state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -m state > > > --state NEW -m tcp -p tcp -m multiport --dports > > > 5901:5903,6001:6003 -j ACCEPT > > > -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j > > > REJECT --reject-with icmp-host-prohibited COMMIT # Completed on Fri > > > Oct 11 17:39:52 2013 > > > > > > > > OK, with this file I'm getting connection timed out - before I was > > getting connection refused so I guess that's some progress. > > > > > > > > > > > -Original Message- > > > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] > > > On Behalf Of Larry Martell > > > Sent: Friday, October 11, 2013 5:36 PM > > > To: CentOS mailing list > > > Subject: Re: [CentOS] VNC > > > > > > On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez > > > > > >wrote: > > > > > > > > > > > On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote: > > > > > I'm trying to set up a VNC server using the instructions at > > > > > > > > > http://www.techrepublic.com/blog/linux-and-open-source/linux-101-e > > > > as > > > > y- > > > > vnc-server-setup/ > > > > > . > > > > > > > > > > I am up to step 6: > > > > > > > > > > Step 6: Edit iptables > > > > > > > > > > In order for the VNC connections to get through, you must allow > > > > > them with iptables. To do this, open up the file > > > > > /etc/sysconfig/iptables and add > > > > the > > > > > line: > > > > > > > > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport > > > > > --dports > > > > > 5901:5903,6001:6003 -j ACCEPT > > > > > > > > > > Save the file and restart iptables with the command: > > > > > > > > > > service iptables restart > > > > > > > > > > When I issue the restart command I get: > > > > > > > > > > iptables: Applying firewall rules: iptables-restore: line 1 > > > > > failed > > > > > > > > > > [FAILED] > > > > > > > > > > Note that I did not have an iptables file before but there is an > > > > > iptables-config file. > > > > > > > > > > Can someone help me complete this configuration. > > > > > > > > Can you post the content of the file, I just edit the config file > > > > and I didn't get any errors when I issue the command > > > > > > > > $ sudo /sbin/service iptables restart > > > > > > > > > > > As I wrote, there was no iptables file. I created one with just that > > > one > > > line: > > > > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > > > 5901:5903,6001:6003 -j ACCEPT > > > ___ > > > 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 > > > > > ___ > > CentOS mailing list > > CentOS@centos.org > > http://lists.centos.org/mailman/listinfo/centos > > >
Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd
I have the latest bios installed - DMI: MICRO-STAR INTERNATIONAL CO.,LTD MS-7596/785GM-E51 (MS-7596), BIOS V2.12 02/18/2011 However, I just used the ELRepo to install kernel-ml (Linux version 3.11.4-1.el6.elrepo.x86_64) and it shuts down fine,.. Of course, it has other errors - lol So I'm leaning toward it’s a kernel bug with these kernel-2.6.32-358.18.1.el6.x86_64 and kernel-2.6.32-358.el6.x86_64 (the two installed by default) Now I'm going to try to locate the kernel version list so I can see if I can get a smaller jump in version up to test with. kernel-ml-3.11.4-1.el6.elrepo.x86_64 worked as expected on the shutdown, but has some other issues. -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of James A. Peltier Sent: Friday, October 11, 2013 6:58 PM To: CentOS mailing list Subject: Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd Update your BIOS if there is one. I've found that to often be the cause. - Original Message - | Same result, doesn't turn off. | | Any other ideas? | | -Original Message- | From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On | Behalf Of Andrew Wyatt | Sent: Friday, October 11, 2013 4:41 PM | To: CentOS mailing list | Subject: Re: [CentOS] Centos 6.4 - doesnt power off with | shutdown/poweroff cmd | | Try using the reboot=pci grub parameter. | | | On Fri, Oct 11, 2013 at 11:40 AM, Terre Porter | wrote: | | > Hello, | > | > | > | > I'm looking for help figuring out why I am having problems with | > shutting down a machine. | > | > | > | > I have tested the machine using Fedora 19 and Ubuntu 12 Live CD's | > and both power down without issues. | > | > | > | > I added acpi.debug_level=1 to the grub boot as it was suggested to | > see more info about ACPI in the logs | > | > | > | > I found the following ACPI Errors in the /var/log/messages | > | > | > | > Oct 11 11:51:36 plum kernel: ACPI Error (psargs-0359): [ECEN] | > Namespace lookup failure, AE_NOT_FOUND | > | > Oct 11 11:51:36 plum kernel: ACPI Error (psparse-0537): Method | > parse/execution failed [\] (Node 81fdbeb0), AE_NOT_FOUND | > | > | > | > Oct 11 11:51:36 plum kernel: ACPI: resource piix4_smbus [io | > 0x0b00-0x0b07] conflicts with ACPI region SOR1 [io 0xb00-0xb0f] | > | > Oct 11 11:51:36 plum kernel: ACPI: If an ACPI driver is available | > for this device, you should use it instead of the native driver | > | > | > | > I used the Centos 6.4 Live CD last night with no hard drive in the | > system. | > | > | > | > I photo'd the shutdown, here is the type up: | > | > | > | > Sending all processes the TERM signal... | > | > Sendng all processes the KILL signal... | > | > Saving random seed: | > | > Syncing hardware clock to system time | > | > Turning off quotas: | > | > umount2: Device or resource busy | > | > umount: /dev/.initramfs/live: device is busy. | > | > (In some cases useful info about processes that use | > | > the device is found by lsof(8) or fuser(11)) | > | > init: Re-executing /sbin/init | > | > Halting System... | > | > r8169 :02:00.0: PME# enabled | > | > ACPI: Preparing to enter system sleep state S5 | > | > ACPI Error (psargs-0359): [PPTS] Namespace lookup failure, | > AE_NOT_FOUND | > | > ACPI Error (psparse-0537): Method parse/execution failed | > [\_SB_.PCI0.SBRG.EPTS] (Node fff88019dbc8c68), AE_NOT_FOUND | > | > ACPI Error (psparse-0537): Method parse/execution failed [\PTS_] | > (Node 88019d043560), AE_NOT_FOUND | > | > ACPI Error (psparse-0537): Method parse/execution failed [\_PTS] | > (Node 88019dbcf9e8), AE_NOT_FOUND | > | > Disabling non-boot CPUS... | > | > SMP alternatives: switching to UP code | > | > Power Down. | > | > acpi_power_off called | > | > | > | > The system doesn't power off, it just sits there. I have to hold the | > power button in for it to shut down. | > | > | > | > The same still occurs with a completed a fresh minimum install of | > Centos 6.4, installed the EPEL repo and did yum update. | > | > | > | > I'm running the latest bios for the motherboard, and even tried | > going back one version. | > | > | > | > MB: 785GM-E51 (MS-7596 1.2) | > | > CPU: AMD Phenom II x4 945 3ghz | > | > 1TB HD, 6 Gig Mem | > | > | > | > Any ideas? | > | > | > | > (Besides using a baseball bat - I am considering it) | > | > | > | > Here is some hardware info from the getinfo.sh script listed the | > forums. | > | > | > | > == BEGIN uname -rmi == | > | > 2.6.32-358.18.1.el6.x86_64 x86_64 x86_64 | > | > == END uname -rmi == | > | > | > | > == BEGIN rpm -qa \*-release\* == | > | > centos-release-6-4.el6.centos.10.x86_64 | > | > epel-release-6-8.noarch | > | > == END rpm -qa \*-release\* == | > | > | > | > == BEGIN cat /etc/redhat-release == | > | > CentOS release 6.4 (Final) | > | > == END cat /etc/redhat-release == | > | > | > | > == BEGIN getenforce == | > | > Enforcing | > | > == EN
Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd
Update your BIOS if there is one. I've found that to often be the cause. - Original Message - | Same result, doesn't turn off. | | Any other ideas? | | -Original Message- | From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On | Behalf | Of Andrew Wyatt | Sent: Friday, October 11, 2013 4:41 PM | To: CentOS mailing list | Subject: Re: [CentOS] Centos 6.4 - doesnt power off with | shutdown/poweroff | cmd | | Try using the reboot=pci grub parameter. | | | On Fri, Oct 11, 2013 at 11:40 AM, Terre Porter | wrote: | | > Hello, | > | > | > | > I'm looking for help figuring out why I am having problems with | > shutting down a machine. | > | > | > | > I have tested the machine using Fedora 19 and Ubuntu 12 Live CD's | > and | > both power down without issues. | > | > | > | > I added acpi.debug_level=1 to the grub boot as it was suggested to | > see | > more info about ACPI in the logs | > | > | > | > I found the following ACPI Errors in the /var/log/messages | > | > | > | > Oct 11 11:51:36 plum kernel: ACPI Error (psargs-0359): [ECEN] | > Namespace lookup failure, AE_NOT_FOUND | > | > Oct 11 11:51:36 plum kernel: ACPI Error (psparse-0537): Method | > parse/execution failed [\] (Node 81fdbeb0), AE_NOT_FOUND | > | > | > | > Oct 11 11:51:36 plum kernel: ACPI: resource piix4_smbus [io | > 0x0b00-0x0b07] conflicts with ACPI region SOR1 [io 0xb00-0xb0f] | > | > Oct 11 11:51:36 plum kernel: ACPI: If an ACPI driver is available | > for | > this device, you should use it instead of the native driver | > | > | > | > I used the Centos 6.4 Live CD last night with no hard drive in the | > system. | > | > | > | > I photo'd the shutdown, here is the type up: | > | > | > | > Sending all processes the TERM signal... | > | > Sendng all processes the KILL signal... | > | > Saving random seed: | > | > Syncing hardware clock to system time | > | > Turning off quotas: | > | > umount2: Device or resource busy | > | > umount: /dev/.initramfs/live: device is busy. | > | > (In some cases useful info about processes that use | > | > the device is found by lsof(8) or fuser(11)) | > | > init: Re-executing /sbin/init | > | > Halting System... | > | > r8169 :02:00.0: PME# enabled | > | > ACPI: Preparing to enter system sleep state S5 | > | > ACPI Error (psargs-0359): [PPTS] Namespace lookup failure, | > AE_NOT_FOUND | > | > ACPI Error (psparse-0537): Method parse/execution failed | > [\_SB_.PCI0.SBRG.EPTS] (Node fff88019dbc8c68), AE_NOT_FOUND | > | > ACPI Error (psparse-0537): Method parse/execution failed [\PTS_] | > (Node | > 88019d043560), AE_NOT_FOUND | > | > ACPI Error (psparse-0537): Method parse/execution failed [\_PTS] | > (Node | > 88019dbcf9e8), AE_NOT_FOUND | > | > Disabling non-boot CPUS... | > | > SMP alternatives: switching to UP code | > | > Power Down. | > | > acpi_power_off called | > | > | > | > The system doesn't power off, it just sits there. I have to hold | > the | > power button in for it to shut down. | > | > | > | > The same still occurs with a completed a fresh minimum install of | > Centos 6.4, installed the EPEL repo and did yum update. | > | > | > | > I'm running the latest bios for the motherboard, and even tried | > going | > back one version. | > | > | > | > MB: 785GM-E51 (MS-7596 1.2) | > | > CPU: AMD Phenom II x4 945 3ghz | > | > 1TB HD, 6 Gig Mem | > | > | > | > Any ideas? | > | > | > | > (Besides using a baseball bat - I am considering it) | > | > | > | > Here is some hardware info from the getinfo.sh script listed the | > forums. | > | > | > | > == BEGIN uname -rmi == | > | > 2.6.32-358.18.1.el6.x86_64 x86_64 x86_64 | > | > == END uname -rmi == | > | > | > | > == BEGIN rpm -qa \*-release\* == | > | > centos-release-6-4.el6.centos.10.x86_64 | > | > epel-release-6-8.noarch | > | > == END rpm -qa \*-release\* == | > | > | > | > == BEGIN cat /etc/redhat-release == | > | > CentOS release 6.4 (Final) | > | > == END cat /etc/redhat-release == | > | > | > | > == BEGIN getenforce == | > | > Enforcing | > | > == END getenforce == | > | > | > | > == BEGIN rpm -qa kernel\* | sort == | > | > kernel-2.6.32-358.18.1.el6.x86_64 | > | > kernel-2.6.32-358.el6.x86_64 | > | > kernel-firmware-2.6.32-358.18.1.el6.noarch | > | > == END rpm -qa kernel\* | sort == | > | > | > | > == BEGIN lspci -nn == | > | > 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS880 Host | > Bridge [1022:9601] | > | > 00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 | > PCI to PCI bridge (int gfx) [1022:9602] | > | > 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 | > PCI to PCI bridge (PCIE port 1) [1022:9605] | > | > 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee | > ATI | > SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] | > | > 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI | > SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] | > | > 00:12.1 USB contr
Re: [CentOS] VNC
You can specify the port with the IP by using the colon with the ip. x.x.x.x:5901 or x.x.x.x:5902 -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Larry Martell Sent: Friday, October 11, 2013 6:35 PM To: CentOS mailing list Subject: Re: [CentOS] VNC On Fri, Oct 11, 2013 at 4:26 PM, Terre Porter wrote: > The instructions out linked to has a type-o at the end says to connect > to > ip:5801 should be 5901. > > If your using a vnc client uvnc, tightvnc.. try using just the ip > without the :port part or :1 for the 5901. > I am unfortunately connecting from a windows box that I do not have admin rights on. I have to use the client provided, which is RealVNC Viewer. All I can do is give the ip. > Try lsof -i -P | grep -i "listen" > > To see what ports are listening... > [root@10 sysconfig]# lsof -i -P | grep -i "listen" | grep vnc Xvnc 22052 motor4u IPv4 527366 0t0 TCP localhost.localdomain:5901 (LISTEN) Xvnc 22286 motor4u IPv4 530145 0t0 TCP localhost.localdomain:5902 (LISTEN) > > -Original Message- > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > Behalf Of Larry Martell > Sent: Friday, October 11, 2013 6:05 PM > To: CentOS mailing list > Subject: Re: [CentOS] VNC > > On Fri, Oct 11, 2013 at 3:42 PM, Terre Porter > wrote: > > > Try this, iptables dump from my fresh install, with ssh allow and > > the vnc you referenced. > > > > Terre > > > > # Generated by iptables-save v1.4.7 on Fri Oct 11 17:39:52 2013 > > *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT > > [45:7091] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A > > INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m > > state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -m state > > --state NEW -m tcp -p tcp -m multiport --dports > > 5901:5903,6001:6003 -j ACCEPT > > -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j > > REJECT --reject-with icmp-host-prohibited COMMIT # Completed on Fri > > Oct 11 17:39:52 2013 > > > > > OK, with this file I'm getting connection timed out - before I was > getting connection refused so I guess that's some progress. > > > > > > > -Original Message- > > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] > > On Behalf Of Larry Martell > > Sent: Friday, October 11, 2013 5:36 PM > > To: CentOS mailing list > > Subject: Re: [CentOS] VNC > > > > On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez > > > >wrote: > > > > > > > > On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote: > > > > I'm trying to set up a VNC server using the instructions at > > > > > > > http://www.techrepublic.com/blog/linux-and-open-source/linux-101-e > > > as > > > y- > > > vnc-server-setup/ > > > > . > > > > > > > > I am up to step 6: > > > > > > > > Step 6: Edit iptables > > > > > > > > In order for the VNC connections to get through, you must allow > > > > them with iptables. To do this, open up the file > > > > /etc/sysconfig/iptables and add > > > the > > > > line: > > > > > > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport > > > > --dports > > > > 5901:5903,6001:6003 -j ACCEPT > > > > > > > > Save the file and restart iptables with the command: > > > > > > > > service iptables restart > > > > > > > > When I issue the restart command I get: > > > > > > > > iptables: Applying firewall rules: iptables-restore: line 1 > > > > failed > > > > > > > > [FAILED] > > > > > > > > Note that I did not have an iptables file before but there is an > > > > iptables-config file. > > > > > > > > Can someone help me complete this configuration. > > > > > > Can you post the content of the file, I just edit the config file > > > and I didn't get any errors when I issue the command > > > > > > $ sudo /sbin/service iptables restart > > > > > > > > As I wrote, there was no iptables file. I created one with just that > > one > > line: > > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > > 5901:5903,6001:6003 -j ACCEPT > > ___ > > 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 > > > ___ > 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 > ___ 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] display full-screen color graphic without X
On Fri, 11 Oct 2013 18:30:08 -0400 ken wrote: > Need to test a monitor attached to a running server, so I'm looking for > an application/utility to display a large color graphic. This must be > possible to do without X because a splash screen comes up when this > system boots. The best graphic to display obviously would be some kind > of fullscreen test pattern. Anyone know where to get that? You probably want the fbi image viewer that comes in the fbida rpm. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VNC
On Fri, Oct 11, 2013 at 4:26 PM, Terre Porter wrote: > The instructions out linked to has a type-o at the end says to connect to > ip:5801 should be 5901. > > If your using a vnc client uvnc, tightvnc.. try using just the ip without > the :port part or :1 for the 5901. > I am unfortunately connecting from a windows box that I do not have admin rights on. I have to use the client provided, which is RealVNC Viewer. All I can do is give the ip. > Try lsof -i -P | grep -i "listen" > > To see what ports are listening... > [root@10 sysconfig]# lsof -i -P | grep -i "listen" | grep vnc Xvnc 22052 motor4u IPv4 527366 0t0 TCP localhost.localdomain:5901 (LISTEN) Xvnc 22286 motor4u IPv4 530145 0t0 TCP localhost.localdomain:5902 (LISTEN) > > -Original Message- > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > Behalf > Of Larry Martell > Sent: Friday, October 11, 2013 6:05 PM > To: CentOS mailing list > Subject: Re: [CentOS] VNC > > On Fri, Oct 11, 2013 at 3:42 PM, Terre Porter > wrote: > > > Try this, iptables dump from my fresh install, with ssh allow and the > > vnc you referenced. > > > > Terre > > > > # Generated by iptables-save v1.4.7 on Fri Oct 11 17:39:52 2013 > > *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT > > [45:7091] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A > > INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m > > state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -m state > > --state NEW -m tcp -p tcp -m multiport --dports > > 5901:5903,6001:6003 -j ACCEPT > > -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j > > REJECT --reject-with icmp-host-prohibited COMMIT # Completed on Fri > > Oct 11 17:39:52 2013 > > > > > OK, with this file I'm getting connection timed out - before I was getting > connection refused so I guess that's some progress. > > > > > > > -Original Message- > > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > > Behalf Of Larry Martell > > Sent: Friday, October 11, 2013 5:36 PM > > To: CentOS mailing list > > Subject: Re: [CentOS] VNC > > > > On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez > >wrote: > > > > > > > > On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote: > > > > I'm trying to set up a VNC server using the instructions at > > > > > > > http://www.techrepublic.com/blog/linux-and-open-source/linux-101-eas > > > y- > > > vnc-server-setup/ > > > > . > > > > > > > > I am up to step 6: > > > > > > > > Step 6: Edit iptables > > > > > > > > In order for the VNC connections to get through, you must allow > > > > them with iptables. To do this, open up the file > > > > /etc/sysconfig/iptables and add > > > the > > > > line: > > > > > > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > > > > 5901:5903,6001:6003 -j ACCEPT > > > > > > > > Save the file and restart iptables with the command: > > > > > > > > service iptables restart > > > > > > > > When I issue the restart command I get: > > > > > > > > iptables: Applying firewall rules: iptables-restore: line 1 failed > > > > > > > > [FAILED] > > > > > > > > Note that I did not have an iptables file before but there is an > > > > iptables-config file. > > > > > > > > Can someone help me complete this configuration. > > > > > > Can you post the content of the file, I just edit the config file > > > and I didn't get any errors when I issue the command > > > > > > $ sudo /sbin/service iptables restart > > > > > > > > As I wrote, there was no iptables file. I created one with just that > > one > > line: > > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > > 5901:5903,6001:6003 -j ACCEPT > > ___ > > 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 > > > ___ > 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 > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cleaning up some LVM stuff
On Fri, Oct 11, 2013 at 9:42 AM, Götz Reinicke - IT Koordinator < goetz.reini...@filmakademie.de> wrote: > Hi, > > one more LVM thing: > > on one server some LVM stores are physically removed but still there are > some informatione somwher spread adcross teh server. > > e.g. if I do a vgdisplay or pvcreat I get an error regarding that old > storage: > > /dev/raid_10/lvol0: read failed after 0 of 4096 at 14000515383296: > Eingabe-/Ausgabefehler > > How can I remove all information? > What you shoul have done is deactivated that volume group before physically removing the storage media. I think what you want is the following: [ Disclaimer: I didn't test this yet. ] vgchange -a n raid_10 > > Thanks for any hint. Regards . Götz > > -- > Götz Reinicke > IT-Koordinator > > Tel. +49 7141 969 82 420 > Fax +49 7141 969 55 420 > E-Mail goetz.reini...@filmakademie.de > > Filmakademie Baden-Württemberg GmbH > Akademiehof 10 > 71638 Ludwigsburg > www.filmakademie.de > > Eintragung Amtsgericht Stuttgart HRB 205016 > > Vorsitzender des Aufsichtsrats: Jürgen Walter MdL > Staatssekretär im Ministerium für Wissenschaft, > Forschung und Kunst Baden-Württemberg > > Geschäftsführer: Prof. Thomas Schadt > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > -- ---~~.~~--- Mike // SilverTip257 // ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] display full-screen color graphic without X
Need to test a monitor attached to a running server, so I'm looking for an application/utility to display a large color graphic. This must be possible to do without X because a splash screen comes up when this system boots. The best graphic to display obviously would be some kind of fullscreen test pattern. Anyone know where to get that? tia, ken ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VNC
The instructions out linked to has a type-o at the end says to connect to ip:5801 should be 5901. If your using a vnc client uvnc, tightvnc.. try using just the ip without the :port part or :1 for the 5901. Try lsof -i -P | grep -i "listen" To see what ports are listening... Terre -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Larry Martell Sent: Friday, October 11, 2013 6:05 PM To: CentOS mailing list Subject: Re: [CentOS] VNC On Fri, Oct 11, 2013 at 3:42 PM, Terre Porter wrote: > Try this, iptables dump from my fresh install, with ssh allow and the > vnc you referenced. > > Terre > > # Generated by iptables-save v1.4.7 on Fri Oct 11 17:39:52 2013 > *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT > [45:7091] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A > INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m > state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -m state > --state NEW -m tcp -p tcp -m multiport --dports > 5901:5903,6001:6003 -j ACCEPT > -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j > REJECT --reject-with icmp-host-prohibited COMMIT # Completed on Fri > Oct 11 17:39:52 2013 > > OK, with this file I'm getting connection timed out - before I was getting connection refused so I guess that's some progress. > > > -Original Message- > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > Behalf Of Larry Martell > Sent: Friday, October 11, 2013 5:36 PM > To: CentOS mailing list > Subject: Re: [CentOS] VNC > > On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez >wrote: > > > > > On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote: > > > I'm trying to set up a VNC server using the instructions at > > > > > http://www.techrepublic.com/blog/linux-and-open-source/linux-101-eas > > y- > > vnc-server-setup/ > > > . > > > > > > I am up to step 6: > > > > > > Step 6: Edit iptables > > > > > > In order for the VNC connections to get through, you must allow > > > them with iptables. To do this, open up the file > > > /etc/sysconfig/iptables and add > > the > > > line: > > > > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > > > 5901:5903,6001:6003 -j ACCEPT > > > > > > Save the file and restart iptables with the command: > > > > > > service iptables restart > > > > > > When I issue the restart command I get: > > > > > > iptables: Applying firewall rules: iptables-restore: line 1 failed > > > > > > [FAILED] > > > > > > Note that I did not have an iptables file before but there is an > > > iptables-config file. > > > > > > Can someone help me complete this configuration. > > > > Can you post the content of the file, I just edit the config file > > and I didn't get any errors when I issue the command > > > > $ sudo /sbin/service iptables restart > > > > > As I wrote, there was no iptables file. I created one with just that > one > line: > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > 5901:5903,6001:6003 -j ACCEPT > ___ > 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 > ___ 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] VNC
On Fri, Oct 11, 2013 at 3:42 PM, Terre Porter wrote: > Try this, iptables dump from my fresh install, with ssh allow and the vnc > you referenced. > > Terre > > # Generated by iptables-save v1.4.7 on Fri Oct 11 17:39:52 2013 > *filter > :INPUT ACCEPT [0:0] > :FORWARD ACCEPT [0:0] > :OUTPUT ACCEPT [45:7091] > -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT > -A INPUT -p icmp -j ACCEPT > -A INPUT -i lo -j ACCEPT > -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > 5901:5903,6001:6003 -j ACCEPT > -A INPUT -j REJECT --reject-with icmp-host-prohibited > -A FORWARD -j REJECT --reject-with icmp-host-prohibited > COMMIT > # Completed on Fri Oct 11 17:39:52 2013 > > OK, with this file I'm getting connection timed out - before I was getting connection refused so I guess that's some progress. > > > -Original Message- > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > Behalf > Of Larry Martell > Sent: Friday, October 11, 2013 5:36 PM > To: CentOS mailing list > Subject: Re: [CentOS] VNC > > On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez >wrote: > > > > > On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote: > > > I'm trying to set up a VNC server using the instructions at > > > > > http://www.techrepublic.com/blog/linux-and-open-source/linux-101-easy- > > vnc-server-setup/ > > > . > > > > > > I am up to step 6: > > > > > > Step 6: Edit iptables > > > > > > In order for the VNC connections to get through, you must allow them > > > with iptables. To do this, open up the file /etc/sysconfig/iptables > > > and add > > the > > > line: > > > > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > > > 5901:5903,6001:6003 -j ACCEPT > > > > > > Save the file and restart iptables with the command: > > > > > > service iptables restart > > > > > > When I issue the restart command I get: > > > > > > iptables: Applying firewall rules: iptables-restore: line 1 failed > > >[FAILED] > > > > > > Note that I did not have an iptables file before but there is an > > > iptables-config file. > > > > > > Can someone help me complete this configuration. > > > > Can you post the content of the file, I just edit the config file and > > I didn't get any errors when I issue the command > > > > $ sudo /sbin/service iptables restart > > > > > As I wrote, there was no iptables file. I created one with just that one > line: > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > 5901:5903,6001:6003 -j ACCEPT > ___ > 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 > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VNC
Try this, iptables dump from my fresh install, with ssh allow and the vnc you referenced. Terre # Generated by iptables-save v1.4.7 on Fri Oct 11 17:39:52 2013 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [45:7091] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports 5901:5903,6001:6003 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT # Completed on Fri Oct 11 17:39:52 2013 -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Larry Martell Sent: Friday, October 11, 2013 5:36 PM To: CentOS mailing list Subject: Re: [CentOS] VNC On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez wrote: > > On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote: > > I'm trying to set up a VNC server using the instructions at > > > http://www.techrepublic.com/blog/linux-and-open-source/linux-101-easy- > vnc-server-setup/ > > . > > > > I am up to step 6: > > > > Step 6: Edit iptables > > > > In order for the VNC connections to get through, you must allow them > > with iptables. To do this, open up the file /etc/sysconfig/iptables > > and add > the > > line: > > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > > 5901:5903,6001:6003 -j ACCEPT > > > > Save the file and restart iptables with the command: > > > > service iptables restart > > > > When I issue the restart command I get: > > > > iptables: Applying firewall rules: iptables-restore: line 1 failed > >[FAILED] > > > > Note that I did not have an iptables file before but there is an > > iptables-config file. > > > > Can someone help me complete this configuration. > > Can you post the content of the file, I just edit the config file and > I didn't get any errors when I issue the command > > $ sudo /sbin/service iptables restart > > As I wrote, there was no iptables file. I created one with just that one line: -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports 5901:5903,6001:6003 -j ACCEPT ___ 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] VNC
On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez wrote: > > On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote: > > I'm trying to set up a VNC server using the instructions at > > > http://www.techrepublic.com/blog/linux-and-open-source/linux-101-easy-vnc-server-setup/ > > . > > > > I am up to step 6: > > > > Step 6: Edit iptables > > > > In order for the VNC connections to get through, you must allow them with > > iptables. To do this, open up the file /etc/sysconfig/iptables and add > the > > line: > > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > > 5901:5903,6001:6003 -j ACCEPT > > > > Save the file and restart iptables with the command: > > > > service iptables restart > > > > When I issue the restart command I get: > > > > iptables: Applying firewall rules: iptables-restore: line 1 failed > >[FAILED] > > > > Note that I did not have an iptables file before but there is > > an iptables-config file. > > > > Can someone help me complete this configuration. > > Can you post the content of the file, I just edit the config file and I > didn't get any errors when I issue the command > > $ sudo /sbin/service iptables restart > > As I wrote, there was no iptables file. I created one with just that one line: -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports 5901:5903,6001:6003 -j ACCEPT ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VNC
On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote: > I'm trying to set up a VNC server using the instructions at > http://www.techrepublic.com/blog/linux-and-open-source/linux-101-easy-vnc-server-setup/ > . > > I am up to step 6: > > Step 6: Edit iptables > > In order for the VNC connections to get through, you must allow them with > iptables. To do this, open up the file /etc/sysconfig/iptables and add the > line: > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports > 5901:5903,6001:6003 -j ACCEPT > > Save the file and restart iptables with the command: > > service iptables restart > > When I issue the restart command I get: > > iptables: Applying firewall rules: iptables-restore: line 1 failed >[FAILED] > > Note that I did not have an iptables file before but there is > an iptables-config file. > > Can someone help me complete this configuration. > > Thanks! > -larry > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos Can you post the content of the file, I just edit the config file and I didn't get any errors when I issue the command $ sudo /sbin/service iptables restart -- Kind Regards Earl Ramirez GPG Key: http://trinipino.com/PublicKey.asc signature.asc Description: This is a digitally signed message part ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] VNC
I'm trying to set up a VNC server using the instructions at http://www.techrepublic.com/blog/linux-and-open-source/linux-101-easy-vnc-server-setup/ . I am up to step 6: Step 6: Edit iptables In order for the VNC connections to get through, you must allow them with iptables. To do this, open up the file /etc/sysconfig/iptables and add the line: -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports 5901:5903,6001:6003 -j ACCEPT Save the file and restart iptables with the command: service iptables restart When I issue the restart command I get: iptables: Applying firewall rules: iptables-restore: line 1 failed [FAILED] Note that I did not have an iptables file before but there is an iptables-config file. Can someone help me complete this configuration. Thanks! -larry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd
Same result, doesn't turn off. Any other ideas? -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Andrew Wyatt Sent: Friday, October 11, 2013 4:41 PM To: CentOS mailing list Subject: Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd Try using the reboot=pci grub parameter. On Fri, Oct 11, 2013 at 11:40 AM, Terre Porter wrote: > Hello, > > > > I'm looking for help figuring out why I am having problems with > shutting down a machine. > > > > I have tested the machine using Fedora 19 and Ubuntu 12 Live CD's and > both power down without issues. > > > > I added acpi.debug_level=1 to the grub boot as it was suggested to see > more info about ACPI in the logs > > > > I found the following ACPI Errors in the /var/log/messages > > > > Oct 11 11:51:36 plum kernel: ACPI Error (psargs-0359): [ECEN] > Namespace lookup failure, AE_NOT_FOUND > > Oct 11 11:51:36 plum kernel: ACPI Error (psparse-0537): Method > parse/execution failed [\] (Node 81fdbeb0), AE_NOT_FOUND > > > > Oct 11 11:51:36 plum kernel: ACPI: resource piix4_smbus [io > 0x0b00-0x0b07] conflicts with ACPI region SOR1 [io 0xb00-0xb0f] > > Oct 11 11:51:36 plum kernel: ACPI: If an ACPI driver is available for > this device, you should use it instead of the native driver > > > > I used the Centos 6.4 Live CD last night with no hard drive in the system. > > > > I photo'd the shutdown, here is the type up: > > > > Sending all processes the TERM signal... > > Sendng all processes the KILL signal... > > Saving random seed: > > Syncing hardware clock to system time > > Turning off quotas: > > umount2: Device or resource busy > > umount: /dev/.initramfs/live: device is busy. > > (In some cases useful info about processes that use > > the device is found by lsof(8) or fuser(11)) > > init: Re-executing /sbin/init > > Halting System... > > r8169 :02:00.0: PME# enabled > > ACPI: Preparing to enter system sleep state S5 > > ACPI Error (psargs-0359): [PPTS] Namespace lookup failure, > AE_NOT_FOUND > > ACPI Error (psparse-0537): Method parse/execution failed > [\_SB_.PCI0.SBRG.EPTS] (Node fff88019dbc8c68), AE_NOT_FOUND > > ACPI Error (psparse-0537): Method parse/execution failed [\PTS_] (Node > 88019d043560), AE_NOT_FOUND > > ACPI Error (psparse-0537): Method parse/execution failed [\_PTS] (Node > 88019dbcf9e8), AE_NOT_FOUND > > Disabling non-boot CPUS... > > SMP alternatives: switching to UP code > > Power Down. > > acpi_power_off called > > > > The system doesn't power off, it just sits there. I have to hold the > power button in for it to shut down. > > > > The same still occurs with a completed a fresh minimum install of > Centos 6.4, installed the EPEL repo and did yum update. > > > > I'm running the latest bios for the motherboard, and even tried going > back one version. > > > > MB: 785GM-E51 (MS-7596 1.2) > > CPU: AMD Phenom II x4 945 3ghz > > 1TB HD, 6 Gig Mem > > > > Any ideas? > > > > (Besides using a baseball bat - I am considering it) > > > > Here is some hardware info from the getinfo.sh script listed the forums. > > > > == BEGIN uname -rmi == > > 2.6.32-358.18.1.el6.x86_64 x86_64 x86_64 > > == END uname -rmi == > > > > == BEGIN rpm -qa \*-release\* == > > centos-release-6-4.el6.centos.10.x86_64 > > epel-release-6-8.noarch > > == END rpm -qa \*-release\* == > > > > == BEGIN cat /etc/redhat-release == > > CentOS release 6.4 (Final) > > == END cat /etc/redhat-release == > > > > == BEGIN getenforce == > > Enforcing > > == END getenforce == > > > > == BEGIN rpm -qa kernel\* | sort == > > kernel-2.6.32-358.18.1.el6.x86_64 > > kernel-2.6.32-358.el6.x86_64 > > kernel-firmware-2.6.32-358.18.1.el6.noarch > > == END rpm -qa kernel\* | sort == > > > > == BEGIN lspci -nn == > > 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS880 Host > Bridge [1022:9601] > > 00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 > PCI to PCI bridge (int gfx) [1022:9602] > > 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 > PCI to PCI bridge (PCIE port 1) [1022:9605] > > 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] > > 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] > > 00:12.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0 USB OHCI1 Controller [1002:4398] > > 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] > > 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] > > 00:13.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0 USB OHCI1 Controller [1002:4398] > > 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB EH
Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd
Try using the reboot=pci grub parameter. On Fri, Oct 11, 2013 at 11:40 AM, Terre Porter wrote: > Hello, > > > > I'm looking for help figuring out why I am having problems with shutting > down a machine. > > > > I have tested the machine using Fedora 19 and Ubuntu 12 Live CD's and both > power down without issues. > > > > I added acpi.debug_level=1 to the grub boot as it was suggested to see more > info about ACPI in the logs > > > > I found the following ACPI Errors in the /var/log/messages > > > > Oct 11 11:51:36 plum kernel: ACPI Error (psargs-0359): [ECEN] Namespace > lookup failure, AE_NOT_FOUND > > Oct 11 11:51:36 plum kernel: ACPI Error (psparse-0537): Method > parse/execution failed [\] (Node 81fdbeb0), AE_NOT_FOUND > > > > Oct 11 11:51:36 plum kernel: ACPI: resource piix4_smbus [io 0x0b00-0x0b07] > conflicts with ACPI region SOR1 [io 0xb00-0xb0f] > > Oct 11 11:51:36 plum kernel: ACPI: If an ACPI driver is available for this > device, you should use it instead of the native driver > > > > I used the Centos 6.4 Live CD last night with no hard drive in the system. > > > > I photo'd the shutdown, here is the type up: > > > > Sending all processes the TERM signal... > > Sendng all processes the KILL signal... > > Saving random seed: > > Syncing hardware clock to system time > > Turning off quotas: > > umount2: Device or resource busy > > umount: /dev/.initramfs/live: device is busy. > > (In some cases useful info about processes that use > > the device is found by lsof(8) or fuser(11)) > > init: Re-executing /sbin/init > > Halting System... > > r8169 :02:00.0: PME# enabled > > ACPI: Preparing to enter system sleep state S5 > > ACPI Error (psargs-0359): [PPTS] Namespace lookup failure, AE_NOT_FOUND > > ACPI Error (psparse-0537): Method parse/execution failed > [\_SB_.PCI0.SBRG.EPTS] (Node fff88019dbc8c68), AE_NOT_FOUND > > ACPI Error (psparse-0537): Method parse/execution failed [\PTS_] (Node > 88019d043560), AE_NOT_FOUND > > ACPI Error (psparse-0537): Method parse/execution failed [\_PTS] (Node > 88019dbcf9e8), AE_NOT_FOUND > > Disabling non-boot CPUS... > > SMP alternatives: switching to UP code > > Power Down. > > acpi_power_off called > > > > The system doesn't power off, it just sits there. I have to hold the power > button in for it to shut down. > > > > The same still occurs with a completed a fresh minimum install of Centos > 6.4, installed the EPEL repo and did yum update. > > > > I'm running the latest bios for the motherboard, and even tried going back > one version. > > > > MB: 785GM-E51 (MS-7596 1.2) > > CPU: AMD Phenom II x4 945 3ghz > > 1TB HD, 6 Gig Mem > > > > Any ideas? > > > > (Besides using a baseball bat - I am considering it) > > > > Here is some hardware info from the getinfo.sh script listed the forums. > > > > == BEGIN uname -rmi == > > 2.6.32-358.18.1.el6.x86_64 x86_64 x86_64 > > == END uname -rmi == > > > > == BEGIN rpm -qa \*-release\* == > > centos-release-6-4.el6.centos.10.x86_64 > > epel-release-6-8.noarch > > == END rpm -qa \*-release\* == > > > > == BEGIN cat /etc/redhat-release == > > CentOS release 6.4 (Final) > > == END cat /etc/redhat-release == > > > > == BEGIN getenforce == > > Enforcing > > == END getenforce == > > > > == BEGIN rpm -qa kernel\* | sort == > > kernel-2.6.32-358.18.1.el6.x86_64 > > kernel-2.6.32-358.el6.x86_64 > > kernel-firmware-2.6.32-358.18.1.el6.noarch > > == END rpm -qa kernel\* | sort == > > > > == BEGIN lspci -nn == > > 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS880 Host Bridge > [1022:9601] > > 00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 PCI to > PCI bridge (int gfx) [1022:9602] > > 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 PCI to > PCI bridge (PCIE port 1) [1022:9605] > > 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] > > 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] > > 00:12.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0 > USB OHCI1 Controller [1002:4398] > > 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] > > 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] > > 00:13.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0 > USB OHCI1 Controller [1002:4398] > > 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] > > 00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus > Controller [1002:4385] (rev 3c) > > 00:14.1 IDE interface [0101]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 IDE Controller [1002:439c] > > 00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI SBx00 > Aza
Re: [CentOS] suddenly X gives black screen with small clock cursor
On Fri, Oct 11, 2013 at 09:41:08AM -0400, Fred Smith wrote: > On Fri, Oct 11, 2013 at 02:50:14AM -0700, John Doe wrote: > > From: Fred Smith > > > > > I rebooted a while ago (and in between the down and up, I installed > > > Fedora > > > 20 Beta on a USB hard drive, making sure it wouldn't mess with my > > > Centos system). The install went fine, but afterwards, when I reboot > > > Centos, it > > > comes up with a black screen and a clock as the mouse cursor (small > > > clock). > > > > > > chmod a+rw /dev/null > > > chmod a+rw /dev/urandom > > > chmod a+rw /dev/zero > > > chmod a+rw /dev/full > > > chmod a+rw /dev/random > > > > > > Can anyone suggest an accurate way to have the system fix all the > > > permissions > > > in /dev? some arcane options on rpm, perhaps? > > > > Nothing at all in the logs...? > > Nothing I can see in the logs looks particularly damning. > > > Global check: rpm -qVa > running that right now, will post again if anything interesting turns up. > > > Maybe check udev confs...? > I was thinking of that, but the amount I know aobut udev wouldn't cover > the head of a pin. Open to suggestions, though. Looking in /lib/udev/rules.d/50-udev-default.rules I see: KERNEL=="ptmx", GROUP="tty", MODE="0666" KERNEL=="null|zero|full|random|urandom", MODE="0666" so if I understand them right, /dev/ptmx, /dev/null, /dev/zero, /dev/full, /dev/random, and /dev/urandom should all come up as 'rw' for all users after a system boot, but they don't. I reboot and they all come up as 0644, crw-rw. grepping for "null" in /lib/udev finds only that single entry in all of the files, as does "ptmx". So, I wonder if something is preventing this file from being run (which seems unlikely, given that it contains a ton of rules which would all be skipped). I note that /etc/udev/rules.d contains a rules file with exactly the same name (which sets up some firewire stuff) and wonder if that's a problem,... anyone know? -- Fred Smith -- fre...@fcshome.stoneham.ma.us - "For the word of God is living and active. Sharper than any double-edged sword, it penetrates even to dividing soul and spirit, joints and marrow; it judges the thoughts and attitudes of the heart." Hebrews 4:12 (niv) -- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd
Hello, I'm looking for help figuring out why I am having problems with shutting down a machine. I have tested the machine using Fedora 19 and Ubuntu 12 Live CD's and both power down without issues. I added acpi.debug_level=1 to the grub boot as it was suggested to see more info about ACPI in the logs I found the following ACPI Errors in the /var/log/messages Oct 11 11:51:36 plum kernel: ACPI Error (psargs-0359): [ECEN] Namespace lookup failure, AE_NOT_FOUND Oct 11 11:51:36 plum kernel: ACPI Error (psparse-0537): Method parse/execution failed [\] (Node 81fdbeb0), AE_NOT_FOUND Oct 11 11:51:36 plum kernel: ACPI: resource piix4_smbus [io 0x0b00-0x0b07] conflicts with ACPI region SOR1 [io 0xb00-0xb0f] Oct 11 11:51:36 plum kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver I used the Centos 6.4 Live CD last night with no hard drive in the system. I photo'd the shutdown, here is the type up: Sending all processes the TERM signal... Sendng all processes the KILL signal... Saving random seed: Syncing hardware clock to system time Turning off quotas: umount2: Device or resource busy umount: /dev/.initramfs/live: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(11)) init: Re-executing /sbin/init Halting System... r8169 :02:00.0: PME# enabled ACPI: Preparing to enter system sleep state S5 ACPI Error (psargs-0359): [PPTS] Namespace lookup failure, AE_NOT_FOUND ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.SBRG.EPTS] (Node fff88019dbc8c68), AE_NOT_FOUND ACPI Error (psparse-0537): Method parse/execution failed [\PTS_] (Node 88019d043560), AE_NOT_FOUND ACPI Error (psparse-0537): Method parse/execution failed [\_PTS] (Node 88019dbcf9e8), AE_NOT_FOUND Disabling non-boot CPUS... SMP alternatives: switching to UP code Power Down. acpi_power_off called The system doesn't power off, it just sits there. I have to hold the power button in for it to shut down. The same still occurs with a completed a fresh minimum install of Centos 6.4, installed the EPEL repo and did yum update. I'm running the latest bios for the motherboard, and even tried going back one version. MB: 785GM-E51 (MS-7596 1.2) CPU: AMD Phenom II x4 945 3ghz 1TB HD, 6 Gig Mem Any ideas? (Besides using a baseball bat - I am considering it) Here is some hardware info from the getinfo.sh script listed the forums. == BEGIN uname -rmi == 2.6.32-358.18.1.el6.x86_64 x86_64 x86_64 == END uname -rmi == == BEGIN rpm -qa \*-release\* == centos-release-6-4.el6.centos.10.x86_64 epel-release-6-8.noarch == END rpm -qa \*-release\* == == BEGIN cat /etc/redhat-release == CentOS release 6.4 (Final) == END cat /etc/redhat-release == == BEGIN getenforce == Enforcing == END getenforce == == BEGIN rpm -qa kernel\* | sort == kernel-2.6.32-358.18.1.el6.x86_64 kernel-2.6.32-358.el6.x86_64 kernel-firmware-2.6.32-358.18.1.el6.noarch == END rpm -qa kernel\* | sort == == BEGIN lspci -nn == 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS880 Host Bridge [1022:9601] 00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge (int gfx) [1022:9602] 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 1) [1022:9605] 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] 00:12.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0 USB OHCI1 Controller [1002:4398] 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] 00:13.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0 USB OHCI1 Controller [1002:4398] 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] 00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller [1002:4385] (rev 3c) 00:14.1 IDE interface [0101]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 IDE Controller [1002:439c] 00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) [1002:4383] 00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d] 00:14.4 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SBx00 PCI to PCI Bridge [1002:4384] 00:14.5 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI2 Controller [1002:4399] 00:18.0 Host bridge
Re: [CentOS] Odd useradd/LDAP behaviour
On Fri, 11 Oct 2013, Paul Jones wrote: > So why is LDAP making useradd use the wrong values? It isn't. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Odd useradd/LDAP behaviour
Hello list, On our CentOS 6.4 machines I've LDAP enabled such that Windows users with the requisite unix attributes can log into the machines. These remote windows users have UID/GID starting at 2 so are well out of the way of local users. If I now create a local user with useradd, the UID/GID of the local user is the next available number in the range used by the Windows users. This is, users created before setting up LDAP are UID 501, 502 etc, but new users are 200XX. This then potentially causes problems when a new LDAP user is added, as we then have two users with the same UID/GID values. I've resolved this by editing the UID_MAX and GID_MAX fields in /etc/login.defs so the value is below the range used by the windows users. New test user gets UID/GID 503 as expected. I guess specifying the values in the useradd command would also work. So why is LDAP making useradd use the wrong values? Thanks for any suggestions, Paul ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] cleaning up some LVM stuff
Hi, one more LVM thing: on one server some LVM stores are physically removed but still there are some informatione somwher spread adcross teh server. e.g. if I do a vgdisplay or pvcreat I get an error regarding that old storage: /dev/raid_10/lvol0: read failed after 0 of 4096 at 14000515383296: Eingabe-/Ausgabefehler How can I remove all information? Thanks for any hint. Regards . Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 82 420 Fax +49 7141 969 55 420 E-Mail goetz.reini...@filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Jürgen Walter MdL Staatssekretär im Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg Geschäftsführer: Prof. Thomas Schadt ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] suddenly X gives black screen with small clock cursor
On Fri, Oct 11, 2013 at 02:50:14AM -0700, John Doe wrote: > From: Fred Smith > > > I rebooted a while ago (and in between the down and up, I installed Fedora > > 20 Beta on a USB hard drive, making sure it wouldn't mess with my > > Centos system). The install went fine, but afterwards, when I reboot > > Centos, it > > comes up with a black screen and a clock as the mouse cursor (small clock). > > > > chmod a+rw /dev/null > > chmod a+rw /dev/urandom > > chmod a+rw /dev/zero > > chmod a+rw /dev/full > > chmod a+rw /dev/random > > > > Can anyone suggest an accurate way to have the system fix all the > > permissions > > in /dev? some arcane options on rpm, perhaps? > > Nothing at all in the logs...? Nothing I can see in the logs looks particularly damning. > Global check: rpm -qVa running that right now, will post again if anything interesting turns up. > Maybe check udev confs...? I was thinking of that, but the amount I know aobut udev wouldn't cover the head of a pin. Open to suggestions, though. -- Fred Smith -- fre...@fcshome.stoneham.ma.us - The Lord is like a strong tower. Those who do what is right can run to him for safety. --- Proverbs 18:10 (niv) - ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS6.4 and Apple keyboard
Hi John, I'm working from home today so I've ask the phd student to launch a PXE boot for a new full kikstart install with a PC keyboard and then try to configure the apple keyboard by hand. See the answers to your questions below. John Doe a écrit : > From: Patrick Bégou > >> I have just installed (with kikstart) centOS6.4 on a PC which was >> previously running OpenSUSE (11.x). >> This PC has an apple keyboard and I'm unable to setup this keyboard. >> In .xsession-errors I get this messages : >> >> Error:No Symbols named "latin9" in the include file >> "macintosh_vndr/fr" >> Exiting >> Abandoning symbols file "(null)" >> >> ** (gnome-settings-daemon:8160): WARNING **: Could not activate the XKB >> configuration >> Error:No Symbols named "latin9" in the include file >> "macintosh_vndr/fr" >> Exiting >> Abandoning symbols file "(null)" >> >> ** (gnome-settings-daemon:8160): WARNING **: Could not activate the XKB >> configuration > What do you have in these files? The PC is re-installed with a standard keyboard this morning and I have now: >/etc/sysconfig/keyboard KEYTABLE="fr-latin9" MODEL="pc105" LAYOUT="fr" KEYBOARDTYPE="pc" VARIANT="latin9" >/etc/X11/xorg.conf Doesn't exist >/etc/X11/xorg.conf.d/* Empty directory > > Maybe retry system-setup-keyboard? It was the idea this morning: restart with a fresh install and a standard pc keyboard and switch to the apple one after. But when selecting the apple keyboard in system-setup-keyboard menu I get: Error activating XKB configuration. It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: CentOS 1130 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd So it is possible to work on the PC with the standard french PC keyboard but still not possible to use the apple keyboard. Patrick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SSH login from user with empty password
On 11.Okt.2013, at 10:58, Rainer Traut wrote: > Am 11.10.2013 09:27, schrieb Michael Schultz: >> Thanks everyone, >> >> secure log tells me exactly what the problem is: >> "User username not allowed because account is locked" >> >> Setting a password for that account unlocks it and ssh works as >> expected. I guess I have to work on my account creation routine. >> >> > > I haven't tried but > maybe you could just try the obvious and unlock the account? > I think it is > passwd -u [user] from the usermod and passwd manual page ... This puts a ´!´ in front of the encrypted password ... ... by prefixing the encrypted string with an ! ... What I have as an example /etc/passwd:login:x:1:1::/home/login:/bin/bash /etc/shadow:login:!!:15546:0:9:7::: and ssh with keys works fine What is in Michaels passwd and shadow? Maybe he does not use shadow passwords and the behaviour is different ? Another thougt, are there any AVCs in /var/log/audit/audit.log, maybe it is a selinux issue? Michael? -- Markus Resident do not top post guerilla http://centos.org/modules/tinycontent/index.php?id=16 (The guidelines part) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SSH login from user with empty password
I question why you want accounts without passwords when logging in via SSH and public keys does not use a password or even ask for one. Also anyone logged in can change users with only an su - and not need a password. Have you tried setting PASS_MIN_LEN in /etc/login.defs to 0? Mike On 10/11/2013 03:27 AM, Michael Schultz wrote: > Thanks everyone, > > secure log tells me exactly what the problem is: > "User username not allowed because account is locked" > > Setting a password for that account unlocks it and ssh works as > expected. I guess I have to work on my account creation routine. > > > Michael > > > Am 10.10.2013 21:49, schrieb James Hogarth: >> On 10 Oct 2013 14:45, "Michael Schultz" wrote: >>> on a CentOS 6.4 machine I'm creating accounts with empty passwords. Each >>> user's public key is located in /.ssh/authorized_keys. >>> >>> When trying to ssh into that machine, following error message is >> displayed: >>> Permission denied (publickey). >>> >> Check /var/log/secure on the server for more details... >> >> ___ >> 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 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS6.4 and Apple keyboard
From: Patrick Bégou > I have just installed (with kikstart) centOS6.4 on a PC which was > previously running OpenSUSE (11.x). > This PC has an apple keyboard and I'm unable to setup this keyboard. > In .xsession-errors I get this messages : > > Error: No Symbols named "latin9" in the include file > "macintosh_vndr/fr" > Exiting > Abandoning symbols file "(null)" > > ** (gnome-settings-daemon:8160): WARNING **: Could not activate the XKB > configuration > Error: No Symbols named "latin9" in the include file > "macintosh_vndr/fr" > Exiting > Abandoning symbols file "(null)" > > ** (gnome-settings-daemon:8160): WARNING **: Could not activate the XKB > configuration What do you have in these files? /etc/sysconfig/keyboard /etc/X11/xorg.conf /etc/X11/xorg.conf.d/* Maybe retry system-setup-keyboard? JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] suddenly X gives black screen with small clock cursor
From: Fred Smith > I rebooted a while ago (and in between the down and up, I installed Fedora > 20 Beta on a USB hard drive, making sure it wouldn't mess with my > Centos system). The install went fine, but afterwards, when I reboot Centos, > it > comes up with a black screen and a clock as the mouse cursor (small clock). > > chmod a+rw /dev/null > chmod a+rw /dev/urandom > chmod a+rw /dev/zero > chmod a+rw /dev/full > chmod a+rw /dev/random > > Can anyone suggest an accurate way to have the system fix all the permissions > in /dev? some arcane options on rpm, perhaps? Nothing at all in the logs...? Global check: rpm -qVa Maybe check udev confs...? JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SSH login from user with empty password
This only works when there's been a password set for the account before locking it. For obvious reasons empty passwords are not allowed :) Am 11.10.2013 10:58, schrieb Rainer Traut: > Am 11.10.2013 09:27, schrieb Michael Schultz: >> Thanks everyone, >> >> secure log tells me exactly what the problem is: >> "User username not allowed because account is locked" >> >> Setting a password for that account unlocks it and ssh works as >> expected. I guess I have to work on my account creation routine. >> >> > > I haven't tried but > maybe you could just try the obvious and unlock the account? > I think it is > passwd -u [user] > > ___ > 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] SSH login from user with empty password
Am 11.10.2013 09:27, schrieb Michael Schultz: > Thanks everyone, > > secure log tells me exactly what the problem is: > "User username not allowed because account is locked" > > Setting a password for that account unlocks it and ssh works as > expected. I guess I have to work on my account creation routine. > > I haven't tried but maybe you could just try the obvious and unlock the account? I think it is passwd -u [user] ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SSH login from user with empty password
You are right, that would do the trick when writing a script. But what I'm actually trying to accomplish is creating user accounts with the configuration manager "salt". In a blog post someone explained how to create users with it and he didn't set a password, so I gave it chance and came across the ssh problem. Am 11.10.2013 10:14, schrieb John R Pierce: > On 10/11/2013 12:27 AM, Michael Schultz wrote: >> Setting a password for that account unlocks it and ssh works as >> expected. I guess I have to work on my account creation routine. > > you might look into mkpasswd, its probably excessively complicated, but > it can set a users password > > # mkpasswd -l 20 xyzzy > zhRovbjh24hcqrg?xqoF > > sets a gnarly 20 character password for the xyzzy user. easy to script. > > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SSH login from user with empty password
On 10/11/2013 12:27 AM, Michael Schultz wrote: > Setting a password for that account unlocks it and ssh works as > expected. I guess I have to work on my account creation routine. you might look into mkpasswd, its probably excessively complicated, but it can set a users password # mkpasswd -l 20 xyzzy zhRovbjh24hcqrg?xqoF sets a gnarly 20 character password for the xyzzy user. easy to script. -- 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] SSH login from user with empty password
Thanks everyone, secure log tells me exactly what the problem is: "User username not allowed because account is locked" Setting a password for that account unlocks it and ssh works as expected. I guess I have to work on my account creation routine. Michael Am 10.10.2013 21:49, schrieb James Hogarth: > On 10 Oct 2013 14:45, "Michael Schultz" wrote: >> on a CentOS 6.4 machine I'm creating accounts with empty passwords. Each >> user's public key is located in /.ssh/authorized_keys. >> >> When trying to ssh into that machine, following error message is > displayed: >> Permission denied (publickey). >> > > Check /var/log/secure on the server for more details... > > ___ > 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
