A bizarre problem in the boot scripts
Hi, I have a problem with a Dell poweredge 1800. My box has the Sata Raid controller from Dell and the linux support is on the recent kernels >2.6.10 and >2.4.27, I think ...at least, the sarge cd inst doesn't recognize the controller and the hds. I installed a Sarge and configured the raid system and put a 2.6.12 from testing (some months ago). More or less, all was working like a charm during this weeks. Howeber, I had big electrify cut and the server was poweroff suddenly. My problems began then. Although I did all the fsck tests and no problem, the system when reboots stop in some point of the initscripts, after mount all the partitions without any error. After many tests and no success and installed a installed a 2.6.16 from backports but nothing was solved. I'm really desperately because I really don't know how to solve this issue. The only way that I have to boot is to boot from a cd, comment the /usr partition on the fstab, reboot the box, then an error on the rcS scripts occurs, but continues. Log in to the box, mount the /usr partition, an do a rc 2, and then all is ok. I'm not a senior in the system administration but I understand that the boot procedure begins to execute all the scripts (in alphabetically order SXX) on the /etc/rcS.d/ directory and after, depending on the inittab mode, goes to the /etc/rcX.d/ directory and executes the rest of the scripts. Is this correct this explication? Otherwise, I would like to ask how I can know what is happens? I have modified almost all the boot scripts putting flags saying echo "I' doing this .." and my box is hanged in the bootmisc.sh script. There's a deadlock in this point, in the bootclean mountall but I don't understand what is happens. I don't know if is about the udev of the > 2.6.12 kernels and the mountvirtfs, or what. I really have NO idea. Please, could someone tell me at least how can I try to find the dammed problem? Thank's in advance, Leo Pd please, CC to me, I'm not in this list :-( -- -- Linux User 152692 PGP: 0xF944807E Catalonia pgpa6Jwdi0uxl.pgp Description: PGP signature
A bizarre problem in the boot scripts
Hi, I have a problem with a Dell poweredge 1800. My box has the Sata Raid controller from Dell and the linux support is on the recent kernels >2.6.10 and >2.4.27, I think ...at least, the sarge cd inst doesn't recognize the controller and the hds. I installed a Sarge and configured the raid system and put a 2.6.12 from testing (some months ago). More or less, all was working like a charm during this weeks. Howeber, I had big electrify cut and the server was poweroff suddenly. My problems began then. Although I did all the fsck tests and no problem, the system when reboots stop in some point of the initscripts, after mount all the partitions without any error. After many tests and no success and installed a installed a 2.6.16 from backports but nothing was solved. I'm really desperately because I really don't know how to solve this issue. The only way that I have to boot is to boot from a cd, comment the /usr partition on the fstab, reboot the box, then an error on the rcS scripts occurs, but continues. Log in to the box, mount the /usr partition, an do a rc 2, and then all is ok. I'm not a senior in the system administration but I understand that the boot procedure begins to execute all the scripts (in alphabetically order SXX) on the /etc/rcS.d/ directory and after, depending on the inittab mode, goes to the /etc/rcX.d/ directory and executes the rest of the scripts. Is this correct this explication? Otherwise, I would like to ask how I can know what is happens? I have modified almost all the boot scripts putting flags saying echo "I' doing this .." and my box is hanged in the bootmisc.sh script. There's a deadlock in this point, in the bootclean mountall but I don't understand what is happens. I don't know if is about the udev of the > 2.6.12 kernels and the mountvirtfs, or what. I really have NO idea. Please, could someone tell me at least how can I try to find the dammed problem? Thank's in advance, Leo Pd please, CC to me, I'm not in this list :-( -- -- Linux User 152692 PGP: 0xF944807E Catalonia pgpd1K2QcKnnm.pgp Description: PGP signature
Udev, hotplug dispatcher
Hi, I'm having a problem with the udev and I'm really lost. I had I box that I upgrade from stable to tesing/sid (I like very much kde 3.5 ...). However, I realized that after the upgrade I had I problem with the kernels 2.6.12 and 2.6.15. (also 2.6.8) When I rebooted the box, then the udev service cannot start and I have to do manually ctrl+c and when the boot is finished, then I can start the service. After some ideas and help from the debian-kde list [1] I finally decided to begin from zero and reinstall the complete box. I could install without any problems but if I update the kernel to the 2.6.12, then the udev is stopping again in the same point. And I say stopping, not doing a pause of 60 seconds... I have looked in google, list, etc and I really don't know how to solve this. I have found (in slackware list) that is a problem with the rules files that detect bas terminals, but no solutions. Please, could someone light me and give me some idea about this bizarre problem. Regards, Leo Pd please do a CC to me, I'm not in the list. [1] http://lists.debian.org/debian-kde/2006/01/msg00154.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Fetchmail + spamassassin + exim
Hi, some time ago I installed a little server at home to use it as firewall and mailserver. I got the mail using fetchmail, scanned with spamassassin and the delivered and filter with exim. Something that a lot of pages have explained. I'm using sarge in a P100 with 64Mb of ram. Little server!!!. In general, allworks quiet well, and also I can have mail directly. But sometimes (and now, every day) I have frozen messages, and I don't know why, because this frozen messages exim cannot delivered it to a local account!!. One typical log is: -- 1DwOmC-0003G3-4H-D This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] local delivery failed The following text was generated during the delivery attempt: -- [EMAIL PROTECTED] -- Exim version 4.50 uid=103 gid=103 pid=12497 D=fbb95cfd Berkeley DB: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003) Support for: iconv() IPv6 GnuTLS Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 changed uid/gid: forcing real = effective uid=0 gid=103 pid=12497 auxiliary group list: configuration file is /var/lib/exim4/config.autogenerated log selectors = 0ffc 00020800 trusted user admin user changed uid/gid: privilege not needed uid=103 gid=103 pid=12497 auxiliary group list: user name "" extracted from gecos field "" originator: uid=103 gid=103 login=Debian-exim name= sender address = NULL in hosts_connection_nolog? no (option unset) LOG: smtp_connection MAIN SMTP connection from Debian-exim smtp_setup_msg entered SMTP<< MAIL FROM:<[EMAIL PROTECTED]> SMTP<< RCPT TO:<[EMAIL PROTECTED]> SMTP<< DATA search_tidyup called LOG: lost_incoming_connection smtp_connection MAIN SMTP connection from Debian-exim lost while reading message data (header) Handling error in batched SMTP input An error was detected while processing a file of BSMTP input. The error message was: 421 Lost incoming connection The SMTP transaction started in line 0. The error was detected in line 3. 0 previous messages were successfully processed. The rest of the batch was abandoned. search_tidyup called Exim pid=12497 terminating with rc=2 421 Lost incoming connection Transaction started in line 0 Error detected in line 3 -- I have found this error in one spamassassin bug report, but in teory is was solved by upstream one year ago. I don't understand what happens and I don't know if it's a bug in exim or spamassassin, so I don't know where to report it. Someone have some idea about what could I do? thank's in advance, Leo -- -- Linux User 152692 Catalonia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
