Tag Info

New answers tagged

2

The Linux utility lsscsi written by Doug Gilbert will provide the information you are looking for. It is in the Base repository of CentOS 5, 6, and 7, but YMMV with other distros. The output of lsscsi on my CentOS 7 system with the argument required to display WWNs: [root@sklad ~]# lsscsi --wwn [0:0:0:0] disk 0x5000c50041b932d7 /dev/sda ...


2

Try rpm -qa|grep ImageMagick A blank response means it's not installed. Edit: you may be getting hung up on getting a test to work, when you don't know that it's a good test. You started off wanting convert to work - which is part of Image Magick - and you've confirmed that it does. Can you tell us what your real problem is?


1

The correct fix is to update your SSL certificates. sudo yum upgrade ca-certificates --disablerepo=epel You need to disable the epel repo so that this command will succeed. After you update your certificates you can use yum normally as EPEL will work again.


2

The netmask set on the IP address which the server is using (64.x.x.x) was to 255.0.0.0, this is to wide, meaning that requests for any domains which also start with the IP address 64. were not being routed out of the server correctly. The resolution to this issue was to lower the netmask used on the IP address on the local machine to be 255.255.255.0, ...


0

your boot partition contains efi folder. if you use efi booting grub donot use /etc/boot/grub/grub.conf file. so it is empty. inside efi folder you have a grub config. also from efi partition you may use grub2 hence grub2 has grub2-mkconfig command to build configuration.


0

I ran into the very same issue, I found the cause. It is caused by SELinux, you can disable it temporary with echo 0 >/selinux/enforce but this is not recommended and you should create a policy file for it to run. I might come back to this when I have some free time.


0

I found the issue here. I needed to look at /proc/meminfo and see what the the kernel was caching as slab space. My problem was not understanding how much "free" memory top/ps/free said I had. It was the fact that these numbers were not adding up. The "free" command would tell me I had roughly 1692mb free but my processes only totaled up to about 20% of my ...


3

You have about 1692m in free memory according to Linux. In the top "Mem" line it would seem like your memory is almost 99% (7793m / 7840m) but in reality you're only using about 78% of available memory. See also http://www.linuxatemyram.com/ for a more in-depth explanation. Free vs Top vs /proc/meminfo Process memory. Adding up the memory used by ...


0

I believe you are misreading the Buffers/Cache - there is > 6 gigs being used as memory cache as per the +/- Buffers/Cache line. If this is needed it can be eaten into - as its not, the OS is using it to cache disk reads and similar.


1

Although not a fix for your underlying problem, the mdadm command has the --write-mostly option: -W, --write-mostly subsequent devices listed in a --build, --create, or --add command will be flagged as 'write-mostly'. This is valid for RAID1 only and means that the 'md' driver will avoid reading from these devices if at all possible. This can be useful ...


2

A part of the reason you might want to implement a RAID array is the read speed improvement. Using only a single disk to read from, but writing to both, smells wrong. If your actual problem is that you are experiencing worse read times since replacing a disk in your RAID setup, you might want to troubleshoot that disk instead of working around it. Here ...


0

Check to make sure that x-httpd-suphp in vhost definition matches the handler defined in /etc/httpd/conf.d/suphp.conf. For example: application/x-httpd-suphp="php:/usr/bin/php-cgi"


3

If you had created the PV as partition, you would have to shrink the PV first with pvresize --setphysicalvolumesize 5124M /dev/sdb and then resize the partition in the partition table with tools like fdisk or parted. But in your case you cannot create new partitions there since the PV encompasses the whole drive, so you can't safely make a fresh partition ...


4

You need to have yum version 3.2.26 or above and if you don't have it install yum-utils package which comes with the yumdb script. Using yumdb you can set a certain package to be kept from being removed on updates. yum update yum yum install yum-utils yumdb set installonly keep kernel-2.6.32-279.2.1.el6.x86_64


0

I'm using centos 7 and i don't have this problem, the function execvp is an external functions resolved by the library libdevmapper-event-lvm2thin.so: /usr/lib64/device-mapper/libdevmapper-event-lvm2thin.so [root@localhost ~]# objdump -T /usr/lib64/device-mapper/libdevmapper-event-lvm2thin.so | grep exec 0000000000000000 DF *UND* 0000000000000000 ...


0

The output in your first example is actually from the init script. Check /etc/init.d/sshd if you want to see the full context of what is happening there. If you're trying to replicate this in a docker container, you will need to replicate. The important commands are: $KEYGEN -q -t rsa -f $RSA_KEY -C '' -N '' $KEYGEN -q -t dsa -f $DSA_KEY -C '' -N '' ...


1

I suspect that you are trying to start the sshd application with a non-root user. The permissions of the host key file only allow root to read them. 4 -rw-r--r--. 1 root root 2047 Nov 6 09:07 ssh_config 4 -rw-------. 1 root root 3879 Nov 6 09:07 sshd_config 4 -rw-------. 1 root root 672 Jun 23 13:32 ssh_host_dsa_key 4 -rw-------. 1 root ...


0

assuming you did NOT alter your init.d's Varnish script (try md5 it) [root@6svprx01 ~]# head -1 /etc/init.d/varnish #! /bin/sh [root@6svprx01 ~]# rpm -q varnish varnish-3.0.6-1.el5.centos.x86_64 [root@6svprx01 ~]# md5sum /etc/init.d/varnish a69b3b55a8d5da5b9b9c24a62774aa80 /etc/init.d/varnish [root@6svprx01 ~]# service varnish Usage: /etc/init.d/varnish ...


0

The sudo command and managing SELinux requires some additional handling, but typically simply running the command from an interactive root session is easiest: $ sudo -i Password: # setsebool -P httpd_can_sendmail on I think the issue is that you need to specify a role as part of the sudo command: -r role The -r (role) option causes the new ...


0

"Will be updated" means you already have the package installed. If you want to not have it download both versions, uninstall the one that you don't want. Don't want GCC 64-bit? Use yum remove gcc.x86_64.


2

In general case innodb_force_recovery mode is supposed to let a user to start InnoDB and dump valuable data. A common belief InnoDB will heal tablespace after enabling innodb_force_recovery. No, it won't. (In some cases you can fix a tablespace dropping particular tables, but that's another story). If you are lucky enough and MySQL starts the next step is ...


2

There is an easier way to add routes... This file - /etc/init.d/network - is launched when the PC is booting, and it uses a file /etc/sysconfig/static-routes to add static routes You have to create it because it doesn't exist. If you read carefully the file /etc/init.d/network, it reads in this file each line to add routes, those line must begin by "any", ...


1

Include .i686 along with the package name to install the 32bit package. To install the 64bit package you would use .x86_64. yum install gcc.i686


2

There are two solutions to this issue: 1) You can regenerate the default self-signed certificate using OpenSSL: openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /etc/pki/tls/private/localhost.key -out /etc/ssl/certs/localhost.crt<br/><br/> 2) You can search the Apache config files and replace the self-signed cert with the new ...


1

I had a similar issue recently with one of the domains we relay for. There was a single message in the queue for that domain which caused their gateway to hang and not accept the message. This arrived while their gateway was unavailable for maintenance (so we built up a queue of messages for them before they were back in service). On subsequent queue runs ...


2

your ssl certificate issuer should provide you free replacement or reissue. Just go to digicert and ask them. Generate new key files from server and reissue ssl. Make sure the new ssl should be SHA2 only.


3

Your question says you are "struggling to work out why this waited for so long before being re-tried", but it seems to me that those logs are definitive: your mail server isn't waiting 12 days before re-trying sending. It's retrying it quite often (though without all the logs I can't say how often), but the remote server is being consistently unavailable. ...


1

You may be past this issue, but I wanted to update with the method that worked easily for me. Here was my situation: I was building several python27 SCL RPMs from downloaded egg files using a script to do everything - side note: This was how I pulled in all of the dependencies for our Python Django web app and is run from within the Atlassian Bamboo plan ...


0

Has the SSH host key changed due to the reconfiguration? If so then perhaps the known_hosts file on the REMOTE side is not in sync with the new host key and thus is rejecting the connection.


0

I suspect a change in networking configuration because your MAC address has changed. If you swap out mainboards on an existing Linux installation, the file /etc/udev/rules.d/70-persistent-net.rules will create new entries for your devices and give them new names. So, if you had eth0 and eth1 before, you will now probably have eth2 and eth3. You need to ...



Top 50 recent answers are included