Tag Info

Hot answers tagged

82

You can look at the contents of /etc/redhat-release, which will look something like this: $ cat /etc/redhat-release CentOS release 5.4 (Final) The contents are different for an actual RHEL system. This technique works on all RedHat derivatives, including CentOS, Fedora, and others.


63

You can use the lsb_release command on recent linux distributions. If you issue: lsb_release -i -r it will tell you the Distribution and Version. This is a little bit more accurate than accessing files that may or may not have been modified by the admin or a software package. As well as working across multiple distros.


21

I prefer to use the /etc/issue file. $ cat /etc/issue I've seen many situations where /etc/redhat-release has been modified to meet software compatibility requirements (Dell or HP's management agents, for instance).


21

A patch has been provided by Oracle for el4 : https://oss.oracle.com/el4/SRPMS-updates/bash-3.0-27.0.1.el4.src.rpm https://oss.oracle.com/el4/SRPMS-updates/bash-3.0-27.0.2.el4.src.rpm https://oss.oracle.com/el4/SRPMS-updates/bash-3.0-27.0.3.el4.src.rpm https://oss.oracle.com/el4/SRPMS-updates/bash-3.0-27.el4.src.rpm As it is a src RPM, you need to ...


20

I had to patch an old CentOS 4.9 server, so I pulled the latest source RPM from the Red Hat FTP and added the upstream patch from the GNU FTP. The steps are below: First, follow the "Setup" procedure from http://bradthemad.org/tech/notes/patching_rpms.php. Then run the following commands from your %_topdir: wget ...


14

RHEL 4 is in it's "extended life" phase and security updates will be only available to paying customers. CentOS 4 is out of support since March 2012. No further updates are available for this since this time. Your only options are to Buy a support contract with RedHat Try to build your own package for Bash. Or the winning option: Retire this machine and ...


8

You have Listen directive for the same socket multiple times. Use grep -r Listen /etc/httpd/conf.d/*.conf /etc/httpd/conf/httpd.conf to find the culprit. From apache documentation: Error condition Multiple Listen directives for the same ip address and port will result in an Address already in use error message.


8

We have a system wher we rsync live servers to backup servers (which are built out of cheap 1TB SATA discs) then take full tape backups of the backup servers. It's excellent: Belt and braces - all the advantages of both backups reduces the IO load on the live servers considerably faster restores if you just want one or two files full set of tapes for the ...


6

GlusterFS is very good for this job, you can also consider Lustre maybe (I have not used that one yet though) GlusterFS is NFS independent software but it would be very easy to move on that. You can also use it for Raid 10 networks which you might need in the future and it is very easy to scale.


6

The most reliable way when lsb_release is not installed is: # rpm -q --queryformat '%{VERSION}' redhat-release-server 6Server # rpm -q --queryformat '%{RELEASE}' redhat-release-server 6.4.0.4.el6 On minimal installs, lsb_release is missing. To get this working also with Red Hat clones (credit goes to comments): # rpm -q --queryformat '%{VERSION}' $(rpm ...


5

Assuming it truly is a Red Hat release (not Centos): rpm -q redhat-release Or just run: uname -r And map the output. 2.6.9 kernels are RHEL4, 2.6.18 kernels are RHEL5. If necessary, you can map the full version to the specific update releases from Red Hat (i.e. 2.6.9-89 is RHEL5 U4).


5

Redhat 4.x and CentOS 4.x will install just fine in that RAM/CPU footprint.


5

RHEL 4 is in what Red Hat calls Extended Life Phase. ...For versions of products in the Extended Life Phase, Red Hat will provide limited ongoing technical support. No security fixes, bug fixes, hardware enablement or root-cause analysis will be available during this phase, and support will be provided on existing installations only. You can ...


4

If your mounted points are permanent- placed in /etc/fstab - you can run mount -a to re-read fstab, which is same as a refresh. You could also use remount in case of a temporary mount


4

From my experience - and the reason that we do not use logrotate with Log4j is that the way logrotate works is that it renames the files, then instructs the program to close its logs and reopen them with the old file name (which does not exist anymore), normally using the HUP signal. But Log4j cannot be told to reopen its log files, so I see you use ...


4

I'm not sure how bpbkar works really, but I would use rsync to backup all the files offsite and then keep them in sync, which would consume very little resources, as only changed files are updated. Naturally, this means it would take quite some time for the initial backup, but you already say you've been 'humming for 18 hours'. You would then simply manage ...


3

If your backups take 18 hours to run normally, deprioritising them probably isn't going to solve the problem (unless you want to run your backups for a couple of days at a time). I'd be inclined to setup a disk replication mechanism to another machine (I like DRBD, myself) and then use LVM to take a point-in-time snapshot, backup that, and move on. Because ...


3

Since you're running PHP on that server, I would be cautious about using the Worker MPM. There are some known issues with Worker and PHP. The PHP Installation FAQ recommends against it.


3

bpbkar is Veritas Netbackups backup client. It supports throttling, so the combination of normal I/O and backup I/O doesn't saturate your disks. Look at here: http://seer.entsupport.symantec.com/docs/265707.htm Is there anything stopping you doing full backups at the weekend, as you say the system is mostly busy weekdays, and incremental backups during the ...


3

We had the same problem for a file being written by log4j. The solution was to set the property "Append" for the FileAppender to "true". After this change, we have not seen this problem with files having NUL when rotated by an external program like logrotate.


3

If you ran make install and already had the mysql-server package installed, chances are you had a pre-existing mysql database schema in /var/lib/mysql. The version included with RHEL5 is 5.0.77, which could explain the mysql-upgrade error, as that script updates the schema between MySQL versions. The error could also be very similar if you did not create ...


3

While remarkably hackish, the route I ultimately ended-up following is this: Using VMware ESXi, add datastores that are NFS mounts (from whereever). Create vdisks on those datastores Add the vdisks to a VM running RHEL (because I'm used to RHEL) Put all of the added volumes into an LVM Export the LVM partition via NFS Pros: simple cheap easy to ...


3

There are several things that you need to do to prevent problems and possibly system crash in the future: Create separate partitions for /var, /var/log, /tmp and possibly others to help your system survive (hopefully) in case of one partition got filled accidentally. Use reasonable logrotate configuration to allow a good amount of logs and not consuming a ...


3

Sasha has it almost right, and since I can't comment I'll post this as a standalone answer. Ignoring dependency errors is a Very Bad Idea™. It's also unnecessary in this case since there's an updated version of nscd to go along with glibc. The patched glibc packages are indeed available from Oracle, and I've confirmed that installing them patches the GHOST ...


3

LinuxQuestions.org has an answer: You don't want to have less than 256MB of RAM in your system if you want to run RHEL 4, especially with an X desktop. I also wouldn't go much slower than a 500mhz CPU, either.


2

This post is old but i think is better providing a solution if has been discovered. I have solved simply setting the environment variable MALLOC_CHECK_ explicitly to 0: setenv MALLOC_CHECK_ 0 in the RHEL4 Documentationdocs is explained the cause of the problem (in the section Package Specific Notes / glibc).


2

A kind soul named Lewis Rosenthal has placed updated Bash RPMS for CentOS 4 up on his FTP server. The bash-3.0-27.3 RPM is believed to address CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, and CVE-2014-7187. He has a README with more information, and there was some discussion on the CentOS forums. Don't forget this helpful all-in-one check script--note that ...


2

If you do not have RHEL subscription, Oracle was kind enough to release updated packages for your old RH4 box. For both (i386 and X86_64) systems do: mkdir glibc2015 cd glibc2015 For i386 system do (Note, I had to replace http with h**p to avoid spam filters here.) : wget ...


2

Here's a script you could run against the dead.letter file and maybe catch the process creating it. #! /bin/bash if [ $# -eq 0 ]; then echo "Syntax: $(basename $0) <file_to_watch>" exit 1 fi FILE_TO_WATCH=$1 LOGFILE=/var/tmp/$(basename $0).$(date +"%Y-%m-%d").log SLEEP_DELAY=5 if [ ! -e $LOGFILE ]; then echo -e "DATE ...


2

Does that user have a web content tree being served by a web server of this system? Check their content tree for a CGI or something that handles GET/POST submissions. My guess is they have some standard web software installed -- a page layout tool, or something like WordPress. Some 3rd party/ies is using some security hole in that web software to try to ...



Only top voted, non community-wiki answers of a minimum length are eligible