dbTalk Databases Forums  

[Info-Ingres] Wierd error of the week -- I win!

comp.databases.ingres comp.databases.ingres


Discuss [Info-Ingres] Wierd error of the week -- I win! in the comp.databases.ingres forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Martin Bowes
 
Posts: n/a

Default [Info-Ingres] Wierd error of the week -- I win! - 09-28-2010 , 03:59 AM






Hi All,

I'm running on II 9.2.1 (a64.lnx/103)NPTL + 13904. This also occurs on II 10.0.0 (a64.lnx/127)NPTL

I've just been developed a test case for a lovely little issue. See attached.

It is safe (AFAICT) to execute the program. It doesn't crash the installation.

Essentially the problem is this....

If a terminal monitor script uses \shell to execute a program indicated by ING_SHELL and that program uses ssh then even though the ING_SHELL script is successful and returns to the calling terminal monitor script and it starts to execute from the first line after the \shell...it will fail without error about 4000 characters later...

Sweet or what?

Martin Bowes



This part of mail contained an attachment with prohibited file name:

MIME type: application/octet-stream
File name: test_case.sh
File size: 7.08 kB


The attachment was removed by Kerio Connect 7.0.2
at secure1.fndtn.com.

Reply With Quote
  #2  
Old   
Ingres Forums
 
Posts: n/a

Default Re: [Info-Ingres] Wierd error of the week -- I win! - 09-28-2010 , 04:21 AM






Looks like something to do with stdin redirection? Using "ssh -n" works
ok (provided keys are set up so that interactively entering a password
isn't required).


--
geraintjones

Reply With Quote
  #3  
Old   
Ian Kirkham
 
Posts: n/a

Default Re: [Info-Ingres] Wierd error of the week -- I win! - 09-28-2010 , 04:35 AM



Hi Marty,

I've seen similar behavior with ssh outside of Ingres which might be
related to your problem. The problem for me was that my ssh application
was connecting into a host which had some awkward commands executed in
the .profile that I identified as being the problem. From recollection,
I needed to identify that it was an ssh command coming in and diverting
the .profile execution from running the problem command - this might
have been a terminal inquiry command.

Regards,

Ian



________________________________

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of
Martin Bowes
Sent: 28 September 2010 09:59
To: Ingres and related product discussion forum
Subject: [Info-Ingres] Wierd error of the week -- I win!



Hi All,



I'm running on II 9.2.1 (a64.lnx/103)NPTL + 13904. This also occurs on
II 10.0.0 (a64.lnx/127)NPTL



I've just been developed a test case for a lovely little issue. See
attached.



It is safe (AFAICT) to execute the program. It doesn't crash the
installation.



Essentially the problem is this....



If a terminal monitor script uses \shell to execute a program indicated
by ING_SHELL and that program uses ssh then even though the ING_SHELL
script is successful and returns to the calling terminal monitor script
and it starts to execute from the first line after the \shell...it will
fail without error about 4000 characters later...



Sweet or what?



Martin Bowes

Reply With Quote
  #4  
Old   
Martin Bowes
 
Posts: n/a

Default Re: [Info-Ingres] Wierd error of the week -- I win! - 09-28-2010 , 05:47 AM



Hi All,

Geraint and Ian were right, using ssh -n does solve the problem
....And here is the script seeing as how I can't attach a .sh program

Marty
#! /bin/sh

export ING_SHELL=/tmp/temp.sh
cat - > $ING_SHELL <<ENDSHELL
# This should use ssh -n, but doesn't
ssh 127.0.0.1 date '+%Y%m%d'
ps -f
ENDSHELL

chmod 755 $ING_SHELL

sql iidbdb <<SQL_END
set autocommit on;
\p\g
\shell
select '0000';\p\g -- 8901234567890123456789012345
select '0050';\p\g -- 8901234567890123456789012345
select '0100';\p\g -- 8901234567890123456789012345
select '0150';\p\g -- 8901234567890123456789012345
select '0200';\p\g -- 8901234567890123456789012345
select '0250';\p\g -- 8901234567890123456789012345
select '0300';\p\g -- 8901234567890123456789012345
select '0350';\p\g -- 8901234567890123456789012345
select '0400';\p\g -- 8901234567890123456789012345
select '0450';\p\g -- 8901234567890123456789012345
select '0500';\p\g -- 8901234567890123456789012345
select '0550';\p\g -- 8901234567890123456789012345
select '0600';\p\g -- 8901234567890123456789012345
select '0650';\p\g -- 8901234567890123456789012345
select '0700';\p\g -- 8901234567890123456789012345
select '0750';\p\g -- 8901234567890123456789012345
select '0800';\p\g -- 8901234567890123456789012345
select '0850';\p\g -- 8901234567890123456789012345
select '0900';\p\g -- 8901234567890123456789012345
select '0950';\p\g -- 8901234567890123456789012345
select '1000';\p\g -- 8901234567890123456789012345
select '1050';\p\g -- 8901234567890123456789012345
select '1100';\p\g -- 8901234567890123456789012345
select '1150';\p\g -- 8901234567890123456789012345
select '1200';\p\g -- 8901234567890123456789012345
select '1250';\p\g -- 8901234567890123456789012345
select '1300';\p\g -- 8901234567890123456789012345
select '1350';\p\g -- 8901234567890123456789012345
select '1400';\p\g -- 8901234567890123456789012345
select '1450';\p\g -- 8901234567890123456789012345
select '1500';\p\g -- 8901234567890123456789012345
select '1550';\p\g -- 8901234567890123456789012345
select '1600';\p\g -- 8901234567890123456789012345
select '1650';\p\g -- 8901234567890123456789012345
select '1700';\p\g -- 8901234567890123456789012345
select '1750';\p\g -- 8901234567890123456789012345
select '1800';\p\g -- 8901234567890123456789012345
select '1850';\p\g -- 8901234567890123456789012345
select '1900';\p\g -- 8901234567890123456789012345
select '1950';\p\g -- 8901234567890123456789012345
select '2000';\p\g -- 8901234567890123456789012345
select '2050';\p\g -- 8901234567890123456789012345
select '2100';\p\g -- 8901234567890123456789012345
select '2150';\p\g -- 8901234567890123456789012345
select '2200';\p\g -- 8901234567890123456789012345
select '2250';\p\g -- 8901234567890123456789012345
select '2300';\p\g -- 8901234567890123456789012345
select '2350';\p\g -- 8901234567890123456789012345
select '2400';\p\g -- 8901234567890123456789012345
select '2450';\p\g -- 8901234567890123456789012345
select '2500';\p\g -- 8901234567890123456789012345
select '2550';\p\g -- 8901234567890123456789012345
select '2600';\p\g -- 8901234567890123456789012345
select '2650';\p\g -- 8901234567890123456789012345
select '2700';\p\g -- 8901234567890123456789012345
select '2750';\p\g -- 8901234567890123456789012345
select '2800';\p\g -- 8901234567890123456789012345
select '2850';\p\g -- 8901234567890123456789012345
select '2900';\p\g -- 8901234567890123456789012345
select '2950';\p\g -- 8901234567890123456789012345
select '3000';\p\g -- 8901234567890123456789012345
select '3050';\p\g -- 8901234567890123456789012345
select '3100';\p\g -- 8901234567890123456789012345
select '3150';\p\g -- 8901234567890123456789012345
select '3200';\p\g -- 8901234567890123456789012345
select '3250';\p\g -- 8901234567890123456789012345
select '3300';\p\g -- 8901234567890123456789012345
select '3350';\p\g -- 8901234567890123456789012345
select '3400';\p\g -- 8901234567890123456789012345
select '3450';\p\g -- 8901234567890123456789012345
select '3500';\p\g -- 8901234567890123456789012345
select '3550';\p\g -- 8901234567890123456789012345
select '3600';\p\g -- 8901234567890123456789012345
select '3650';\p\g -- 8901234567890123456789012345
select '3700';\p\g -- 8901234567890123456789012345
select '3750';\p\g -- 8901234567890123456789012345
select '3800';\p\g -- 8901234567890123456789012345
select '3850';\p\g -- 8901234567890123456789012345
select '3900';\p\g -- If the bug is present it ...
select '3950';\p\g -- will fail around here ......
select '4000';\p\g -- 8901234567890123456789012345
select '4050';\p\g -- 8901234567890123456789012345
select '4100';\p\g -- 8901234567890123456789012345
select '4150';\p\g -- 8901234567890123456789012345
select '4200';\p\g -- 8901234567890123456789012345
select '4250';\p\g -- 8901234567890123456789012345
select '4300';\p\g -- 8901234567890123456789012345
select '4350';\p\g -- 8901234567890123456789012345
select '4400';\p\g -- 8901234567890123456789012345
select '4450';\p\g -- 8901234567890123456789012345
select '4500';\p\g -- 8901234567890123456789012345
select '4550';\p\g -- 8901234567890123456789012345
select '4600';\p\g -- 8901234567890123456789012345
select '4650';\p\g -- 8901234567890123456789012345
select '4700';\p\g -- 8901234567890123456789012345
select '4750';\p\g -- 8901234567890123456789012345
select '4800';\p\g -- 8901234567890123456789012345
select '4850';\p\g -- 8901234567890123456789012345
select '4900';\p\g -- 8901234567890123456789012345
select '4950';\p\g -- 8901234567890123456789012345
select 'This is the final line ...';\p\g
\q
SQL_END
-----Original Message-----
From: Ingres Forums [mailto:info-ingres (AT) kettleriverconsulting (DOT) com]
Sent: 28 September 2010 10:22
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] Wierd error of the week -- I win!


Looks like something to do with stdin redirection? Using "ssh -n" works
ok (provided keys are set up so that interactively entering a password
isn't required).


--
geraintjones


_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.