Re: [CentOS] Firefox Flash Update = No Flash
On Tue, Oct 13, 2015 at 2:48 PM, pro alias wrote: > None of my Centos 5 boxen can show flash since the update this morning. > Am I alone or do other people have this issue ?? > Centos 7 boxes work properly. I haven't looked at RHEL 6 boxes yet. > > Although I miss using flash on these boxes, it IS a great security > upgrade > > Installing the previous version of flash-plugin restores the functionality. It appears to be a Glib2 problem, this version was apparently compiled against another glib2. It wants libgio-2.0.so. Copying the so from /usr/lib/vmware to /usr/lib64/ stopped it's complaining but flash still didn't work. Another good reason to upgrade the remaining Centos 5.11 boxes to rhel/centos 7.1. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS7 - Serial Console and Flow Control
Mike - st257 wrote: > Hello List, > > I'm ironing out details to upgrade a few systems to CentOS7. > > My servers have BMC with Serial over LAN support. In C5 and C6, I determined how to have BIOS/POST, kernel, and serial console access. I'm reading up on the method to accomplish the pieces with C7. > > Presently SoL output works, so I see BIOS/POST messages and the GRUB boot list. > My changes to enable serial redirection for the kernel do not appear to work. > > I've made the following changes to GRUB2's /etc/grub/default config file: -- removed rhgb You did take out "quiet", too? mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cant reattach to screen session since upgrade of screen rpm?
On Thu, 15 Oct 2015 15:31:26 -0400 Jason Welsh wrote: > I finished installing all of the rpms > but I still have the issue where screen freezes when i try to reattach. Based on what you have said so far, "something" has apparently changed in the way that screen attaches to or finds a session. You may be out of luck. You could try downgrading back to the previous screen version and see if that will attach, but you're probably better off just killing the existing session and starting a new screen session instead. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS7 - Serial Console and Flow Control
On 10/15/2015 03:05 PM, Mike - st257 wrote: Would anyone be so kind as to share their experience? What has worked for your BMC/SoL configurations? I have a C7 server with a physical RS-232 console, but the config should be similar. I did not have to generate a systemd service for this; systemd saw the console line and automatically started the getty without me having to generate a .service file (as far as I recall all I had to do was generate the proper /etc/default/grub, and then run 'grub2-mkconfig -o /boot/grub2/grub.cfg' and it Just Worked). Now, I have the system set for console on both the VGA and on ttyS0, and I am not using flow-control. Here's what I have that works (again with a physical ttyS0): [root@backup670 ~]# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_SERIAL_COMMAND="serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1" GRUB_TERMINAL_OUTPUT="console serial" GRUB_CMDLINE_LINUX="rd.md.uuid=long-uuid-string crashkernel=auto rd.lvm.lv=vg/swap rd.lvm.lv=vg/root rd.md.uuid=another-long-uuid console=tty0 console=ttyS0,9600 rd_NO_PLYMOUTH" GRUB_DISABLE_RECOVERY="true" Also see: http://0pointer.de/blog/projects/serial-console.html There should be no need to modify any .service files; simply editing /etc/default/grub and regenerating grub2's config should be enough; it was in my case (I verified by looking through root's .bash_history and finding the lines around editing /etc/default/grub and not finding any edits of any .service files) ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cant reattach to screen session since upgrade of screen rpm?
I finished installing all of the rpms monsterjam:~ $ cat /etc/redhat-release CentOS release 6.7 (Final) but I still have the issue where screen freezes when i try to reattach. Jason On 10/15/2015 02:59 PM, Leon Fauster wrote: Am 15.10.2015 um 20:36 schrieb Jason Welsh : hey folks, running CentOS release 6.6 (Final) and I was upgrading some rpms and now since screen (and probably some others) were upgraded, I can no longer reattach to my screen session I had running. maybe that are packages of 6.7, therefore I suggest to upgrade completely to 6.7 and see if the problem can be reproduced ... -- LF ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS7 - Serial Console and Flow Control
Hello List, I'm ironing out details to upgrade a few systems to CentOS7. My servers have BMC with Serial over LAN support. In C5 and C6, I determined how to have BIOS/POST, kernel, and serial console access. I'm reading up on the method to accomplish the pieces with C7. Presently SoL output works, so I see BIOS/POST messages and the GRUB boot list. My changes to enable serial redirection for the kernel do not appear to work. I've made the following changes to GRUB2's /etc/grub/default config file: -- removed rhgb -- added the console= settings to GRUB_CMDLINE_LINUX -- added the last two lines related to serial as detailed here [0]. * Is there an option to enable hardware flow control? I recall having to turn on flow control (agetty -h) to make it behave. No mention of flow control at [1] or [2]. Nor does RHEL7 doc [3] mention it. I've already tweaked the systemd service I generated for ttyS1 (I'm using COM2 for SoL) and added the agetty "-h" option (for hardware flow control). Despite modifying the baud rate to reflect the BMC's settings, I only get symbols (so the console settings are amiss). Would anyone be so kind as to share their experience? What has worked for your BMC/SoL configurations? [0] https://fedoraproject.org/wiki/GRUB_2#Enable_Serial_Console_in_Grub [1] http://www.gnu.org/software/grub/manual/grub.html#Serial-terminal [2] http://www.gnu.org/software/grub/manual/grub.html#serial [3] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-GRUB_2_over_Serial_Console.html [4] https://lists.centos.org/pipermail/centos/2014-October/146719.html -- ---~~.~~--- Mike // SilverTip257 // ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cant reattach to screen session since upgrade of screen rpm?
Am 15.10.2015 um 20:36 schrieb Jason Welsh : > hey folks, running CentOS release 6.6 (Final) and I was upgrading some rpms > and now since screen (and probably some others) were upgraded, I can no > longer reattach to my screen session I had running. maybe that are packages of 6.7, therefore I suggest to upgrade completely to 6.7 and see if the problem can be reproduced ... -- LF ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] cant reattach to screen session since upgrade of screen rpm?
hey folks, running CentOS release 6.6 (Final) and I was upgrading some rpms and now since screen (and probably some others) were upgraded, I can no longer reattach to my screen session I had running. monsterjam:~ $ rpm -qi screen Name: screen Relocations: (not relocatable) Version : 4.0.3 Vendor: CentOS Release : 18.el6Build Date: Thu 23 Jul 2015 01:41:46 PM EDT Install Date: Thu 15 Oct 2015 01:15:28 PM EDT Build Host: c6b8.bsys.dev.centos.org Group : Applications/System Source RPM: screen-4.0.3-18.el6.src.rpm monsterjam:~ $ screen -ls There is a screen on: 13262.stuff(Detached) 1 Socket in /var/run/screen/S-jason. when I try to reattach, it just hangs.. monsterjam:~ $ screen -dr 13262.stuff ive found the following and tried them all.. Try detaching it first with screen -d. If that doesn't work, you can try, in increasing order of emphasis, -d|-D [pid.tty.host] does not start screen, but detaches the elsewhere running screen session. It has the same effect as typing "C-a d" from screen's controlling terminal. -D is the equivalent to the power detach key. If no session can be detached, this option is ignored. In combination with the -r/-R option more powerful effects can be achieved: -d -r Reattach a session and if necessary detach it first. -d -R Reattach a session and if necessary detach or even create it first. -d -RR Reattach a session and if necessary detach or create it. Use the first session if more than one session is available. -D -r Reattach a session. If necessary detach and logout remotely first. -D -R Attach here and now. In detail this means: If a session is running, then reattach. If necessary detach and logout remotely first. If it was not running create it and notify the user. This is the author's favorite. -D -RR Attach here and now. Whatever that means, just do it. but none of them seem to work.. any ideas? Jason ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] selinux commands fail on low memory box
On Thu, Oct 15, 2015 at 12:30:22AM -0400, Tim Dunphy wrote: > > How about adding some swap into system? > Not a bad idea, Eero! That worked. You might want to consider permanent swap, particularly for such low-memory systems. For a simple web server, you'd probably benefit from having the rest of the OS swapped out and dedicate more memory to the httpds and disk caches. If you're concerned about your web server processes using swap, you can adjust the vm.swappiness parameter for the httpd systemd unit's cgroup setting. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] copying to a local mirror / repository
On 10/15/2015 07:15 AM, Phelps, Matthew wrote: > On Wed, Oct 14, 2015 at 6:53 PM, Johnny Hughes wrote: > >> On 10/14/2015 04:49 PM, Richer, Mark (CIV) wrote: >>> I am using CentOS on a private network which can’t access the Internet >> so I want to create a local repository of packages on one or more DVDs, and >> get it installed on the private network. Someone had done this for CentOS >> 7, but not for CentOS 6. I have a VM running 6 so I am trying to create it >> for the previous major version. I thought there would be some obvious >> instructions on the preferred/recommended method for doing this, but I have >> failed to find them. >>> >>> Can anyone respond with any useful links on how best to do this or >> provide the recommended set of steps. I have seen various postings on this >> topic, but not anything official from the CentOS community. >>> >>> thanks much, >>> Mark >> >> For CentOS-7 this is quite easy, mount the everything ISO and point to >> it. (Note, it is TOO BIG to fit on a DVD, so it needs to be on a thumb >> drive .. something that will hold at least 7.2 GB) >> >> We roll a new ISO every month, you can get the latest one here: >> >> http://buildlogs.centos.org/rolling/7/isos/x86_64/ >> >> Currently CentOS-7-x86_64-Everything-1509-01.iso >> >> For 6, it is a bit harder, but not overly hard. Pick a mirror that is >> close from here: >> >> https://www.centos.org/download/mirrors/ >> >> Rsync the /6/ tree from that mirror, excluding the ISOs if you do not >> want them. As an example, I will pick the mirrors.kernel.org for this >> example ... this command: >> >> rsync mirrors.kernel.org::centos/6/ >> >> shows this results: >> >> drwxr-xr-x 27 2014/10/19 16:36:15 SCL >> drwxrwxr-x 42 2015/07/28 04:57:54 centosplus >> drwxrwxr-x 27 2015/05/18 11:02:50 cloud >> drwxr-xr-x 42 2014/10/19 16:36:15 contrib >> drwxrwxr-x 42 2015/08/05 07:44:48 cr >> drwxr-xr-x 42 2014/10/19 16:36:15 extras >> drwxr-xr-x 42 2014/10/19 16:36:15 fasttrack >> drwxrwxr-x 42 2015/08/10 11:56:29 isos >> drwxr-xr-x 42 2015/07/25 08:20:23 os >> drwxrwxr-x 42 2015/08/03 05:39:35 updates >> drwxr-xr-x 27 2014/10/19 16:36:15 xen4 >> >> >> So, you can exlude all except the trees you want, and rsync the rest. >> >> Put the os and updates directories (also bigger than 4.7 GB) on a drive >> and mount it somewhere on the other network. >> >> You can also do the same thing with the 7/ directory. >> >> With both the 6 or 7 directories, you just use apache to show the >> directories and and update from them by pointing to that location on >> your remote network. >> >> > Re: the last paragraph, it isn't necessary to use apache. You can just > specify the mounted location of the rsync'ed directories in your > /etc/yum.repos.d/CentOS-Base.repo (or whatever else you need) using the > baseurl=file://(location). E.g: > > [base] > name=CentOS-$releasever - Base > # Comment out the "mirrorlist" line so yum doesn't try to use the network > #mirrorlist= > http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os > # > baseurl=file:///disk/linux/CO6/os/x86_64/ > gpgcheck=1 > gpgkey=file:///disk/linux/CO6/os/x86_64/RPM-GPG-KEY-CentOS-6 Absolutely correct .. I was assuming that one wanted to make it available to multiple machines on a large network, etc. And even then it does not need to be apache, could be any web based server .. OR ftp .. OR NFS and mounted and pointed to on the local file system like you did above .. OR any number of other ways (glusterfs/ceph, etc). signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] copying to a local mirror / repository
On Wed, Oct 14, 2015 at 6:53 PM, Johnny Hughes wrote: > On 10/14/2015 04:49 PM, Richer, Mark (CIV) wrote: > > I am using CentOS on a private network which can’t access the Internet > so I want to create a local repository of packages on one or more DVDs, and > get it installed on the private network. Someone had done this for CentOS > 7, but not for CentOS 6. I have a VM running 6 so I am trying to create it > for the previous major version. I thought there would be some obvious > instructions on the preferred/recommended method for doing this, but I have > failed to find them. > > > > Can anyone respond with any useful links on how best to do this or > provide the recommended set of steps. I have seen various postings on this > topic, but not anything official from the CentOS community. > > > > thanks much, > > Mark > > For CentOS-7 this is quite easy, mount the everything ISO and point to > it. (Note, it is TOO BIG to fit on a DVD, so it needs to be on a thumb > drive .. something that will hold at least 7.2 GB) > > We roll a new ISO every month, you can get the latest one here: > > http://buildlogs.centos.org/rolling/7/isos/x86_64/ > > Currently CentOS-7-x86_64-Everything-1509-01.iso > > For 6, it is a bit harder, but not overly hard. Pick a mirror that is > close from here: > > https://www.centos.org/download/mirrors/ > > Rsync the /6/ tree from that mirror, excluding the ISOs if you do not > want them. As an example, I will pick the mirrors.kernel.org for this > example ... this command: > > rsync mirrors.kernel.org::centos/6/ > > shows this results: > > drwxr-xr-x 27 2014/10/19 16:36:15 SCL > drwxrwxr-x 42 2015/07/28 04:57:54 centosplus > drwxrwxr-x 27 2015/05/18 11:02:50 cloud > drwxr-xr-x 42 2014/10/19 16:36:15 contrib > drwxrwxr-x 42 2015/08/05 07:44:48 cr > drwxr-xr-x 42 2014/10/19 16:36:15 extras > drwxr-xr-x 42 2014/10/19 16:36:15 fasttrack > drwxrwxr-x 42 2015/08/10 11:56:29 isos > drwxr-xr-x 42 2015/07/25 08:20:23 os > drwxrwxr-x 42 2015/08/03 05:39:35 updates > drwxr-xr-x 27 2014/10/19 16:36:15 xen4 > > > So, you can exlude all except the trees you want, and rsync the rest. > > Put the os and updates directories (also bigger than 4.7 GB) on a drive > and mount it somewhere on the other network. > > You can also do the same thing with the 7/ directory. > > With both the 6 or 7 directories, you just use apache to show the > directories and and update from them by pointing to that location on > your remote network. > > Re: the last paragraph, it isn't necessary to use apache. You can just specify the mounted location of the rsync'ed directories in your /etc/yum.repos.d/CentOS-Base.repo (or whatever else you need) using the baseurl=file://(location). E.g: [base] name=CentOS-$releasever - Base # Comment out the "mirrorlist" line so yum doesn't try to use the network #mirrorlist= http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os # baseurl=file:///disk/linux/CO6/os/x86_64/ gpgcheck=1 gpgkey=file:///disk/linux/CO6/os/x86_64/RPM-GPG-KEY-CentOS-6 (etc.) -- Matt Phelps System Administrator, Computation Facility Harvard - Smithsonian Center for Astrophysics mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] abrt-auto-reporting
On 10/15/2015 04:28 AM, Günther J. Niederwimmer wrote: > Hello, > > centos 7(1) > > I have a question about abrt-auto-reporting? > > should this work normal ? > > I have on my System Problems to report the Errors. > > Thanks for a answer, > Yes, it should work normally for non Hardware (non MCE type) errors. Please do understand though that the CentOS team only fixes errors when the fix is rolled into the source code from upstream for RHEL (in base CentOS Linux). What this means is, bugs.centos.org is where one reports issues with CentOS .. AND .. we need members of the community to look though open issues there and to help us determine any errors that the CentOS team/process introduces which are not also upstream in RHEL. We (the CentOS team) will fix issues we have introduced. Issues also present in RHEL need to also be reported via bugzilla.redhat.com. The community is one way we can get that done. So, if you (the community, not an individual person) want to help CentOS (and RHEL) get better, you can look at open bugs in bugs.centos.org .. verify the bug exists in CentOS, verify the bug also exists in RHEL, if you have the skills to recommend a fix then do so, and report the problem on bugzilla.redhat.com if applicable. Then when Red Hat fixes the issue in the released source code, we will get it into CentOS. Thanks, Johnny Hughes signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] abrt-auto-reporting
Hello, centos 7(1) I have a question about abrt-auto-reporting? should this work normal ? I have on my System Problems to report the Errors. Thanks for a answer, -- mit freundlichen Grüssen / best regards, Günther J. Niederwimmer ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Incoming rsync connection attempts
Jeff Boyce писал 2015-10-14 21:13: Greetings - In my logwatch report this morning I noticed reference to an attempt to connect to rsync from an external IP address. It doesn't appear that the connection was successful based on correlating information between /var/log/secure and /var/log/messages. But I am looking for some suggestions for implementing more preventative measures, if necessary. The log information from the last few attempts are shown below. /var/log/secure Oct 13 00:14:08 Bison xinetd[2232]: START: rsync pid=15306 from=180.97.106.36 Oct 13 01:55:51 Bison xinetd[2232]: START: rsync pid=15343 from=85.25.43.94 Oct 13 23:25:35 Bison xinetd[2232]: START: rsync pid=16548 from=114.119.37.86 /var/log/messages Oct 13 00:14:08 Bison rsyncd[15306]: rsync: unable to open configuration file "/etc/rsyncd.conf": No such file or directory (2) Oct 13 00:14:08 Bison rsyncd[15306]: rsync error: syntax or usage error (code 1) at clientserver.c(923) [receiver=3.0.5] Oct 13 01:55:51 Bison rsyncd[15343]: rsync: unable to open configuration file "/etc/rsyncd.conf": No such file or directory (2) Oct 13 01:55:51 Bison rsyncd[15343]: rsync error: syntax or usage error (code 1) at clientserver.c(923) [receiver=3.0.5] Oct 13 23:25:35 Bison rsyncd[16548]: rsync: unable to open configuration file "/etc/rsyncd.conf": No such file or directory (2) Oct 13 23:25:35 Bison rsyncd[16548]: rsync error: syntax or usage error (code 1) at clientserver.c(923) [receiver=3.0.5] There is no /etc/rsyncd.conf file present on the system, so I can see why the connection wasn't successful. Our backups get pushed to this one from other servers using rsync. You can block access to tcp/udp port 873 from external addresses. You probably don't need rsync server either and can just disable it. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
