Re: extrange problem with star
Posted in 2003
Gustavo Tobares wrote:
> Some aditional information:
>
> The problem is present when the engine is started from "informix"
> account. If I shutdown the engine and startup from "root" account, they
> work without problems...
Screw-ball permissions? Check that the SUID root programs are SUID
root. And check that your file system isn't mounted with SUID disabled.
> By now, I solve the problem bringin up the engine from "root", not
> from "informix", but I'm still confused for these behaviour.
>
> Thank's
>
> Gustavo Tobares
> Administrador de Sistemas y DBA
> Centro de Computos - Red Megatone
> TE: 0342-4500972 - Fax: 0342-4500940
>
>
>
> -----Mensaje original-----
> De: Jonathan Leffler [mailto:jleffler@earthlink.net]
> Enviado el: Jueves, 22 de Mayo de 2003 12:42 a.m.
> Para: informix-list@iiug.org
> Asunto: Re: extrange problem with star
>
>
> Gustavo Tobares wrote:
>
>> Im using remote conections from a Server A (solaris 8, informix
>>7.31.UD1) to an other server B (SCO Unix 5.0.5, informix 5.10.UC1)
>>
>> The conection between both server is working
>>
>> Connected (loged) in the server A,
>>
>> case 1) I run dbaccess, select a database "datos" and
>>execute the next sql statement:
>>
>> select * from base@confdb:printers>>
>> The sql work showing the results...
>>
>> base is the name of a database on the server B
>> confdb is the name of the "star" conection.
>>
>> Then, I run the next sql statement
>>
>> select * from confina@confdb:clientes>>
>> they show the results....
>>
>> case 2) I exit from dbaccess, run it again, select the
>>database "datos" and try to run the next sql
>>
>> select * from confina@confdb:clientes (witch work in case 1)>>
>> they show
>>
>> 936: Error on remote connection, confdb, conerr=-25582, oserr=8,
>>errstr=.>>
>> If I runn the case 1 again, still work.
>>
>>
>>Some idea? thank's
>
>
>
> Pretty weird. oserr = 8 => ENOEXEC, which might mean that there is a
> problem with some program being in the wrong format. I'm not sure why
> that would be happening every other time - I'm clutching at straws
> here. Any chance you have two sqlexecd processes running, and one has
> the wrong configuration? I don't think it should be possible, but
> then neither should the scenario you're seeing, yet you are seeing it.
>
>
>>Gustavo Tobares
>>Administrador de Sistemas y DBA
>>Centro de Computos - Red Megatone
>>TE: 0342-4500972 - Fax: 0342-4500940
>>
>
>
>
>
--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/