Problem:ID connector fails to start if old pid-file exists

Knowledge Base Community
, , ,
#1

Problem

If the service cannot be started by the ID connector, it may be due to unprocessed pid file blocking the service. Among other things, this can be caused by a power failure in the system.

You can find the pid file that block the service from starting at the following location:
/tmp/IDConnectorService.pid

The bug 54640 causes this misbehavior.

Solution / Workaround

This resets the state (basically deleting the pid file):

/etc/init.d/ucsschool-id-connector zap

After that a start should work. So the “to be sure it’s running” commands are:

/etc/init.d/ucsschool-id-connector stop
/etc/init.d/ucsschool-id-connector zap
/etc/init.d/ucsschool-id-connector start
#2
Mastodon