Re: [CentOS] wml / centos7
Am 13.09.2014 16:21, schrieb Michael Kress: Hi, anybody got wml running under centos7? Got problems either compiling it or finding an rpm. TIA for any hint! Found a solution: installed centos5, there I got it running. Not the worst thing, it's running on a VM, it's only purpose is to execute wml on a nfs mount from time to time until decommissioned. So thanks for keeping available the old isos! Regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] wml / centos7
Hi, anybody got wml running under centos7? Got problems either compiling it or finding an rpm. TIA for any hint! Regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] wml / centos7
Am 13.09.2014 um 16:21 schrieb Michael Kress: Hi, anybody got wml running under centos7? Got problems either compiling it or finding an rpm. TIA for any hint! ... and BTW, the sw-wml mailing list is not available anymore :-( ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] wml / centos7
Am 13.09.2014 um 20:36 schrieb Reindl Harald: fine that you know what you mean wml can be a lot of different things that's why the www provides links so others know what you are talking about oops sorry, it's the website meta language ... http://thewml.org/ - an offline website generation engine and toolset which in pre-php times provided a nifty way of generating websites with many features like diversion, macro expansion, file inclusion, etc. Regards Michael PS: Ooops, sorry, first reply went to you personally ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 - Firewall always allows outgoing packets?
Am 13.08.2014 um 15:16 schrieb Timothy Murphy: I'm a bit surprised no-one has mentioned shorewall. I'm using it on two tiny home servers, one under CentOS-6 and the other CentOS-7. Basically, this is because I don't understand iptables, or really want to understand it. here, too, I'm using shorewall, because with the semantics in the config files, I can easily express what I want. It makes it easy to create very complex setups without knowing anything of iptables (although it helps to know about it). Moreover, the superb help of Tom Eastep and others in the support mailing list makes shorewall the firewall of my choice. Hence, the first thing I disable on a fresh centos install: firewall and sh** I often wonder if I am in a small minority of CentOS users, who are just running home servers of some kind. welcome to the club ;) Regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] USB 3.0 NIC / Sitecom NL-031
Hi, I have a Sitecom NL-031 USB 3.0 NIC which I'd like to use under centos 6.5, but unfortunately I see no support. Or, I am doing something wrong. According to LKDDb (Linux Kernel Driver DataBase), the correct driver is CONFIG_USB_NET_AX8817X: ASIX AX88xxx Based USB 2.0 Ethernet Adapters but obviously, I've grabbed a non matching iProduct, because mine is obviously 0x0072 (see lsusb below) and the driver lists 0x0056. From the LKDDb: vendor: 0df6 (Sitecom Europe B.V.), product: 0056 (LN-031 10/100/1000 Ethernet Adapter) vendor: 0df6 (Sitecom Europe B.V.), product: 0056 (LN-031 10/100/1000 Ethernet Adapter) When i modprobe for the NIC, I get something very unspectacular ... root@mybox:/root [0] modprobe asix /var/log/messages: Apr 5 20:02:23 mybox kernel: usbcore: registered new interface driver asix dmesg: usbcore: registered new interface driver asix BTW, I got this passed on by ESXi to a CentOS VM. Do you see any chance to get this running? Thanks in advance Michael PS: the lsusb output ... root@mybox:/root [0] lsusb -v -d 0df6:0072 Bus 001 Device 003: ID 0df6:0072 Sitecom Europe B.V. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0df6 Sitecom Europe B.V. idProduct 0x0072 bcdDevice1.00 iManufacturer 1 Sitecom Europe BV iProduct2 Sitecom USB 3.0 Gigabit iSerial 3 01 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 248mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol 0 iInterface 4 Network_Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 11 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Status: 0x (Bus Powered) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] USB 3.0 NIC / Sitecom NL-031
Am 05.04.2014 20:28, schrieb Akemi Yagi: On Sat, Apr 5, 2014 at 10:07 AM, Michael Kress kr...@hal.saar.de wrote: Hi, I have a Sitecom NL-031 USB 3.0 NIC which I'd like to use under centos 6.5, but unfortunately I see no support. Or, I am doing something wrong. I just checked the device ID pair [0df6:0072] against the current CentOS-6 kernel but it returned nothing. However, I did find the driver in ELRepo's kernel-ml: alias usb:v0DF6p0072d*dc*dsc*dp*ic*isc*ip*in* ax88179_178a It shows that the driver that supports your device is ax88179_178a . I suggest you try installing kernel-ml [1] and see if your NIC works. If that works well, you'd want to ask ELRepo if backporting the driver for EL-6 is possible. Hey cool, thanks, using the kernel-ml actually works and gives me a usable ethx device! Ok, proves the concept, but is using a kernel-ml recommended for a production centos6 system? Or should I rather get a different USB 3.0 NIC that actually works with centos6 ? Which one? (Has to be a Gigabit USB NIC) Kind regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] php4 under Centos6
Hello, is there any way of getting php4 installed on Centos6? I'd like to install it in an apache/fastcgi environment. Has anybody got a link to a description/howto describing a clean install? I failed compiling the original php4 tar ball and failed relocating the php binary. Thanks in advance Regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] php4 under Centos6
Am 12.06.2012 22:39, schrieb Reindl Harald: Am 12.06.2012 22:19, schrieb Michael Kress: Hello, is there any way of getting php4 installed on Centos6? I'd like to install it in an apache/fastcgi environment. Has anybody got a link to a description/howto describing a clean install? I failed compiling the original php4 tar ball and failed relocating the php binary. PHP4 IS DEAD SINCE A LONG TIME DO NOT USE PHP4 - THROW AWAY CRAP WHICH DOES NOT WORK WITH PHP5 BECAUSE IT IS UNMAINTAINED AND UNSECURE oh yes, forgot the disclaimer with the above text. Regards Michael -- Michael Kress, kr...@hal.saar.de http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-virt] shut down a Centos 6 guest / libvirt / ACPI
Got the solution - originally, I've installed the system with --noapic \ --noacpi \ Omitting those options, I get this into the xml used during installation: features acpi/apic/pae/ /features and then after installing and starting acpid, shutting down works like a charm. What was hard though, was to add those features later in the xml, even installing acpid wasn't any use, had to reinstall with the above procedure. But now I know how to proceed. Thanks, Regards Michael Am 03.06.2012 01:35, schrieb Trey Dockendorf: What /etc/init.d/acpid restart return or show in /var/log/messages? Minimal should work fine as that's what I've always used to provision KVM guests. On Sat, Jun 2, 2012 at 6:14 PM, Michael Kress kr...@hal.saar.de mailto:kr...@hal.saar.de wrote: Am 02.06.2012 18:02, schrieb Trey Dockendorf: On Jun 2, 2012 10:43 AM, Michael Kress kr...@hal.saar.de mailto:kr...@hal.saar.de wrote: Hi, shutting down a Centos6 kvm guest does not work from outside doing a 'virsh shutdown vmguest', I've installed the CentOS-6.2-x86_64-minimal.iso inside the kvm guest If acpid is installed try rebooting. Ive had issues with acpid starting on first install as its blocked by another daemon. Rebooting or installing during kickstart has solved it for me. - Trey I've done that numerous times, no success. Will try with the regular version of Centos 6 and report again. Regards Michael ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS] Here we go again: SpamAssassin doesn't like the new Perl update...
Am 02.10.2010 08:37, schrieb Michael Kress: Starting spamd: Subroutine NetAddr::IP::UtilPolluted::AF_INET6 redefined at /usr/lib/perl5/5.8.8/Exporter.pm line 65. at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/NetAddr/IP/Util.pm line 180 Hi, same issue here, SA was behaving nicely until I updated it. I saw that it was suddenly coming from rpmforge, but I trusted that and pressed Y. Since then, every sa-update complains about the above routine redefinition. Hi, after updating perl-MailTools and perl-NetAddr-IP, SA updates are silent now. Thanks for fixing it! Michael -- Michael Kress, kr...@hal.saar.de http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Here we go again: SpamAssassin doesn't like the new Perl update...
On Oct 1, 2010, at 4:58 PM, Steve Huff wrote: On Oct 1, 2010, at 10:34 AM, Gilbert Sebenste wrote: Starting spamd: Subroutine NetAddr::IP::UtilPolluted::AF_INET6 redefined at /usr/lib/perl5/5.8.8/Exporter.pm line 65. at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/NetAddr/IP/Util.pm line 180 this does not look like CentOS's fault. $ rpm -qf /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/NetAddr/IP/Util.pm perl-NetAddr-IP-4.032-1.el5.rf first off, the package in question comes from RPMforge. Hi, same issue here, SA was behaving nicely until I updated it. I saw that it was suddenly coming from rpmforge, but I trusted that and pressed Y. Since then, every sa-update complains about the above routine redefinition. Regards Michael -- Michael Kress, kr...@hal.saar.de http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] kvm-shell
Hi, I don't know if that already exists somewhere ... I've written it for me and wanted to share it with you. It's minimal kvm shell for end users - it allows them to start/stop/reboot their own kvm guests. http://www.michael-kress.de/2009/12/kvm-shell/ kvm-shell should run on all platforms. Have fun. Regards Michael -- Michael Kress, kr...@hal.saar.de ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Running SSH on a different port
ML wrote: So I added Port 2977 Under Host * So I have: Host * Port 2977 Never post your real port number here. Otherwise you don't need to hide it from the public. Right? ;-) Regards Michael -- Michael Kress, kr...@hal.saar.de ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Remote backup of server
Hi, you're searching for a solution that makes snapshots with hardlinks 1) use rsync --delete over ssh 2) use cp -al to create generations 3) rotate the generations daily, just with mv The generations use nearly no additional disk space, only changes in the file system consume space (i.e. additions), because of the usage of hardlinks for the rest of the files. With new files, rsync will overwrite the hardlink in the current generation of your backup. The hardlinks of the older generations stay intact, thus the older physical file stays intact. Remember, a file stays alive as long as there's at least one hardlink pointing to it. This mechanism is the relief to your worries - if a data corruption occurs on one of your files then your backups from the past 'n' days will contain a file version that is still good, whereas 'n' is the number of generations you'll keep. An example: day #1: === * first rsync happens, lots of files will be created daily.0/abc (hardlink to file abc with inode 2235) daily.0/def (hardlink to file def with inode 2249) daily.0/ghi (hardlink to file ghi with inode 3456) day #2: === * do a 'cp -al daily.0 daily.1' * do the new rsync on daily.0, modified file abc coming over * the hardlink daily.1/abc stays untouched (so is the file) * the hardlink faily.0/abc is a new one as the file is a new one daily.0/abc (NOTE: hardlink to file abc with inode 8877 ! ) daily.0/def (hardlink to file def with inode 2249) daily.0/ghi (hardlink to file ghi with inode 3456) daily.1/abc (hardlink to file abc with inode 2235) daily.1/def (hardlink to file def with inode 2249) daily.1/ghi (hardlink to file ghi with inode 3456) Each of the files def and ghi consume only once the disk space, whereas abc from daily.0 and abc from daily.1 are different files with different inodes and they of course consume the double amount of disk space. You may secure your ssh connection even more by not using root i.e. by using a non privileged user. In that case you'd have to use a sudo etry (via 'visudo') allowing the non privileged user to use /usr/bin/rsync as the super user, i.e. on EVERY file in the system. The sudo line would be: backupuser ALL=(root)NOPASSWD:/usr/bin/rsync Of course you should only mount the partition you're backing up to as read write when you have to. Otherwise it should stay unmounted or at least mounted read only. The machine you're backing up to should be a single user machine. A user id 501 on machine A, named 'john', may be a different user on machine B, there named 'bill'. So if bill logs into machine B (and if he has user id 501) then he'll be able to see the files from user 'john', in case the backup partition is readable. (That's also why you should keep it unmounted). Data in backups may e.g. contain mysql passwords, smtp passwords, etc. That's not THE ULTIMATE solution, but it works for me and it seems to be quite efficient. I think the main advantage of that solution is that you're independent of any backup software except for cp and rsync. Contact me in case you've got further questions. Michael happymaster23 wrote: Thank you for reply, because rsync is only synchronizing data (with all errors), this is not backup. If on main server will be some data corruption and backup server will connect and synchronize all data with errors, I have nothing :). For example - rdiff-backup is working with increments, so you can restore data a year back... 2009/9/4 Johnny Hughes joh...@centos.org: On 09/04/2009 11:23 AM, happymaster23 wrote: I want mount directory of one server to another over internet. I was looking to NFS4, but there are no security mechanisms. I need encrypted connection using private key (something like SFTP). Or - if there is in CentOS repo (or EPEL) package, that can mount directory over internet using private key and make differential backup (like rdiff-backup). Thank you very much for links or other resources work up Why not just use rsync over ssh? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] saslauthd
Michael Kress wrote: 2) saslpasswd2 -c -a mail -u mail testuser That's a typo - the user is testomat. But, with the same result. :-( 3) testsaslauthd -u testomat -p mypassword -s smtp -r mail shell output of testsaslauthd: 0: NO authentication failed ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] saslauthd
Hi, Kai Schaetzl wrote: I don't know what's going on - it seems that testsaslauthd doesn't lookup the user 'testomat' in /etc/sasldb2 Should it really do that with auth-mech=shadow? oh, I forgot to mention - of course I already tried that one: saslauthd -d -a pam -O /usr/lib64/sasl2/smtpd.conf -r -l Without success. Regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] saslauthd
Hi, Alexander Dalloz wrote: 2) saslpasswd2 -c -a mail -u mail testuser That's a typo - the user is testomat. But, with the same result. :-( 3) testsaslauthd -u testomat -p mypassword -s smtp -r mail shell output of testsaslauthd: 0: NO authentication failed You are mixing things. saslauthd and sasldb are exclusive: either use one or the other (at least on CentOS). ok - I think we're coming closer to the point. It will certainly be sasldb2, because I have an old machine with SMTP AUTH users who are contained in /etc/sasldb2 I want to transfer these users to the new machine without having them to assign new passwords. Given the scenario that I copy the old /etc/sasldb2 to the new machine, how could postfix there authenticate these SMTP AUTH users? On CentOS sasldb can only be used as a plugin by auxprop mechanism. You will have to decided for one way to store your credentials. see above - the decision is already taken by the fact of the migration. Regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] saslauthd
Kai Schaetzl schrieb: If it doesn't matter which POP/IMAP server you use I would recommend going with Dovecot. The purpose for using /etc/sasldb2 is to use SMTP AUTH. (See my other posting). Regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to clone CentOS server ?
przemol...@poczta.fm wrote: I'd like to clone existing CentOS server. Can anybody recommend any working solution to achieve that ? 1) virsh shutdown vmxx 2) cp /etc/libvirt/qemu/vmxx /etc/libvirt/qemu/vmyy 3) cp old image file new image file 4) perl -pi -w -e 's/old image file/new image file/g;' /etc/libvirt/qemu/vmyy 5) adjust new name in /etc/libvirt/qemu/vmyy 6) reload libvirtd 7) virsh start vmxx virsh start vmyy HTH Regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] saslauthd
Alexander Dalloz wrote:
First you will have to configure Postfix through main.cf:
...
Next you have to make the link between Postfix and Cyrus-SASL in
/usr/lib{64}/sasl2/smtpd.conf:
...
You are done.
Yes I am! :-)
In fact, I DID all the above (with more or less variants), but I was
wondering why the command testsaslauthd wouldn't allow me to test
authentication. Now I don't care anymore - what I need it for is: postfix
with SASL AUTH agains smtp clients and for THAT I only need a properly
filled and protected (postfix will have to be able to read the file)
/etc/sasldb2 file.
I was also wondering because on the machine that I'm migrating away from
the testsaslauthd command worked. Same config and both using the same
centos release. Ok - nevermind, the authentication works, a nice thing to
start a thursday with.
Thanks @Alexander, Kai and Nataraj and all others who cared!
Kind regards
Michael
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] saslauthd
Hello, I'm having trouble to get saslauthd running on a centos-5.3. I can't autheticate via testsaslauthd. Here's what I do using a fresh /etc/sasldb2: 1) start saslauthd in debug mode: saslauthd -d -a shadow -O /usr/lib64/sasl2/smtpd.conf -r -l 2) saslpasswd2 -c -a mail -u mail testuser 3) testsaslauthd -u testomat -p mypassword -s smtp -r mail shell output of testsaslauthd: 0: NO authentication failed shell output of saslauthd: [r...@x02-new ~]# saslauthd -d -a shadow -O /usr/lib64/sasl2/smtpd.conf -r -l saslauthd[1936] :main: num_procs : 5 saslauthd[1936] :main: mech_option: /usr/lib64/sasl2/smtpd.conf saslauthd[1936] :main: run_path : /var/run/saslauthd saslauthd[1936] :main: auth_mech : shadow saslauthd[1936] :detach_tty : master pid is: 0 saslauthd[1936] :ipc_init: listening on socket: /var/run/saslauthd/mux saslauthd[1936] :main: using process model saslauthd[1936] :have_baby : forked child: 1937 saslauthd[1936] :have_baby : forked child: 1938 saslauthd[1936] :have_baby : forked child: 1939 saslauthd[1936] :have_baby : forked child: 1941 saslauthd[1937] :do_auth : auth failure: [user=testo...@mail] [service=smtp] [realm=mail] [mech=shadow] [reason=Unknown] saslauthd[1937] :do_request : response: NO output in /var/log/messages: Aug 26 07:41:31 x02-new saslauthd[1673]: server_exit : master exited: 0 Aug 26 07:41:33 x02-new saslauthd[1936]: detach_tty : master pid is: 0 Aug 26 07:41:33 x02-new saslauthd[1936]: ipc_init: listening on socket: /var/run/saslauthd/mux Aug 26 07:41:38 x02-new saslauthd[1937]: do_auth : auth failure: [user=testo...@mail] [service=smtp] [realm=mail] [mech=shadow] [reason=Unknown] output of saslfinger: #csaslfinger -s saslfinger - postfix Cyrus sasl configuration Mi 26. Aug 07:43:47 CEST 2009 version: 1.0.2 mode: server-side SMTP AUTH -- basics -- Postfix: 2.3.3 System: CentOS release 5.3 (Final) -- smtpd is linked to -- libsasl2.so.2 = /usr/lib64/libsasl2.so.2 (0x2b0ffbdee000) -- active SMTP AUTH and TLS parameters for smtpd -- broken_sasl_auth_clients = yes smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = mail smtpd_sasl_security_options = noanonymous -- listing of /usr/lib64/sasl2 -- insgesamt 2916 drwxr-xr-x 2 root root 4096 26. Aug 07:34 . drwxr-xr-x 52 root root 20480 26. Aug 00:32 .. -rwxr-xr-x 1 root root890 7. Jan 2007 libanonymous.la -rwxr-xr-x 1 root root 15880 7. Jan 2007 libanonymous.so -rwxr-xr-x 1 root root 15880 7. Jan 2007 libanonymous.so.2 -rwxr-xr-x 1 root root 15880 7. Jan 2007 libanonymous.so.2.0.22 -rwxr-xr-x 1 root root862 7. Jan 2007 liblogin.la -rwxr-xr-x 1 root root 16480 7. Jan 2007 liblogin.so -rwxr-xr-x 1 root root 16480 7. Jan 2007 liblogin.so.2 -rwxr-xr-x 1 root root 16480 7. Jan 2007 liblogin.so.2.0.22 -rwxr-xr-x 1 root root862 7. Jan 2007 libplain.la -rwxr-xr-x 1 root root 16448 7. Jan 2007 libplain.so -rwxr-xr-x 1 root root 16448 7. Jan 2007 libplain.so.2 -rwxr-xr-x 1 root root 16448 7. Jan 2007 libplain.so.2.0.22 -rwxr-xr-x 1 root root936 7. Jan 2007 libsasldb.la -rwxr-xr-x 1 root root 892920 7. Jan 2007 libsasldb.so -rwxr-xr-x 1 root root 892920 7. Jan 2007 libsasldb.so.2 -rwxr-xr-x 1 root root 892920 7. Jan 2007 libsasldb.so.2.0.22 -rw-r--r-- 1 root root167 26. Aug 07:34 smtpd.conf -- listing of /usr/lib/sasl2 -- insgesamt 2912 drwxr-xr-x 2 root root 4096 26. Aug 07:41 . drwxr-xr-x 30 root root 12288 26. Aug 00:33 .. -rwxr-xr-x 1 root root884 7. Jan 2007 libanonymous.la -rwxr-xr-x 1 root root 14372 7. Jan 2007 libanonymous.so -rwxr-xr-x 1 root root 14372 7. Jan 2007 libanonymous.so.2 -rwxr-xr-x 1 root root 14372 7. Jan 2007 libanonymous.so.2.0.22 -rwxr-xr-x 1 root root856 7. Jan 2007 liblogin.la -rwxr-xr-x 1 root root 14752 7. Jan 2007 liblogin.so -rwxr-xr-x 1 root root 14752 7. Jan 2007 liblogin.so.2 -rwxr-xr-x 1 root root 14752 7. Jan 2007 liblogin.so.2.0.22 -rwxr-xr-x 1 root root856 7. Jan 2007 libplain.la -rwxr-xr-x 1 root root 14848 7. Jan 2007 libplain.so -rwxr-xr-x 1 root root 14848 7. Jan 2007 libplain.so.2 -rwxr-xr-x 1 root root 14848 7. Jan 2007 libplain.so.2.0.22 -rwxr-xr-x 1 root root930 7. Jan 2007 libsasldb.la -rwxr-xr-x 1 root root 905200 7. Jan 2007 libsasldb.so -rwxr-xr-x 1 root root 905200 7. Jan 2007 libsasldb.so.2 -rwxr-xr-x 1 root root 905200 7. Jan 2007 libsasldb.so.2.0.22 -- listing of /etc/sasl2 -- insgesamt 24 drwxr-xr-x 2 root root 4096 26. Aug 07:36 . drwxr-xr-x 85 root root 12288 26. Aug 07:38 .. -- content of /usr/lib64/sasl2/smtpd.conf -- auto_transition: true pwcheck_method: auxprop saslauthd_version: 2 auxprop_plugin: sasldb allowanonymouslogin: 0 allowplaintext: 1 mech_list: PLAIN LOGIN log_level: 3 -- active services
Re: [CentOS-virt] centos 4.7 / kvm
Michael Kress wrote:
I'm trying to install centos-4.7 under kvm (for legacy reasons). I can't
get the beast installed, it crashes (see output below).
I'm using:
qemu 0.9.1
kvm-72
libvirt-0.4.6
kernel 2.6.26
What can I do in order to get the installation being done?
The host is a x86_64 machine (debian5).
...
8011ea9c{setup_apic_nmi_watchdog+47}
...
Hi, just to let you know, I found out myself, have to add the following
kernel parameter:
nmi_watchdog=0
Can anybody judge if this has severe consequences or is there a chance
that the machine could run stable as a plain web server?
Regards
Michael
--
Michael Kress, kr...@hal.saar.de
http://www.michael-kress.de / http://kress.net
P E N G U I N S A R E C O O L
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS] kvm, CentOS as guest / recommendations needed
Hello, I'm still searching for the ideal solution for Matryoshka-ing CentOS, i.e. using it as a guest under qemu/kvm. Given the fact that I'm a victim of this bug http://bugs.centos.org/view.php?id=2912 (5.2 host/5.2 guest) I'm stuck a little bit, so I tried different debian variants as hosts: sid unstable: ok proxmox VE: ok intrepid ibex (8.10): ok hardy heron (8.04): not ok Using an intel-vt capable dual cpu server / x86_64 arc, with the above effect, what would you recommend to me as a host OS if I wanted to run CentOS 4.x/5.x and debian guests with kvm only? I'd like to administer the whole thing with virsh. TIA, regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Crash with qemu: 5.2 host and 5.2 guest
I wrote: Adding the following to the things I tried without success: * installed the kernel-xen from http://people.redhat.com/dzickus/el5/128.el5/x86_64/ Does this mean that both RHEL 5.3 and (thus) CentOS 5.3 won't ship a solution to my problem for now? Regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Crash with qemu: 5.2 host and 5.2 guest
Ralph Angenendt wrote: Here's what I already tried, all without success: * installed a minimal 5.1 * updated the 5.1 with yum update That should work. Only the 5.2 install kernel has those issues, current kernels (should) work. Unfortuantely that _doesn't_ work with a plain 5.1. Adding the following to the things I tried without success: * installed the kernel-xen from http://people.redhat.com/dzickus/el5/128.el5/x86_64/ * updated the minimal 5.1 installation to 5.2 with yum update and booted the 128 kernel from dzickus Regards Michael -- Michael Kress, kr...@hal.saar.de http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-virt] Crash with qemu install: 5.2 as host and 5.2 as guest
I wrote: ok, I did that, installed 5.1 I tried with 5.1 and I got that same fatal exception again Then I updated from the original 5.1's kernel-xen 2.6.18-53 to 2.6.18-92.1.18 still no luck, still the same error. now I don't know what else I can do. All I'm tryin is to get 5.2 running as a kvm/qemu guest. Now I even tried an non-updated 5.1 with this kernel-xen as a host system: http://people.centos.org/hughesjr/kernel/5/bz443853/x86_64/ Still no luck. Still getting that powernowk8_init guest kernel crash while installing. Maybe I made something wrong from ground up using the 5.2 x86_64 installation image. Under debian that worked, so it should work here as well. Now I tend to use debian a base and virtualize my systems there. It seems to be the only way that works for me (already tried that). But I'd prefer to use CentOS. So if you can help me, I'll be lucky. Otherwise I'll have to fight my way through using debian... (that's no menace ;-) ) Regards Michael ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Crash with qemu install: 5.2 as host and 5.2 as guest
Hello, Karanbir Singh wrote: no, it should be : install 5.1 yum update to latest released kernel in the main distro ok, I did that, installed 5.1 I tried with 5.1 and I got that same fatal exception again Then I updated from the original 5.1's kernel-xen 2.6.18-53 to 2.6.18-92.1.18 still no luck, still the same error. * reboot yes, to get the 2.6.18-92.1.18.el5 kernel; rest of the steps you mentioned are ignorable / local site policy driven, have no implications with the issue. Sounds reasonable, but no luck here. :-( Any further hints for me? TIA Michael -- Michael Kress, kr...@hal.saar.de http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Crash with qemu install: 5.2 as host and 5.2 as guest
Manuel Wolfshant wrote: Install a minimal 5.1 and update to a kernel post -92.1.6 Ok, just to understand it for myself: * install minimal 5.1 / do NOT yum update * install johnny's Kernel * reboot * uninstall older kernels (necessary?) * wait for 5.3 / do NOT yum update during that period * test with 5.3 live or rescue cd - if 5.2 guests run, then continue * yum update as soon as 5.3 is out and be happy with 5.3 * if 5.3 fails, reinstall 5.1 - the image files for the guests would be on another partition, so dom0 can be freshly installed. Is that the roadmap to follow in my case? What about security, staying for 2 or 3 months at an old release? IMHO it's not THAT severe, because my main work will take place within the guests and there it's possible to keep the software up to date. Therefore the dom0 would only have ssh, ftp and possibly vnc as running services, just the minimum to run guests. Regards Michael ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Crash with qemu install: 5.2 as host and 5.2 as guest
Manuel Wolfshant wrote: EIP: [c041041c] powernowk8_init+0x5e/0x1c2 SS:EST 0068:dfa47fa0 0Kernel panic - not syncing: Fatal exception Looks very much alike the known bug described at http://bugs.centos.org/view.php?id=2912 / https://bugzilla.redhat.com/show_bug.cgi?id=443853 and also listed at the end of http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.2#head-447967c60eb305ef2c5dbbc3f4e8b3c4c5170632 I just tried that kernel on dom0: http://people.centos.org/hughesjr/kernel/5/bz443853/x86_64/ (kernel-xen-2.6.18-92.1.6.el5.bz_pre53.x86_64.rpm) but the error still persists. What else could I do? Michael -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Crash with qemu install: 5.2 as host and 5.2 as guest
Hi, I'm trying to install a CentOS 5.2 guest with virt-manager/qemu on a CentOS 5.2 system (X86_x64, 3ware 9650SE, 2 x Intel VT capable xeon cpus, 8 GB) Unfortunately I'm getting a crash in the guest install process. Other systems are installing smoothely, even Windows xp, but the above combination won't install. What works, too: CentOS 5.2 xen unmodified (i.e. fully virtual) guest, but no luck with qemu. I already tried the kernel-xen kernel from centosplus. Have you got any idea? TIA Regards Michael PS: Here's the crash, I hope I typed everything right. ;-) (I didn't want to bother you with a gif). I couldn't get further up in order to grab more from the screen. Shift - PgUp doesn't work. -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Crash with qemu install: 5.2 as host and 5.2 as guest
Michael Kress schrieb:
PS: Here's the crash, I hope I typed everything right. ;-) (I didn't
want to bother you with a gif).
I couldn't get further up in order to grab more from the screen. Shift -
PgUp doesn't work.
Here's really the crash, sorry.
Modules linked in:
CPU:0
EIP:0060:[c041041c]Tainted: G SVLI
EFLAGS:0202 (2.6.18-92.el5 #1)
EIP is at powernowk8_init+0x5e/0x1c2
eax: ebx: ecx: 000e edx: 0020
esi: edi: c06242c3 ebp: esp: dfa47fa0
ds: 007bes: 007bss: 0068
Process swapper (pid: 1, ti=dfa47000 task=dfa46aa0 task.ti=dfa47000)
Stack: c071bbe4 c06ec5a8 c06e7fd8 c0404dee 0202
c06ec42b
c06ec42b
c0506c3b
Call Trace:
[c06ec5a8] init+0x17d/0x24a
[c0404dee] ret_from_fork+0x6/0x1c
[c06ec42b] init+0x0/0x24a
[c06ec42b] init+0x0/0x24a
[c0405c3b] kernel_thread_helper+0x7/0x10
===
Code: 83 3d 20 41 67 c0 01 75 40 83 3d 84 d4 76 c0 00 75 37 b8 01 00 00
00 bf c3
42 62 c0 e8 ba 12 19 00 b9 0f 00 00 00 89 c6 49 78 08 ac ae 75 08 84
c0 75 f5
31 c0 eb 04 19 c0 0c 01 85 c0 75 0a c7
EIP: [c041041c] powernowk8_init+0x5e/0x1c2 SS:EST 0068:dfa47fa0
0Kernel panic - not syncing: Fatal exception
--
Michael Kress, [EMAIL PROTECTED]
http://www.michael-kress.de / http://kress.net
P E N G U I N S A R E C O O L
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Crash with qemu install: 5.2 as host and 5.2 as guest
Manuel Wolfshant wrote: ... EIP: [c041041c] powernowk8_init+0x5e/0x1c2 SS:EST 0068:dfa47fa0 0Kernel panic - not syncing: Fatal exception Looks very much alike the known bug described at http://bugs.centos.org/view.php?id=2912 / https://bugzilla.redhat.com/show_bug.cgi?id=443853 and also listed at the end of http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.2#head-447967c60eb305ef2c5dbbc3f4e8b3c4c5170632 It does, thanx, but how could the Johnny's Kernel from http://people.centos.org/hughesjr/kernel/5/bz443853/x86_64/ be used in a production environment? I mean, would I receive the regular kernel updates or would I always be stuck with that particular kernel version/binary? Regards Michael -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS] Centos 5.2 install problem
nate wrote: Hi, I'm trying a fresh install on a x86_64 (Supermicro X7dbe, 2xIntel Xeon X5450, 8 GB, 3WARE 9650SE-8LPML, 3 disks in RAID 5). The format takes quite long (2,7 TB), that seems to be normal, but then the first boot will not take place, instead the system loops. Any hints? Try again using a volume that is less than 2TB in size and see if it makes a difference? Just found in the 3ware manual: Even though the Linux 2.6 kernel supports partitions larger than 2 TB, the installers for SuSE and Redhat do not. Turn auto-carving on to prevent the installation from failing. Well, it's actually not the installer, but anyways, I'll give it a try and then give you a feedback! I don't really need partitions 2TB. Regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 5.2 install problem (SOLVED)
Hi, Michael Kress wrote: Try again using a volume that is less than 2TB in size and see if it makes a difference? Just found in the 3ware manual: Even though the Linux 2.6 kernel supports partitions larger than 2 TB, the installers for SuSE and Redhat do not. Turn auto-carving on to prevent the installation from failing. Well, it's actually not the installer, but anyways, I'll give it a try and then give you a feedback! I don't really need partitions 2TB. That's exactly how I just solved the issue - in the 3ware BIOS I defined a bootable device of 50GB for the base system and the rest was carved by auto-carving into chunks of 1024 GB. Works like a charm! Thanks for your hints! cu Michael -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Centos 5.2 install problem
Hi, I'm trying a fresh install on a x86_64 (Supermicro X7dbe, 2xIntel Xeon X5450, 8 GB, 3WARE 9650SE-8LPML, 3 disks in RAID 5). The format takes quite long (2,7 TB), that seems to be normal, but then the first boot will not take place, instead the system loops. Any hints? The message follows: Regards Michael Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] xfs on 5.2 (live cd + dvd)
Brent L. Bates wrote: As far as I'm concerned, XFS is the ONLY file system to use, period. If you care about not only performance, but also reliability, use XFS. I can confirm this, I had quite a few power line cuts and xfs always had mercy upon me. XFS compiled into kernel support isn't needed any more since 4.x. It is now in modules. On the Scientific Linux group, the person doing the 4.x Live CD/DVD added XFS support at one point, after I asked him about it. I do not know if he has made that standard now or not. So can I consider the xfs module implementation as being well tested and stable? Red Hat strips out XFS support from everything they do, so that makes things harder to do. I guess they do not like competition from SGI and do their best to discourage XFS use. Some Scientific Linux and CentOS people try to put it back in to some extent. I've had to create my own DVD's with full XFS support, including fresh full installs of only XFS file systems. Also included XFS support in rescue mode. I did that for 4.x. I didn't do it completely right and I haven't had a chance to try it again for 5.x. I really need to do that, but just never have the time to get it done. I wish someone else with more experience doing these things would do it. Greetings Michael -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] xfs on 5.2 (live cd + dvd)
Hello, I'm planning a server migration and being able to mount xfs file systems with the live cd would be a cruical feature. So before I download and try ... can anyone tell me whether the xfs is included in the 5.2 live cd? Later on I'm planning to install a new system with xen, 3ware 9550SX-4LP and xfs. The xen domains are of course located on xfs partitions. Do these features come with the standard dvd or do I have to build a custom kernel for that? Under centos-4.5 I chose xfs for performance reasons. With 5.2, is it still the fs of choice when it comes to performance or do you have better recommendations? (It will be a combined web and mail server with moderate traffic, i.e. not t much but not tooo little). Thanks in advance Regards Michael -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] xfs on 5.2 (live cd + dvd)
Johnny Hughes wrote: There are xfs modules and tools for centos in centos-extras ... so you can install them for the main kernel. Ah, that's right, it's the centosplus repo that contains that stuff. At least I know now that I can use standard means that are really updateable via 'yum update' and it's only a matter of a) enabling the repo centosplus, b) installing the kernel, c) rebooting and that's it. Cool. No objections to using the centosplus kernel in production environments? Under centos-4.5 I chose xfs for performance reasons. With 5.2, is it still the fs of choice when it comes to performance or do you have better recommendations? (It will be a combined web and mail server with moderate traffic, i.e. not t much but not tooo little). XFS is not supported by Red Hat ... and it does not recover from loss of power very well. The only way I would recommend XFS is if your have tried to run it on ext3 and it will not work without the performance increase you can get with XFS. (All the performance in the world does not matter if you loose your partition on a loss of power). Indeed, I already had some poweroffs and I think I can be lucky that my 3ware 9550SX-4LP has a cache battery. Knock-on-wood, there wasn't any severe catastrophe yet. Another question: Can I also find 'quota' in the standard kernel? That would make the thing perfect. :) Thanx for your answers Michael -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Re: dovecot fails to start at boot, but starts manually
Kenneth Porter schrieb: Ah, good possibility. Dovecot starts at priority 65, while saslauthd starts at 95. Shouldn't this only be a problem once someone attempts a login? Perhaps it's a Dovecot bug. My mail related stuff looks and works like this: lrwxrwxrwx 1 root root 17 Sep 18 2007 S65dovecot - ../init.d/dovecot lrwxrwxrwx 1 root root 17 Sep 18 2007 S80postfix - ../init.d/postfix lrwxrwxrwx 1 root root 22 Sep 18 2007 S80spamassassin - ../init.d/spamassassin lrwxrwxrwx 1 root root 19 Sep 18 2007 S95saslauthd - ../init.d/saslauthd lrwxrwxrwx 1 root root 25 Sep 18 2007 S99pop-before-smtp - ../init.d/pop-before-smtp But, I don't use mysql for storing any information. Greetings - Michael -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] dovecot fails to start at boot, but starts manually
Kenneth Porter wrote:
[EMAIL PROTECTED] ~]$ chkconfig --list dovecot
dovecot 0:off 1:off 2:off 3:on4:on5:on6:off
[EMAIL PROTECTED] ~]$ runlevel
N 3
despite that which seems to be correct, can you please post the output
of the following?
find /etc/rc* -name \*dovecot\* -exec ls -l \{\} \;
ciao - Michael
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] concat mount
Hi, I've got a buffalo 1TB DriveStation run in RAID 1 mode, i.e. 500G space available, but that beast is preformatted in vfat. Buffalo doesn't recommend to run it as ext2/ext3, so I mount a vfat drive wich has the limitations no symlinks, no uids, no gids, etc.. As I just want to use the DriveStation as a backup target, I did the following: I created files of 4G size with 'dd if=/dev/zero of=x01-backup.ext3 bs=1G count=4' (as 4GB is the maximum file size under vfat) and formatted them as ext3. I can mount them and work with them, no prob. Now I'd like to have my 25 files of 4GB file size each coherently mounted as one 100G drive. Is this possible? Must be something like Raid 0. TIA Michael -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] hosting panel
Hi there, what's your favorite (OS) hosting panel for centos5 ? What's most interesting for me is the usability by others i.e. users who don't know the tool very much, so it has to be very simple. Second is of course security. Greetings TIA Michael -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] migration considerations
Hi, I've got a 3ware 9550SX-4LP on a dual xeon 3.6GHz machine (no HVM possible). 4 SATA-HDs in RAID 5 installed. xen 3.0.3 with centos-4.4 as xen0. centos-4.4 is also installed on the numerous xenUs. The xenUs are installed in LVs which are formatted as xfs. Now I'd like to move over to centos 5.0 This is what I thought to be good as an upgrade procedure: 1) install a xen0 to a (bootable) USB hard disk this allows me to go back to my old configuration as soon as I encounter irresolvable probs 2) mount xenU-partitions from xen0 and put modules from the centos5-supplied kernel in there with this test I also test if the 3w_9xxx driver runs smoothly, I'll try bonnie++. 3) run xenUs and test them (Will they run and work?) 4) if all runs good, install xen0 over the old xen0, make backup before. My particular question here is: As it's important to have the 3w_9xxx driver properly loaded with this step, is there anything special I shouldn't forget here? All this shouldn't take me more than 2 hours. What's your opinion? Any more hints? Thanks Michael -- Michael Kress, [EMAIL PROTECTED] http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
