ECC master agent for Linux won't start on reboot

I see a lot of "Resource temporarily -    unavailable" but I see that alot on Solaris and Windows servers that work.

[root@naln24rh MGA610]# cat MGA_B1_Err.log
LOG 14:09:00 L I F -137160496 Log.cxx:739 DATE="2013-01-29" IP=" " VERSION="610" TYPE="MGA"
-    HOST="naln24rh" OSNAME="Linux 2.6.18-308.el5" ROLLOVER=0 COMPONENT=" "
-    COMMAND="/usr/ecc/exec/mstragent '-s'" ECC_HOME="/usr/ecc/exec" COMPILED="MGA: BUILD
-    ECC610120A.30NOV2011.2317.159; ECC610120A.30NOV2011.2317.159; COMPILED Nov 30 2011 23:52:27,
-    SDK: BUILD ECC610120A.30NOV2011.2317.159; ECC610120A.30NOV2011.2317.159; COMPILED Nov 30 2011
-    23:46:55" STARTED="2013-01-29 14:09:00"  STARTED BY USER="root"
-    External Version Identifier="MGA: Version 6.1.0, SDK: Version 6.1.0"
-    Internal Version Identifier="MGA: 6.1.0.12.259, SDK: 6.1.0.12.259"
-    Version KitSpec Identifier="MGA: GA3, SDK: GA3"
-    Build Label Identifier="MGA: ECC610120A.30NOV2011.2317.159, SDK:
-    ECC610120A.30NOV2011.2317.159"
-    Build Name Identifier="MGA: ECC610120A.30NOV2011.2317.159, SDK:
-    ECC610120A.30NOV2011.2317.159"
SDK 14:09:00 C P F 4157806800 (0.11 MB) swrx_system::getPersistHostGUID => New DATE="2013-01-29"
SDK 14:09:10 SDK 1 P E 4157806800 (0.11 MB) DataCommSocketLibrary(98)::bind => Address already in use
SDK 14:09:11 SDK 1 P E 4142922640 (0.11 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable
SDK 14:09:21 SDK 1 P E 4142922640 (0.18 MB -12.000000K) DataCommSocketLibrary(11)::accept => Resource
-    temporarily unavailable
SDK 14:09:26 SDK 1 P E 4142922640 (0.18 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable
SDK 14:11:23 SDK 1 P E 4142922640 (0.25 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable
SDK 14:11:23 SDK 1 P E 4142922640 (0.25 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable
SDK 14:11:28 SDK 1 P E 4142922640 (0.30 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable
SDK 14:12:01 SDK 1 P E 4142922640 (0.30 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable
SDK 14:12:05 SDK 1 P E 4142922640 (0.30 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable
SDK 14:12:25 SDK 1 P E 4142922640 (0.33 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable
SDK 14:12:46 SDK 1 P E 4142922640 (0.33 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable
SDK 14:13:40 SDK 1 P E 4142922640 (0.33 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable
SDK 14:16:28 SDK 1 P E 4142922640 (0.33 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable
SDK 14:21:24 SDK 1 P E 4142922640 (0.33 MB) DataCommSocketLibrary(11)::accept => Resource temporarily
-    unavailable

That is pretty typical noise. I would pay attention to what might be at the end of the Master and the Error logs. Beyond that one of the things that come to mind might be an internal firewall that is shutting down the proc because of port usage that has not been permitted.

--Doug

Daniel,

The MGA610 log files should point you in the right direction.

No firewalls.

Check if it's trying to start twice.. Maybe once in init and one in rc or boot... or some other method of startup.. I've seen that before and it manifested similar to this...