Re: [hobbit] dbcheck for RAC connections refused

["Xymon User in Richmond" <hobbit (at) epperson.homelinux.net>]

On Wed, July 29, 2009 15:29, martin.flemming (at) desy.de wrote:
>
> Hi !
>
> I want to use dbcheck.pl from
>
> http://sourceforge.net/projects/hobbit-perl-cl/
>
> .. but unfortunatley something is going wrong, i get only
> "Connection Refused" Messages and no data  .. :-(
>
> My config is below:
[SNIP]
>
> dbcheck.ini:
>
> oraclehome              = /opt/products/oracle-client/10.2g/
> username                = XXXX
> password                = XXXXXXXXXXXXXXXXXXXXXXX
>
>
> [atlas_tag_db]
> dbtype                  = Oracle
> oraclerac               = yes
> hostname                = lcg3d-a-v-4   # hostname of the rac instance n.2
> sid                     = atlas_tag_db  # sid of the rac instance n.2
> port                    = 1521          # port of listener on rac instance
> n.2
> username                = XXXX
> password                = XXXXXXXXXXXX
>
> [atlast1]
> dbtype                  = Oracle
> hostname                = lcg3d-a-v-1   # hostname of the rac instance n.2
> sid                     = atlast1       # sid of the rac instance n.2
> port                    = 1521          # port of listener on rac instance
> n.2
> username                = XXXX
> password                = XXXXXXXXXXX
>
> [atlast2]
> dbtype                  = Oracle
> hostname                = lcg3d-a-v-2   # hostname of the rac instance n.2
> sid                     = atlast2       # sid of the rac instance n.2
> port                    = 1521          # port of listener on rac instance
> n.2
> username                = XXXXX
> password                = XXXXXXXXXXXXXXX
>
>
> [atlast3]
> dbtype                  = Oracle
> hostname                = lcg3d-a-v-3   # hostname of the rac instance n.2
> sid                     = atlast3       # sid of the rac instance n.2
> port                    = 1521          # port of listener on rac instance
> n.2
> username                = XXXXXX
> password                = XXXXXXXXXXXXXXXX
>
> [atlast4]
> dbtype                  = Oracle
> hostname                = lcg3d-a-v-4   # hostname of the rac instance n.2
> sid                     = atlast4       # sid of the rac instance n.2
> port                    = 1521          # port of listener on rac instance
> n.2
> username                = XXXXXXXX
> password                = XXXXXXXXXXXXXXXXXXX
>
[SNIP]
> Errors
> No General Errors
> atlas_tag_db
> Wed Jul 29 18:52:47 2009:ERROR: Timeout connecting to
> DBI:Oracle:host=lcg3d-a-v-4   # hostname of the rac instance n.2;port=1521
> # port of listener on rac instance n.2;sid=atlas_tag_db  # sid of the rac
> instance n.2!
> atlast1
> Wed Jul 29 18:52:47 2009:ERROR: Timeout connecting to
> DBI:Oracle:host=lcg3d-a-v-1   # hostname of the rac instance n.2;port=1521
> # port of listener on rac instance n.2;sid=atlast1       # sid of the rac
> instance n.2!
> atlast2
> Wed Jul 29 18:52:47 2009:ERROR: Timeout connecting to
> DBI:Oracle:host=lcg3d-a-v-2   # hostname of the rac instance n.2;port=1521
> # port of listener on rac instance n.2;sid=atlast2       # sid of the rac
> instance n.2!
> atlast3
> Wed Jul 29 18:52:47 2009:ERROR: Timeout connecting to
> DBI:Oracle:host=lcg3d-a-v-3   # hostname of the rac instance n.2;port=1521
> # port of listener on rac instance n.2;sid=atlast3       # sid of the rac
> instance n.2!
> atlast4
> Wed Jul 29 18:52:47 2009:ERROR: Timeout connecting to
> DBI:Oracle:host=lcg3d-a-v-4   # hostname of the rac instance n.2;port=1521
> # port of listener on rac instance n.2;sid=atlast4       # sid of the rac
> instance n.2!
>
> Warnings
> No General Warnings
> No Hosts Warnings
>
>
> dbcheck.pl version 1.08 - column dbcheck lifetime 60, tested in ~ 00:00:01
> (max 00:02:00)
>
> I use the old and also the new version of dbcheck.pl ...
>
> Any idea why could my enviroment be damaged ?

I don't use this code, but your error output suggests that it's trying to
use your hostname, sid, and port from dbcheck.ini exactly as written,
comments and all.  I don't see anything in the sample dbcheck.ini file
that suggests that you can use trailing comments in the way that you are
doing, so perhaps you should try without those.