DS Mobility 1.2.5 build 250
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 2
Server has been running mobility fine since Mar 2010 and started on build 39. 10 users, 13 devices, 28% disk used.
No changes since build 250 was installed end of Feb.
For some inexplicable reason for the last month or so, when the connectors restart overnight to rotate logs or whatever housekeeping they do, the mobility connector doesn't restart correctly. Running "rcdatasync status" shows everything is fine and running but checking the web admin screen shows the mobili6ty connector status as "stopped". To get everything working again you just need to click the start button next to it and everything is fine again until the next overnight restart failure, which may be the next night or a few nights down the line. Nothing out of the ordinary in the logs that I can see, it must have done this 4 or 5 times now with nothing I can see triggering it.
Any ideas?
BR,
Mark.
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 2
Server has been running mobility fine since Mar 2010 and started on build 39. 10 users, 13 devices, 28% disk used.
No changes since build 250 was installed end of Feb.
For some inexplicable reason for the last month or so, when the connectors restart overnight to rotate logs or whatever housekeeping they do, the mobility connector doesn't restart correctly. Running "rcdatasync status" shows everything is fine and running but checking the web admin screen shows the mobili6ty connector status as "stopped". To get everything working again you just need to click the start button next to it and everything is fine again until the next overnight restart failure, which may be the next night or a few nights down the line. Nothing out of the ordinary in the logs that I can see, it must have done this 4 or 5 times now with nothing I can see triggering it.
Any ideas?
BR,
Mark.