Discuss

discuss@lists.centos.org

2 participants
34758 discussions

centos & mysql
by Stephen A. Wright 02 Jun '06

02 Jun '06

Hi everyone, as a newbie to linux Im having a but of a problem getting up and running. Hopefully one of you you can point me in the right direction. I have installed Centos4 on an old server here at work as a dev box, installation went well, and I have mysql up and running. However when I try and connect from my laptop using mysql administrator I get an error saying "the host is not allowed to connect to this server" I tried disabling the firewall to see if that helped and it made no difference. I also tried pinging the server and that was fine. I tried connecting using the servers ip, name localhost and password as blank. When im logged in a root on the server this allows be to login ok. Any ideas? Thanks in advance Steve

2 2

RPM install vs. NFS mount and code versioning
by Alfred von Campe 02 Jun '06

02 Jun '06

The ongoing discussion regarding Perl modules and RPMs, prompted me to post an issue I am currently facing. I support a development team that uses various third party tools, some free, some not, some of which are installed via RPMs, and some that are not. The development cycle is 18-24 months long, and then there are many years of support (continuing engineering) after that, for which the various versions of the tools need to be available. There are a few dozen engineers on the project. Let say that I want to install SuperTool V1.1, and it's available to install only via RPMs. After thorough testing/qualification on one workstation, I need to install it on the few dozen workstations, which is straightforward but possibly time consuming (and you have to deal with workstations that may be down when you are doing the installs). When V1.2 comes out, I can again test it on one workstation, and then deploy it on the remaining workstations. But what if I there is a bug, and we need to test it against the old version of the tool? With RPMs, it is cumbersome to go back and forth between versions. Contrast that with a tar based install, where I can untar the tool in a directory that includes a version number in the path, and then automount that directory to all the workstations. There is only one install, and I can easily move back and forth among the various versions. Now I understand the benefits of RPMs, but when it comes to supporting tool vendors, dealing with tar based installations and using automounts really simplifies things. I am thinking about installing the RPM based tools on one system, and then copying the entire install tree to a NAS and automount it. I know this is not ideal, but I can't think of a better solution. Any thoughts from the members of this list? Have you tried to solve similar problems in the past? If so, how did you do it? Alfred

2 1

Re: [CentOS] [CSL #301925] centosplus kernel xfs patches and CVE-2006-1855
by David Thompson 01 Jun '06

01 Jun '06

Johnny Hughes wrote: > >There is a centosplus kernel that has that errata ... it is version: > kernel-2.6.9-34.107.plus.c4 Excellent. Is there a general way to map from upstream errata kernels to centosplus kernels? The (apparently??) previous convention of suffixing .106.unsupported to the upstream release number seemed to work well, and I don't want to either guess or take up mailing list bandwidth asking every time upstream revs. >However ... if the only thing you need from the centosplus kernel is the >xfs ... you should use the normal (non-centosplus) kernel and the >kernel-xfs-module that matches it from here: > >http://dev.centos.org/centos/4/testing/i386/RPMS/ > >or > >http://dev.centos.org/centos/4/testing/x86_64/RPMS/ Ooooh. That would be cool. I'll look into it. Thanks again. Dave Thompson UW-Madison

2 1

Installing el3 packages on CentOS 4
by José Alburquerque 01 Jun '06

01 Jun '06

Is it possible to install el3 packages on CentOS 4? I'm wondering because there are some packages on dag (for example ac3dec) that are built for el3 and not for el4. Is it better to rebuild the source rpm? Thanks. Sincerely Jose Alburquerque

2 4

[CSL #301925] centosplus kernel xfs patches and CVE-2006-1855
by David Thompson 01 Jun '06

01 Jun '06

Hi All, we've run into a problem with the xfs component in the centosplus kernel (2.6.9-34.106.unsupportedsmp) where synchronous writes sometimes fail with EAGAIN. It's causing headaches for DB2 installs and for our database research group. There is a fix reported at: http://marc.theaimsgroup.com/?l=linux-xfs&m=110808122904352&w=2 ...that's supposed to take care of things. If there is any way these patches could be included in a future centosplus kernel, we would greatly appreciate it. We are enjoying the performance lift from xfs on many systems, and hate to throw it away to get a database to work. Also, are there plans to produce a centosplus kernel that corresponds to the newest RHEL errata kernel (2.6.9-34.0.1.EL)? Cheers and thanks, Dave Thompson UW-Madison

2 1

Re: [CentOS] libtiff build error
by Robert Moskowitz 01 Jun '06

01 Jun '06

At 04:24 PM 6/1/2006, Jim Perrin wrote: >>But there is no rpm for libtiff v 3.8.2 for Centos. Every indication >>is that I need this. Well we will see what is supplied in the new >>Trixbox (Asterisk@home's new name). > >Very true, but you can always build your own. In any even, I won't >preach about this one too much. Thanks for your pointers. Almost time to quit for holiday (Shavous), so this will be resumed monday. I think I see how to proceed. I have two A@H systems, replace one wiht Trixbox and see what if haves, if not shotgun everything I need onto other box, move the files over and make install.... And figure out the necessary symbolic links. Gee I have not done any of that since working on Suns 12+ years ago..... >> >> But the make had the following error: >> >> >> >> ./libtool: line 837: g++: command not found >> > >> >This one line has your winner. You lack the proper build tools to >> >complete your desired task. You're missing the gcc-c++, and probably >> >several other things you'll need. >> >>?? yum groupinstall gcc-c++ > >There's no group by that name. If you're going to do the shotgun >approach like that then >yum groupinstall "Development Tools" is probably what you want > >> >> >> make[2]: Leaving directory `/root/tiff-3.8.2/libtiff' > >>So I log in as user foo. I do all the makes as foo. But everything >>in /usr/var is owned by root... ?? > >configure and make are run as your user. Make install (which should >really just be moving files to their final location) is the only thing >you need to run as root or with sudo. > > >>I have looked for some reasonable howtos but so far have come up short. > >I don't really have any to offer. Maybe someone else on the list will. > >> >>1104 -r--r--r-- 1 root root 1126338 May 9 07:38 libtiff.a >> 0 lrwxrwxrwx 1 root root 14 May 24 11:07 libtiff.so -> >>libtiff.so.3.6 >> 0 lrwxrwxrwx 1 root root 14 May 24 11:07 libtiff.so.3 -> >>libtiff.so.3.6 >> 308 -rwxr-xr-x 1 root root 311088 May 9 07:38 libtiff.so.3.6 > >This may not be as obvious as you think. The way you're doing things >right now would install libtiff in /usr/local/ so you'd end up with >both versions. and your asterisk application would have to be >specifically told which one to use, as it'll probably link against the >files in /usr before the files in /usr/local > > >-- >This message has been double ROT13 encoded for security. Anyone other >than the intended recipient attempting to decode this message will be >in violation of the DMCA >_______________________________________________ >CentOS mailing list >CentOS(a)centos.org >http://lists.centos.org/mailman/listinfo/centos

1 0

Re: [CentOS] libtiff build error
by Robert Moskowitz 01 Jun '06

01 Jun '06

It would be nice if the world were flat... At 02:48 PM 6/1/2006, Jim Perrin wrote: >> ./configure >> make clean >> make > >Not going to get into how much of a bad idea this is, or how it should >really be in an rpm. But there is no rpm for libtiff v 3.8.2 for Centos. Every indication is that I need this. Well we will see what is supplied in the new Trixbox (Asterisk@home's new name). >> But the make had the following error: >> >> ./libtool: line 837: g++: command not found > >This one line has your winner. You lack the proper build tools to >complete your desired task. You're missing the gcc-c++, and probably >several other things you'll need. ?? yum groupinstall gcc-c++ >> make[2]: Leaving directory `/root/tiff-3.8.2/libtiff' > >This line would seem to imply that you're building software as root. >This is generally a very bad idea. If the code's cleanup scripts are >wrong, or if there's a typo... it's running as root and could very >easily rm -rf your system, instead or rm -rf the buildroot or tmp >files its using, not to mention other nefarious code tricks that make >this a bad idea. So I log in as user foo. I do all the makes as foo. But everything in /usr/var is owned by root... ?? >> and make install did not work: > >that's because you had prior errors. Just making sure. Obvious answer, but I have been seeing some non-obvious stuff lately. >> So what is missing? And where do I start from. > >You should really consider reading up on compiling software and/or >building custom rpms. I have looked for some reasonable howtos but so far have come up short. >> It looks like things are not 'broken' from how far it got. > >They're not broken because they haven't gotten that far yet. You're >missing the compiler required to make/break them. Again, obvious from: 1104 -r--r--r-- 1 root root 1126338 May 9 07:38 libtiff.a 0 lrwxrwxrwx 1 root root 14 May 24 11:07 libtiff.so -> libtiff.so.3.6 0 lrwxrwxrwx 1 root root 14 May 24 11:07 libtiff.so.3 -> libtiff.so.3.6 308 -rwxr-xr-x 1 root root 311088 May 9 07:38 libtiff.so.3.6 thanks. >-- >This message has been double ROT13 encoded for security. Anyone other >than the intended recipient attempting to decode this message will be >in violation of the DMCA Illegitimi non Carborundum

2 1

RE: [CentOS] Assistance with startup script
by Bowie Bailey 01 Jun '06

01 Jun '06

Will McDonald wrote: > > If you added something like... > > # chkconfig: 345 20 80 > # description: Does LDM stuff > > ... after your shabang #!/bin/sh line that should suffice. That would > start your LDM script after networking in runlevels 345 and stop it > before networking's stopped when hopping back down through the > runleves. > > I can't recall if you need a "chkconfig --add ldm" but if your > script's not visible in "chkconfig --list" then try it. The chkconfig > man page's RUNLEVEL FILES section should have all the info you need. Yes, you do need the "chkconfig --add ldm". This is what creates the links in the runlevel directories. > If you wanted to go the whole hog you could also look at integrating > your startup stuff into /var/lock/subsys etc. Just have a look through > an existing init script. If you want init to shutdown the service for you, you need a lock file in /var/lock/subsys with the same name as your main script. Just have the start routine touch it and the stop routine remove it. -- Bowie

4 5

Assistance with startup script
by Sam Drinkard 01 Jun '06

01 Jun '06

Could someone give me some assistance in getting this startup script to conform to chkconfig and such where the service will start up after networking comes up, and then shut down when networking goes away? Where all do entries need to be made, and what would they consist of? Many thanks..... Sam ------------------------------------------------------------------------ #! /bin/sh export PATH=/bin:/usr/bin LDMHOME=/usr/local/ldm LDMBIN=$LDMHOME/bin LDMADMIN=$LDMBIN/ldmadmin PQCHECK=$LDMBIN/pqcheck PQCAT=$LDMBIN/pqcat PQ=$LDMHOME/data/ldm.pq LOG="logger -p local0.err $0:" case "$1" in start) $LOG 'Starting LDM system...' if [ -x $LDMADMIN ] ; then if su - ldm -c "$LDMADMIN isrunning"; then $LOG "LDM system is already running." else if [ ! -f $PQ ] ; then $LOG "Product-queue doesn't exist. Creating..." if ! su - ldm -c "$LDMADMIN mkqueue"; then $LOG "Aborting..." exit 1 fi else # # Test the product-queue for corruption. # if ! $PQCHECK -l /dev/null -q $PQ; then case $? in 1) $LOG "System error checking product-queue. Aborting..." exit 1 ;; 2) $LOG "Adding writer-counter to product-queue..." if ! $PQCHECK -F -q $PQ; then $LOG "Aborting..." exit 1 fi ;; 3) $LOG "Product-queue was incorrectly closed. " \ "Checking..." if $PQCAT -s -l /dev/null; then $LOG "Product-queue appears OK. " $LOG "Clearing writer-counter..." if ! $PQCHECK -F -q $PQ; then $LOG "Couldn't clear counter. Aborting..." exit 1 fi else $LOG "Product-queue appears corrupt. Deleting." rm $PQ if ! su - ldm -c "$LDMADMIN mkqueue -f"; then $LOG "Couldn't make new product-queue. Aborting..." exit 1 fi fi ;; 4) $LOG "Product-queue is corrupt. Deleting." rm $PQ if ! su - ldm -c "$LDMADMIN mkqueue -f"; then $LOG "Couldn't make new product-queue. Aborting..." exit 1 fi ;; esac fi fi su - ldm -c "$LDMADMIN clean" su - ldm -c "$LDMADMIN start" fi fi ;; stop) $LOG 'Stopping the LDM system.' if [ -x $LDMADMIN ] ; then su - ldm -c "$LDMADMIN stop" fi ;; esac -- Sam W.Drinkard -- sam(a)wa4phy.net WEB http://wa4phy.net Augusta Mesonet cell 706.825.8513 Home 706.868.7253 MAIL 4438 Branchwood Drive, Martinez Georgia, 30907-1304

4 4

libtiff build error
by Robert Moskowitz 01 Jun '06

01 Jun '06

OK. Trying to build libtiff here. Info from http://www.asteriskguru.com/tutorials/spandsp.html Libtiff from tar: ftp://ftp.remotesensing.org/pub/libtiff 3.8.2 put tiff-3.8.2.tar.gz in /root then tar -zxvf tiff-3.8.2.tar.gz followed by: /configure make clean make But the make had the following error: ./libtool: line 837: g++: command not found make[2]: *** [tif_stream.lo] Error 1 make[2]: Leaving directory `/root/tiff-3.8.2/libtiff' make[1]: *** [all] Error 2 make[1]: Leaving directory `/root/tiff-3.8.2/libtiff' make: *** [all-recursive] Error 1 and make install did not work: Making install in port make[1]: Entering directory `/root/tiff-3.8.2/port' make[2]: Entering directory `/root/tiff-3.8.2/port' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/root/tiff-3.8.2/port' make[1]: Leaving directory `/root/tiff-3.8.2/port' Making install in libtiff make[1]: Entering directory `/root/tiff-3.8.2/libtiff' source='tif_stream.cxx' object='tif_stream.lo' libtool=yes \ DEPDIR=.deps depmode=none /bin/sh ../config/depcomp \ /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I. -I. -c -o tif_stream.lo tif_stream.cxx libtool: compile: g++ -DHAVE_CONFIG_H -I. -I. -I. -I. -c tif_stream.cxx -o .libs/tif_stream.o ./libtool: line 837: g++: command not found make[1]: *** [tif_stream.lo] Error 1 make[1]: Leaving directory `/root/tiff-3.8.2/libtiff' make: *** [install-recursive] Error 1 So what is missing? And where do I start from. It looks like things are not 'broken' from how far it got.

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss