8.7.1 upgrade 8.7.2 file check fails

Hello,



after a upgrade our file check monitor fails.. i've checked the location and file is there, nothing has been edited after the upgrade.



thanks.

Hello,



We are checking on this to see if it is a bug here. Can you tell if the check is executing and failing or is the check just not happening?

it seems its executing but simply fails.



L

Can you run the webserver in debug mode and then perform a test settings with the monitor. Reply with the debug output.



http://wiki.serverscheck.com/index.php/Webserver_debug

# Starting up app



= file edited =

The log doesn't show any TEST SETTINGS being performed

and ?



i've followed the instructions and made sure that there was no s-server.exe running, after that i ran s-server.exe the way it was explained in the manual, and this is the output.

You need to perform a TEST SETTINGS on the monitor that is failing

# Start: Wed Feb 2 15:57:57 2011 - End: Wed Feb 2 15:58:06 2011

#

# Configuration server ready, serving on port "1272"...

#

#

# Wed Feb 2 15:59:47 2011 Reading configuration file - last was

# Wed Feb 2 15:59:47 2011 Reading conf file completed

# Wed Feb 2 15:59:55 2011 Importing current status of each monitor

# Wed Feb 2 16:00:02 2011 End importing current status of each monitor

3

# Wed Feb 2 16:00:28 2011 Logs from 1296601200:Wed Feb 2 00:00:00 2011 to 1296687600:Thu Feb 3 00:00:00 2011

# Wed Feb 2 16:00:28 2011 Scanning log: alerts-2011-2-2

# Wed Feb 2 16:00:44 2011 Serving Wizard 3 in test mode? 1

# Wed Feb 2 16:00:44 2011 Serving Wizard 4

# Wed Feb 2 16:00:53 2011 Reading configuration file - last was 1296658787

# Wed Feb 2 16:00:53 2011 Reading conf file completed

# Wed Feb 2 16:00:53 2011 Serving Wizard 4_1 - 0

# Wed Feb 2 16:00:59 2011 Serving Wizard 4_1 - 1

# Wed Feb 2 16:01:05 2011 Serving Wizard 4_1 - 2

# Wed Feb 2 16:01:11 2011 Serving Wizard 4_1 - 3

# Wed Feb 2 16:01:17 2011 Serving Wizard 4_1 - 4

# test Wed Feb 2 16:01:19 2011 Starting Monitoring Rule Thread test

# Running in test mode

testmode:1

# test Wed Feb 2 16:01:19 2011 TEST - Starting check

executing file

check: amsadmfs1serverscheck$*.txt<X><X>1

# test Wed Feb 2 16:01:19 2011 testing amsadmfs1serverscheck$*.txt

found: amsadmfs1serverscheck$test.txt

ID:

# test Wed Feb 2 16:01:19 2011 TEST - OK - -

# Wed Feb 2 16:01:23 2011 Serving Wizard 4_1 - 5

# Wed Feb 2 16:01:25 2011 Importing current status of each monitor

# Wed Feb 2 16:01:29 2011 End importing current status of each monitor

# Wed Feb 2 16:01:55 2011 Reading configuration file - last was 1296658853

# Wed Feb 2 16:01:55 2011 Reading conf file completed

3

Based on the debug output the TEST SETTINGS works with the test file being found.



The debug mode runs under the Windows Account you are logged in as. As a service does not run under a Windows Account, you need to assign one to the ServersCheck Monitoring Service.



See wiki for setting the service settings at http://wiki.serverscheck.com

Hello,



as i have stated in my previous post, the check always worked, and it looks like that an upgrade somehow resetten de service settings. I have changed the service account settings and it seems to work again. This was not the first place for me to look since one doesn't assume a upgrade would reset the settings.



L

hmmmm... the upgrade could have possibly reset the service 'runas' account to local system?



i.e. my systems run under a specific account with the correct account of domain access levels.



for a test... try setting the services for the webservice + monitoringservice to run as an admin account... if that works ok, then it looks like you will need to set it to run against a specific domain/user account.