Discuss

discuss@lists.centos.org

34753 discussions

CentOS 7.2 and KDE
by Jeff Layton 18 Jul '16

18 Jul '16

Good afternoon, I apologize if this is off-topic. I just installed CentOS 7 on my laptop and I used KDE. I can't seem to get the "hibernate" option. I've tried editing the options under "Power" but it hasn't appeared. Any thoughts? Thanks! Jeff

3 2

Problem with cloud-init on re-boot
by Timothy Murphy 18 Jul '16

18 Jul '16

When I re-boot my CentOS 7 machine I get lots of error/warning messages like the following: ------------------------------ Jan 1 14:39:04 alfred cloud-init: 2016-01-01 14:39:04,351 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: unexpected error ['NoneType' object has no attribute 'status_code'] ------------------------------ Re-booting with the current kernel, 3.10.0-327.22.2.el7.x86_64, sometimes fails, I think because of this problem, although the previous kernel seems to avoid the issue. I've actually disabled cloud-init, but I'm wondering if there is a simple solution to the problem? Actually, I don't remember installing cloud-init; maybe it was brought in by some other package? It's not clear to me why I should need it; is it a necessary adjunct to libvirtd? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

2 1

mate crash
by Alice Wonder 17 Jul '16

17 Jul '16

While playing an audio in totem, the mate desktop crashed. I couldn't switch to a console like I use to be able to do with ctrl-alt-F{n} - seems that is gone is from CentOS. I couldn't open a terminal by right clicking on the desktop. I was able to open a folder, navigate to /usr/bin and open gnome-terminal that way and issue the shutdown command. Since switching to virtual consoles no longer seems to work, what is the proper way to deal with rebooting a system when the window manager with all its menus crashes? CentOS 7 -- -=- Sent my from my laptop, may not be able to respond timely

2 2

firewalld cloud-init dhcp error
by 望月忠雄 17 Jul '16

17 Jul '16

Dear members, Please tell me what's wrong. After setig firewalld, I got fail on cloud-init with reboot. The server is rebooted, but I cannot access from internet. Before reboot I can access form internet. And before setig firewalld, there's no problem on reboot. /var/log/cloud-init.log shows following Jul 17 14:18:46 biz105 cloud-init: ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Jul 17 14:21:01 biz105 cloud-init: 2016-07-17 14:21:01,476 - url_helper.py[WARNING]: Calling ' http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: unexp ected error ['NoneType' object has no attribute 'status_code'] Jul 17 14:21:04 biz105 cloud-init: 2016-07-17 14:21:04,482 - url_helper.py[WARNING]: Calling ' http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [6/120s]: unexp ected error ['NoneType' object has no attribute 'status_code'] Jul 17 14:21:07 biz105 cloud-init: 2016-07-17 14:21:07,488 - url_helper.py[WARNING]: Calling ' http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [9/120s]: unexp ected error ['NoneType' object has no attribute 'status_code'] # cat /etc/firewalld/direct.xml <?xml version="1.0" encoding="utf-8"?> <direct> <rule priority="0" table="nat" ipv="ipv4" chain="POSTROUTING_direct">-s 192.168.1.5 -o eth0 -j SNAT --to 153.153.xxx.xxx</rule> <rule priority="0" table="nat" ipv="ipv4" chain="PREROUTING_direct">-s 153.153.xxx.xxx -o eth0 -j DNAT --to 192.168.1.5</rule> </direct> # firewall-cmd --zone=external --list-all external (active) interfaces: eth0 sources: services: dns ftp http https imaps pop3s smtp ssh ports: 110/tcp 21/tcp 106/tcp 53/tcp 990/tcp 5432/tcp 8447/tcp 113/tcp 143/tcp 3306/tcp 5224/tcp 22/tcp 465/tcp 995/tcp 25/tcp 8443/tcp 993/tcp 443/tcp 8880/tcp 587/tcp 20/tcp 53/udp 12768/tcp masquerade: yes forward-ports: icmp-blocks: rich rules: # nmcli c show System-eth0 | grep connection.autoconnect connection.autoconnect: yes connection.autoconnect-priority: 0

1 0

PolicyKit calls fail from rtkit-daemon
by Edgecombe, Jason 15 Jul '16

15 Jul '16

Hi everyone, I'm having some odd system behavior on two CentOS 7 machines. I suspect that the trouble is related to polkitd and dbus I think that the following error message is a key clue, but I'm not sure how to continue troubleshooting it:. --------------------------begin log----------------------- Jul 15 10:00:27 localhost rtkit-daemon[1609]: Warning: PolicyKit call failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. --------------------------end log----------------------- I can confirm that things seem to temporarily improve by killing polkitd and letting it be restarted by systemd. I was getting "out of memory" errors form polkitd until I increased the stack memory limit This is all part of various login issues when using the Gnome and Gnome-classic desktop environments over XRDP. I've temporarily disabled the GNOME and Gnome-classic environments for my users when sing RDP and set the default to MATE, since MATE seems to be acting correctly. KDE seems to be fine as well. Other pertinent info: # uname -r 3.10.0-327.10.1.el7.x86_64 # rpm -q systemd systemd-219-19.el7_2.9.x86_64 # rpm -q polkit polkit-0.112-6.el7_2.x86_64 Any help or guidance that can be given is appreciated. Sincerely, Jason --------------------------------------------------------------------------- Jason Edgecombe | Linux Administrator UNC Charlotte | The William States Lee College of Engineering 9201 University City Blvd. | Charlotte, NC 28223-0001 Phone: 704-687-1943 jwedgeco(a)uncc.edu | http://engr.uncc.edu | Facebook --------------------------------------------------------------------------- If you are not the intended recipient of this transmission or a person responsible for delivering it to the intended recipient, any disclosure, copying, distribution, or other use of any of the information in this transmission is strictly prohibited. If you have received this transmission in error, please notify me immediately by reply e-mail or by telephone at 704-687-1943. Thank you.

1 0

I am unable to build atlas rpm from centos7.2
by SUDHANSHU BHUTANI 15 Jul '16

15 Jul '16

Hi all, I just cloned from git clone https://git.centos.org/git/rpms/atlas And rpmbuild is failing with error in building ATLAS:- make[1]: Leaving directory `/home/sudhanshu/rpmbuild/BUILD/ATLAS/x86_64_base' DONE configure + '[' base = base ']' + sed -i 's#ARCH =.*#ARCH = P4E64SSE3#' Make.inc + sed -i s#-DATL_AVX## Make.inc + sed -i s#-mavx#-msse3# Make.inc + echo 'base makefile edited' base makefile edited + make build make -f Make.top build make[1]: Entering directory `/home/sudhanshu/rpmbuild/BUILD/ATLAS/x86_64_base' cd bin/ ; make xatlas_build make[2]: Entering directory `/home/sudhanshu/rpmbuild/BUILD/ATLAS/x86_64_base/bin' /usr/bin/x86_64-redhat-linux-gcc -DL2SIZE=4194304 -I/home/sudhanshu/rpmbuild/BUILD/ATLAS/x86_64_base/include -I/home/sudhanshu/rpmbuild/BUILD/ATLAS/x86_64_base/..//include -I/home/sudhanshu/rpmbuild/BUILD/ATLAS/x86_64_base/..//include/contrib -DAdd_ -DF77_INTEGER=int -DStringSunStyle -DATL_OS_Linux -DATL_ARCH_UNKNOWNx86 -DATL_CPUMHZ=2399 MAC -DATL_AVX -DATL_SSE3 -DATL_SSE2 -DATL_SSE1 -DATL_USE64BITS -DATL_GAS_x8664 -m64 -DWALL -DATL_FULL_LAPACK -DATL_NCPU=4 -O -fomit-frame-pointer -g -fstack-protector-strong -Wa,--noexecstack -fPIC -m64 -c /home/sudhanshu/rpmbuild/BUILD/ATLAS/x86_64_base/..//bin/atlas_tee.c x86_64-redhat-linux-gcc: error: MAC: No such file or directory make[2]: *** [atlas_tee.o] Error 1 make[2]: Leaving directory `/home/sudhanshu/rpmbuild/BUILD/ATLAS/x86_64_base/bin' make[1]: *** [build] Error 2 make[1]: Leaving directory `/home/sudhanshu/rpmbuild/BUILD/ATLAS/x86_64_base' make: *** [build] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.LYBFLC (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.LYBFLC (%build) "log" 465L, 31535C ----- uname -a: Linux localhost.localdomain 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -bash-4.2$ ----- Any pointers? I am not sure, why MAC is getting added to Makefile on my machine? Regards Sudhanshu Bhutani

2 1

command line file completion on CentOS 7
by Jerry Geis 14 Jul '16

14 Jul '16

I have noticed on CentOS 7.2 that when I am doing command line file TAB completion it behaves differently. if I have a file /tmp/file 1.txt (notice the space) when I do: ls /tmp/file and hit TAB it works but if I do: more /tmp/file and hit TAB it does NOT work. What I get is 1.txt file versus just expanding to /tmp/file 1.txt Why are they not the same? Thanks, Jerry

3 3

Broken output for fdisk -l
by Hersh 14 Jul '16

14 Jul '16

Hi, There was some problem with our system so I re-installed the server with CentOS 7. Now, when I am trying to run 'fdisk -l' command, it is returning a broken output. It throws this error- "fdisk: cannot open /dev/sdc: Input/output error". There are valid /dev/sdd and /dev/sde devices which are mounted and they are accessible but, somehow /dev/sdc is having a problem and 'fdisk -l' is not returning the full output. Below is an output of fdisk -l for reference. Any suggestion on how to fix this would be very helpful. ---------------------------- [root@localhost ~]# fdisk -l Disk /dev/sda: 1932.7 GB, 1932735283200 bytes, 3774873600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0004118b Device Boot Start End Blocks Id System /dev/sda1 * 2048 1026047 512000 83 Linux /dev/sda2 1026048 3774873599 1886923776 8e Linux LVM Disk /dev/sdb: 1664.6 GB, 1664568262656 bytes, 3251109888 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x00000081 Device Boot Start End Blocks Id System /dev/sdb1 * 63 3251106179 1625553058+ 83 Linux fdisk: cannot open /dev/sdc: Input/output error [root@localhost ~]# [root@localhost ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/centos-root 50G 4.8G 46G 10% / devtmpfs 63G 0 63G 0% /dev tmpfs 63G 300K 63G 1% /dev/shm tmpfs 63G 18M 63G 1% /run tmpfs 63G 0 63G 0% /sys/fs/cgroup /dev/mapper/MD3200-results 19T 9.0T 9.3T 50% /data/results /dev/sdb1 1.5T 234M 1.5T 1% /share /dev/mapper/centos-home 1.8T 5.5G 1.7T 1% /home /dev/sda1 497M 158M 340M 32% /boot tmpfs 13G 32K 13G 1% /run/user/1000 tmpfs 13G 36K 13G 1% /run/user/0 /dev/sde 917G 625G 247G 72% /media/usb [root@localhost ~]# fdisk -l /dev/sdc fdisk: cannot open /dev/sdc: Input/output error [root@localhost ~]# ------------------------------ Regards Hersh

5 6

CentOS7 firewalld ploblem
by 望月忠雄 14 Jul '16

14 Jul '16

Dear Members, Please tell me how can I fix this problem. Against allow imap on firewalld, I cannot access to the server. [root@speedex ~]# telnet 153.153.xxx.xxx 110 Trying 153.153.xxx.xxx... telnet: connect to address 153.153.xxx.xxx: No route to host After stopping forewalld I can access to the server. [root@speedex ~]# telnet 153.153.xxx.xxx 110 Trying 153.153.xxx.xxx... Connected to 153.153.xxx.xxx. Escape character is '^]'. +OK Dovecot ready. ^] telnet> quit I have attached nmcli and firewalld data. Please check it. If you need more please tell me. Tadao

3 5

vnc on C7
by Jerry Geis 14 Jul '16

14 Jul '16

I am trying to get a remote screen on C7. I did the following on C7 server: yum install tigervnc-server cp /lib/systemd/system/vncserver@.service /etc/systemd/system/vncserver@:1.service systemctl daemon-reload edit /etc/systemd/system/vncserver@:1.service and replace <USER> with myuser su - myuser run vncpassword to set password systemctl start vncserver@:1.service systemctl enable vncserver@:1.service Then when I use something like vncviewer from a windows laptop into the linux desktop I get the password prompt, but the next screen says "oh no, something went wrong". Did I do something wrong above? Thanks, Jerry

5 8

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