Error Registering With Staf 21
Contents |
Test Automation Framework Brought to you by: crankin_work, dave2268, slucas Summary Files Reviews Support Wiki Mailing Lists Tickets ▾ Bugs Feature Requests Patches Support Requests News Discussion Code Create error registering with staf rc 21 linux Topic Stats Graph Forums Help 2322 Open Discussion 453 Help Formatting Help
Error Registering With Staf Rc 21 Windows
staf local RC 21 - but works fine from remote Forum: Help Creator: Karin Steckler Created: 2011-12-13 Updated: 2013-06-12
Staf Ping
Karin Steckler - 2011-12-13 Starting STAFProc works fine staf
Staf Process Start Shell Command Example
STAF348-setup-winamd64.exe installed on windows 64-bit Selected tcpip protocol ipv4_ipv6 as both are confgured on the system Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::c5f2:5ef3:c53d:dce4%10 IPv4 Address. . . . . . . . . . . : 9.152.122.64 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway staf rc 16 . . . . . . . . . : 9.152.122.1 tried with different PROTOCOL settings for tcp interface but nothing helped. Using default STAF instance "STAF" - was set as STAF/Config/InstanceName during installation STAF/Env/STAF_INSTANCE_NAME was missing after installation but also setting this variable doesn't solve the problem. ping localhost gives back -> Reply from ::1: time<1ms ping localhost -4 gives back -> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 what else can I check? If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Sharon Lucas - 2011-12-18 The problem is one that only the "local" interface for STAF is having (which is why using the STAF TCP interfaces work fine - and would work if you specified the local machine's host name or IP address). The reason the "local" interface is failing with RC 21 is probably due to a configuration issue. Note that you should never set/change a STAF variable (like STAF/Config/InstanceName) that is set by STAF based on the environment when STAFProc is started. Instead, you should set environment variable
Test Automation Framework Brought to you by: crankin_work, dave2268, slucas Summary Files Reviews Support Wiki Mailing Lists Tickets ▾ Bugs Feature Requests Patches Support Requests News Discussion Code Create Ticket View Stats Group staf insufficient trust level All Next Unix Unix::Linux Unix::Solaris Win32 Win32::Win2000 Win32::Win2003 Searches Changes Closed Tickets Open staf fs copy file example Tickets STAX bugs Sharon's Bugs Help Formatting Help #970 RC 21 when STAFProc really is running Milestone: Unix Status: closed-fixed how to check if staf is running on linux Owner: Sharon Lucas Labels: STAFProc (180) Priority: 5 Updated: 2014-08-26 Created: 2007-06-22 Creator: Sharon Lucas Private: No Occasionally we've seen a problem where any request submitted on a local machine returns a RC https://sourceforge.net/p/staf/discussion/104046/thread/be02bd77/ 21 (STAF Not Running) when STAFProc really is running and when using the correct STAF_INSTANCE_NAME env variable. C:\>staf local ping ping Error submitting request, RC: 21 C:\>staf staf1d ping ping Error submitting request, RC: 21 Other machines running STAF can successfully ping the machine. C:\>staf staf1d ping ping Response -------- PONG We've seen this problem on a Windows 2003 machine (staf1d) and on a Linux machine (staf1e). https://sourceforge.net/p/staf/bugs/970/ Both were running STAF V3.2.2. Added some debug code to stafif/STAF.cpp so that if the connect fails with a STAF exception, if you set the STAF_DEBUG_RC_21 environment variable to something, it will cout some additional information about the STAF exception. Here's a cvs diff of the debug changes: Index: stafif/STAF.cpp RCS file: /cvsroot/staf/src/staf/stafif/STAF.cpp,v retrieving revision 1.12 diff -r1.12 STAF.cpp 104c104 < catch (STAFConnectionProviderException) --- > catch (STAFConnectionProviderException &se) 105a106,113 > // Added to debug a problem where get RC 21 (STAF Not Running) > // submitting any request on the local machine, but other machines > // running STAF can successfully ping the machine. > > if (getenv("STAF_DEBUG_RC_21") != NULL) > cout << "STAF::makeConnection - STAFConnectionProviderException: " > << se.getText() << " RC=" << se.getErrorCode() << endl; > 109a118,121 > if (getenv("STAF_DEBUG_RC_21") != NULL) > cout << "STAF::makeConnection - STAFException: " > << se.getText() << " RC=" << se.getErrorCode() << endl; > 114a127,129 > if (getenv("STAF_DEBUG_RC_21") != NULL) > cout << "STAF::makeConnection - Unknown exception: " << endl; > Discussion Sharon Lucas - 2007-06-22 Logged In: YES user_id=285070 Originator: YES Recreated the problem by running David's security job (C:\automation\staf1d.xml on staf1f) and here's the exception information whic
You've searched the web, and everyone http://wordpress.hypergumbo.com/archives/407 says, "start staf", and you say "staf is already https://www.mail-archive.com/staf-users@lists.sourceforge.net/msg02141.html running, see this ping from a remote box?". So, how long as your staf been up? I ran into the problem on one of our boxes recently, and discovered our STAFProc had been running for 270 odd days. error registering Restarting him seems to have resolved our issues; now able to ping remote and local. UPDATE2: How to restart staf? The recommended way is to (as root, or sudo) run /usr/local/staf/startSTAFProc.sh The script handles setting up environment variables needed by the staf daemon, and redirects output to error registering with a nohup file, and is should be part of your staf install. If you are on a Sparc Solaris box, you may find staf crashes randomly anyways. As of yet, no solution to that problems has been found. Wrote a simple shell script that uses pgrep to see if STAFProc is no longer running, and calls startSTAFProc if it's not. Just make sure you have core files set to overwrite, or you'll soon run out of room, as each crash seems to come with one. Tags: staf This entry was posted on Thursday, March 19th, 2009 at 9:13 am and is filed under tech stuff. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed. Comments are closed. Hyper Gumbo is proudly powered by WordPress Entries (RSS) and Comments (RSS).
bits). I configured it and I can see it in # STAF local service list. However when I am trying to send any email its showing the error message. below is the command what I am using and highlighted one is the error which I am getting. C:\STAF>STAF local EMAIL SEND TO xx...@xxx.com message "Testcase aborted wi th error code 5312." SUBJECT "Testcase aborted" AUTHUSER x...@xxx.com AUTH PASSWORD xxxxxxxxxxx Error submitting request, RC: 4504 Additional info --------------- 504 5.7.4 Unrecognized authentication type Could you please correct me, if I am doing any mistake? Thanks, Ratikant On Wed, Jan 30, 2013 at 7:10 PM, Ratikant Singh