Nagios Support Forum

belvdr wrote:The error:

Code: Select all

The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION

means that the plugin is issuing the ROLLBACK TRANSACTION command in Transact-SQL but that requires it issuing a BEGIN TRANSACTION first. A transaction is nothing more than a set of statements you wish to occur as a group.

The following flow may help:

Code: Select all

BEGIN TRANSACTION
  <update some rows>
  <if failure>
      ROLLBACK TRANSACTION
  <else>
      COMMIT
END TRANSACTION

So, I'm guessing the plugin is not coded correctly.

That plugin is not doing anything critical that needs a transaction.
It certainly looks like an issue with coding logic.

Anyway I temporarily got around the issue by using

./check_mssql_health --server TEST -port 1433 --username monitor --password abc123 --mode connection-time 2>/dev/null
OK - 0.11 seconds to connect as monitor | connection_time=0.11;1;5

Did some looking around and I've seen this mentioned a few times in regards to this plugin, but not specifically just with connection time, usually with more in-depth checks, which would indicate the majority of users are not having the same problem... or have not reported it. Thanks for letting us know that you temporarily worked around the problem, going to continue to poke around.

slansing wrote:Did some looking around and I've seen this mentioned a few times in regards to this plugin, but not specifically just with connection time, usually with more in-depth checks, which would indicate the majority of users are not having the same problem... or have not reported it. Thanks for letting us know that you temporarily worked around the problem, going to continue to poke around.

Not familiar with Perl else would have got rid of the transactions.
Let me know if you managed to find anything on this issue.

Not coming up with much, have you tried another flag other than just connection time? Does it result in the same transaction fault as well? Do you have another mssql server you can test against?

slansing wrote:Not coming up with much, have you tried another flag other than just connection time? Does it result in the same transaction fault as well? Do you have another mssql server you can test against?

Yes, same issue with the other types of queries and other DB servers.

In the event that this is happening for most if not all flags on that plugin, I would probably suggest that you post an issue for it on their github page. It certainly sounds like the underlying perl packages they need may have updated and they have not altered the code to work with these changes. Unfortunately we don't develop this particular one, or I would have a talk with the developers about taking a look.

sreinhardt wrote:In the event that this is happening for most if not all flags on that plugin, I would probably suggest that you post an issue for it on their github page. It certainly sounds like the underlying perl packages they need may have updated and they have not altered the code to work with these changes. Unfortunately we don't develop this particular one, or I would have a talk with the developers about taking a look.

Any idea how to find out which perl modules it requires?

Open up the plugin and any line beginning with "use" will list the modules.