New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger not properly catching errors on NetScaler devices in some cases #74

jathanism opened this Issue Feb 21, 2013 · 1 comment


None yet
1 participant

jathanism commented Feb 21, 2013

This command:

set service -servicestcpprofile not_going_to_work

Results in this error:

>  set service -servicestcpprofile not_going_to_work
ERROR: No such argument [-servicestcpprofile]
Usage: set service <name>@ [-IPAddress <ip_addr|ipv6_addr|*>@]
    [-maxClient <positive_integer>] [-maxReq <positive_integer>]
    [-cacheable ( YES | NO )] [-cip ( ENABLED | DISABLED )  [<cipHeader>]]
    [-usip ( YES | NO )] [-useproxyport ( YES | NO )] [-sc ( ON | OFF )]
    [-sp ( ON | OFF )] [-rtspSessionidRemap ( ON | OFF )] [-healthMonitor ( YES | NO )]
    [-cltTimeout <secs>] [-svrTimeout <secs>] [-serverID <positive_integer>]
    [-CKA ( YES | NO )] [-TCPB ( YES | NO )] [-CMP ( YES | NO )]
    [-maxBandwidth <positive_integer>] [-accessDown ( YES | NO )]
    [-monThreshold <positive_integer>] [-weight <positive_integer>  <monitorName>]
    [-downStateFlush ( ENABLED | DISABLED )] [-tcpProfileName <string>]
    [-httpProfileName <string>] [-hashId <positive_integer>] [-comment <string>]
    [-appflowLog ( ENABLED | DISABLED )]

Trigger only detects NetScaler errors if they start with ERROR:. This needs to be improved.


This comment has been minimized.


jathanism commented Feb 21, 2013

In the case where the NetScaler CLI is trying to be more "helpful", it's not parsing this result properly and falling back to a CommandTimeout.

@jathanism jathanism closed this in fa69209 Mar 5, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment