Discuss January 2016

discuss@lists.centos.org

132 participants
121 discussions

SSD for Centos SWAP /tmp & /var/ partition
by Keith Roberts 03 Sep '25

03 Sep '25

Has anyone actually used a SSD in a Centos setup? My little experiment with a s/h WD drive for /tmp and SWAP partitions kicked the bucket on Wednesday, when the poor WD drive caught the click-of-death. It was a s/h drive to start with and lasted about 4 months. But that was without the /var/log/ partition being written to it, as I mounted that back onto /var/log from the original drive. So I had to install another (WD) drive, and repartion it and rebuild my RPM package database, from the backed-up Packages file. That seems to be all OK now. I'm wondering if it would be a good idea to use a new SSD for moving all the disk i/o to, that Linux likes to do so often. Plus putting SWAP onto a decent SSD should speed things up somewhat. Here's a short video of a laptop fitted with a SSD drive booting macOS, compared to a similar laptop booting from the standard HDD. The laptop with the SSD boots and loads some apps in 28 seconds. The other one takes twice as long. http://eshop.macsales.com/shop/SSD/OWC/Mercury_Extreme_Pro_6G/?utm_source=t… Kind Regards, Keith Roberts ----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------

33 96

I want to connect to a l2tp server from centos.
by Eliezer Croitoru 22 Mar '17

22 Mar '17

I have a server currently connecting to a pptp remote server. This server(lns\lac) has the option for pptp connections and l2tp connections. The l2tp connections are not using ipsec encryption at all. I have seen couple guides\tutorials on the internet: - https://raymii.org/s/tutorials/IPSEC_L2TP_vpn_on_CentOS_-_Red_Hat_Enterpris… - https://wiki.archlinux.org/index.php/L2TP/IPsec_VPN_client_setup But all the guides that I have found are using ipsec with "secret". On ubuntu there is a gui applet that helps setting these kind of connections up but I am working with a CentOS server and not Ubuntu desktop. If someone used l2tp the same way I want to use on CentOS 7 please give me some advice. If you have a guide which might help me I will be more then happy to see this one. Thanks, Eliezer

4 8

Broadcom BCM4313 support broken with kernel 2.6.32-573.7.1.el6.centos.plus.x86_64?
by wwp 24 Aug '16

24 Aug '16

Hello, I noticed that with latest kernel (2.6.32-573.7.1.el6.centos.plus.x86_64), my laptop's Wifi doesn't work, whereas with previous kernel (2.6.32-504.30.3.el6.centos.plus.x86_64), it works fine. Is this a known issue or did I miss something new? BTW, `lspci` says: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01) Regards, -- wwp

2 2

Any further developments on CentOS7 for i386?
by Kay Schenk 22 Jun '16

22 Jun '16

Well I haven't tested out the CentOS 7 for i386 yet as sent in the message of 06/02-- https://lists.centos.org/pipermail/centos-devel/2015-June/013426.html Nor have I seen any additional information. So how is this going? I'm almost ready to jump in as I would really prefer to be on Gnome 3. -- -------------------------------------------- MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu

3 7

Google Chrome and CentOS 6?
by Sorin Srbu 19 Apr '16

19 Apr '16

Hi all, Just recently I started getting the dreaded message about my CentOS 6.7 x64-installation wasn't going to be supported anymore by Google Chrome. "This computer will soon stop receiving Google Chrome updates because this Linux system will no longer be supported." Doing some google searches I found this; http://superuser.com/questions/1011832/this-computer-will-soon-stop-receivi… Which in itself wasn't too uplifting... Following the suggestion about installing Chromium instead worked, but it seems to be stuck at an ancient version of the browser. Recompiling the available Chromium source is of course an option, but not for me. Not unless there are step-by-step guides doing it. There was a rather long and somewhat heated discussion regarding Chrome on CentOS a while ago. Was there any real conclusion about Google Chrome on CentOS and how to get around this problem? Are the views on this matter still infected? I'm not looking forward to go back to the sluggish Firefox. 8-/ -- BW, Sorin ----------------------------------------------------------- # Sorin Srbu, Sysadmin # Uppsala University # Dept of Medicinal Chemistry # Div of Org Pharm Chem # Box 574 # SE-75123 Uppsala # Sweden# # Phone: +46 (0)18-4714482 # Visit: BMC, Husargatan 3, D5:512b # Web: http://www.orgfarm.uu.se ----------------------------------------------------------- # () ASCII ribbon campaign - Against html E-mail # /\ # # This message was not sent from an iProduct! # # Please consider the environment before printing this email. # Join the campaign at http://thinkBeforePrinting.org # # MotD follows: # "You guys got something against spam?" -de Vriess, in Alien^4

9 20

vpn - xl2tpd and routing to a net?
by lejeczek 31 Mar '16

31 Mar '16

hi everybody I'm having a, I'd like to think a "regular" VPN with IPsec/xl2tpd and it all works OK, except.. One thing that I never needed but now I do and I wonder.... is it my iptables, or/and routing or maybe VPN server config..? vpn clients with established tunnels can get to VPN server's NICs/IPs but cannot get through to the net behind the server. Well... they can, but only if on a host (eg. 192.168.2.33) on VPN server's net I do: route add -host 192.168.2.10 gw 192.168.2.100 # 192.168.2.10 is VPN client I thought this I'd not need since that local net (eg. 192.168.2.33) use VPN server's 192.168.2.100 as the default gw. is it by design and nature of that VPN solution it works this way or I actually have missed/messed up something? I hope the latter and adding routing on per "to host" basis is redundant. many thanks

3 8

abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected
by Michael H 15 Feb '16

15 Feb '16

Hi All, I've been tuning a server recently and just today this has started to appear in my top/htop output. [root@db1 ~]# ps -aux | grep kernel root 1011 0.0 0.0 212048 4532 ? Ss 13:34 0:00 /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Machine Check Exception: Machine check events logged divide error: bounds: coprocessor segment overrun: invalid TSS: segment not present: invalid opcode: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD I had made a few changes to sysctl.conf which I have now reverted and the error still exists. my sysctl.conf contained; vm.swappiness=0 vm.overcommit_memory=2 vm.overcommit_ratio=90 - this was only added this morning because of an 'out of memory' error in postgresql. kernel.shmmax=35433480192 kernel.shmall=2214592512 which I have now removed. Can anyone shine any light on this? A little search on Google mentions faulty memory, I will install memtest today and see what the output is like. Thanks Michael

2 1

devtoolset-4
by Kay Diederichs 05 Feb '16

05 Feb '16

Hi, is there any way to get access to devtoolset-4 ? I see alot of stuff at http://cbs.centos.org/koji/packageinfo?packageID=2076 . Is this not yet released? thanks, Kay

2 1

CentOS 7 - DNAT with firewalld
by Django 03 Feb '16

03 Feb '16

HI, here I have an eMail with connected to a DMZ 10.0.0.0/24 network. This server holds 10.0.0.87 There are two firewall-hosts one with CentOS 6 10.0.0.10 and one with CentOS 7 10.0.0.17 The CentOS 6 has the following iptables-rule (extract): ----------------------8<----------------------8<----------------------8< *nat -A POSTROUTING -o eth1 -j MASQUERADE -A PREROUTING -i eth1 -d 217.91.103.190/32 -p tcp -m tcp --dport 25 -j DNAT --to-destination 10.0.0.87:25 *filter -A FORWARD -d 10.0.0.87/32 -i ppp0 -o eth0 -p tcp -m state --state NEW -m tcp --dport 25 -j ACCEPT ----------------------8<----------------------8<----------------------8< If a external mailserver access the firewall, the traffic is routed to 10.0.0.87 port 25. As IP-adress from the external server I see hois public-IP. Here's the part of maillog: Jan 26 13:03:20 vml000087 postfix/postscreen[14214]: CONNECT from [88.198.212.215]:36131 to [10.0.0.87]:25 Jan 26 13:03:20 vml000087 postfix/postscreen[14214]: PASS OLD [88.198.212.215]:36131 Jan 26 13:03:20 vml000087 postfix/smtpd[10268]: connect from mx1.piratenpartei-bayern.de[88.198.212.215] Jan 26 13:03:31 vml000087 postfix/smtpd[10268]: disconnect from mx1.piratenpartei-bayern.de[88.198.212.215] so far so good, this work'ed fine the last 5 years ... Now I've a second network with a CentOS 7 base firewall. I've tried to adapt the roules I've mad on the old firewall. ----------------------8<----------------------8<----------------------8< # cat /etc/firewalld/zones/public.xml <?xml version="1.0" encoding="utf-8"?> <zone> <short>Public</short> <description>For use on external networks. You do not trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted.</description> <interface name="eth1"/> <service name="ssh"/> </zone> # cat /etc/firewalld/zones/private.xml <?xml version="1.0" encoding="utf-8"?> <zone> <short>Private</short> <description>For use on internal networks. You mostly trust the other computers on the networks to not harm your computer. Only selected incoming connections are accepted.</description> <interface name="eth0"/> <service name="ssh"/> <masquerade/> </zone> # cat /etc/firewalld/direct.xml <?xml version="1.0" encoding="utf-8"?> <direct> <rule priority="0" table="nat" ipv="ipv4" chain="POSTROUTING">-o eth1 -j MASQUERADE</rule> <rule priority="0" table="nat" ipv="ipv4" chain="PREROUTING">-i eth1 -d 192.168.0.17/32 -p tcp -m tcp --dport 25 -j DNAT --to-destination 10.0.0.87:25</rule> <rule priority="0" table="filter" ipv="ipv4" chain="FORWARD">-i eth1 -d 10.0.0.87/32 -p tcp -m state --state NEW -m tcp --dport 25 -j ACCEPT</rule> </direct> ----------------------8<----------------------8<----------------------8< The traffic over this firewall is routed to my mailserver, too. BUT I did'nt see the external customer-IP, I only can see the IP-address of my own firewall. Jan 26 13:04:52 vml000087 postfix/postscreen[14214]: CONNECT from [10.0.0.17]:33803 to [10.0.0.87]:25 Jan 26 13:04:52 vml000087 postfix/postscreen[14214]: WHITELISTED [10.0.0.17]:33803 Jan 26 13:04:52 vml000087 postfix/smtpd[10268]: connect from vml000017.dmz.nausch.org[10.0.0.17] Jan 26 13:04:53 vml000087 postfix/smtpd[11397]: disconnect from vml000017.dmz.nausch.org[10.0.0.17] So I think destination NAT (DNAT) isn't working on my CentOS 7 host. As I seaid on my CentOS6 host DNAT is working very well. So where's my error? in my configuration or in my head? ;) Thanx 4 help! ttyl Django -- "Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God http://wetterstation-pliening.info http://dokuwiki.nausch.org http://wiki.piratenpartei.de/Benutzer:Django

1 1

Folding At Home
by Mark LaPierre 02 Feb '16

02 Feb '16

Hey Y'all, I have the Stanford University Folding At Home project running on three of my machines. I had them all set up so that I could control them all from my main machine, 192.168.15.101, but some time ago something changed so that I can no longer connect to the FAH clients on the other two machines. I figured it wasn't really important so I would look into it later. Well time has passed and my Christmas break is almost passed too to I guess this is the time to figure it out. I can still SSH onto both machines. I can ping both machines. When I open the FAH Control on my machine connection to clients running on 192.168.15.105 and 192.168.15.107 fails. I'm assuming that there would be an entry in a log on those two machines detailing the failed connection attempt. What log file should I be looking at? -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

2 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2016