It was still called Foxray when I left here last - Killed?

[Joseph Riccardi]

Foxray Folks,

 

Below is the history of my problem sent to the fox...@freelists.org.  No solution yet so trying here...

 

I'm trying to repair the Foxray installations here.  I discovered that the host AW51E on the UNIX Node was restored from a tape that did not have Foxray installed so obviously all Foxray files were wiped out including changes to cron.  I believe I have restored all Foxray files and revised cron accordingly.  My next step was to manually run the individual command lines in all of the *collect.sh scripts.  However, as I execute them all the system response each time is "Killed".  I have never seen this response before so I am at a loss as for what is wrong.  

 

Can anyone explain what this 'Killed' response means?  Is it a UNIX or Foxray response?

 

Thanks

 

Joseph M. Riccardi

386-451-7607 Cell

 

J...@eRiccardi.com

 

"To give real service you must add something that cannot be bought or measured with money; and that is sincerity and integrity." - Donald A. Adams

[Ricardo Abech]

Can you send me a screenshot? You just get a message saying killed?

Can you confirm you moved the BINARY files (no extension) as BIN and the ASCII as ASCII (you can VI the foxray.icc and foxray.ftp to check).

This may be related to this. Also make sure you made all executable active with CHMOD +X

Thanks

Ricardo

--
You received this message because you are subscribed to the Google Groups "LimeWare foxray™" group.
To unsubscribe from this group and stop receiving emails from it, send an email to limeware-foxr...@googlegroups.com.
To post to this group, send email to limewar...@googlegroups.com.
Visit this group at https://groups.google.com/group/limeware-foxray.
For more options, visit https://groups.google.com/d/optout.

[Joseph Riccardi]

Ricardo, the Cavalry has arrived!  :-) YEA!!!

Can you send me a screenshot? 

I will attach some to follow.  The easiest way for me is to reply to my email from my iPhone as that is what I use to take pics...

You just get a message saying killed?

Yes, you can see from the pics to follow.  Just 'Killed' when I run the *collect.sh scripts or each command line individually.

Can you confirm you moved the BINARY files (no extension) as BIN and the ASCII as ASCII (you can VI the foxray.icc and foxray.ftp to check).

The engineer that moved the backed up files to the AW used an office computer we always use to transfer files via Hummingbird Neighborhood FTP.  I believe that is what I also used when I originally set Foxray up.  It is supposed to transfer as BIN and ASCII as required; no?  I checked both Foxray files in vi and they look fine, no extraneous or gobbledygook characters.

This may be related to this. Also make sure you made all executable active with CHMOD +X

Yes, you can see from the pics to follow. 

I have other issues with keeping the Automated Watchdog Configuration updated.  I have traced data through the collect and import scripts and scheduled tasks but...  It is your weekend and all of this can wait until next week.  I will be around here at Genentech yet tonight for a couple of hours and I am here for 1 more week.

Thanks

Joe

--

Joseph M. Riccardi

386-451-7607

[Joseph Riccardi]

On Fri, Sep 28, 2018 at 5:25 PM Joseph Riccardi <jricca...@gmail.com> wrote:

[Joseph Riccardi]

On Fri, Sep 28, 2018 at 5:25 PM Joseph Riccardi <jricca...@gmail.com> wrote:

[Joseph Riccardi]

On Fri, Sep 28, 2018 at 5:25 PM Joseph Riccardi <jricca...@gmail.com> wrote:

Files were too big for gmail so sending individually. This is the 3rd pic. 

[Joseph Riccardi]

Gmail sucks but this should be the 3rd pic...

[ricardoabech]

Couple of things

Make sure you run this on VT100 directly, telnet or KSH.

The error on the 2>&1 (ambiguous output redirect) normally happe  when in an unsupported shell.

Alao the Killed messages normally are a result of lack of resources on the Box. Can you check memory, cpu etc?

Thanks Ricardo

Sent via the Samsung Galaxy S8+, an AT&T 4G LTE smartphone

[Joseph Riccardi]

Ricardo,

I am back on the 2 systems Monday...

Make sure you run this on VT100 directly, telnet or KSH.

Yes, I am always sitting in front of the AWs in VT100 mode.  

The error on the 2>&1 (ambiguous output redirect) normally happen  when in an unsupported shell.

I just tried to run the scripts as shown in the cron file.  But I also ran the *collect.sh scripts and also each command line individually as you show in the Foxray Installation Manual.  Same response in all cases; Killed.

Also the Killed messages normally are a result of lack of resources on the Box. Can you check memory, cpu etc?

I don't remember how to check memory or cpu time but all disk partitions are <60% capacity.  Someone else suggested a memory issue so I rebooted the AW and immediately tried to run the Foxray scripts again and same response; Killed.

The Foxray issues here are basically:

• The Automated Update Watchdog Configuration for both Nodes shows everything updating except the CP, Inhibited Alarms, Tags in Manual, Tuning, Historian, and Displays Modules.  
• The UNIX Node *collect.sh scripts or the individual commands cannot run because everything responds Killed.  All other scripts/commands I run outside of Foxray run OK.
• The Foxboro Network segment in the main display for both Nodes shows no Stations (WindowsNT) or Stations not connected (UNIX).
• Some other issues on the WindowsNT Node I have not sorted out yet.

Thanks

Joe

[Joseph Riccardi]

On Mon, Oct 1, 2018 at 12:11 PM Joseph Riccardi <jricca...@gmail.com> wrote:

[Joseph Riccardi]