Thread: [Sqlrelay-discussion] Strange problem with sqlrsh
Brought to you by:
mused
From: Ville S. <vs...@eb...> - 2005-06-23 15:44:09
|
Hi, I'm using SQL Relay 0.36 with rudiments-0.28.2 on three different Linux machines (all web servers). I just noticed today that sqlrsh dumps core (Segmentation fault) on one of the machines. I can use PySQLRClient without any problems, it's just a problem with sqlrsh. The machine is: Red Hat Linux release 9 (Shrike) Linux 2.4.20-8rlx4smp #1 SMP Is there something I can do to find out what goes wrong? I turned debug logging on, but the problem seems to be just with sqlrsh client, not the listener or connections. I also restarted SQL Relay, but it didn't help. sqlrsh works ok in the other machines: CentOS release 3.4 (final) Linux 2.4.21-27.0.1.ELsmp #1 SMP I've compiled SQL Relay on the first machine and the installation is shared between all the machines over NFS. (If I compile it on CentOS, the C libraries differ too much and it doesn't work on the older Linux OS.) Thanks, Ville |
From: Ville S. <vs...@eb...> - 2005-06-23 16:24:00
|
Hi again, I forgot to mention that I get the usage text from sqlrsh successfully, so I haven't completely botched the compilation. ;-) $ sqlrsh usage: sqlrsh host port socket user password [script] or sqlrsh [-config configfile] -id id [script] $ sqlrsh -id web1-sysdev Segmentation fault $ sqlrsh -config /swlib/v1/etc/sqlrelay.conf -id web1-sysdev Segmentation fault Cheers, Ville On Thu, 23 Jun 2005, Ville Silventoinen wrote: > Hi, > > I'm using SQL Relay 0.36 with rudiments-0.28.2 on three different Linux > machines (all web servers). I just noticed today that sqlrsh dumps core > (Segmentation fault) on one of the machines. I can use PySQLRClient without > any problems, it's just a problem with sqlrsh. > > The machine is: > Red Hat Linux release 9 (Shrike) > Linux 2.4.20-8rlx4smp #1 SMP > > Is there something I can do to find out what goes wrong? I turned debug > logging on, but the problem seems to be just with sqlrsh client, not the > listener or connections. I also restarted SQL Relay, but it didn't help. > > sqlrsh works ok in the other machines: > > CentOS release 3.4 (final) > Linux 2.4.21-27.0.1.ELsmp #1 SMP > > I've compiled SQL Relay on the first machine and the installation > is shared between all the machines over NFS. (If I compile it on > CentOS, the C libraries differ too much and it doesn't work on the > older Linux OS.) > > > Thanks, > Ville > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Sqlrelay-discussion mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion > |
From: Firstworks/4access <dav...@fi...> - 2005-06-28 17:34:35
|
Could you run "strace sqlrsh -id web1-sysdev" and send me the output. It'll help me track down the crash. Dave dav...@fi... On Thu, 2005-06-23 at 17:23 +0100, Ville Silventoinen wrote: > Hi again, > > I forgot to mention that I get the usage text from sqlrsh successfully, so > I haven't completely botched the compilation. ;-) > > $ sqlrsh > usage: sqlrsh host port socket user password [script] > or sqlrsh [-config configfile] -id id [script] > $ sqlrsh -id web1-sysdev > Segmentation fault > $ sqlrsh -config /swlib/v1/etc/sqlrelay.conf -id web1-sysdev > Segmentation fault > > Cheers, > Ville > > > > On Thu, 23 Jun 2005, Ville Silventoinen wrote: > > > Hi, > > > > I'm using SQL Relay 0.36 with rudiments-0.28.2 on three different Linux > > machines (all web servers). I just noticed today that sqlrsh dumps core > > (Segmentation fault) on one of the machines. I can use PySQLRClient without > > any problems, it's just a problem with sqlrsh. > > > > The machine is: > > Red Hat Linux release 9 (Shrike) > > Linux 2.4.20-8rlx4smp #1 SMP > > > > Is there something I can do to find out what goes wrong? I turned debug > > logging on, but the problem seems to be just with sqlrsh client, not the > > listener or connections. I also restarted SQL Relay, but it didn't help. > > > > sqlrsh works ok in the other machines: > > > > CentOS release 3.4 (final) > > Linux 2.4.21-27.0.1.ELsmp #1 SMP > > > > I've compiled SQL Relay on the first machine and the installation > > is shared between all the machines over NFS. (If I compile it on > > CentOS, the C libraries differ too much and it doesn't work on the > > older Linux OS.) > > > > > > Thanks, > > Ville > > > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > > from IBM. Find simple to follow Roadmaps, straightforward articles, > > informative Webcasts and more! Get everything you need to get up to > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > _______________________________________________ > > Sqlrelay-discussion mailing list > > Sql...@li... > > https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Sqlrelay-discussion mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion > |
From: Ville S. <vs...@eb...> - 2005-06-29 08:11:40
|
Hi Dave, I ran strace and it looks like the problem is that the user doesn't have a home directory in the machine: open("/homes/swlib/.sqlrelay.conf", O_RDONLY) = -1 ENOENT (No such file or directory) open("/swlib/v1/etc/sqlrsh", O_RDONLY) = -1 ENOENT (No such file or directory) open("/homes/swlib/.sqlrshrc", O_RDONLY) = -1 ENOENT (No such file or directory) open("/homes/swlib/.sqlrsh_history", O_WRONLY|O_APPEND|O_CREAT, 0666) = -1 ENOENT (No such file or directory) --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ I will create a fake home directory for this user. Thanks very much for the help! Ville On Tue, 28 Jun 2005, Firstworks/4access wrote: > Could you run "strace sqlrsh -id web1-sysdev" and send me the output. > It'll help me track down the crash. > > Dave > dav...@fi... > > On Thu, 2005-06-23 at 17:23 +0100, Ville Silventoinen wrote: >> Hi again, >> >> I forgot to mention that I get the usage text from sqlrsh successfully, so >> I haven't completely botched the compilation. ;-) >> >> $ sqlrsh >> usage: sqlrsh host port socket user password [script] >> or sqlrsh [-config configfile] -id id [script] >> $ sqlrsh -id web1-sysdev >> Segmentation fault >> $ sqlrsh -config /swlib/v1/etc/sqlrelay.conf -id web1-sysdev >> Segmentation fault >> >> Cheers, >> Ville >> >> >> >> On Thu, 23 Jun 2005, Ville Silventoinen wrote: >> >>> Hi, >>> >>> I'm using SQL Relay 0.36 with rudiments-0.28.2 on three different Linux >>> machines (all web servers). I just noticed today that sqlrsh dumps core >>> (Segmentation fault) on one of the machines. I can use PySQLRClient without >>> any problems, it's just a problem with sqlrsh. >>> >>> The machine is: >>> Red Hat Linux release 9 (Shrike) >>> Linux 2.4.20-8rlx4smp #1 SMP >>> >>> Is there something I can do to find out what goes wrong? I turned debug >>> logging on, but the problem seems to be just with sqlrsh client, not the >>> listener or connections. I also restarted SQL Relay, but it didn't help. >>> >>> sqlrsh works ok in the other machines: >>> >>> CentOS release 3.4 (final) >>> Linux 2.4.21-27.0.1.ELsmp #1 SMP >>> >>> I've compiled SQL Relay on the first machine and the installation >>> is shared between all the machines over NFS. (If I compile it on >>> CentOS, the C libraries differ too much and it doesn't work on the >>> older Linux OS.) >>> >>> >>> Thanks, >>> Ville >>> >>> >>> >>> ------------------------------------------------------- >>> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >>> from IBM. Find simple to follow Roadmaps, straightforward articles, >>> informative Webcasts and more! Get everything you need to get up to >>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >>> _______________________________________________ >>> Sqlrelay-discussion mailing list >>> Sql...@li... >>> https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion >>> >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >> from IBM. Find simple to follow Roadmaps, straightforward articles, >> informative Webcasts and more! Get everything you need to get up to >> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> _______________________________________________ >> Sqlrelay-discussion mailing list >> Sql...@li... >> https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion >> > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Sqlrelay-discussion mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion > |