Discuss

discuss@lists.centos.org

3 participants
34748 discussions

netbook screen suddenly goes black
by Fred Smith 02 Jul '16

02 Jul '16

Hi all! I'm running an up to date Centos-7 on my Acer Aspire One netbook. have been for, well, ever since C7 was released. Just had an event today that also happened 2 or 3 times with earlier systems installed, but I never pursued it. What happens is that suddenly while working away on the desktop the display suddenly goes black... not black as in turned off, I can see that the backlight is still on, but no image is displayed. Nothing I can do fixes it except a reboot. I've tried CTRL-ALT-BKSP, CTRL-ALT-DEL, alt+printscreen+r+e+i+s+u+b. none of them do anything noticeable. I've been looking at system logs and don't find anything that gives me a clue what is going wrong when that happens. neither dmesg, /var/log/Xorg*, nor /var/log/messages contins much. I've tried digging thru "man journalctl" and ultimately reading thru the output of journalctl with no arguments. Can anyone of you provide further hints on what I should be looking for or at? thanks! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- But God demonstrates his own love for us in this: While we were still sinners, Christ died for us. ------------------------------- Romans 5:8 (niv) ------------------------------

8 18

Securing RPC
by Leon Vergottini 02 Jul '16

02 Jul '16

Dear Community I hope you are all doing well. Recently I have been receiving several complaints from our service provider. Please see the complaint below: A public-facing device on your network, running on IP address XXX.XXX.XXX.XXX, operates a RPC port mapping service responding on UDP port 111 and participated in a large-scale attack against a customer of ours, generating responses to spoofed requests that claimed to be from the attack target. Please consider reconfiguring this server in one or more of these ways: 1. Adding a firewall rule to block all access to this host's UDP port 111 at your network edge (it would continue to be available on TCP port 111 in this case). 2. Adding firewall rules to allow connections to this service (on UDP port 111) from authorized endpoints but block connections from all other hosts. 3. Disabling the port mapping service entirely (if it is not needed). Unfortunately, I cannot disable NFS which lies at the root of this problem. In addition, I am struggling to find a proper tutorial of moving NFS from udp over to tcp. May I kindly ask you to point me in a direction or provide me with ideas on how to nail this thing in the .... Kind Regards Leon

4 3

how to update glib-2.28.8 to glib-2.40.0 or newer version
by qw 01 Jul '16

01 Jul '16

Hi, I'm trying to build gstreamer sdk on centos 6.7. When configure is run for 'gstreamer-1.8.2.tar.xz' on centos 6.7, error messages are reported as below: checking for GLIB... no configure: Requested 'glib-2.0 >= 2.40.0' but version of GLib is 2.28.8 configure: error: This package requires GLib >= 2.40.0 to compile. The command of 'yum install glib*' can only update glib to glib-2.28.8. How to update glib to the version of >=2.40.0 on centos 6.7? Thanks! Regards Andrew

3 2

[CENTOS ]IPTABLES - How Secure & Best Practice
by Leon Vergottini 01 Jul '16

01 Jul '16

Dear Members I hope you are all doing well. I am busy teaching myself iptables and was wondering if I may get some advise. The scenario is the following: 1. Default policy is to block all traffic 2. Allow web traffic and SSH 3. Allow other applications I have come up with the following: #!/bin/bash # RESET CURRENT RULE BASE iptables -F service iptables save # DEFAULT FIREWALL POLICY iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT DROP # ------------------------------------------------------ # INPUT CHAIN RULES # ------------------------------------------------------ # MOST COMMON ATTACKS iptables -A INPUT -p tcp --tcp-flags ALL NONE -j DROP iptables -A INPUT -p tcp ! --syn -m state --state NEW -j DROP iptables -A INPUT -p tcp --tcp-flags ALL ALL -j DROP # LOOPBACK, ESTABLISHED & RELATED CONNECTIONS iptables -A INPUT -i lo -j ACCEPT iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT # SSH iptables -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT # WEB SERVICES iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT # EMAIL iptables -A INPUT -p tcp -m tcp --dport 143 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 993 -j ACCEPT # OTHER APPLICATIONS iptables -A INPUT -p tcp -m tcp --dport XXXXX -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport XXXXX -j ACCEPT # ------------------------------------------------------ # OUTPUT CHAIN RULES # ------------------------------------------------------ # UDP iptables -A OUTPUT -p udp -j DROP # LOOPBACK, ESTABLISHED & RELATED CONNECTIONS iptables -A OUTPUT -i lo -j ACCEPT iptables -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT # SSH iptables -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT # WEB SERVICES iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT # EMAIL iptables -A INPUT -p tcp -m tcp --dport 143 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 993 -j ACCEPT # OTHER APPLICATIONS iptables -A INPUT -p tcp -m tcp --dport 11009 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 12009 -j ACCEPT # ------------------------------------------------------ # SAVE & APPLY # ------------------------------------------------------ service iptables save service iptables restart To note: 1. The drop commands at the beginning of each chain is for increase performance. It is my understanding that file gets read from top to bottom and applied accordingly. Therefore, applying them in the beginning will increase the performance by not reading through all the rules only to apply the default policy. 2. I know the above point will not really affect the performance, so it is more of getting into a habit of structuring the rules according to best practice, or at least establishing a pattern for myself. How secure is this setup? Is there any mistakes or things that I need to look out for? Thank you in advance for your feedback. Kind Regards Leon

9 16

CentOS-announce Digest, Vol 137, Issue 1
by centos-announce-request＠centos.org 01 Jul '16

01 Jul '16

1 0

Does centos 6.8 support gstreamer 1.8?
by qw 01 Jul '16

01 Jul '16

Hi, I found gstreamer offcial have just announced 1.8.2 version. ("gstreamer.freedesktop.org") But centos 6 only support gstreamer 0.10. When will centos 6 support gstreamer 1.8? Thanks! Regards Andrew

3 2

CentOS-7 Screen black after boot
by Venkata Balaji N 30 Jun '16

30 Jun '16

Hello Community, This is my first ever email to CentOS community. Firstly, CentOS is a great open-source operating system. I have been using it for years and recommending the same for production use to our customers. I have installed CentOS-7 operating system couple of days ago and everything was working fine. Yesterday, the screen got struck and the whole system was unresponsive, after a long wait, i have restarted the system. Since, then, i can only see the black screen and GUI is not coming up. I can remotely login to the system from Putty and can operate without any issues, the only issue is that GUI is not coming up. I have installed CentOS-7 server-GUI. Any help would be appreciated here. Regards, Venkata B N

1 0

VNC server issue- Gnome - oh no! Something has gone wrong
by Hersh 29 Jun '16

29 Jun '16

Hi, I have been using VNC on CentOS 7 server from last couple of months and it was running all fine till last night. Unfortunately, there was an abrupt power failure and system got restarted. Now, when I try to login with VNCviwer, it thrown an error message- "*Gnome - oh no! Something has gone wrong "* with a logout option. When I click on logout, I see black/dark gray screen with 3 check boxes. I googled to figure out a solution and tried several solutions but could not fix the problem. Any suggestion would be very helpful. Regards Hersh

3 4

CentOS-announce Digest, Vol 136, Issue 6
by centos-announce-request＠centos.org 29 Jun '16

29 Jun '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEBA-2016:1349 CentOS 7 lvm2 BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 29 Jun 2016 00:12:11 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1349 CentOS 7 lvm2 BugFix Update Message-ID: <20160629001211.GA46363(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1349 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1349.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 9f8f2152738415ddef6509c16881468f8abedf7488490bfe724561ee7eb582c7 cmirror-2.02.130-5.el7_2.5.x86_64.rpm e23f39c92b83682c140324b0891d426bf538fbdc68cf7f267c2a87356816d89c device-mapper-1.02.107-5.el7_2.5.x86_64.rpm 0c3dc7d9d7957e749ad019f06e0cc1c87f3db76cb500457050ce2c3e46080b8b device-mapper-devel-1.02.107-5.el7_2.5.i686.rpm 4da48171c8f599255dd47809d5ed2cdbd23afe152c44540e4e6c41bb88cf7f6b device-mapper-devel-1.02.107-5.el7_2.5.x86_64.rpm b1f004cceca52345c14d2dec35b44d989d39003d3a0e37ae14ee08210296e157 device-mapper-event-1.02.107-5.el7_2.5.x86_64.rpm 6a8203ef009bd1dae1c2575bfaa89582a5d9b402e9a450ce3a787c22ead8f4a6 device-mapper-event-devel-1.02.107-5.el7_2.5.i686.rpm a2a822a1de226771fd00b9d6bce566def68a67b5c4ef1351f7d4e756a3d23e03 device-mapper-event-devel-1.02.107-5.el7_2.5.x86_64.rpm 44d8c251698d60f8bf82d71d774652c7743515edd9077a780bb33709303188e6 device-mapper-event-libs-1.02.107-5.el7_2.5.i686.rpm 59b65674dcab344b3d219b6961722bfd40780455bc0bce6bd02edd6dd768453c device-mapper-event-libs-1.02.107-5.el7_2.5.x86_64.rpm 8475f1a20a99c5f1d041187a531b5c5406c67bf84afb926096d11810f1a53d8e device-mapper-libs-1.02.107-5.el7_2.5.i686.rpm 4d964e6a7643010f2862791e2588e08f6011e4c656540d61d3ebe937ac9ce13a device-mapper-libs-1.02.107-5.el7_2.5.x86_64.rpm b7a90ef80f4e8ddb35257802a57c07660e1ddc7e2c4a9957edf382ff67ec1567 lvm2-2.02.130-5.el7_2.5.x86_64.rpm 65a4c81480d0efba21f0da7969a2f820d69e26934af24bf4fdb8c449a2d502dc lvm2-cluster-2.02.130-5.el7_2.5.x86_64.rpm 04d6d35438ff31602702872775f9fdc758c94d1e9656319dcfa09580ef21609d lvm2-devel-2.02.130-5.el7_2.5.i686.rpm e53af702e6143a89598e64754410bbdbb079fb3e5b657091d88f44fec28fa391 lvm2-devel-2.02.130-5.el7_2.5.x86_64.rpm abafec8cbed90c9e68a796b61235bab160be70a8d0a8290041d78c155d41804e lvm2-libs-2.02.130-5.el7_2.5.i686.rpm 6c0f6537d19eecc549c1c7adf01cdee3aa6d805b30496946fbcc73cb4b3fe582 lvm2-libs-2.02.130-5.el7_2.5.x86_64.rpm 39727f939e993c9baac491080ef3901b3d18536c3c4a7e12668bf381f15f99e9 lvm2-lockd-2.02.130-5.el7_2.5.x86_64.rpm 2f3b320f5108eef429344b89416a2fcf6e15a47e014faeff5b47c6a3ebe234a3 lvm2-python-libs-2.02.130-5.el7_2.5.x86_64.rpm 53316ba2995b27f5b7a4137817a66cd811c42c4ce286e682869d565f5bae76be lvm2-sysvinit-2.02.130-5.el7_2.5.x86_64.rpm Source: 399d8210953038b445e7ac3fc91fc13b517b11dc1a849f820f17296a27477a56 lvm2-2.02.130-5.el7_2.5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 136, Issue 6 ***********************************************

1 0

Errors on yum upgrade
by henimp＠openmail.cc 29 Jun '16

29 Jun '16

During yum upgrade a couple days ago, I saw this: Cleanup : kernel-3.10.0-229.20.1.el7.x86_64 35/64 warning: file /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.softdep: remove failed: No such file or directory warning: file /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.devname: remove failed: No such file or directory Should I be concerned about this? What could have caused it? ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss