Tag Info

New answers tagged

0

It turns out that spamd needed to run under perl 5.10.1, the originally installed version on this server. So, instead of having a shebang of:- #!/usr/bin/perl -T -w it just needed #!/usr/bin/perl5.10.1 -T -w Partly the clue was in the error message (reading the wrong include files) and mainly it was down to thrig's comment - thanks


1

when you do ps aux | grep cron you are running two commands - ps aux and grep cron. ps aux lists all processes currently running, and grep cron matches any lines which contain "cron" in them. Obviously the crond process matches the word cron, but so does the grep cron process you just ran. It's matching itself recursively.


2

This very much looks like a DNS configuration problem inside the VM. Start from looking at /etc/resolv.conf contents. My guess is that adding/removing interfaces may change routing table and this way influence name resolving. What happens when you change nameservers order? A result from host -v google.com. could help you find the correctly working nameserver ...


1

As a root user, you can append the JAVA_HOME value in /etc/profile export JAVA_HOME=/opt/jdkpath PATH=$PATH:$HOME/bin:/opt/jdkpath/bin Change /opt/jdkpath to the correct path of your jdk installation. Once you do that you can logout & login back & execute the service command


2

It seems like this could be a routing issue. Since the VMs inside KVM can route independently of the host, the issue is not going to be your physical network connectivity, but rather your logical network connectivity. Check your default gateway and static routes, make sure those are configured properly. If your host cannot find a route back to the devices ...


1

For the next foolio....The actual path to the nagios.cmd is /var/spool/nagios. Once I set the right path in the NSCA.cfg file, everything started working. Remember, that nsca puts in a file nsca.dump which has all the data. nsca.dump needs to consumed by nagios.cmd.


4

You're using the syntax for an entry in /etc/crontab which has the user ID in the 6th column, but if you use crontab -e, you're editing the entry in /var/spool/crontab, which does not have this column since they are already separated per user. In other words, this is what you would put in /etc/crontab: 0 1 * * * root /sbin/shutdown -r now And this is ...


1

I solved, in my case, using noperm option in fstab entry


0

Okay, I found the problem. I was using puppetlabs-release-pc1-el-6 repository instead of the right one which is puppetlabs-release-el-6. The release packages were taken from: https://yum.puppetlabs.com/


2

SOLVED: Stupid mistake, I were trying to load a key in .ppk format by specifying it in preferences, the solution, use Pageant and set as "Try autologin" in preferences instead.


1

You should install a version of the fwknopd package which is built for CentOS 6, rather than Fedora 21. Sadly, it doesn't appear that the Cipherdyne site provides up-to-date binary RPMs for anything else, so you're stuck with downloading the SRPMs and building them yourself.


0

The two repos, remi and mysql56-community, cannot be used together because they are using incompatible package naming schemes. yum info mysql will not show anything from the MySQL community repo because none of the packages is named mysql under the new naming scheme. Try yum info mysql\* instead. Consequently, you cannot update MySQL directly from Remi to ...


0

Though the question is already answered and accepted, I think its incomplete. There are a few points missing from the accepted answer. You need to run top in batch mode using -b if you are running it as a child process and want to grab any meaningful output. If not it will have a mix of control characters as a result of running in interactive mode. Specify ...


1

A new release of CentOS just came out a few days ago. It's not surprising that there's a sudden influx of new packages.


0

Sounds like a DNS issue. Verify /etc/resolv.conf is configured correctly. Verify you are able to reach the name servers you have defined (using nslookup and ping). Also, make sure you are able to reach the internet at all. You can ping one of Google's DNS servers to verify: ping 8.8.8.8


0

The kojihub and kojiweb certificates must have their CN set to the fully qualified domain name of each respective server. This was in the documentation: Two of the certificates (kojihub and kojiweb) are used as server side certificates that authenticate the server to the client. For this reason, you want the common name on both of those certs to be the ...


18

The key thing to pick up is centos-release.x86_64, which is being upgraded to 6-7.el6.centos.12.3. You haven't said which subversion of CentOS you're on, but assuming you're up to patch, you're on 6.6 - this is the new 6.7 release hitting the mirrors. Those of us using the cr (continuous release) repository saw many of these packages arrive late last week. ...


41

As you can see from the output, the release version has changed from 6.6 to 6.7: centos-release.x86_64 6-7.el6.centos.12.3 base So this is perfectly normal. http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.7


0

try man iptables and be careful not to lock yourself out, also get yourself familiar with following: How To Setup a Basic IP Tables Configuration on Centos 6 | DigitalOcean probably following is missing: iptables -A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT


1

The problem is that your firewall is not stateful, and it only allowed traffic to pass in one direction. There is nothing here to allow return traffic. So, while a client request is passed through, the response from the server doesn't match any rules and is dropped. Write instead normal stateful rules. For example: -A FORWARD -m conntrack --ctstate ...


0

Well, the results for a search for inurl:"httpd/CHANGES_2.2" look like CHANGES_2.2 for the Apache web server made its way to some other sites: http://supergsego.com/apache/httpd/CHANGES_2.2 It looks like most of these changes fix bugs, add new directives, or remove security problems. The changes that are not bugfixes or security patches from Apache ...


1

You can try implementing sudosh - http://sourceforge.net/projects/sudosh/ It acts like a VCR, you can see the commands the people ran and who exactly ran it. Hope this helps.


3

You can look into /var/log/secure to get login times. If there was only one user at the time, it's a strong indication he was the culprit (but not necessary a proof). If there where more users logged in, you can't identify the offending IP this way. With users sharing a username, even the auditing subsystem won't help you much, I guess. Having shared ...


0

I just found the same problem with my chroot Apache install on the CentOS Linux for the Yii2 project. Seems it just because pdo_mysql.so PHP module expect to open libmysqlclient.so.18 in the /usr/lib64, but acutally mariadb already CONTAIN it in the /usr/lib64/mysql. It's simple to fix so: # ln -s /usr/lib64/mysql/libmysqlclient.so.18.0.0 ...



Top 50 recent answers are included