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 - 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]
