Re: [qmailtoaster] Upgrade Script
Dear Shubes, Thank you very much on your reply, I'll try to look on your URL link. So upgrading won't change my vpopmail users and domains right ..? Do the latest relesease of qmt stiil able to use my previous Mysql database of vpopmail .. and squirrelmail or i should modify certain changes on the mysql..?? Thank you , David J. - Original Message - From: Eric Shubes [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Friday, February 02, 2007 11:10 PM Subject: Re: [qmailtoaster] Upgrade Script David J. wrote: Dear All, Is it safe to use the upgrade script from http://www.qmailtoaster.com/info/upgrade.sh to upgrade my current qmailtoaster ..?? Does it keep my current configuration, domains, users, password and it's mails afterward..?? or there are things that I should do manually. Does it also update my current qmailtoaster packages to the latest ones..?? My current qmailtoaster packages are as follows : libdomainkeys-toaster-0.68-1.3.1 ezmlm-cgi-toaster-0.53.324-1.3.1 spamassassin-toaster-3.1.3-1.3.1 daemontools-toaster-0.76-1.3.1 autorespond-toaster-2.0.4-1.3.1 isoqlog-toaster-2.1-1.3.1 ucspi-tcp-toaster-0.88-1.3.1 qmail-pop3d-toaster-1.03-1.3.5 control-panel-toaster-0.5-1.3.1 qmailmrtg-toaster-4.2-1.3.1 ripmime-toaster-1.4.0.6-1.3.1 vpopmail-toaster-5.4.13-1.3.1 courier-authlib-toaster-0.58-1.3.1 ezmlm-toaster-0.53.324-1.3.1 maildrop-toaster-2.0.2-1.3.1 squirrelmail-toaster-1.4.7-1.3.2 simscan-toaster-1.2-1.3.1 courier-imap-toaster-4.1.1-1.3.2 maildrop-toaster-devel-2.0.2-1.3.1 vqadmin-toaster-2.3.4-1.3.2 qmail-toaster-1.03-1.3.5 qmailadmin-toaster-1.2.9-1.3.1 clamav-toaster-0.88.3-1.3.2 Need some info here. Highly appreciate your comment on this. Best Regards, David J. I wouldn't use it. I don't know if anyone's maintaining it or not. If not, then it won't work (it doesn't include libsrs2-toaster which is now required). I'd use qtp-newmodel. It's robust and simple. It'll upgrade your toaster to the latest ones including letting you install from devel if you want. There is nothing 'manual' to do. It handles everything, including stopping and restarting qmail at the appropriate points to minimize down time. See http://wiki.qmailtoaster.com/index.php/Upgrading for details. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script
David J. wrote: Dear Shubes, Thank you very much on your reply, I'll try to look on your URL link. So upgrading won't change my vpopmail users and domains right ..? Right. Do the latest relesease of qmt stiil able to use my previous Mysql database of vpopmail Right. There haven't been any database changes since 1.3.1, the release you're presently running. .. and squirrelmail or i should modify certain changes on the mysql..?? Everything in the mysql database remains intact, unchanged by the upgrade. The upgrade doesn't touch the database, and there haven't been any changes to the database since the version you're running, so the newer versions should work just fine with what your present database. I hope EE or Jake will chime in if this isn't correct. Thank you , David J. - Original Message - From: Eric Shubes [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Friday, February 02, 2007 11:10 PM Subject: Re: [qmailtoaster] Upgrade Script David J. wrote: Dear All, Is it safe to use the upgrade script from http://www.qmailtoaster.com/info/upgrade.sh to upgrade my current qmailtoaster ..?? Does it keep my current configuration, domains, users, password and it's mails afterward..?? or there are things that I should do manually. Does it also update my current qmailtoaster packages to the latest ones..?? My current qmailtoaster packages are as follows : libdomainkeys-toaster-0.68-1.3.1 ezmlm-cgi-toaster-0.53.324-1.3.1 spamassassin-toaster-3.1.3-1.3.1 daemontools-toaster-0.76-1.3.1 autorespond-toaster-2.0.4-1.3.1 isoqlog-toaster-2.1-1.3.1 ucspi-tcp-toaster-0.88-1.3.1 qmail-pop3d-toaster-1.03-1.3.5 control-panel-toaster-0.5-1.3.1 qmailmrtg-toaster-4.2-1.3.1 ripmime-toaster-1.4.0.6-1.3.1 vpopmail-toaster-5.4.13-1.3.1 courier-authlib-toaster-0.58-1.3.1 ezmlm-toaster-0.53.324-1.3.1 maildrop-toaster-2.0.2-1.3.1 squirrelmail-toaster-1.4.7-1.3.2 simscan-toaster-1.2-1.3.1 courier-imap-toaster-4.1.1-1.3.2 maildrop-toaster-devel-2.0.2-1.3.1 vqadmin-toaster-2.3.4-1.3.2 qmail-toaster-1.03-1.3.5 qmailadmin-toaster-1.2.9-1.3.1 clamav-toaster-0.88.3-1.3.2 Need some info here. Highly appreciate your comment on this. Best Regards, David J. I wouldn't use it. I don't know if anyone's maintaining it or not. If not, then it won't work (it doesn't include libsrs2-toaster which is now required). I'd use qtp-newmodel. It's robust and simple. It'll upgrade your toaster to the latest ones including letting you install from devel if you want. There is nothing 'manual' to do. It handles everything, including stopping and restarting qmail at the appropriate points to minimize down time. See http://wiki.qmailtoaster.com/index.php/Upgrading for details. -- -Eric 'shubes' -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script
Does the clamav pakage which are just released on the development pakage will be installed too..?? or should I wait until it releass on stable one ..?? Appreciate your amazing work on the qmt projects. Regards, David J. - Original Message - From: Eric Shubes [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Monday, February 05, 2007 10:43 AM Subject: Re: [qmailtoaster] Upgrade Script David J. wrote: Dear Shubes, Thank you very much on your reply, I'll try to look on your URL link. So upgrading won't change my vpopmail users and domains right ..? Right. Do the latest relesease of qmt stiil able to use my previous Mysql database of vpopmail Right. There haven't been any database changes since 1.3.1, the release you're presently running. .. and squirrelmail or i should modify certain changes on the mysql..?? Everything in the mysql database remains intact, unchanged by the upgrade. The upgrade doesn't touch the database, and there haven't been any changes to the database since the version you're running, so the newer versions should work just fine with what your present database. I hope EE or Jake will chime in if this isn't correct. Thank you , David J. - Original Message - From: Eric Shubes [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Friday, February 02, 2007 11:10 PM Subject: Re: [qmailtoaster] Upgrade Script David J. wrote: Dear All, Is it safe to use the upgrade script from http://www.qmailtoaster.com/info/upgrade.sh to upgrade my current qmailtoaster ..?? Does it keep my current configuration, domains, users, password and it's mails afterward..?? or there are things that I should do manually. Does it also update my current qmailtoaster packages to the latest ones..?? My current qmailtoaster packages are as follows : libdomainkeys-toaster-0.68-1.3.1 ezmlm-cgi-toaster-0.53.324-1.3.1 spamassassin-toaster-3.1.3-1.3.1 daemontools-toaster-0.76-1.3.1 autorespond-toaster-2.0.4-1.3.1 isoqlog-toaster-2.1-1.3.1 ucspi-tcp-toaster-0.88-1.3.1 qmail-pop3d-toaster-1.03-1.3.5 control-panel-toaster-0.5-1.3.1 qmailmrtg-toaster-4.2-1.3.1 ripmime-toaster-1.4.0.6-1.3.1 vpopmail-toaster-5.4.13-1.3.1 courier-authlib-toaster-0.58-1.3.1 ezmlm-toaster-0.53.324-1.3.1 maildrop-toaster-2.0.2-1.3.1 squirrelmail-toaster-1.4.7-1.3.2 simscan-toaster-1.2-1.3.1 courier-imap-toaster-4.1.1-1.3.2 maildrop-toaster-devel-2.0.2-1.3.1 vqadmin-toaster-2.3.4-1.3.2 qmail-toaster-1.03-1.3.5 qmailadmin-toaster-1.2.9-1.3.1 clamav-toaster-0.88.3-1.3.2 Need some info here. Highly appreciate your comment on this. Best Regards, David J. I wouldn't use it. I don't know if anyone's maintaining it or not. If not, then it won't work (it doesn't include libsrs2-toaster which is now required). I'd use qtp-newmodel. It's robust and simple. It'll upgrade your toaster to the latest ones including letting you install from devel if you want. There is nothing 'manual' to do. It handles everything, including stopping and restarting qmail at the appropriate points to minimize down time. See http://wiki.qmailtoaster.com/index.php/Upgrading for details. -- -Eric 'shubes' -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script
That's up to you. qtp-newmodel lets you pick from the devel site as well as the main site, if you choose to do so. (IMHO), the devel packages are historically pretty stable for the most part (EE does a great job!). However, if you're not very Linux savvy and you highly value stability and there's not a feature in development that you gotta have, you're probably best off upgrading only from the main site. That being said, the clamav package on the devel site is a rc3 version, meaning that it is the third release candidate of version 0.90. This is not yet a production release, so you might want to wait. I'm guessing that EE will roll it over to stable once the final 0.90 verion is released. David J. wrote: Does the clamav pakage which are just released on the development pakage will be installed too..?? or should I wait until it releass on stable one ..?? Appreciate your amazing work on the qmt projects. Regards, David J. - Original Message - From: Eric Shubes [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Monday, February 05, 2007 10:43 AM Subject: Re: [qmailtoaster] Upgrade Script David J. wrote: Dear Shubes, Thank you very much on your reply, I'll try to look on your URL link. So upgrading won't change my vpopmail users and domains right ..? Right. Do the latest relesease of qmt stiil able to use my previous Mysql database of vpopmail Right. There haven't been any database changes since 1.3.1, the release you're presently running. .. and squirrelmail or i should modify certain changes on the mysql..?? Everything in the mysql database remains intact, unchanged by the upgrade. The upgrade doesn't touch the database, and there haven't been any changes to the database since the version you're running, so the newer versions should work just fine with what your present database. I hope EE or Jake will chime in if this isn't correct. Thank you , David J. - Original Message - From: Eric Shubes [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Friday, February 02, 2007 11:10 PM Subject: Re: [qmailtoaster] Upgrade Script David J. wrote: Dear All, Is it safe to use the upgrade script from http://www.qmailtoaster.com/info/upgrade.sh to upgrade my current qmailtoaster ..?? Does it keep my current configuration, domains, users, password and it's mails afterward..?? or there are things that I should do manually. Does it also update my current qmailtoaster packages to the latest ones..?? My current qmailtoaster packages are as follows : libdomainkeys-toaster-0.68-1.3.1 ezmlm-cgi-toaster-0.53.324-1.3.1 spamassassin-toaster-3.1.3-1.3.1 daemontools-toaster-0.76-1.3.1 autorespond-toaster-2.0.4-1.3.1 isoqlog-toaster-2.1-1.3.1 ucspi-tcp-toaster-0.88-1.3.1 qmail-pop3d-toaster-1.03-1.3.5 control-panel-toaster-0.5-1.3.1 qmailmrtg-toaster-4.2-1.3.1 ripmime-toaster-1.4.0.6-1.3.1 vpopmail-toaster-5.4.13-1.3.1 courier-authlib-toaster-0.58-1.3.1 ezmlm-toaster-0.53.324-1.3.1 maildrop-toaster-2.0.2-1.3.1 squirrelmail-toaster-1.4.7-1.3.2 simscan-toaster-1.2-1.3.1 courier-imap-toaster-4.1.1-1.3.2 maildrop-toaster-devel-2.0.2-1.3.1 vqadmin-toaster-2.3.4-1.3.2 qmail-toaster-1.03-1.3.5 qmailadmin-toaster-1.2.9-1.3.1 clamav-toaster-0.88.3-1.3.2 Need some info here. Highly appreciate your comment on this. Best Regards, David J. I wouldn't use it. I don't know if anyone's maintaining it or not. If not, then it won't work (it doesn't include libsrs2-toaster which is now required). I'd use qtp-newmodel. It's robust and simple. It'll upgrade your toaster to the latest ones including letting you install from devel if you want. There is nothing 'manual' to do. It handles everything, including stopping and restarting qmail at the appropriate points to minimize down time. See http://wiki.qmailtoaster.com/index.php/Upgrading for details. -- -Eric 'shubes' -- -Eric 'shubes' -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script
David J. wrote: Dear All, Is it safe to use the upgrade script from http://www.qmailtoaster.com/info/upgrade.sh to upgrade my current qmailtoaster ..?? Does it keep my current configuration, domains, users, password and it's mails afterward..?? or there are things that I should do manually. Does it also update my current qmailtoaster packages to the latest ones..?? My current qmailtoaster packages are as follows : libdomainkeys-toaster-0.68-1.3.1 ezmlm-cgi-toaster-0.53.324-1.3.1 spamassassin-toaster-3.1.3-1.3.1 daemontools-toaster-0.76-1.3.1 autorespond-toaster-2.0.4-1.3.1 isoqlog-toaster-2.1-1.3.1 ucspi-tcp-toaster-0.88-1.3.1 qmail-pop3d-toaster-1.03-1.3.5 control-panel-toaster-0.5-1.3.1 qmailmrtg-toaster-4.2-1.3.1 ripmime-toaster-1.4.0.6-1.3.1 vpopmail-toaster-5.4.13-1.3.1 courier-authlib-toaster-0.58-1.3.1 ezmlm-toaster-0.53.324-1.3.1 maildrop-toaster-2.0.2-1.3.1 squirrelmail-toaster-1.4.7-1.3.2 simscan-toaster-1.2-1.3.1 courier-imap-toaster-4.1.1-1.3.2 maildrop-toaster-devel-2.0.2-1.3.1 vqadmin-toaster-2.3.4-1.3.2 qmail-toaster-1.03-1.3.5 qmailadmin-toaster-1.2.9-1.3.1 clamav-toaster-0.88.3-1.3.2 Need some info here. Highly appreciate your comment on this. Best Regards, David J. I wouldn't use it. I don't know if anyone's maintaining it or not. If not, then it won't work (it doesn't include libsrs2-toaster which is now required). I'd use qtp-newmodel. It's robust and simple. It'll upgrade your toaster to the latest ones including letting you install from devel if you want. There is nothing 'manual' to do. It handles everything, including stopping and restarting qmail at the appropriate points to minimize down time. See http://wiki.qmailtoaster.com/index.php/Upgrading for details. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script
Eric Shubes wrote: I wouldn't use it. I don't know if anyone's maintaining it or not. If not, then it won't work (it doesn't include libsrs2-toaster which is now required). I'd use qtp-newmodel. It's robust and simple. It'll upgrade your toaster to the latest ones including letting you install from devel if you want. There is nothing 'manual' to do. It handles everything, including stopping and restarting qmail at the appropriate points to minimize down time. See http://wiki.qmailtoaster.com/index.php/Upgrading for details. That said I can not get qtp-newmodel to upgrade my toasters. It fails on the djbdns installation with conflicts. I believe this was covered in someone else's post but I do not believe the script has been updated to resolve this issue. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script
Ed Morrison wrote: Eric Shubes wrote: I wouldn't use it. I don't know if anyone's maintaining it or not. If not, then it won't work (it doesn't include libsrs2-toaster which is now required). I'd use qtp-newmodel. It's robust and simple. It'll upgrade your toaster to the latest ones including letting you install from devel if you want. There is nothing 'manual' to do. It handles everything, including stopping and restarting qmail at the appropriate points to minimize down time. See http://wiki.qmailtoaster.com/index.php/Upgrading for details. That said I can not get qtp-newmodel to upgrade my toasters. It fails on the djbdns installation with conflicts. I believe this was covered in someone else's post but I do not believe the script has been updated to resolve this issue. This is true. I'm working on that, but the fix is not trivial. In the meantime, simply do not select djbdns for upgrading, and qtp-newmodel will upgrade the rest of the packages just fine (AFAIK). djbdns has not functionally changed. It only has a new release number to reflect the FC6 compatibility. Please let me know if you have any probem. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script
Eric Shubes wrote: This is true. I'm working on that, but the fix is not trivial. In the meantime, simply do not select djbdns for upgrading, and qtp-newmodel will upgrade the rest of the packages just fine (AFAIK). djbdns has not functionally changed. It only has a new release number to reflect the FC6 compatibility. Please let me know if you have any probem. Sorry Eric, that was not a criticism in any manner. I just wanted to put the reminder out there and I didn't realize you were the person working on it. I do want to thank all that work so hard on this project. Your dedication is admirable and I appreciate your efforts greatly. Ed - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script
Ed Morrison wrote: Eric Shubes wrote: This is true. I'm working on that, but the fix is not trivial. In the meantime, simply do not select djbdns for upgrading, and qtp-newmodel will upgrade the rest of the packages just fine (AFAIK). djbdns has not functionally changed. It only has a new release number to reflect the FC6 compatibility. Please let me know if you have any probem. Sorry Eric, that was not a criticism in any manner. I just wanted to put the reminder out there and I didn't realize you were the person working on it. I do want to thank all that work so hard on this project. Your dedication is admirable and I appreciate your efforts greatly. Ed No problem, Ed. I too want everyone to be aware of what's going on. FWIW, I began installing Trac today on svn.shubes.net. We'll see if/how that might help with keeping folks informed (among other things). -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script
Shelly wrote: Im thinking of using the QmailToaster Plus to upgrade my old (read 18 months) Toaster install - Which version(s)? # rpm -qa | grep toaster Im not sure if its been covered, but this will continue to run the current qmail setup, build the new version in the background Pretty much, just not in background in the technical sense. It builds the new version (and the binary rpms needed to do the upgrade) in the sandbox. This happens while the present system continues to operate as normal. and then copy over Sort of. It copies the new binary rpms out of the sandbox (the sandbox is disposable), backs up configuration files, stops qmail, upgrades the existing toaster with a single 'rpm -Uvh' command using all the new binary rpms, restores the configuration files (if so chosen - the script lets you choose to do the restores or not), and starts the new qmail toaster. and restart to run the new version of the toaster with all the settings from the previous version? In a nutshell, yes. Is there anything I need to manually back up? There shouldn't be. Backups are always a good thing though. You may want to run qtp-backup beforehand as a safety measure. Also, everything that the qtp-newmodel script backs up is retained in the /usr/src/qtp-upgrade/backup directory, just in case you need to manually restore something, or for future reference. And also - will this copy all existing email in a users directory? Thanks All existing email is untouched, as are queues. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script
I've tried to upgrade by upgrade.sh, it's very straight forward. The only concern is that you may have to take down your qmail for a while and wait for all packages to be rebuilt. Take a look about qmail-toaster plus: http://wiki.qmailtoaster.com/index.php/QmailToaster-Plusand http://wiki.qmailtoaster.com/index.php/Upgrading. It provides you a sandbox to play with before you really apply the changes to the production system. Best regards, Bill On 11/13/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: How safe is it to run the upgrade script on a production server.I wouldto upgrade to the latest packages but I'm a little nervous.Thanks. -QmailToaster hosted by: VR Hosted http://www.vr.org- To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script
[EMAIL PROTECTED] wrote: How safe is it to run the upgrade script on a production server. I would to upgrade to the latest packages but I'm a little nervous. Thanks. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I just did it last night no problems. Actually with the new qtp-newmodel upgrade is about as safe as any upgrade can be. It creates a sandbox and compiles everything in it so that your mail servers stay up until everything is compile, then it just copies over the files and restarts the services.
Re: [qmailtoaster] upgrade script
I also ran the qtp-newmodel upgrade using qtp-menu on my production server and it worked like a charm.Ryan Gibbons [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote:How safe is it to run the upgrade script on a production server. I wouldto upgrade to the latest packages but I'm a little nervous. Thanks.- QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I just did it last night no problems. Actually with the new qtp-newmodel upgrade is about as safe as any upgrade can be. It creates a sandbox and compiles everything in it so that your mail servers stay up until everything is compile, then it just copies over the files and restarts the services. Francisco "Paco" Peralta
RE: [qmailtoaster] upgrade script
Certainy it should work great, but i don't like unassisted updates. I don't want being woke up at 3 o'clock because out alert system a trivial problem stopped the corporative mail system. I thinks is good idea to retrieve source rpms, build the binary rpm's nightly, and wait for the sysadmin to tell to install in an apropriate moment (if everything runs ok, it will take less than 2 minutes, anyway). Just my opinion *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | David Sanchez Martin | [EMAIL PROTECTED] Administrador de Sistemas| http://www.e2000.es http://www.e2000.es/ E2000 Nuevas Tecnologias | | E2000 Organizacion de Empresarios|Tel : +34 902 19 61 77 Mediadores de Seguros | | Agustin Bravo Esquina Calle C| 33120 Pravia Asturias Spain | | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* De: Francisco Paco Peralta [mailto:[EMAIL PROTECTED] Enviado el: lunes, 13 de noviembre de 2006 17:58 Para: qmailtoaster-list@qmailtoaster.com Asunto: Re: [qmailtoaster] upgrade script I also ran the qtp-newmodel upgrade using qtp-menu on my production server and it worked like a charm. Ryan Gibbons [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: How safe is it to run the upgrade script on a production server. I would to upgrade to the latest packages but I'm a little nervous. Thanks. - QmailToaster hosted by: VR Hosted http://www.vr.org http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I just did it last night no problems. Actually with the new qtp-newmodel upgrade is about as safe as any upgrade can be. It creates a sandbox and compiles everything in it so that your mail servers stay up until everything is compile, then it just copies over the files and restarts the services. Francisco Paco Peralta BEGIN:VCARD VERSION:2.1 N:Sánchez Martín;David FN:[EMAIL PROTECTED] ([EMAIL PROTECTED]) ORG:E2000 Financial Investments, S.A.;Centro de Nuevas Tecnologías TITLE:Administrador de Sistemas TEL;WORK;VOICE:902196177 ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;Agust=EDn Bravo 17 2=BA B=0D=0A33120 PRAVIA;Asturias;;;Espa=F1a LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Agust=EDn Bravo 17 2=BA B=0D=0A33120 PRAVIA=0D=0AAsturias=0D=0AEspa=F1a URL;WORK:http://www.e2000.es EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20060705T152542Z END:VCARD - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script
Certainy, out alert system, I thinks BTW i'm not in drugs, just typed uncarefully :-D -Mensaje original- De: David Sánchez Martín [mailto:[EMAIL PROTECTED] Enviado el: lunes, 13 de noviembre de 2006 18:11 Para: qmailtoaster-list@qmailtoaster.com Asunto: RE: [qmailtoaster] upgrade script Certainy it should work great, but i don't like unassisted updates. I don't want being woke up at 3 o'clock because out alert system a trivial problem stopped the corporative mail system. I thinks is good idea to retrieve source rpms, build the binary rpm's nightly, and wait for the sysadmin to tell to install in an apropriate moment (if everything runs ok, it will take less than 2 minutes, anyway). Just my opinion *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | David Sanchez Martin | [EMAIL PROTECTED] Administrador de Sistemas| http://www.e2000.es http://www.e2000.es/ E2000 Nuevas Tecnologias | | E2000 Organizacion de Empresarios|Tel : +34 902 19 61 77 Mediadores de Seguros | | Agustin Bravo Esquina Calle C| 33120 Pravia Asturias Spain | | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* De: Francisco Paco Peralta [mailto:[EMAIL PROTECTED] Enviado el: lunes, 13 de noviembre de 2006 17:58 Para: qmailtoaster-list@qmailtoaster.com Asunto: Re: [qmailtoaster] upgrade script I also ran the qtp-newmodel upgrade using qtp-menu on my production server and it worked like a charm. Ryan Gibbons [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: How safe is it to run the upgrade script on a production server. I would to upgrade to the latest packages but I'm a little nervous. Thanks. - QmailToaster hosted by: VR Hosted http://www.vr.org http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I just did it last night no problems. Actually with the new qtp-newmodel upgrade is about as safe as any upgrade can be. It creates a sandbox and compiles everything in it so that your mail servers stay up until everything is compile, then it just copies over the files and restarts the services. Francisco Paco Peralta - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script
I totally agree, David. That's why I wrote the qtp-newmodel scripts to do just that! They do everything except the update ahead of time in the sandbox, so the production server is not affected. Then at the appropriate moment, the sysadmin can re-run the script, automatically skipping over everything that's already been done, and apply the update (which is done with a single rpm -Uvh command btw). You might want to give it a try! ;) David Sánchez Martín wrote: Certainy it should work great, but i don't like unassisted updates. I don't want being woke up at 3 o'clock because out alert system a trivial problem stopped the corporative mail system. I thinks is good idea to retrieve source rpms, build the binary rpm's nightly, and wait for the sysadmin to tell to install in an apropriate moment (if everything runs ok, it will take less than 2 minutes, anyway). Just my opinion *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | David Sanchez Martin | [EMAIL PROTECTED] Administrador de Sistemas| http://www.e2000.es http://www.e2000.es/ E2000 Nuevas Tecnologias | | E2000 Organizacion de Empresarios|Tel : +34 902 19 61 77 Mediadores de Seguros | | Agustin Bravo Esquina Calle C| 33120 Pravia Asturias Spain | | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* De: Francisco Paco Peralta [mailto:[EMAIL PROTECTED] Enviado el: lunes, 13 de noviembre de 2006 17:58 Para: qmailtoaster-list@qmailtoaster.com Asunto: Re: [qmailtoaster] upgrade script I also ran the qtp-newmodel upgrade using qtp-menu on my production server and it worked like a charm. Ryan Gibbons [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: How safe is it to run the upgrade script on a production server. I would to upgrade to the latest packages but I'm a little nervous. Thanks. - QmailToaster hosted by: VR Hosted http://www.vr.org http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I just did it last night no problems. Actually with the new qtp-newmodel upgrade is about as safe as any upgrade can be. It creates a sandbox and compiles everything in it so that your mail servers stay up until everything is compile, then it just copies over the files and restarts the services. Francisco Paco Peralta -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script
Great!, i was totally misunderstood :-) I'll give it a try (or two :-P ), I promise. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | David Sanchez Martin | [EMAIL PROTECTED] Administrador de Sistemas| http://www.e2000.es E2000 Nuevas Tecnologias | | E2000 Organizacion de Empresarios|Tel : +34 902 19 61 77 Mediadores de Seguros | | Agustin Bravo Esquina Calle C| 33120 Pravia Asturias Spain | | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* -Mensaje original- De: Eric Shubes [mailto:[EMAIL PROTECTED] Enviado el: lunes, 13 de noviembre de 2006 18:22 Para: qmailtoaster-list@qmailtoaster.com Asunto: Re: [qmailtoaster] upgrade script I totally agree, David. That's why I wrote the qtp-newmodel scripts to do just that! They do everything except the update ahead of time in the sandbox, so the production server is not affected. Then at the appropriate moment, the sysadmin can re-run the script, automatically skipping over everything that's already been done, and apply the update (which is done with a single rpm -Uvh command btw). You might want to give it a try! ;) David Sánchez Martín wrote: Certainy it should work great, but i don't like unassisted updates. I don't want being woke up at 3 o'clock because out alert system a trivial problem stopped the corporative mail system. I thinks is good idea to retrieve source rpms, build the binary rpm's nightly, and wait for the sysadmin to tell to install in an apropriate moment (if everything runs ok, it will take less than 2 minutes, anyway). Just my opinion *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | David Sanchez Martin | [EMAIL PROTECTED] Administrador de Sistemas| http://www.e2000.es http://www.e2000.es/ E2000 Nuevas Tecnologias | | E2000 Organizacion de Empresarios|Tel : +34 902 19 61 77 Mediadores de Seguros | | Agustin Bravo Esquina Calle C| 33120 Pravia Asturias Spain | | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* De: Francisco Paco Peralta [mailto:[EMAIL PROTECTED] Enviado el: lunes, 13 de noviembre de 2006 17:58 Para: qmailtoaster-list@qmailtoaster.com Asunto: Re: [qmailtoaster] upgrade script I also ran the qtp-newmodel upgrade using qtp-menu on my production server and it worked like a charm. Ryan Gibbons [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: How safe is it to run the upgrade script on a production server. I would to upgrade to the latest packages but I'm a little nervous. Thanks. - QmailToaster hosted by: VR Hosted http://www.vr.org http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I just did it last night no problems. Actually with the new qtp-newmodel upgrade is about as safe as any upgrade can be. It creates a sandbox and compiles everything in it so that your mail servers stay up until everything is compile, then it just copies over the files and restarts the services. Francisco Paco Peralta -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] BEGIN:VCARD VERSION:2.1 N:Sánchez Martín;David FN:[EMAIL PROTECTED] ([EMAIL PROTECTED]) ORG:E2000 Financial Investments, S.A.;Centro de Nuevas Tecnologías TITLE:Administrador de Sistemas TEL;WORK;VOICE:902196177 ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;Agust=EDn Bravo 17 2=BA B=0D=0A33120 PRAVIA;Asturias;;;Espa=F1a LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Agust=EDn Bravo 17 2=BA B=0D=0A33120 PRAVIA=0D=0AAsturias=0D=0AEspa=F1a URL;WORK:http://www.e2000.es EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20060705T152542Z END:VCARD - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
Re: [qmailtoaster] upgrade script
I have noted that the restore processing in the script could use some enhancing. Presently, it simply allows you to restore the configuration files or bypass restoration. Bryan, if you selected to do the restore, then this is a bug. If you chose not to restore, then this is as it should be. Did you select to do the restore? If you did, I need to fix the script. Bryan Daley wrote: Just done my server and all is ok apart from a default tcp.smtp being installed which was no big issue as it backed up the original. [EMAIL PROTECTED] wrote: How safe is it to run the upgrade script on a production server. I would to upgrade to the latest packages but I'm a little nervous. Thanks. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script
Maybe doing in drugs is worth trying, maybe it imporove the carefullness. ;P Q On Mon, 13 Nov 2006 18:15:16 +0100, David Sánchez Martín wrote: Certainy, out alert system, I thinks BTW i'm not in drugs, just typed uncarefully :-D - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script
Im thinking of using the QmailToaster Plus to upgrade my old (read 18 months) Toaster install - Im not sure if its been covered, but this will continue to run the current qmail setup, build the new version in the background and then copy over and restart to run the new version of the toaster with all the settings from the previous version? Is there anything I need to manually back up? And also - will this copy all existing email in a users directory? Thanks"Eric \"Shubes\"" [EMAIL PROTECTED] wrote: I totally agree, David. That's why I wrote the qtp-newmodel scripts to dojust that!They do everything except the update ahead of time in the sandbox, so theproduction server is not affected. Then at the appropriate moment, thesysadmin can re-run the script, automatically skipping over everythingthat's already been done, and apply the update (which is done with a singlerpm -Uvh command btw).You might want to give it a try! ;)David Sánchez Martín wrote: Certainy it should work great, but i don't like unassisted updates. I don't want being woke up at 3 o'clock because out alert system a trivial problem stopped the corporative mail system. I thinks is good idea to retrieve source rpms, build the binary rpm's nightly, and wait for the sysadmin to tell to install in an apropriate moment (if everything runs ok, it will take less than 2 minutes, anyway). Just my opinion *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | David Sanchez Martin | [EMAIL PROTECTED] Administrador de Sistemas| http://www.e2000.es E2000 Nuevas Tecnologias | | E2000 Organizacion de Empresarios|Tel : +34 902 19 61 77 Mediadores de Seguros | | Agustin Bravo Esquina Calle C| 33120 Pravia Asturias Spain | | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* De: Francisco Paco Peralta [mailto:[EMAIL PROTECTED] Enviado el: lunes, 13 de noviembre de 2006 17:58 Para: qmailtoaster-list@qmailtoaster.com Asunto: Re: [qmailtoaster] upgrade script I also ran the qtp-newmodel upgrade using qtp-menu on my production server and it worked like a charm. Ryan Gibbons <[EMAIL PROTECTED]> wrote:[EMAIL PROTECTED] wrote: How safe is it to run the upgrade script on a production server. I would to upgrade to the latest packages but I'm a little nervous. Thanks. -QmailToaster hosted by: VR Hosted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I just did it last night no problems.Actually with the new qtp-newmodel upgrade is about as safe as any upgrade can be. It creates a sandbox and compiles everything in it so that your mail servers stay up until everything is compile, then it just copies over the files and restarts the services. Francisco "Paco" Peralta -- -Eric 'shubes'- QmailToaster hosted by: VR Hosted -To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED] Send instant messages to your online friends http://au.messenger.yahoo.com
Re: [qmailtoaster] upgrade script / whatami.sh
Harry Zink wrote: As good a time as any to ask this - I'm about to proceed with an update of my QMT installation, and running qtp-whatami.sh yields this: qtp-whatami v0.1.1 DISTRO=CentOS OSVER=4.4 ARCH=x86_64 BUILD_DIST=cnt40 BUILD_DIR=/usr/src/redhat This machine's OS is supported, but this version/arch has not been tested. Now, as far as I recall reading, the claims for the update script are that the x86_64 architecture is well supported by the script, so why does it give me the warning? It has indeed been run on x86_64 successfully. The 'not been tested' message indicates that the version/arch of your OS was not tested (officially) by the developers. It may, however, still be supported, as the message indicates. Is there something I can change here to make things clearer? My gut tells me that it'd be okay to proceed (after making sure everything is backed up), but just wanted to make sure to check with the list first. Harry You too seem to have an older version of the script(s), as they no longer have the .sh suffix. You should download the current scripts for best results. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script / whatami.sh
On Oct 22, 2006, at 8:38 AM, Eric Shubes wrote: You too seem to have an older version of the script(s), as they no longer have the .sh suffix. You should download the current scripts for best results. I downloaded the ones linked at: http://wiki.qmailtoaster.com/index.php/Upgrading#Instructions (These are the ones without the .sh suffix - I mistyped when I listed the script I was using with he .sh.) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script / whatami.sh
As good a time as any to ask this - I'm about to proceed with an update of my QMT installation, and running qtp-whatami.sh yields this: qtp-whatami v0.1.1 DISTRO=CentOS OSVER=4.4 ARCH=x86_64 BUILD_DIST=cnt40 BUILD_DIR=/usr/src/redhat This machine's OS is supported, but this version/arch has not been tested. Now, as far as I recall reading, the claims for the update script are that the x86_64 architecture is well supported by the script, so why does it give me the warning? My gut tells me that it'd be okay to proceed (after making sure everything is backed up), but just wanted to make sure to check with the list first. Harry On Oct 21, 2006, at 12:27 PM, Kyle Quillen wrote: Hey all, Getting ready for my mail server upgrade tonight I ran the qtp-whatami.sh script and this is what i got back am i still safe to go? [EMAIL PROTECTED] qtp]# sh qtp-whatami.sh qtp-whatami v0.1.1 DISTRO=CentOS OSVER=4.4 ARCH=i686 BUILD_DIST=cnt40 BUILD_DIR=/usr/src/redhat This machine's OS is supported, but this version/arch has not been tested. qtp-whatami.sh: line 413: return: can only `return' from a function or sourced s cript thanks in advance KQ On Wed, 2006-10-18 at 18:11 -0700, Eric Shubes wrote: Oops. Sorry. Thanks for the catch, EE. According to http://www.inter7.com/simscan/ChangeLog, SPAM_HITS wasn't working until 10/05. Looks like you're due for an upgrade, Kyle. No big deal. See http://wiki.qmailtoaster.com/index.php/Upgrading Erik Espinoza wrote: Nope, you can't. This requires simscan 1.2, and subsequently ripmime. Thanks, Erik On 10/18/06, Eric Shubes [EMAIL PROTECTED] wrote: You can simply create a /var/qmail/control/simcontrol file (it became included with version 1.3.something). Here's the default: :clam=yes,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif (all one line). To make it active, you need to rebuild the simcontrol.cdb file. That is done in newer toaster versions by simply: # qmailctl cdb but I don't think your version includes the simcontrol make. To rebuild it in older versions, # /var/qmail/bin/simscanmk TIA for updating the wiki! Kyle Quillen wrote: This is what I get daemontools-toaster-0.76-1.2.10 qmail-pop3d-toaster-1.03-1.2.11 ezmlm-toaster-0.53.324-1.2.10 maildrop-toaster-1.8.1-1.2.10 squirrelmail-toaster-1.4.6-1.2.14 ucspi-tcp-toaster-0.88-1.2.10 qmail-toaster-1.03-1.2.11 courier-imap-toaster-3.0.8-1.2.9 control-panel-toaster-0.5-1.2.8 ezmlm-cgi-toaster-0.53.324-1.2.10 qmailmrtg-toaster-4.2-1.2.10 maildrop-toaster-devel-1.8.1-1.2.10 vqadmin-toaster-2.3.4-1.2.12 spamassassin-toaster-3.1.1-1.2.13 simscan-toaster-1.1-1.2.6 vpopmail-toaster-5.4.13-1.2.11 autorespond-toaster-2.0.4-1.2.8 qmailadmin-toaster-1.2.9-1.2.12 isoqlog-toaster-2.1-1.2.9 clamav-toaster-0.88.2-1.2.14 On Wed, 2006-10-18 at 17:38 -0700, Eric Shubes wrote: Which version of the toaster do you have? # rpm -qa | grep toaster Kyle Quillen wrote: Eric, Looked at the /var/qmail/control/simcontrol But i only have simcontrol.cdb any ideas? On Wed, 2006-10-18 at 20:26 -0400, Kyle Quillen wrote: I will surely look into adding that on the wiki.. how about deleting tagged messages any ideas? On Wed, 2006-10-18 at 17:11 -0700, Eric Shubes wrote: Kyle Quillen wrote: Hey all I hope someone can help me out. I need to modify the spam filter to have the spam score lower than it is now can someone direct me to where this is. I have tried searching for it but i must be missing something some where because i can't find it. I have inherited this system and really like it just need to get over a few hurdles. I am also having trouble finding a way to take all emails marked as ***Spam*** and either just delete them or drop them into a junk email folder. I am not worried about storage space as we have plenty. Much thanks Q spam_hits variable in /var/qmail/control/simcontrol specifies at what level (spam) spam is rejected. required_hits setting in /etc/mail/spamassassin/local.cf specifies at what level (score) spam is tagged. This should be explained in the wiki, but I don't see it off hand. :( Care to add it? It's a good question. Maybe should be in the FAQs too. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script?
[EMAIL PROTECTED] wrote: Greetings, A quick question: I have a newly built toaster (end of July of this year) on CentOS 4.x which I'm finally getting ready to deploy. Before I do so, is it necessary/appropriate to run the upgrade script I just found on the toaster website, or am I better off just leaving my system unchanged and run with it as is? AFAICT, it looks like there have been only two minor package revisions since my original build... MTIA, --Duncan Personally, I like to have things as up to date as possible (while maintaining stability). I would go ahead and apply the updates before deploying, especially if you're using the upgrade.sh script, because that requires that qmail is down during the entire build process. Alternatively, you can use the qtp-* scripts at http://qmt.shubes.net to do the upgrade. They take a bit longer to run because they create a sandbox for building the binary rpms, however the qmail downtime is minimal. I expect that this will become the preferred upgrade method at some point. HTH. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script?
On Thu, October 5, 2006 12:33 pm, [EMAIL PROTECTED] wrote: Greetings, A quick question: I have a newly built toaster (end of July of this year) on CentOS 4.x which I'm finally getting ready to deploy. Before I do so, is it necessary/appropriate to run the upgrade script I just found on the toaster website, or am I better off just leaving my system unchanged and run with it as is? AFAICT, it looks like there have been only two minor package revisions since my original build... MTIA, --Duncan - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] i'd wget the new rpms, rpmbuild --rebuild --with (insert distro params here), then manually install them with a -Uhv...now current with the least amount of work/downtime/cpu cycles. -- fuzzy (toasting since 04/2006) Current stable + Erik's updates Centos 4.4 (32bit) the easy way (+KDE) Athlon 3200+, 512m, 80g - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script?
fuzzy wrote: On Thu, October 5, 2006 12:33 pm, [EMAIL PROTECTED] wrote: Greetings, A quick question: I have a newly built toaster (end of July of this year) on CentOS 4.x which I'm finally getting ready to deploy. Before I do so, is it necessary/appropriate to run the upgrade script I just found on the toaster website, or am I better off just leaving my system unchanged and run with it as is? AFAICT, it looks like there have been only two minor package revisions since my original build... MTIA, --Duncan - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] i'd wget the new rpms, rpmbuild --rebuild --with (insert distro params here), then manually install them with a -Uhv...now current with the least amount of work/downtime/cpu cycles. Don't forget the rpmbuild --target `uname -m` parameter for optimization. ;) Also, be sure to install all of the binary rpms that are built. Some source rpms build multiple binary packages. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script?
On Thu, 5 Oct 2006, Eric Shubes wrote: Eric, Alternatively, you can use the qtp-* scripts at http://qmt.shubes.net to do the upgrade. They take a bit longer to run because they create a sandbox for building the binary rpms, however the qmail downtime is minimal. I expect that this will become the preferred upgrade method at some point. This looks like an interesting alternative. Essentially, one downloads the scripts in question, then runs 'qtp-newmodel' from the command line, right? Thanks, --Duncan - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Upgrade Script?
[EMAIL PROTECTED] wrote: On Thu, 5 Oct 2006, Eric Shubes wrote: Eric, Alternatively, you can use the qtp-* scripts at http://qmt.shubes.net to do the upgrade. They take a bit longer to run because they create a sandbox for building the binary rpms, however the qmail downtime is minimal. I expect that this will become the preferred upgrade method at some point. This looks like an interesting alternative. Essentially, one downloads the scripts in question, then runs 'qtp-newmodel' from the command line, right? Thanks, --Duncan Yep. See http://wiki.qmailtoaster.com/index.php/Upgrading for details. Note, please use the scripts at qmt.shubes.net instead of svn.shubes.net for the time being. I hope to have the svn version running within a weeks or so. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: I got exactly the same response within /opt/qmt-sandbox/usr/src/: /opt/qmt-sandbox/usr/src/qmt/ ? /opt/qmt-sandbox/usr/src/qmt/caller Just to let the list know, Ron and I took this off list and the new upgrade script has been successfully tested on CentOS4 64-bit. In the process, we uncovered a couple bugs that were not 64-bit related, and they have been fixed as of today at 14:00 MST. Please be sure to download the latest version before running the script. The bugs wouldn't cause any damage, but they might be aggravating. Thank you Ron for your patience and dedicated testing. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote:
# ls -l /bin/bash
-rwxr-xr-x 1 root root 772760 Feb 17 2005 /bin/bash
# ls -l /lib/libtermcap.so.2
lrwxrwxrwx 1 root root 19 Sep 29 2005 /lib/libtermcap.so.2 -
libtermcap.so.2.0.8
# ls -l /lib/libdl.so.2
lrwxrwxrwx 1 root root 14 Mar 22 06:00 /lib/libdl.so.2 - libdl-2.3.4.so
# ls -l /lib/tls/libc.so.6
lrwxrwxrwx 1 root root 13 Mar 22 06:00 /lib/tls/libc.so.6 - libc-2.3.4.so
# ls -l /lib/ld-linux.so.2
lrwxrwxrwx 1 root root 11 Mar 22 06:00 /lib/ld-linux.so.2 - ld-2.3.4.so
Now let's verify that they look the same in the sandbox:
# ls -l /opt/qmt-sandbox/bin/bash
-rwxr-xr-x 1 root root 772760 Feb 17 2005 /opt/qmt-sandbox/bin/bash
# ls -l /opt/qmt-sandbox/lib/libtermcap.so.2
lrwxrwxrwx 1 root root 20 Aug 20 12:18 /opt/qmt-sandbox/lib/libtermcap.so.2
- libtermcap.so.2.0.8
# ls -l /opt/qmt-sandbox/lib/libdl.so.2
lrwxrwxrwx 1 root root 15 Aug 20 12:17 /opt/qmt-sandbox/lib/libdl.so.2 -
libdl-2.3.4.so
# ls -l /opt/qmt-sandbox/lib/tls/libc.so.6
lrwxrwxrwx 1 root root 14 Aug 20 12:17 /opt/qmt-sandbox/lib/tls/libc.so.6
- libc-2.3.4.so
# ls -l /opt/qmt-sandbox/lib/ld-linux.so.2
lrwxrwxrwx 1 root root 12 Aug 20 12:18 /opt/qmt-sandbox/lib/ld-linux.so.2
- ld-2.3.4.so
Ron, let's back up a bit. A straight 'chroot /opt/qmt-sandbox' should work,
and give you a bash prompt.
[EMAIL PROTECTED] bin]# chroot /opt/qmt-sandbox/
Chroot: cannot run command '/bin/bash' : No such file or directory
Please do these commands on your machine and post the results. I'm thinking
at this point that
64-bit might have something to do with it, but that's just a guess since
it's the only thing I see
that's different (so far).
See results of commands (above) shown below the commands themselves
Ron
Man, this error is subtle. There's a bug in the script that causes bash64 to
include a space in front of the link target names (notice - ld-2.3.4.so).
Much easier to notice when doing ls -l while logged on to your machine -
invalid symlinks are bold red. For whatever reason, bash32 interprets the
leading space as being outside of the variable name when it's not quoted, so
it 'worked', but it wasn't quite right.
I've got a fix for you to try. I'm confident that this will at least fix
this bug.
Edit qmt-newmodel.sh, changing line 783 from
target=${ls#*-}
to
target=${ls#*- }
IOW, add a space after the '', and the leading space will be removed from
$target.
Then rerun the script, rebuilding the sandbox. While the sandbox is
building, you can 'ls -l /opt/qmt-sandbox/lib' after that directory is
built, and you should see no more broken links (bold red).
Let me know how you make out.
--
-Eric 'shubes'
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
I'm not Eric, but the URL is http://qmt.shubes.net/
On 8/23/06, George Sweetnam [EMAIL PROTECTED] wrote:
Eric,
You should include a link to your website (test installation qmt) in your
sig file. I had some time this afternoon on a fedora5 box and was going to
run it. Repost the link if you would and I'll see if I can test build for
you.
George Sweetnam.
- Original Message -
From: Eric Shubes [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Cc: [EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 3:05 PM
Subject: Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote:
# ls -l /bin/bash
-rwxr-xr-x 1 root root 772760 Feb 17 2005 /bin/bash
# ls -l /lib/libtermcap.so.2
lrwxrwxrwx 1 root root 19 Sep 29 2005 /lib/libtermcap.so.2 -
libtermcap.so.2.0.8
# ls -l /lib/libdl.so.2
lrwxrwxrwx 1 root root 14 Mar 22 06:00 /lib/libdl.so.2 - libdl-2.3.4.so
# ls -l /lib/tls/libc.so.6
lrwxrwxrwx 1 root root 13 Mar 22 06:00 /lib/tls/libc.so.6 -
libc-2.3.4.so
# ls -l /lib/ld-linux.so.2
lrwxrwxrwx 1 root root 11 Mar 22 06:00 /lib/ld-linux.so.2 - ld-2.3.4.so
Now let's verify that they look the same in the sandbox:
# ls -l /opt/qmt-sandbox/bin/bash
-rwxr-xr-x 1 root root 772760 Feb 17 2005 /opt/qmt-sandbox/bin/bash
# ls -l /opt/qmt-sandbox/lib/libtermcap.so.2
lrwxrwxrwx 1 root root 20 Aug 20 12:18
/opt/qmt-sandbox/lib/libtermcap.so.2
- libtermcap.so.2.0.8
# ls -l /opt/qmt-sandbox/lib/libdl.so.2
lrwxrwxrwx 1 root root 15 Aug 20 12:17 /opt/qmt-sandbox/lib/libdl.so.2 -
libdl-2.3.4.so
# ls -l /opt/qmt-sandbox/lib/tls/libc.so.6
lrwxrwxrwx 1 root root 14 Aug 20 12:17 /opt/qmt-sandbox/lib/tls/libc.so.6
- libc-2.3.4.so
# ls -l /opt/qmt-sandbox/lib/ld-linux.so.2
lrwxrwxrwx 1 root root 12 Aug 20 12:18 /opt/qmt-sandbox/lib/ld-linux.so.2
- ld-2.3.4.so
Ron, let's back up a bit. A straight 'chroot /opt/qmt-sandbox' should
work,
and give you a bash prompt.
[EMAIL PROTECTED] bin]# chroot /opt/qmt-sandbox/
Chroot: cannot run command '/bin/bash' : No such file or directory
Please do these commands on your machine and post the results. I'm
thinking
at this point that
64-bit might have something to do with it, but that's just a guess since
it's the only thing I see
that's different (so far).
See results of commands (above) shown below the commands themselves
Ron
Man, this error is subtle. There's a bug in the script that causes bash64 to
include a space in front of the link target names (notice - ld-2.3.4.so).
Much easier to notice when doing ls -l while logged on to your machine -
invalid symlinks are bold red. For whatever reason, bash32 interprets the
leading space as being outside of the variable name when it's not quoted, so
it 'worked', but it wasn't quite right.
I've got a fix for you to try. I'm confident that this will at least fix
this bug.
Edit qmt-newmodel.sh, changing line 783 from
target=${ls#*-}
to
target=${ls#*- }
IOW, add a space after the '', and the leading space will be removed from
$target.
Then rerun the script, rebuilding the sandbox. While the sandbox is
building, you can 'ls -l /opt/qmt-sandbox/lib' after that directory is
built, and you should see no more broken links (bold red).
Let me know how you make out.
--
-Eric 'shubes'
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
George Sweetnam wrote: Eric, You should include a link to your website (test installation qmt) in your sig file. I had some time this afternoon on a fedora5 box and was going to run it. Repost the link if you would and I'll see if I can test build for you. George Sweetnam. Thanks, George. If you haven't started yet, you might want to use the qtp-* scripts. There are three of them. Should work the same as the qmt- versions. Same instructions apply. Oh, and I guess you got the URL from Erik (thanks, EE). http://qmt.shubes.net -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
Did you see it the script create /usr/lib64 and /lib64 directories? Do /opt/qmt-sandbox/usr/lib64 and /opt/qmt-sandbox/lib64 directories exist I'm guessing not. Actually they do: /opt/qmt-sandbox/lib64/ /opt/qmt-sandbox/usr/lib64/ Are both there What does # uname -m tell you? I've probably got the wrong constant in there for 64bit machines. #uname -m returns 'x86_64' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: Did you see it the script create /usr/lib64 and /lib64 directories? Do /opt/qmt-sandbox/usr/lib64 and /opt/qmt-sandbox/lib64 directories exist I'm guessing not. Actually they do: /opt/qmt-sandbox/lib64/ /opt/qmt-sandbox/usr/lib64/ Are both there What does # uname -m tell you? I've probably got the wrong constant in there for 64bit machines. #uname -m returns 'x86_64' Dang. I was hoping that was it. I think I'll take you up on your offer to use your box for testing. Please email me off list. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
[EMAIL PROTECTED] qmt-sandbox]# ldd bin/bash libtermcap.so.2 = /lib64/libtermcap.so.2 (0x003aaf70) libdl.so.2 = /lib64/libdl.so.2 (0x003c9cc0) libc.so.6 = /lib64/tls/libc.so.6 (0x003c9c90) /lib64/ld-linux-x86-64.so.2 (0x003c9c70) Ron I forgot to mention, you still need to check that these files exist. Do an ls -l on them like in the other email. What do you get? When I do an ls on these files (actually I did ls | grep filename) I find them all - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
I used two 'test' scripts when I was testing this problem: # cat caller echo about to call p1=parm1 p2=parm2 p3=parm3 chroot /opt/qmt-sandbox \ /usr/src/qmt/called \ $p1 \ $p2 \ $p3 echo returned from called # cat called echo 0=$0 1=$1 2=$2 3=$3 exit Try creating caller, called in /opt/qmt-sandbox/usr/src/qmt/, then run caller. What do you get? I created /opt/qmt-sandbox/usr/src/qmt/caller Chmod +x caller And pasted in the script When I ran it, I got the following output: [EMAIL PROTECTED] qmt]# ./caller About to call Chroot: cannot run command '/usr/src/qmt/called': No such file or directory returned from called 0=./caller 1= 2= 3= I tried running it in /usr/src/qmt as well and got the same output Ron - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: I used two 'test' scripts when I was testing this problem: # cat caller echo about to call p1=parm1 p2=parm2 p3=parm3 chroot /opt/qmt-sandbox \ /usr/src/qmt/called \ $p1 \ $p2 \ $p3 echo returned from called # cat called echo 0=$0 1=$1 2=$2 3=$3 exit Try creating caller, called in /opt/qmt-sandbox/usr/src/qmt/, then run caller. What do you get? I created /opt/qmt-sandbox/usr/src/qmt/caller Chmod +x caller And pasted in the script When I ran it, I got the following output: [EMAIL PROTECTED] qmt]# ./caller About to call Chroot: cannot run command '/usr/src/qmt/called': No such file or directory returned from called 0=./caller 1= 2= 3= I tried running it in /usr/src/qmt as well and got the same output Ron Did you create the 'called' script in the same manner? -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
Did you create the 'called' script in the same manner? Oops.. Lol No Ok, what I've just done is gone to /usr/src/qmt; Cp caller called Then: [EMAIL PROTECTED] qmt]# ./caller About to call Chroot: cannot run command '/usr/src/qmt/called' : No such file or directory Returned from called 0=./caller 1= 2= 3= - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: Did you create the 'called' script in the same manner? Oops.. Lol No Ok, what I've just done is gone to /usr/src/qmt; Cp caller called 'caller' is different than 'called'. 'caller' should be: # cat /opt/qmt-sandbox/usr/src/qmt/called echo 0=$0 1=$1 2=$2 3=$3 exit Then: [EMAIL PROTECTED] qmt]# ./caller About to call Chroot: cannot run command '/usr/src/qmt/called' : No such file or directory Returned from called 0=./caller 1= 2= 3= 'called' needs to be withing the chroot'd environment, i.e. it needs to be in /opt/qmt-sandbox/usr/src/qmt. Make sure it's executable, and that permissions are ok. Try again. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
Then: [EMAIL PROTECTED] qmt]# ./caller About to call Chroot: cannot run command '/usr/src/qmt/called' : No such file or directory Returned from called 0=./caller 1= 2= 3= 'called' needs to be withing the chroot'd environment, i.e. it needs to be in /opt/qmt-sandbox/usr/src/qmt. Make sure it's executable, and that permissions are ok. No luck... I got exactly the same response within /opt/qmt-sandbox/usr/src/: [EMAIL PROTECTED] qmt]# ./caller about to call chroot: cannot run command `/usr/src/qmt/called': No such file or directory returned from called 0=./caller 1= 2= 3= - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: Then: [EMAIL PROTECTED] qmt]# ./caller About to call Chroot: cannot run command '/usr/src/qmt/called' : No such file or directory Returned from called 0=./caller 1= 2= 3= 'called' needs to be withing the chroot'd environment, i.e. it needs to be in /opt/qmt-sandbox/usr/src/qmt. Make sure it's executable, and that permissions are ok. No luck... I got exactly the same response within /opt/qmt-sandbox/usr/src/: /opt/qmt-sandbox/usr/src/qmt/ ? [EMAIL PROTECTED] qmt]# ./caller about to call chroot: cannot run command `/usr/src/qmt/called': No such file or directory returned from called 0=./caller 1= 2= 3= -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Eric Shubes wrote: Ron Jones wrote: Ok... [EMAIL PROTECTED] qmt]# chroot /opt/qmt-sandbox Returned: chroot: cannot run command '/bin/bash' : No such file or directory Ron, That's basically the same error I experienced during testing (I'm not getting it now, on two separate boxes). I expected such. At least now it's easily reproduced, so we should know when we get it fixed. /opt/qmt-sandbox exists, and /opt/qmt-sandbox/bin/bash does too, right? chroot should run the shell script by default, and it doesn't find that either (like it didn't find qmt-build-rpms.sh). There's something somewhere that's keeping chroot from doing its thing. Perhaps the sandbox isn't being created properly (I kinda doubt it, but I've been known to be wrong), so let's double check. Please verify: # ldd /bin/bash libtermcap.so.2 = /lib/libtermcap.so.2 (0x002bf000) libdl.so.2 = /lib/libdl.so.2 (0x00294000) libc.so.6 = /lib/tls/libc.so.6 (0x00168000) /lib/ld-linux.so.2 (0x0014f000) These are the dynamic modules bash needs to execute. Let's see what they look like in the primary tree: # ls -l /bin/bash -rwxr-xr-x 1 root root 616184 Feb 21 2005 /bin/bash # ls -l /lib/libtermcap.so.2 lrwxrwxrwx 1 root root 19 May 16 14:17 /lib/libtermcap.so.2 - libtermcap.so.2.0.8 # ls -l /lib/libdl.so.2 lrwxrwxrwx 1 root root 14 May 16 14:17 /lib/libdl.so.2 - libdl-2.3.4.so # ls -l /lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 May 16 14:17 /lib/tls/libc.so.6 - libc-2.3.4.so # ls -l /lib/ld-linux.so.2 lrwxrwxrwx 1 root root 11 May 16 14:17 /lib/ld-linux.so.2 - ld-2.3.4.so Now let's verify that they look the same in the sandbox: # ls -l /opt/qmt-sandbox/bin/bash -rwxr-xr-x 1 root root 616184 Feb 21 2005 /opt/qmt-sandbox/bin/bash # ls -l /opt/qmt-sandbox/lib/libtermcap.so.2 lrwxrwxrwx 1 root root 19 Jul 31 23:44 /opt/qmt-sandbox/lib/libtermcap.so.2 - libtermcap.so.2.0.8 # ls -l /opt/qmt-sandbox/lib/libdl.so.2 lrwxrwxrwx 1 root root 14 Jul 31 23:44 /opt/qmt-sandbox/lib/libdl.so.2 - libdl-2.3.4.so # ls -l /opt/qmt-sandbox/lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 Jul 31 23:44 /opt/qmt-sandbox/lib/tls/libc.so.6 - libc-2.3.4.so # ls -l /opt/qmt-sandbox/lib/ld-linux.so.2 lrwxrwxrwx 1 root root 11 Jul 31 23:44 /opt/qmt-sandbox/lib/ld-linux.so.2 - ld-2.3.4.so Does everything in the sandbox look ok? It should be identical to the main branch. Ron, let's back up a bit. A straight 'chroot /opt/qmt-sandbox' should work, and give you a bash prompt. Please do these commands on your machine and post the results. I'm thinking at this point that 64-bit might have something to do with it, but that's just a guess since it's the only thing I see that's different (so far). -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Eric, This will fail because your sandbox doesn't copy (link?) the /lib64 and /usr/lib64 directories which contain the 64 bit libs. Your script is not 64-bit safe yet and will need some work and testing. Thanks, Erik On 8/21/06, Eric Shubes [EMAIL PROTECTED] wrote: Eric Shubes wrote: Ron Jones wrote: Ok... [EMAIL PROTECTED] qmt]# chroot /opt/qmt-sandbox Returned: chroot: cannot run command '/bin/bash' : No such file or directory Ron, That's basically the same error I experienced during testing (I'm not getting it now, on two separate boxes). I expected such. At least now it's easily reproduced, so we should know when we get it fixed. /opt/qmt-sandbox exists, and /opt/qmt-sandbox/bin/bash does too, right? chroot should run the shell script by default, and it doesn't find that either (like it didn't find qmt-build-rpms.sh). There's something somewhere that's keeping chroot from doing its thing. Perhaps the sandbox isn't being created properly (I kinda doubt it, but I've been known to be wrong), so let's double check. Please verify: # ldd /bin/bash libtermcap.so.2 = /lib/libtermcap.so.2 (0x002bf000) libdl.so.2 = /lib/libdl.so.2 (0x00294000) libc.so.6 = /lib/tls/libc.so.6 (0x00168000) /lib/ld-linux.so.2 (0x0014f000) These are the dynamic modules bash needs to execute. Let's see what they look like in the primary tree: # ls -l /bin/bash -rwxr-xr-x 1 root root 616184 Feb 21 2005 /bin/bash # ls -l /lib/libtermcap.so.2 lrwxrwxrwx 1 root root 19 May 16 14:17 /lib/libtermcap.so.2 - libtermcap.so.2.0.8 # ls -l /lib/libdl.so.2 lrwxrwxrwx 1 root root 14 May 16 14:17 /lib/libdl.so.2 - libdl-2.3.4.so # ls -l /lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 May 16 14:17 /lib/tls/libc.so.6 - libc-2.3.4.so # ls -l /lib/ld-linux.so.2 lrwxrwxrwx 1 root root 11 May 16 14:17 /lib/ld-linux.so.2 - ld-2.3.4.so Now let's verify that they look the same in the sandbox: # ls -l /opt/qmt-sandbox/bin/bash -rwxr-xr-x 1 root root 616184 Feb 21 2005 /opt/qmt-sandbox/bin/bash # ls -l /opt/qmt-sandbox/lib/libtermcap.so.2 lrwxrwxrwx 1 root root 19 Jul 31 23:44 /opt/qmt-sandbox/lib/libtermcap.so.2 - libtermcap.so.2.0.8 # ls -l /opt/qmt-sandbox/lib/libdl.so.2 lrwxrwxrwx 1 root root 14 Jul 31 23:44 /opt/qmt-sandbox/lib/libdl.so.2 - libdl-2.3.4.so # ls -l /opt/qmt-sandbox/lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 Jul 31 23:44 /opt/qmt-sandbox/lib/tls/libc.so.6 - libc-2.3.4.so # ls -l /opt/qmt-sandbox/lib/ld-linux.so.2 lrwxrwxrwx 1 root root 11 Jul 31 23:44 /opt/qmt-sandbox/lib/ld-linux.so.2 - ld-2.3.4.so Does everything in the sandbox look ok? It should be identical to the main branch. Ron, let's back up a bit. A straight 'chroot /opt/qmt-sandbox' should work, and give you a bash prompt. Please do these commands on your machine and post the results. I'm thinking at this point that 64-bit might have something to do with it, but that's just a guess since it's the only thing I see that's different (so far). -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
That would do it all right. ;) I wasn't aware that these directories existed! It's going to take me a little while to do fix this right. I'll let you know when it's ready, hopefully by tomorrow. Thanks, Erik! P.S. What took you so long to chime in on this? ;) Erik Espinoza wrote: Eric, This will fail because your sandbox doesn't copy (link?) the /lib64 and /usr/lib64 directories which contain the 64 bit libs. Your script is not 64-bit safe yet and will need some work and testing. Thanks, Erik On 8/21/06, Eric Shubes [EMAIL PROTECTED] wrote: Eric Shubes wrote: Ron Jones wrote: Ok... [EMAIL PROTECTED] qmt]# chroot /opt/qmt-sandbox Returned: chroot: cannot run command '/bin/bash' : No such file or directory Ron, That's basically the same error I experienced during testing (I'm not getting it now, on two separate boxes). I expected such. At least now it's easily reproduced, so we should know when we get it fixed. /opt/qmt-sandbox exists, and /opt/qmt-sandbox/bin/bash does too, right? chroot should run the shell script by default, and it doesn't find that either (like it didn't find qmt-build-rpms.sh). There's something somewhere that's keeping chroot from doing its thing. Perhaps the sandbox isn't being created properly (I kinda doubt it, but I've been known to be wrong), so let's double check. Please verify: # ldd /bin/bash libtermcap.so.2 = /lib/libtermcap.so.2 (0x002bf000) libdl.so.2 = /lib/libdl.so.2 (0x00294000) libc.so.6 = /lib/tls/libc.so.6 (0x00168000) /lib/ld-linux.so.2 (0x0014f000) These are the dynamic modules bash needs to execute. Let's see what they look like in the primary tree: # ls -l /bin/bash -rwxr-xr-x 1 root root 616184 Feb 21 2005 /bin/bash # ls -l /lib/libtermcap.so.2 lrwxrwxrwx 1 root root 19 May 16 14:17 /lib/libtermcap.so.2 - libtermcap.so.2.0.8 # ls -l /lib/libdl.so.2 lrwxrwxrwx 1 root root 14 May 16 14:17 /lib/libdl.so.2 - libdl-2.3.4.so # ls -l /lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 May 16 14:17 /lib/tls/libc.so.6 - libc-2.3.4.so # ls -l /lib/ld-linux.so.2 lrwxrwxrwx 1 root root 11 May 16 14:17 /lib/ld-linux.so.2 - ld-2.3.4.so Now let's verify that they look the same in the sandbox: # ls -l /opt/qmt-sandbox/bin/bash -rwxr-xr-x 1 root root 616184 Feb 21 2005 /opt/qmt-sandbox/bin/bash # ls -l /opt/qmt-sandbox/lib/libtermcap.so.2 lrwxrwxrwx 1 root root 19 Jul 31 23:44 /opt/qmt-sandbox/lib/libtermcap.so.2 - libtermcap.so.2.0.8 # ls -l /opt/qmt-sandbox/lib/libdl.so.2 lrwxrwxrwx 1 root root 14 Jul 31 23:44 /opt/qmt-sandbox/lib/libdl.so.2 - libdl-2.3.4.so # ls -l /opt/qmt-sandbox/lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 Jul 31 23:44 /opt/qmt-sandbox/lib/tls/libc.so.6 - libc-2.3.4.so # ls -l /opt/qmt-sandbox/lib/ld-linux.so.2 lrwxrwxrwx 1 root root 11 Jul 31 23:44 /opt/qmt-sandbox/lib/ld-linux.so.2 - ld-2.3.4.so Does everything in the sandbox look ok? It should be identical to the main branch. Ron, let's back up a bit. A straight 'chroot /opt/qmt-sandbox' should work, and give you a bash prompt. Please do these commands on your machine and post the results. I'm thinking at this point that 64-bit might have something to do with it, but that's just a guess since it's the only thing I see that's different (so far). -- -Eric 'shubes' -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
P.S. What took you so long to chime in on this? I've been trying to field ones that hadn't been responded too by the major users such as you and Jake. I'll try to pay more attention. Erik - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Erik Espinoza wrote: P.S. What took you so long to chime in on this? I've been trying to field ones that hadn't been responded too by the major users such as you and Jake. I'll try to pay more attention. Erik blushes I'm just yankin' your chain. Me a major user? Not compared to you and Jake! (I'm getting there though, I hope) Thanks again. I think the patch will be trivial, should have it available soon. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Erik Espinoza wrote: Eric, This will fail because your sandbox doesn't copy (link?) the /lib64 and /usr/lib64 directories which contain the 64 bit libs. Your script is not 64-bit safe yet and will need some work and testing. Thanks, Erik On 8/21/06, Eric Shubes [EMAIL PROTECTED] wrote: Eric Shubes wrote: Ron Jones wrote: Ok... [EMAIL PROTECTED] qmt]# chroot /opt/qmt-sandbox Returned: chroot: cannot run command '/bin/bash' : No such file or directory Ron, That's basically the same error I experienced during testing (I'm not getting it now, on two separate boxes). I expected such. At least now it's easily reproduced, so we should know when we get it fixed. /opt/qmt-sandbox exists, and /opt/qmt-sandbox/bin/bash does too, right? chroot should run the shell script by default, and it doesn't find that either (like it didn't find qmt-build-rpms.sh). There's something somewhere that's keeping chroot from doing its thing. Perhaps the sandbox isn't being created properly (I kinda doubt it, but I've been known to be wrong), so let's double check. Please verify: # ldd /bin/bash libtermcap.so.2 = /lib/libtermcap.so.2 (0x002bf000) libdl.so.2 = /lib/libdl.so.2 (0x00294000) libc.so.6 = /lib/tls/libc.so.6 (0x00168000) /lib/ld-linux.so.2 (0x0014f000) These are the dynamic modules bash needs to execute. Let's see what they look like in the primary tree: # ls -l /bin/bash -rwxr-xr-x 1 root root 616184 Feb 21 2005 /bin/bash # ls -l /lib/libtermcap.so.2 lrwxrwxrwx 1 root root 19 May 16 14:17 /lib/libtermcap.so.2 - libtermcap.so.2.0.8 # ls -l /lib/libdl.so.2 lrwxrwxrwx 1 root root 14 May 16 14:17 /lib/libdl.so.2 - libdl-2.3.4.so # ls -l /lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 May 16 14:17 /lib/tls/libc.so.6 - libc-2.3.4.so # ls -l /lib/ld-linux.so.2 lrwxrwxrwx 1 root root 11 May 16 14:17 /lib/ld-linux.so.2 - ld-2.3.4.so Now let's verify that they look the same in the sandbox: # ls -l /opt/qmt-sandbox/bin/bash -rwxr-xr-x 1 root root 616184 Feb 21 2005 /opt/qmt-sandbox/bin/bash # ls -l /opt/qmt-sandbox/lib/libtermcap.so.2 lrwxrwxrwx 1 root root 19 Jul 31 23:44 /opt/qmt-sandbox/lib/libtermcap.so.2 - libtermcap.so.2.0.8 # ls -l /opt/qmt-sandbox/lib/libdl.so.2 lrwxrwxrwx 1 root root 14 Jul 31 23:44 /opt/qmt-sandbox/lib/libdl.so.2 - libdl-2.3.4.so # ls -l /opt/qmt-sandbox/lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 Jul 31 23:44 /opt/qmt-sandbox/lib/tls/libc.so.6 - libc-2.3.4.so # ls -l /opt/qmt-sandbox/lib/ld-linux.so.2 lrwxrwxrwx 1 root root 11 Jul 31 23:44 /opt/qmt-sandbox/lib/ld-linux.so.2 - ld-2.3.4.so Does everything in the sandbox look ok? It should be identical to the main branch. Ron, let's back up a bit. A straight 'chroot /opt/qmt-sandbox' should work, and give you a bash prompt. Please do these commands on your machine and post the results. I'm thinking at this point that 64-bit might have something to do with it, but that's just a guess since it's the only thing I see that's different (so far). -- -Eric 'shubes' Ok Ron. A 64-bit compatible (I hope) script is available now. Please download it and give it a try. It shouldn't hurt anything if it doesn't work (but you do have a backup, right?). You'll need to recreate the sandbox when you run it. You should see the /usr/lib64 and /lib64 directories created after all the others. Note, as you seem to be the 64-bit guinea pig, you should probably browse through the log after the packages are built (before updating) to verify that there weren't any problems, even though the script should terminate if there are errors. Cross your fingers. ;) -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
I got exactly the same response within /opt/qmt-sandbox/usr/src/: /opt/qmt-sandbox/usr/src/qmt/ ? /opt/qmt-sandbox/usr/src/qmt/caller - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
Eric, This will fail because your sandbox doesn't copy (link?) the /lib64 and /usr/lib64 directories which contain the 64 bit libs. Your script is not 64-bit safe yet and will need some work and testing. Thanks, Erik Oops :) Well, I can't write, but I can test. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
That would do it all right. ;) I wasn't aware that these directories existed! It's going to take me a little while to do fix this right. I'll let you know when it's ready, hopefully by tomorrow. If you don't have a 64-bit box to play with, you're welcome to use mine. Ron - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
Ok Ron. A 64-bit compatible (I hope) script is available now. Please download it and give it a try. It shouldn't hurt anything if it doesn't work (but you do have a backup, right?). You'll need to recreate the sandbox when you run it. You should see the /usr/lib64 and /lib64 directories created after all the others. Note, as you seem to be the 64-bit guinea pig, you should probably browse through the log after the packages are built (before updating) to verify that there weren't any problems, even though the script should terminate if there are errors. Cross your fingers. ;) Lucky for me it's not a production box ;) But seriously, I'll take a whack at it and see what happens. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: That would do it all right. ;) I wasn't aware that these directories existed! It's going to take me a little while to do fix this right. I'll let you know when it's ready, hopefully by tomorrow. If you don't have a 64-bit box to play with, you're welcome to use mine. Ron Thanks for the offer, Ron. I don't have one, but will keep you in mind should the need arise. I guess we're using yours anyhow! :) -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
Thanks for the offer, Ron. I don't have one, but will keep you in mind should the need arise. I guess we're using yours anyhow! :) Well, it's running right now... We'll see ;) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: Thanks for the offer, Ron. I don't have one, but will keep you in mind should the need arise. I guess we're using yours anyhow! :) Well, it's running right now... We'll see ;) Has it started into the compiles yet, or is it still building the sandbox? -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
Has it started into the compiles yet, or is it still building the sandbox? still building the sandbox, /usr/share That seems to take a while - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
Last step in the sandbox /usr/var Now it's REALLY time to go get coffee - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
Has it started into the compiles yet, or is it still building the sandbox? It errored out again... chroot: cannot run command '/usr/src/qmt/qmt-build-rpms.sh' : No such file or directory Build failed, Exiting. Well... Is there a log file somewhere that may give a more specific reason behind the failure? Ron - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: Has it started into the compiles yet, or is it still building the sandbox? It errored out again... chroot: cannot run command '/usr/src/qmt/qmt-build-rpms.sh' : No such file or directory Build failed, Exiting. Well... Is there a log file somewhere that may give a more specific reason behind the failure? Ron Not that I'm aware of. Did you see it the script create /usr/lib64 and /lib64 directories? Do /opt/qmt-sandbox/usr/lib64 and /opt/qmt-sandbox/lib64 directories exist? I'm guessing not. What does # uname -m tell you? I've probably got the wrong constant in there for 64bit machines. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors
Ron Jones wrote: That still doesn't explain how /usr/src got wiped out though. You didn't run it with SANDROOT=/usr/src did you? Well... I don't believe so. Also: During the last 40 minutes, I've been running a fresh instance of the upgrade script, it failed again. Just to make sure everything worked as it should, I downloaded (via wget) completely new copies of qmt-newmodel.sh qmt-build-rpms.sh directly to /usr/src/qmt/ Left the variables as shown below: UPGRADE_DIR=/usr/src/qmt SANDROOT=/opt/qmt-sandbox Then I chmodded them to 755 Then I ran ./qmt-newmodel.sh, chose new sandbox, it deleted the old and created the new in /opt/qmt-sandbox/ Here is the output (after Creating /opt/qmt-sandbox/var ...: Sandbox has been build successfully! Starting to build the binary rpms ...(pizza anyone?) If you want to view compile messages, you can open another terminal and: #tail -f /opt/qmt-sandbox/usr/src/qmt/log/build-recent.log Chroot: cannot run command '/usr/src/qmt/qmt-build-rpms.sh' : No such file or directory Build failed, Exiting Am I missing something obvious? Ron, I've fixed the script so that it won't run with an erroneous SANDROOT setting (/ and any others) any more, and it also downloads the qmt-build-rpms.sh script automatically now (and sets permissions). I don't have reason to believe that the No such file problem is fixed, but I'd like you to do this (again): .) delete the scripts you have .) reboot the server if at all feasible. /etc/mtab might be a bit wacky with the abnormal exits, and I just want to eliminate that from a possibility .) download qmt-newmodel.sh and try running it again. In the meantime, I'll continue to try and remember what has caused this No such file error in the past. Thanks for your patience and effort. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: I don't have reason to believe that the No such file problem is fixed, but I'd like you to do this (again): .) delete the scripts you have .) reboot the server if at all feasible. /etc/mtab might be a bit wacky with the abnormal exits, and I just want to eliminate that from a possibility .) download qmt-newmodel.sh and try running it again. Well, here is what I did, - deleted the scripts, also deleted /opt/qmt-sandbox/* - rebooted server - su - 'd to root - cd to /usr/src/qmt/ - ran wget http://qmt.shubes.net/qmt-newmodel.sh (in /usr/src/qmt) - then ran sh qmt-newmodel.sh; this script will also download qmt-build-rpms and chmod it to 755 - qmt-newmodel created the sandbox and copied over both scripts to /opt/qmt-sandbox/usr/src/qmt/ Unfortunately, I got the same error message upon completion of qmt-newmodel.sh: chroot: cannot run command '/usr/src/qmt/qmt-build-rpms.sh' : No such file or directory Build failed, Exiting. This error drove me nuts one time testing. I can't yet remember the solution. Unfortunately I didn't ask the question on my local LUG or I'd have posted the answer. I really need to make notes sometimes. Ok, let's see if we can nail this down. If I remember right, when I ran some test scripts just playing around with this error, chroot wouldn't even find the default shell. If you go to /usr/src/qmt as root and simply do '# chroot', do you get a shell prompt or does it say it can't find 'bin/sh'? Care to IRC? I just logged in to the #QmailToaster chat room if you'd like. Might be easier that way. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
This error drove me nuts one time testing. I can't yet remember the
solution. Unfortunately I didn't ask the question on my local LUG or I'd
have posted the answer. I really need to make notes sometimes.
Yes, I know the feeling, I've got to document more than I do
Ok, let's see if we can nail this down. If I remember right, when I ran
some
test scripts just playing around with this error, chroot wouldn't even find
the default shell. If you go to /usr/src/qmt as root and simply do '#
chroot', do you get a shell prompt or does it say it can't find 'bin/sh'?
When I cd'd to /usr/src/qmt as root:
[EMAIL PROTECTED] qmt]# chroot
I get chroot: too few arguments
Try 'chroot --help' for more information
So then I:
[EMAIL PROTECTED] qmt]#chroot --help
Usage: chroot NEWROOT [COMMAND...]
or: chroot OPTION
Run COMMAND with root directory set to NEWROOT.
--help display this help and exit
--version output version information and exit
If no command is given, run ''${SHELL} -I (default: /bin/sh).
So... Just for kicks, I ran:
[EMAIL PROTECTED] qmt]#chroot '${SHELL} -i'
And got:
chroot: cannot change root directory to /bin/bash: Not a directory
Care to IRC? I just logged in to the #QmailToaster chat room if you'd like.
Might be easier that way.
She who must be obeyed has asked that we run to wally world. But for
future reference, where to I download a Windows XP client for IRC, and
what's the address?
Thanks,
Ron
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote:
This error drove me nuts one time testing. I can't yet remember the
solution. Unfortunately I didn't ask the question on my local LUG or I'd
have posted the answer. I really need to make notes sometimes.
Yes, I know the feeling, I've got to document more than I do
Ok, let's see if we can nail this down. If I remember right, when I ran
some
test scripts just playing around with this error, chroot wouldn't even find
the default shell. If you go to /usr/src/qmt as root and simply do '#
chroot', do you get a shell prompt or does it say it can't find 'bin/sh'?
When I cd'd to /usr/src/qmt as root:
[EMAIL PROTECTED] qmt]# chroot
I get chroot: too few arguments
Try 'chroot --help' for more information
So then I:
[EMAIL PROTECTED] qmt]#chroot --help
Usage: chroot NEWROOT [COMMAND...]
or: chroot OPTION
Run COMMAND with root directory set to NEWROOT.
--help display this help and exit
--version output version information and exit
If no command is given, run ''${SHELL} -I (default: /bin/sh).
So... Just for kicks, I ran:
[EMAIL PROTECTED] qmt]#chroot '${SHELL} -i'
And got:
chroot: cannot change root directory to /bin/bash: Not a directory
Oops. I forgot the format. Try
# chroot /opt/qmt-sandbox
That should either give you a shell prompt in the named directory. If it
tells you it can't find shell, that the same error as we're seeing in the
script. We'll take it from there.
BTW, which distro/version are you running? I doubt that it would make any
difference, but good to know. I'm using current CentOS.
Care to IRC? I just logged in to the #QmailToaster chat room if you'd like.
Might be easier that way.
She who must be obeyed has asked that we run to wally world. But for
future reference, where to I download a Windows XP client for IRC, and
what's the address?
I don't know what which IRC clients run on XP (google is your friend), there
must be at least a handful. The address is irc.freenode.net, #QmailToaster
channel.
Thanks,
Ron
Have fun at WW!
--
-Eric 'shubes'
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
Oops. I forgot the format. Try # chroot /opt/qmt-sandbox That should either give you a shell prompt in the named directory. If it tells you it can't find shell, that the same error as we're seeing in the script. We'll take it from there. Ok... [EMAIL PROTECTED] qmt]# chroot /opt/qmt-sandbox Returned: chroot: cannot run command '/bin/bash' : No such file or directory BTW, which distro/version are you running? I doubt that it would make any difference, but good to know. I'm using current CentOS. As am I - CentOS current. Uname -a returns: Linux server.rej.us 2.6.9-34.0.2.Elsmp #1 SMP Fri Jul 7 18:22:55 CDT 2006 x86_64 x86_64 x86_64 GNU/Linux I don't know what which IRC clients run on XP (google is your friend), there must be at least a handful. The address is irc.freenode.net, #QmailToaster channel. I'll have a look around and check it out. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: Ok... [EMAIL PROTECTED] qmt]# chroot /opt/qmt-sandbox Returned: chroot: cannot run command '/bin/bash' : No such file or directory Ron, That's basically the same error I experienced during testing (I'm not getting it now, on two separate boxes). I expected such. At least now it's easily reproduced, so we should know when we get it fixed. /opt/qmt-sandbox exists, and /opt/qmt-sandbox/bin/bash does too, right? chroot should run the shell script by default, and it doesn't find that either (like it didn't find qmt-build-rpms.sh). There's something somewhere that's keeping chroot from doing its thing. Perhaps the sandbox isn't being created properly (I kinda doubt it, but I've been known to be wrong), so let's double check. Please verify: # ldd /bin/bash libtermcap.so.2 = /lib/libtermcap.so.2 (0x002bf000) libdl.so.2 = /lib/libdl.so.2 (0x00294000) libc.so.6 = /lib/tls/libc.so.6 (0x00168000) /lib/ld-linux.so.2 (0x0014f000) These are the dynamic modules bash needs to execute. Let's see what they look like in the primary tree: # ls -l /bin/bash -rwxr-xr-x 1 root root 616184 Feb 21 2005 /bin/bash # ls -l /lib/libtermcap.so.2 lrwxrwxrwx 1 root root 19 May 16 14:17 /lib/libtermcap.so.2 - libtermcap.so.2.0.8 # ls -l /lib/libdl.so.2 lrwxrwxrwx 1 root root 14 May 16 14:17 /lib/libdl.so.2 - libdl-2.3.4.so # ls -l /lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 May 16 14:17 /lib/tls/libc.so.6 - libc-2.3.4.so # ls -l /lib/ld-linux.so.2 lrwxrwxrwx 1 root root 11 May 16 14:17 /lib/ld-linux.so.2 - ld-2.3.4.so Now let's verify that they look the same in the sandbox: # ls -l /opt/qmt-sandbox/bin/bash -rwxr-xr-x 1 root root 616184 Feb 21 2005 /opt/qmt-sandbox/bin/bash # ls -l /opt/qmt-sandbox/lib/libtermcap.so.2 lrwxrwxrwx 1 root root 19 Jul 31 23:44 /opt/qmt-sandbox/lib/libtermcap.so.2 - libtermcap.so.2.0.8 # ls -l /opt/qmt-sandbox/lib/libdl.so.2 lrwxrwxrwx 1 root root 14 Jul 31 23:44 /opt/qmt-sandbox/lib/libdl.so.2 - libdl-2.3.4.so # ls -l /opt/qmt-sandbox/lib/tls/libc.so.6 lrwxrwxrwx 1 root root 13 Jul 31 23:44 /opt/qmt-sandbox/lib/tls/libc.so.6 - libc-2.3.4.so # ls -l /opt/qmt-sandbox/lib/ld-linux.so.2 lrwxrwxrwx 1 root root 11 Jul 31 23:44 /opt/qmt-sandbox/lib/ld-linux.so.2 - ld-2.3.4.so Does everything in the sandbox look ok? It should be identical to the main branch. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: Oops. I forgot the format. Try # chroot /opt/qmt-sandbox That should either give you a shell prompt in the named directory. If it tells you it can't find shell, that the same error as we're seeing in the script. We'll take it from there. Ok... [EMAIL PROTECTED] qmt]# chroot /opt/qmt-sandbox Returned: chroot: cannot run command '/bin/bash' : No such file or directory I just found an easier way to check this out. You should be able to just # cd /opt/qmt-sandbox # ldd bin/bash libtermcap.so.2 = /lib/libtermcap.so.2 (0x002bf000) libdl.so.2 = /lib/libdl.so.2 (0x00294000) libc.so.6 = /lib/tls/libc.so.6 (0x00168000) /lib/ld-linux.so.2 (0x0014f000) What do you get? -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors - Still no love
I just found an easier way to check this out. You should be able to just # cd /opt/qmt-sandbox # ldd bin/bash libtermcap.so.2 = /lib/libtermcap.so.2 (0x002bf000) libdl.so.2 = /lib/libdl.so.2 (0x00294000) libc.so.6 = /lib/tls/libc.so.6 (0x00168000) /lib/ld-linux.so.2 (0x0014f000) What do you get? When I cd to /opt/qmt-sandbox and run the command, here is what I get: [EMAIL PROTECTED] qmt-sandbox]# ldd bin/bash libtermcap.so.2 = /lib64/libtermcap.so.2 (0x003aaf70) libdl.so.2 = /lib64/libdl.so.2 (0x003c9cc0) libc.so.6 = /lib64/tls/libc.so.6 (0x003c9c90) /lib64/ld-linux-x86-64.so.2 (0x003c9c70) Ron - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: I just found an easier way to check this out. You should be able to just # cd /opt/qmt-sandbox # ldd bin/bash libtermcap.so.2 = /lib/libtermcap.so.2 (0x002bf000) libdl.so.2 = /lib/libdl.so.2 (0x00294000) libc.so.6 = /lib/tls/libc.so.6 (0x00168000) /lib/ld-linux.so.2 (0x0014f000) What do you get? When I cd to /opt/qmt-sandbox and run the command, here is what I get: [EMAIL PROTECTED] qmt-sandbox]# ldd bin/bash libtermcap.so.2 = /lib64/libtermcap.so.2 (0x003aaf70) libdl.so.2 = /lib64/libdl.so.2 (0x003c9cc0) libc.so.6 = /lib64/tls/libc.so.6 (0x003c9c90) /lib64/ld-linux-x86-64.so.2 (0x003c9c70) Ron I forgot to mention, you still need to check that these files exist. Do an ls -l on them like in the other email. What do you get? -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors - Still no love
Ron Jones wrote: I just found an easier way to check this out. You should be able to just # cd /opt/qmt-sandbox # ldd bin/bash libtermcap.so.2 = /lib/libtermcap.so.2 (0x002bf000) libdl.so.2 = /lib/libdl.so.2 (0x00294000) libc.so.6 = /lib/tls/libc.so.6 (0x00168000) /lib/ld-linux.so.2 (0x0014f000) What do you get? When I cd to /opt/qmt-sandbox and run the command, here is what I get: [EMAIL PROTECTED] qmt-sandbox]# ldd bin/bash libtermcap.so.2 = /lib64/libtermcap.so.2 (0x003aaf70) libdl.so.2 = /lib64/libdl.so.2 (0x003c9cc0) libc.so.6 = /lib64/tls/libc.so.6 (0x003c9c90) /lib64/ld-linux-x86-64.so.2 (0x003c9c70) Ron I used two 'test' scripts when I was testing this problem: # cat caller echo about to call p1=parm1 p2=parm2 p3=parm3 chroot /opt/qmt-sandbox \ /usr/src/qmt/called \ $p1 \ $p2 \ $p3 echo returned from called # cat called echo 0=$0 1=$1 2=$2 3=$3 exit Try creating caller, called in /opt/qmt-sandbox/usr/src/qmt/, then run caller. What do you get? -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors
Ron Jones wrote: I'm running CentOS 4.3, and tried running the upgrade script on the wiki (not on a production box, just my home email server) : qmt-newmodel.sh and qmt-build-rpms.sh It seemed to go well through the creation of the sandbox. I got the Sandbox has been built successfully! message Then... Starting to build the binary rpms ... (pizza anyone?) message followed by: If you want to view the compile messages, you can open another terminal and: # tail -f /opt/qmt-sandbox/usr/src/qmt/log/build-recent.log That's when I got the error message: chroot: cannot run command '/usr/src/qmt/qmt-build-rpms.sh': Permission denied Build failed, Exiting I checked the above log file, but it's empty as it didn't start compiling. Any suggestions? I'm guessing that ownership of qmt-bulid-rpms.sh isn't root. Oops, my bad. I gather you obtained the scripts under a different user id. # ls -l /opt/qmt-sandbox/usr/src/qmt/qmt-build-rpms.sh to verify that it's not owned by root, then # chown root:root /opt/qmt-sandbox/usr/src/qmt/qmt-build-rpms.sh to change its ownership. You should probably change the ownership of the scripts too, in /usr/src/qmt/, so you won't have this problem again if you were to need to rebuild the sandbox. Once you've done that, simply rerun the script. You'll need to answer all the questions again, but it won't re-download the sources, and you don't need to build the sandbox again. You should see compile messages in the log file shortly after compiles start. Please report back on the rest of your experience. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors
Eric Shubes wrote: Ron Jones wrote: I'm running CentOS 4.3, and tried running the upgrade script on the wiki (not on a production box, just my home email server) : qmt-newmodel.sh and qmt-build-rpms.sh It seemed to go well through the creation of the sandbox. I got the Sandbox has been built successfully! message Then... Starting to build the binary rpms ... (pizza anyone?) message followed by: If you want to view the compile messages, you can open another terminal and: # tail -f /opt/qmt-sandbox/usr/src/qmt/log/build-recent.log That's when I got the error message: chroot: cannot run command '/usr/src/qmt/qmt-build-rpms.sh': Permission denied Build failed, Exiting I checked the above log file, but it's empty as it didn't start compiling. Any suggestions? I'm guessing that ownership of qmt-bulid-rpms.sh isn't root. Oops, my bad. I gather you obtained the scripts under a different user id. # ls -l /opt/qmt-sandbox/usr/src/qmt/qmt-build-rpms.sh to verify that it's not owned by root, then # chown root:root /opt/qmt-sandbox/usr/src/qmt/qmt-build-rpms.sh to change its ownership. You should probably change the ownership of the scripts too, in /usr/src/qmt/, so you won't have this problem again if you were to need to rebuild the sandbox. Once you've done that, simply rerun the script. You'll need to answer all the questions again, but it won't re-download the sources, and you don't need to build the sandbox again. You should see compile messages in the log file shortly after compiles start. Please report back on the rest of your experience. P.S. I've changed permissions of both scripts to 755 so this shouldn't happen again, provided that wget preserves permission settings. If the scripts are downloaded from a web browser, I'm not sure what permissions they'd get. You can change permissions or ownership to fix this this problem if you've already downloaded the scripts. I think I'll update the wiki. Thanks for catching this, Ron. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors
I'm guessing that ownership of qmt-bulid-rpms.sh isn't root. Oops, my bad. I gather you obtained the scripts under a different user id. No, I started with: su - Then did wget and sh all as root # ls -l /opt/qmt-sandbox/usr/src/qmt/qmt-build-rpms.sh to verify that it's not owned by root, then # chown root:root /opt/qmt-sandbox/usr/src/qmt/qmt-build-rpms.sh to change its ownership. You should probably change the ownership of the scripts too, in /usr/src/qmt/, so you won't have this problem again if you were to need to rebuild the sandbox. Both files are already 'root root' with 644 permissions ? Ron - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade script errors
P.S. I've changed permissions of both scripts to 755 so this shouldn't happen again, provided that wget preserves permission settings. I just changed the permissions to 755 and it's running as we 'speak,' so I'll keep you posted. An interesting aside... When it didn't work the first time, I thought what the heck, I'll try it using the hard link method. When I started the run, I got nothing but row upon row of error messages. Obviously they were flashing by a bit quickly, but I did see a lot of already exists messages. When it finished, my /usr/src directory was completely empty. I just installed the kernel source, and recreated the file structure, so it was no big deal. But it did give me a start. Ron - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors
Ron Jones wrote: I'm guessing that ownership of qmt-bulid-rpms.sh isn't root. Oops, my bad. I gather you obtained the scripts under a different user id. No, I started with: su - Then did wget and sh all as root # ls -l /opt/qmt-sandbox/usr/src/qmt/qmt-build-rpms.sh to verify that it's not owned by root, then # chown root:root /opt/qmt-sandbox/usr/src/qmt/qmt-build-rpms.sh to change its ownership. You should probably change the ownership of the scripts too, in /usr/src/qmt/, so you won't have this problem again if you were to need to rebuild the sandbox. Both files are already 'root root' with 644 permissions ? Ron I see. 'twas the permissions that caused the problem. I'm kinda surprised that no one's mentioned this up to now. The permissions that the file takes on from a wget is probably determined by umask, which can vary. Anywise, thanks for finding this. The wiki has been updated. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors
Ron Jones wrote: P.S. I've changed permissions of both scripts to 755 so this shouldn't happen again, provided that wget preserves permission settings. I just changed the permissions to 755 and it's running as we 'speak,' so I'll keep you posted. An interesting aside... When it didn't work the first time, I thought what the heck, I'll try it using the hard link method. When I started the run, I got nothing but row upon row of error messages. Obviously they were flashing by a bit quickly, but I did see a lot of already exists messages. When it finished, my /usr/src directory was completely empty. I just installed the kernel source, and recreated the file structure, so it was no big deal. But it did give me a start. This is disturbing to me. You didn't point the SANDROOT variable to /usr/src, did you? That would be not a good thing. I should probably mention in the wiki something about making it a *new* directory that doesn't already exist. I don't see how the script otherwise could wipe out the contents of /usr/src/. Can you be a bit more specific about what you did initially to create this symptom? Ron -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors
Ron Jones wrote: This is disturbing to me. You didn't point the SANDROOT variable to /usr/src, did you? That would be not a good thing. I should probably mention in the wiki something about making it a *new* directory that doesn't already exist. I don't see how the script otherwise could wipe out the contents of /usr/src/. Can you be a bit more specific about what you did initially to create this symptom? The only change I made was to point the SANDROOT at / That explains it. By pointing SANDROOT at /, you were telling it to create the sandbox over top of itself. That would result in 'already exists' messages for every file all right, hard linked or copied. Shouldn't have hurt anything though. Good thing you didn't tell it to create a new sandbox. The first thing it does in that case is # rm -rf $SANDROOT - you'd've lost your whole system. I've gotta put some safeguards in the script, and some better instructions on the wiki. That still doesn't explain how /usr/src got wiped out though. You didn't run it with SANDROOT=/usr/src did you? -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors
Ron Jones wrote: That still doesn't explain how /usr/src got wiped out though. You didn't run it with SANDROOT=/usr/src did you? Well... I don't believe so. Also: During the last 40 minutes, I've been running a fresh instance of the upgrade script, it failed again. Just to make sure everything worked as it should, I downloaded (via wget) completely new copies of qmt-newmodel.sh qmt-build-rpms.sh directly to /usr/src/qmt/ Left the variables as shown below: UPGRADE_DIR=/usr/src/qmt SANDROOT=/opt/qmt-sandbox Then I chmodded them to 755 Then I ran ./qmt-newmodel.sh, chose new sandbox, it deleted the old and created the new in /opt/qmt-sandbox/ Here is the output (after Creating /opt/qmt-sandbox/var ...: Sandbox has been build successfully! Starting to build the binary rpms ...(pizza anyone?) If you want to view compile messages, you can open another terminal and: #tail -f /opt/qmt-sandbox/usr/src/qmt/log/build-recent.log Chroot: cannot run command '/usr/src/qmt/qmt-build-rpms.sh' : No such file or directory Build failed, Exiting Am I missing something obvious? No, you're missing something very subtle, and I wish I could remember what it was. I had this problem at one point during testing, and can't remember now what I did to fix it. I remember it driving me nuts though. /opt/qmt-sandbox/usr/src/qmt/qmt-build-rpms.sh exists, right? It should be created as part of the sandbox building process. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade script errors
Ron Jones wrote: This is disturbing to me. You didn't point the SANDROOT variable to /usr/src, did you? That would be not a good thing. I should probably mention in the wiki something about making it a *new* directory that doesn't already exist. I don't see how the script otherwise could wipe out the contents of /usr/src/. Can you be a bit more specific about what you did initially to create this symptom? The only change I made was to point the SANDROOT at / FWIW, I found out how the script clobbered your /usr/src directory. That's where the scripts were located, right? Having SANDROOT at / caused this. It would have clobbered whatever directory you had the script located in. I'm working on a fix so that SANDROOT can't be set to an unsafe value, which will prevent this from happening. This would only happen if SANDROOT and / were the same. SANDROOT is supposed to be somewhere BENEATH / ! ;) I probably should have called the variable SANDBOX in hindsight. Still don't remember about the chroot not found solution. Bear with me. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
