Re: [WebDNA] How do we tell what's misconfigured? Or which WebDNA 7 version to use?
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107222
interpreted = N
texte = Ken, it seems you are using the 32-bit version. And we do not have a = 32-bit build for libmysql16: Ubuntu 10 or 11, or Debian 6 are recent OS = and we assume no recent OS runs with a 32bit processor. can you please run uname -a This way we can confirm you have a 32-bit install of the OS. - chris On Aug 16, 2011, at 13:12, Kenneth Grome wrote: > Hi Chris, >=20 > Looks like the problem is with libmysqlclient.so.15. Maybe=20 > Debian 6 uses libmysqlclient.so.16? Does this mean I'm=20 > using the wrong executable? >=20 >=20 > Here are the results you asked for: >=20 > root@kengrome:~# ls -l /var/www/WebDNA/WebDNA.fcgi > -rwxrwxr-x 1 root root 5230068 Feb 22 08:10=20 > /var/www/WebDNA/WebDNA.fcgi >=20 > root@kengrome:~# ldd /var/www/WebDNA/WebDNA.fcgi > libpthread.so.0 =3D> /lib/libpthread.so.0 (0xb7fc2000) > libdl.so.2 =3D> /lib/libdl.so.2 (0xb7fbe000) > libnsl.so.1 =3D> /lib/libnsl.so.1 (0xb7fa6000) > libssl.so.0.9.8 =3D> /usr/lib/i686/cmov/libssl.so.0.9.8=20 > (0xb7f5c000) > libz.so.1 =3D> /usr/lib/libz.so.1 (0xb7f48000) > libmysqlclient.so.15 =3D> not found > libstdc++.so.6 =3D> /usr/lib/libstdc++.so.6 (0xb7e53000) > libm.so.6 =3D> /lib/libm.so.6 (0xb7e2c000) > libgcc_s.so.1 =3D> /lib/libgcc_s.so.1 (0xb7e0e000) > libc.so.6 =3D> /lib/libc.so.6 (0xb7cc9000) > libcrypto.so.0.9.8 =3D>=20 > /usr/lib/i686/cmov/libcrypto.so.0.9.8 (0xb7b71000) > /lib/ld-linux.so.2 (0xb7fe1000) >=20 > root@kengrome:~# /var/www/WebDNA/WebDNA.fcgi > /var/www/WebDNA/WebDNA.fcgi: error while loading shared=20 > libraries: libmysqlclient.so.15: cannot open shared object=20 > file: No such file or directory >=20 > ... and thanks for the commands that we can use to help=20 > diagnose the problem! >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 >> Ken, could you run these commands: >>=20 >> 1.) ls -l /var/www/WebDNA/WebDNA.fcgi >> 2.) ldd /var/www/WebDNA/WebDNA.fcgi >> 3.) /var/www/WebDNA/WebDNA.fcgi >>=20 >> This will tell us: >> 1.) What WebDNA.fcgi file you are running >> 2.) What libraries it is linked to >> 3.) If the executable reports any errors such as "cannot >> open shared object file", which would tell us what >> library is missing >>=20 >> thank you! >>=20 >> - chris >>=20 >> On Aug 16, 2011, at 12:38, Kenneth Grome wrote: >>>> Hi Ken! checking now with a developer. So far, WebDNA >>>> 7.0 can run with any linux version, including Ubuntu >>>> 11. It should work with Debian 6. Just give us few >>>> daytime hours :-) >>>>=20 >>>> WebDNA 7.0 will run with any linux version, we just >>>> need to know if it is a 32bit or 64bit, if it is a >>>> glibcv2 (Fedora, Red Hat, CentOS..) or glibcv3 >>>> (Debian, Ubutuntu...) and finally, Ubuntu 10 or 11 >>>> will request a specific libmysql. >>>=20 >>> Hi Chris, >>>=20 >>> Thanks for this info. Of course I'll give you more >>> daytime hours to help me get WebDNA working again! :) >>>=20 >>> I wonder if Debian 5 and 6 request different libmysql >>> files similar to the way Ubuntu does? >>>=20 >>> I also wonder if it might be better for WSC if you were >>> to have your developer code WebDNA so that it looks >>> for its required dependencies inside the WebDNA folder >>> from now on? Then let us create symlinks to the >>> required files in the WebDNA folder. >>>=20 >>> Wouldn't this eliminate the possibility of WebDNA >>> failing to find a dependency and then failing to start >>> if the dependency is not in the expected location, or >>> if it is but has a different name? >>>=20 >>> In Debian 5 we already need to create a symlink to >>> libssl.so.6 because the file WebDNA expects to find is >>> actually named libssl.so. But we are putting that >>> symlink in the /usr/lib/ folder rather than in the >>> WebDNA folder like this: >>>=20 >>> # ln -s /usr/lib/libssl.so /usr/lib/libssl.so.6 >>>=20 >>> All I'm suggesting here is that we create a symlink to >>> the same libssl.so file, then put it inside the WebDNA >>> folder instead of in /usr/lib/. And do the same thing >>> for all the other dependency files. >>>=20 >>> Then no matter what build we're using, WebDNA will >>> always look for required files inside the WebDNA >>> folder. And when WebDNA fails to start we can confirm >>> that it's dependencies exist (or do not exist) simply >>> by looking inside the WebDNA folder and checking to >>> see that all the required symlinks exist -- and are >>> connected to the correct original files. >>>=20 >>> Is there any reason why this would not work? >>>=20 >>> Another good change might be for the WebDNA executable >>> to have an obvious naming convention that tells us >>> which build we are actually using. For example: >>>=20 >>> WebDNAv0701b32g2.fcgi =3D version 7.1 32bit glibcv2 >>> WebDNAv0724b32g3.fcgi =3D version 7.24 32bit glibcv3 >>> WebDNAv0703b64g2.fcgi =3D version 7.3 64bit glibcv2 >>> WebDNAv0748b64g3.fcgi =3D version 7.48 64bit glibcv3 >>>=20 >>> If this were possible I might not have experienced this >>> problem in the first place, assuming I'm using the >>> wrong executable, because I would have known which one >>> to use from the beginning. >>>=20 >>> If you decide to adopt such a naming convention we can >>> just use a symlink from one of the above executables >>> to WebDNA.fcgi so that our apache / lighttpd / nginx >>> configuration does not have to change when we switch >>> from one WebDNA executable to another. >>>=20 >>> Just some thoughts for possible consideration, that's >>> all. >>>=20 >>> :) >>>=20 >>> Sincerely, >>> Kenneth Grome >>>=20 >>> P.S. I have a WebDNA.fcgi that works on my Ubuntu >>> 10.10 desktop development computer, but I'm going to >>> need one that works on Ubuntu 11 when I upgrade pretty >>> soon too, so maybe you can send me the ones for Debian >>> 6 and Ubuntu 11 when they are ready. Thanks! >>>=20 >>> ------------------------------------------------------- >>> -- This message is sent to you because you are >>> subscribed to the mailing list
. >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Ken, it seems you are using the 32-bit version. And we do not have a = 32-bit build for libmysql16: Ubuntu 10 or 11, or Debian 6 are recent OS = and we assume no recent OS runs with a 32bit processor. can you please run uname -a This way we can confirm you have a 32-bit install of the OS. - chris On Aug 16, 2011, at 13:12, Kenneth Grome wrote: > Hi Chris, >=20 > Looks like the problem is with libmysqlclient.so.15. Maybe=20 > Debian 6 uses libmysqlclient.so.16? Does this mean I'm=20 > using the wrong executable? >=20 >=20 > Here are the results you asked for: >=20 > root@kengrome:~# ls -l /var/www/WebDNA/WebDNA.fcgi > -rwxrwxr-x 1 root root 5230068 Feb 22 08:10=20 > /var/www/WebDNA/WebDNA.fcgi >=20 > root@kengrome:~# ldd /var/www/WebDNA/WebDNA.fcgi > libpthread.so.0 =3D> /lib/libpthread.so.0 (0xb7fc2000) > libdl.so.2 =3D> /lib/libdl.so.2 (0xb7fbe000) > libnsl.so.1 =3D> /lib/libnsl.so.1 (0xb7fa6000) > libssl.so.0.9.8 =3D> /usr/lib/i686/cmov/libssl.so.0.9.8=20 > (0xb7f5c000) > libz.so.1 =3D> /usr/lib/libz.so.1 (0xb7f48000) > libmysqlclient.so.15 =3D> not found > libstdc++.so.6 =3D> /usr/lib/libstdc++.so.6 (0xb7e53000) > libm.so.6 =3D> /lib/libm.so.6 (0xb7e2c000) > libgcc_s.so.1 =3D> /lib/libgcc_s.so.1 (0xb7e0e000) > libc.so.6 =3D> /lib/libc.so.6 (0xb7cc9000) > libcrypto.so.0.9.8 =3D>=20 > /usr/lib/i686/cmov/libcrypto.so.0.9.8 (0xb7b71000) > /lib/ld-linux.so.2 (0xb7fe1000) >=20 > root@kengrome:~# /var/www/WebDNA/WebDNA.fcgi > /var/www/WebDNA/WebDNA.fcgi: error while loading shared=20 > libraries: libmysqlclient.so.15: cannot open shared object=20 > file: No such file or directory >=20 > ... and thanks for the commands that we can use to help=20 > diagnose the problem! >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 >> Ken, could you run these commands: >>=20 >> 1.) ls -l /var/www/WebDNA/WebDNA.fcgi >> 2.) ldd /var/www/WebDNA/WebDNA.fcgi >> 3.) /var/www/WebDNA/WebDNA.fcgi >>=20 >> This will tell us: >> 1.) What WebDNA.fcgi file you are running >> 2.) What libraries it is linked to >> 3.) If the executable reports any errors such as "cannot >> open shared object file", which would tell us what >> library is missing >>=20 >> thank you! >>=20 >> - chris >>=20 >> On Aug 16, 2011, at 12:38, Kenneth Grome wrote: >>>> Hi Ken! checking now with a developer. So far, WebDNA >>>> 7.0 can run with any linux version, including Ubuntu >>>> 11. It should work with Debian 6. Just give us few >>>> daytime hours :-) >>>>=20 >>>> WebDNA 7.0 will run with any linux version, we just >>>> need to know if it is a 32bit or 64bit, if it is a >>>> glibcv2 (Fedora, Red Hat, CentOS..) or glibcv3 >>>> (Debian, Ubutuntu...) and finally, Ubuntu 10 or 11 >>>> will request a specific libmysql. >>>=20 >>> Hi Chris, >>>=20 >>> Thanks for this info. Of course I'll give you more >>> daytime hours to help me get WebDNA working again! :) >>>=20 >>> I wonder if Debian 5 and 6 request different libmysql >>> files similar to the way Ubuntu does? >>>=20 >>> I also wonder if it might be better for WSC if you were >>> to have your developer code WebDNA so that it looks >>> for its required dependencies inside the WebDNA folder >>> from now on? Then let us create symlinks to the >>> required files in the WebDNA folder. >>>=20 >>> Wouldn't this eliminate the possibility of WebDNA >>> failing to find a dependency and then failing to start >>> if the dependency is not in the expected location, or >>> if it is but has a different name? >>>=20 >>> In Debian 5 we already need to create a symlink to >>> libssl.so.6 because the file WebDNA expects to find is >>> actually named libssl.so. But we are putting that >>> symlink in the /usr/lib/ folder rather than in the >>> WebDNA folder like this: >>>=20 >>> # ln -s /usr/lib/libssl.so /usr/lib/libssl.so.6 >>>=20 >>> All I'm suggesting here is that we create a symlink to >>> the same libssl.so file, then put it inside the WebDNA >>> folder instead of in /usr/lib/. And do the same thing >>> for all the other dependency files. >>>=20 >>> Then no matter what build we're using, WebDNA will >>> always look for required files inside the WebDNA >>> folder. And when WebDNA fails to start we can confirm >>> that it's dependencies exist (or do not exist) simply >>> by looking inside the WebDNA folder and checking to >>> see that all the required symlinks exist -- and are >>> connected to the correct original files. >>>=20 >>> Is there any reason why this would not work? >>>=20 >>> Another good change might be for the WebDNA executable >>> to have an obvious naming convention that tells us >>> which build we are actually using. For example: >>>=20 >>> WebDNAv0701b32g2.fcgi =3D version 7.1 32bit glibcv2 >>> WebDNAv0724b32g3.fcgi =3D version 7.24 32bit glibcv3 >>> WebDNAv0703b64g2.fcgi =3D version 7.3 64bit glibcv2 >>> WebDNAv0748b64g3.fcgi =3D version 7.48 64bit glibcv3 >>>=20 >>> If this were possible I might not have experienced this >>> problem in the first place, assuming I'm using the >>> wrong executable, because I would have known which one >>> to use from the beginning. >>>=20 >>> If you decide to adopt such a naming convention we can >>> just use a symlink from one of the above executables >>> to WebDNA.fcgi so that our apache / lighttpd / nginx >>> configuration does not have to change when we switch >>> from one WebDNA executable to another. >>>=20 >>> Just some thoughts for possible consideration, that's >>> all. >>>=20 >>> :) >>>=20 >>> Sincerely, >>> Kenneth Grome >>>=20 >>> P.S. I have a WebDNA.fcgi that works on my Ubuntu >>> 10.10 desktop development computer, but I'm going to >>> need one that works on Ubuntu 11 when I upgrade pretty >>> soon too, so maybe you can send me the ones for Debian >>> 6 and Ubuntu 11 when they are ready. Thanks! >>>=20 >>> ------------------------------------------------------- >>> -- This message is sent to you because you are >>> subscribed to the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
christophe.billiottet@webdna.us
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Server Error Question (2004)
Protect (1997)
Multiple catalog databases and showcart (1997)
Problems getting parameters passed into email. (1997)
Problem with formatting dates stored in db (2003)
trouble updating records in database (1998)
The List is Changing (1997)
Showif, Hideif reverse logic ? (1997)
WebCat2b15MacPlugin - showing [math] (1997)
WebCat2b15MacPlugin - showing [math] (1997)
Web Developer Product Awards (1997)
Bug Report, maybe (1997)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
Email notification to one of multiple vendors ? (1997)
Strange Search Results (2004)
Displaying photo attached to first record (1997)
rename a file (1997)
Adding Header Values with [SetHeader] (1998)
Subject: Authenticating users without dialog box (1997)
Shipping.db (1998)