Discuss

discuss@lists.centos.org

2 participants
34758 discussions

mediawiki on centos-4
by Anne Possoz 30 Oct '05

30 Oct '05

I have centos-4 updated to 4.2. Looking for mediawiki with yum, I find it on Dag repository yum --enable dag list mediawiki* Available Packages mediawiki.i386 1.4.7-1.2.el4.rf dag But the installation fails with Error: Missing Dependency: php >= 4.3.11 is needed by package mediawiki Where could I find a yum repository with php-4.3.11 for centos-4? I fell I miss a point. Anne

4 3

CentOS proviiding additional services > was Setting up Tomcat
by Collins Richey 30 Oct '05

30 Oct '05

This thread (... Tomcat ...) emphasizes the essential conundrom of CentOS whose mission is to provide a community-based, well-maintained and freely distributable version of the stable enterprise software from the Well Known North American VENDOR (WKNAV). There is a essential gap betweenthe community (I want lots of current packages) and the WKNAV base (you get what I choose to provide). As CentOS becomes more popular and reaches more desktop and server users, the gap becomes more evident. And there is also the ever present clamor for software that is not freely distributable due to licensing considerations. What I would recommend to assist those who love the CentOS stable base but want more than CentOS can (legally or otherwise) provide is to follow the documentation approach taken by Ubuntu. Ubuntu is based on the Well Known GNU/Linux Provider (KKGLP) but goes well beyond what the WKGLP chooses to privide. The community of Ubuntu has provided a single document with brief HOWTOs and website references for a lot of commonly needed services that are not provided by Ubuntu or the WKGLP. Granted this document (based on Ubuntu 5.04) but not really updated for Ubunto 5.10) is rapidly aging, but it is an example of what could be a very valuable service. Ubunto also provides a well-organized list of HOWTOs on its forums. This is the place for services like Tomcat which have non-redistributable components. It's perfectly legal to provide concise, up-to-date HOWTOs for software that cannot be redistributed. Perhaps someone (or a group of someones) would like to take on organizing such a compendium of instructions on the CentOS Forum and keeping the compendium up to date? Think how many hours of googling and searching mail archives and copious RTFM could be saved! Instead of firing off a mail to this list, you could first look in a well known place on the Forum and avoid recasting a round object. I'm not in a position to undertake such an endeavor. I keep current with CentOS, and I want to see CentOS thrive, but I have only a peripheral interest in CentOS, and that peripheral interst is a work connection. My employer, like many others, prefers to have a contractural arrangement (who can I kick around if it breaks even though it never breaks?) and to pay big bucks to the WKNAV for that privilege. CentOS is the closest thing I can get for my home system without paying the WKNAV, and this I will not do. Some food for thought. -- Collins Richey Debugging is twice as hard as writing the code ... If you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

6 8

iproute create policy routes after reboot
by Robin Mordasiewicz 30 Oct '05

30 Oct '05

Which files do I need to edit in order to initialize a route after a reboot. I have a 802.1q tagged VLAN interface which I need to create a rule, and a route for. I see on my CentOs 4.2 box that in /etc/iproute2 there are the following files. I realize that I can add my tables to /etc/iproute2/rt_tables, but when I want to create a rule I am not sure where to put the information for the next reboot. [root@smtcormx01 ~ ]# ls -la /etc/iproute2/ total 104 drwxr-xr-x 2 root root 4096 Oct 28 13:44 . drwxr-xr-x 87 root root 12288 Oct 28 21:47 .. -rw-r--r-- 1 root root 299 Feb 21 2005 rt_dsfield -rw-r--r-- 1 root root 286 Feb 21 2005 rt_dsfield.rt_config -rw-r--r-- 1 root root 296 Feb 21 2005 rt_protos -rw-r--r-- 1 root root 276 Feb 21 2005 rt_protos.rt_config -rw-r--r-- 1 root root 113 Feb 21 2005 rt_realms -rw-r--r-- 1 root root 112 Feb 21 2005 rt_realms.rt_config -rw-r--r-- 1 root root 98 Feb 21 2005 rt_scopes -rw-r--r-- 1 root root 92 Feb 21 2005 rt_scopes.rt_config -rw-r--r-- 1 root root 91 Feb 21 2005 rt_tables -rw-r--r-- 1 root root 87 Feb 21 2005 rt_tables.rt_config

2 2

sshd problems
by Thomas E Dukes 30 Oct '05

30 Oct '05

Hello, For some reason ssh has stopped working. Its been a good while since I tried to login remotely so I figure an upgrade is probably to blame as it was working some time ago. This is the only error I see when sshd is started: Oct 28 21:55:52 sshd[7137]: Server listening on :: port 22. Oct 28 21:55:52 sshd[7137]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. What does this mean? TIA

6 7

another postfix question
by Steven Vishoot 29 Oct '05

29 Oct '05

hello, i was thinking of using postfix for a mail server, the question is can i use this just for in bound email only and have my clients access this server locally. the clients would be outlook. I want this to check certain email accounts i have and download them to the postfix mail server. The reason i would think about doing this is my wife and i need to access both of these accounts and i do not want to keep them on the email account. is this feasable and secure? thanks Steven "On the side of the software box, in the 'System Requirements' section, it said 'Requires Windows or better'. So I installed Linux."

3 2

UP vs SMP kernel ?
by Robert 29 Oct '05

29 Oct '05

There was a discussion here several days ago that was precipitated by my decision to manually install the new kernel before YUMming the upgrade to CentOS 4.2. The upgrade went south but I recovered by doing a fresh install and a bunch of copying from backups. All's well EXCEPT that I'm back in the same "box", thanks to anaconda. I set out to upgrade kernels this morning: [root@mavis download]# yum update kernel\* Setting up Update Process Setting up repositories dag 100% |=========================| 1.1 kB 00:00 update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Downloading header for kernel-hugemem-devel to pack into transaction set. kernel-hugemem-devel-2.6. 100% |=========================| 656 kB 00:04 ---> Package kernel-hugemem-devel.i686 0:2.6.9-22.0.1.EL set to be updated ---> Downloading header for kernel-smp-devel to pack into transaction set. kernel-smp-devel-2.6.9-22 100% |=========================| 648 kB 00:04 ---> Package kernel-smp-devel.i686 0:2.6.9-22.0.1.EL set to be updated ---> Downloading header for kernel-devel to pack into transaction set. kernel-devel-2.6.9-22.0.1 100% |=========================| 642 kB 00:04 ---> Package kernel-devel.i686 0:2.6.9-22.0.1.EL set to be installed ---> Downloading header for kernel to pack into transaction set. kernel-2.6.9-22.0.1.EL.i6 100% |=========================| 151 kB 00:00 ---> Package kernel.i686 0:2.6.9-22.0.1.EL set to be installed ---> Downloading header for kernel-smp to pack into transaction set. kernel-smp-2.6.9-22.0.1.E 100% |=========================| 151 kB 00:00 ---> Package kernel-smp.i686 0:2.6.9-22.0.1.EL set to be installed ---> Downloading header for kernel-doc to pack into transaction set. kernel-doc-2.6.9-22.0.1.E 100% |=========================| 123 kB 00:00 ---> Package kernel-doc.noarch 0:2.6.9-22.0.1.EL set to be updated --> Running transaction check Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Installing: kernel i686 2.6.9-22.0.1.EL update 9.7 M kernel-devel i686 2.6.9-22.0.1.EL update 3.6 M kernel-smp i686 2.6.9-22.0.1.EL update 9.4 M Updating: kernel-doc noarch 2.6.9-22.0.1.EL update 2.0 M kernel-hugemem-devel i686 2.6.9-22.0.1.EL update 3.6 M kernel-smp-devel i686 2.6.9-22.0.1.EL update 3.6 M Transaction Summary ============================================================================= Install 3 Package(s) Update 3 Package(s) Remove 0 Package(s) Total download size: 32 M Is this ok [y/N]: n Exiting on user Command Complete! You have new mail in /var/spool/mail/root [root@mavis download]# rpm -qa | grep kernel kernel-smp-devel-2.6.9-22.EL kernel-2.6.9-22.EL kernel-hugemem-devel-2.6.9-22.EL kernel-utils-2.4-13.1.69 kernel-devel-2.6.9-22.EL kernel-doc-2.6.9-22.EL kernel-smp-2.6.9-22.EL [root@mavis download]# ...and was reminded that anaconda installed both kernels from the CentOS 4.2 DVD. I verified that I had, indeed repaired /boot/grub/grub.conf following the install: [root@mavis download]# cat /etc/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hdb default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu title CentOS-4 i386-up (2.6.9-22.EL) root (hd0,0) kernel /vmlinuz-2.6.9-22.EL ro root=/dev/VolGroup00/LogVol00 initrd /initrd-2.6.9-22.EL.img You have new mail in /var/spool/mail/root Then, I proceeded with the kernel upgrade and checked grub.conf again [root@mavis download]# cat /etc/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hdb default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu title CentOS (2.6.9-22.0.1.ELsmp) root (hd0,0) kernel /vmlinuz-2.6.9-22.0.1.ELsmp ro root=/dev/VolGroup00/LogVol00 initrd /initrd-2.6.9-22.0.1.ELsmp.img title CentOS (2.6.9-22.0.1.EL) root (hd0,0) kernel /vmlinuz-2.6.9-22.0.1.EL ro root=/dev/VolGroup00/LogVol00 initrd /initrd-2.6.9-22.0.1.EL.img title CentOS-4 i386-up (2.6.9-22.EL) root (hd0,0) kernel /vmlinuz-2.6.9-22.EL ro root=/dev/VolGroup00/LogVol00 initrd /initrd-2.6.9-22.EL.img You have new mail in /var/spool/mail/root [root@mavis download]# To find that the ^%#$@ smp kernel is once more the default! And THAT is why this automagic stuff sometimes scares hell outta me.

3 2

VLAN tagging problems
by Robin Mordasiewicz 29 Oct '05

29 Oct '05

We are using Centos behind an F5 Bigip load balancer. The linux box is using bonding and tagged VLAN's Everything works fine except that when traffic is forwarded from the BigIP to the linux box on the VLAN where the web server is running the linux box returns the traffic on the wrong VLAN, It returns traffic on the lowest ordered VLAN. ie. here is a tcpdump on my load balancer showing traffic being sent on VLAN 911 to the linux box, but the linux box returns traffic on VLAN 902. The linux box is returning traffic on the same VLAN as its configured default gateway. If I change the default gateway to be on the VLAN 911 then everytyhing works. Any ideas ? 07:38:15.480141 802.1Q vlan#911 P0 10.90.11.244.http > 10.90.11.1.47970: . ack 9 win 1098 (DF) 07:38:15.691074 802.1Q vlan#911 P0 10.10.0.27.34023 > 10.90.11.244.http: S 2715145345:2715145345(0) win 4380 <mss 1460,nop,wscale 0,nop,nop,timestamp 72820060 0,sackOK,eol> (DF) 07:38:15.691074 802.1Q vlan#902 P0 10.90.11.244.http > 10.10.0.27.34023: S 514059651:514059651(0) ack 2715145346 win 5808 <mss 1464,sackOK,timestamp 51754641 72820060,nop,wscale 2> (DF) 07:38:18.630101 802.1Q vlan#902 P0 10.90.11.244.http > 10.10.0.27.34023: S 514059651:514059651(0) ack 2715145346 win 5808 <mss 1464,sackOK,timestamp 51757641 72820060,nop,wscale 2> (DF) 07:38:18.630101 802.1Q vlan#911 P0 10.10.0.27.34023 > 10.90.11.244.http: S 2715145345:2715145345(0) win 4380 <mss 1460,nop,wscale 0,nop,nop,timestamp 72823060 0,sackOK,eol> (DF) 07:38:18.630101 802.1Q vlan#902 P0 10.90.11.244.http > 10.10.0.27.34023: S 514059651:514059651(0) ack 2715145346 win 5808 <mss 1464,sackOK,timestamp 51757642 72820060,nop,wscale 2> (DF) 07:38:20.520099 802.1Q vlan#911 P0 10.90.11.1.48003 > 10.90.11.244.http: S 1650014488:1650014488(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 0> (DF)

4 9

CentOS with VMware issues
by Dustin Krysak 29 Oct '05

29 Oct '05

Good day everyone..... I have an install of centos 4.0 patched to 4.2 as my base install. I then installed VMWare 3.2 (gx) over top. I was then going through the install of centos 4.2 (non-patched - latest ISO's) into a virtual machine. Now here is where the issue happens.... on the install, the file "xorg-x11" causes a typical "file can not be access/ file not found" error. I have tried 2 sets of disks (different media even) on my older ISO images, and then even started with the current ISO images on another set of new media. The same symptom always occurs. On the same file, every-time. HAs anyone come across this? Does anyone have CentOS working with VMWare? Thanks in advance! Dustin

2 2

prepare for centos on compaq dl380 G1
by Robert 28 Oct '05

28 Oct '05

greetings i have a few dual P3 Compaq 1850R units and use compaq smartstart 5.5 on them before a CentOS 4 load i have acquired some dual P3 Compaq DL380 G1 i.e. Generation 1 units and am wondering which specific smartstart download i should be using for them from this URL below h18004.www1.hp.com/support/files/server/us/subscription/ssdownloads.asp would someone please share their experience on this so i dont have to waste time and bandwidth? thank you and kind regards - rh -- Robert Hanson - Abba Communications Computer & Internet Services (509) 624-7159 - www.abbacomm.net

3 3

kernel panic when booting with new lvm group/volume
by Aleksandar Milivojevic 28 Oct '05

28 Oct '05

I've added new volume group with single logical volume: pvcreate /dev/sdb1 vgcreate -s 32m xxx_vg /dev/sdb1 lvcreate -l 1234 -n yyy_lv xxx_vg and rebooted the server after it. When booting, the kernel panics with can't mount root file system. Looking at the console output, it seems all volume groups and all logical volumes on them were imported correctly. However, if I go to rescue mode, and re-create initrd image: chroot /mnt/sysimage cd /boot rm initrd-ver.img mkinitrd initrd-ver.img ver lilo then reboot, the server comes up just fine. This is kind of wierd. The root file system was available (at least according to vgscan output which claimed it imported my sys_vg volume group with all the logical volumes I have on it), I haven't touched sys_vg at all, however unless I actually rebuild initrd image, the kernel fails to mount it!? ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0

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