04-22-2015
Trying to pass a password: bash: syntax error near unexpected token `('
howdy,
so I'm make a plugin work for Nagios, and the commandline is:
/usr/lib/nagios/plugins/check_mssql -H MySQLServerName -u MySqlAccountName -p MyPassword(#XXXXX -d MyDatabaseName
it is barfing with:
bash: syntax error near unexpected token `('
Thoughts?
Do I have to wrap something around these freakish characters?
Peace,
Rich
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I'm getting the following error:
line 21: syntax error near unexpected token `done`
line 21: `done`
and I haven't been able to figure out why.
Here is my code
#!/bin/sh
if ; then
echo 'Usage: rename getexp/replStr '
exit 0
fi
arg = $1
shift
while ; do (5 Replies)
Discussion started by: NullPointer
5 Replies
2. UNIX for Advanced & Expert Users
Hi,
When I run the below shell script I'm getting the error " syntax error near unexpected token `"
Script:
REM :: File Name : Refresh_OTL.bat
REM :: Parameters : %1 - Region
REM :: : %2 - Cube Type
REM :: :
REM :: Notes :
REM ============================== set ENVIRONMENT... (2 Replies)
Discussion started by: tomailraj
2 Replies
3. Shell Programming and Scripting
Hi all,
Here is a simple script that is working in one server and is giving a syntax error in other server. Can somebody help me ?
#!/bin/bash
# ftp files
done < $file
errors:
I tried..with no success:
if ; then (21 Replies)
Discussion started by: Lenora2009
21 Replies
4. Shell Programming and Scripting
Hi all,
This is a script which converts hex to bin. However am finding an error while executing
syntax error near unexpected token `='
`($hexfile, $binfile) = @ARGV;'
I am running using ./fil.pl <hexfile> <binfile>
###################################################
#
# this script... (3 Replies)
Discussion started by: jaango123
3 Replies
5. Homework & Coursework Questions
1. The problem statement, all variables and given/known data:
line 37: syntax error near unexpected token 'else'
line 37: ' else'
the script is made to take 1 or 2 command line arguments however i get the above stated error when trying to process it. This happens with or without arguments... (6 Replies)
Discussion started by: Ren_kun
6 Replies
6. Shell Programming and Scripting
Hi,
I am trying to read the session log through script. But it keeps showing me some error near. I have tried everything. Even tried converting the script using sed command to remove the hidden characters(\r).But nothing seems to be working.Below is the script :
#!/bin/bash
cd... (6 Replies)
Discussion started by: Aryan12345
6 Replies
7. Shell Programming and Scripting
I tried to execute the code but I got this error
./Array.c: line 9: syntax error near unexpected token '('
./Array.c: line 9: ' nvals = get_data(a,MAXARRAY);'
and
#include<stdio.h>
#define MAXARRAY 1000
main()
{
int a,
nvals;
nvals =... (7 Replies)
Discussion started by: sgradywhite
7 Replies
8. Shell Programming and Scripting
// AIX 6.1
I am getting a syntax error below. Please advise what to be corrected. :confused:
runmqsc CERN.$(echo `hostname` | cut -d'.' -f1 | tr '' '').$(echo $environment | tr '' '') <<! | egrep -i '(FROM.NC.APPLIANCE)' | sort -u |awk '{print $2}' | cut -d '(' -f2 | cut -d ')' -f1 |... (1 Reply)
Discussion started by: Daniel Gate
1 Replies
9. Shell Programming and Scripting
Hello every one!!
I don't know where I am going wrong but I am finding it difficult to clear this error of syntax error near unexpected token `else'
I am writing a simple shell script to find a file in a directory and if found execute that else return an error to the log file
... (14 Replies)
Discussion started by: masubram
14 Replies
10. UNIX for Beginners Questions & Answers
Hello all,
Please i have this command i used to zip different files in differents directory, but i have an error. Note that when i run the command in one directory it works fine.
/X5/WORK/BGH/INV/REG/pdf/SEND/BGH12523/1/*.fo
/X5/WORK/BGH/INV/REG/pdf/SEND/BGH24523/1/*.fo... (3 Replies)
Discussion started by: gillesi
3 Replies
LEARN ABOUT DEBIAN
collectd-nagios
COLLECTD-NAGIOS(1) collectd COLLECTD-NAGIOS(1)
NAME
collectd-nagios - Nagios plugin for querying collectd
SYNOPSIS
collectd-nagios -s socket -n value_spec -H hostname [options]
DESCRIPTION
This small program is the glue between collectd and nagios. collectd collects various performance statistics which it provides via the
"unixsock plugin", see collectd-unixsock(5). This program is called by Nagios, connects to the UNIX socket and reads the values from
collectd. It then returns OKAY, WARNING or CRITICAL depending on the values and the ranges provided by Nagios.
ARGUMENTS AND OPTIONS
The following arguments and options are required and understood by collectd-nagios. The order of the arguments generally doesn't matter, as
long as no argument is passed more than once.
-s socket
Path of the UNIX socket opened by collectd's "unixsock plugin".
-n value_spec
The value to read from collectd. The argument is in the form "plugin[-instance]/type[-instance]".
-H hostname
Hostname to query the values for.
-d data_source
Each value_spec may be made of multiple "data sources". With this option you can select one or more data sources. To select multiple
data sources simply specify this option again. If multiple data sources are examined they are handled according to the consolidation
function given with the -g option.
-g none|average|sum
When multiple data sources are selected from a value spec, they can be handled differently depending on this option. The values of the
following meaning:
none
No consolidation if done and the warning and critical regions are applied to each value independently.
average
The warning and critical ranges are applied to the average of all values.
sum The warning and critical ranges are applied to the sum of all values.
percentage
The warning and critical ranges are applied to the ratio (in percent) of the first value and the sum of all values. A warning is
returned if the first value is not defined or if all values sum up to zero.
-c range
-w range
Set the critical (-c) and warning (-w) ranges. These options mostly follow the normal syntax of Nagios plugins. The general format is
"min:max". If a value is smaller than min or bigger than max, a warning or critical status is returned, otherwise the status is
success.
The tilde sign (~) can be used to explicitly specify infinity. If ~ is used as a min value, negative infinity is used. In case of max,
it is interpreted as positive infinity.
If the first character of the range is the at sign (@), the meaning of the range will be inverted. I. e. all values within the range
will yield a warning or critical status, while all values outside the range will result in a success status.
min (and the colon) may be omitted, min is then assumed to be zero. If max (but not the trailing colon) is omitted, max is assumed to
be positive infinity.
-m If this option is given, "Not a Number" (NaN) is treated as critical. By default, the none consolidation reports NaNs as warning. Other
consolidations simply ignore NaN values.
RETURN VALUE
As usual for Nagios plugins, this program writes a short, one line status message to STDOUT and signals success or failure with it's return
value. It exits with a return value of 0 for success, 1 for warning and 2 for critical. If the values are not available or some other error
occurred, it returns 3 for unknown.
SEE ALSO
collectd(1), collectd.conf(5), collectd-unixsock(5), <http://nagios.org/>
AUTHOR
Florian Forster <octo at verplant.org>
5.1.0 2012-04-02 COLLECTD-NAGIOS(1)