Jump to content


bmowens

Trouble with Linux clients reaching MP

Recommended Posts

Hello, everyone!

 

I'm having a bit of trouble trying to get any of my Linux servers to communicate with SCCM. I'm fairly new to Linux, but the SCCM environment is functioning well from a Windows perspective.

 

The issue: Linux client installs ok (installed as root), but is getting a 404 message returned from the management point (there is only 1 MP and no FSP's in this environment).

 

I've re-installed the MP, verified MP functionality, verified authentication method is HTTP and not HTTPS, allowed internet clients (has since been turned off), ran wireshark to verify the client is getting a 404 return from SMS_MP on the MP. I've also added the FQDN of the MP into the hosts file on the Linux client (as well as a machine name alias), and verified I can ping the FQDN and machine name. There are no windows firewalls on the clients, and all ports are open between the MP and the Linux client. I've tried this on other Linux servers with the same exact results.

 

My install command is:

./install -mp FQDN -sitecode SITECODE ccm-Universalx64.tar

 

Linux OS: Ubuntu 12.04.2 LTS

Windows OS: Server 2012 R2

Latest Linux/Unix client from MS

SCCM 2012 R2 up-to-date

 

Both SCCM and the Linux client are VMs.

 

With a fresh client install, I receive these errors in the client log:

2015-08-19T16:19:07,224Z Warning [scx.client.locationservices.RefreshLocationServicesTask:143:23388:139806701348672] Failed to connect to the assigned Management Point. Attempting to resync the management point list. $$<LinuxUNIXClient><08-19-2015 18:19:07.000+120><thread=139806701348672 (0x7fffca9237d8)> 2015-08-19T16:19:07,224Z Error [scx.client.messaging.HttpBroker:66:23388:139806701348672] HttpBroker::Send -- Required parameters empty $$<LinuxUNIXClient><08-19-2015 18:19:07.000+120><thread=139806701348672 (0x7fffca922638)> 2015-08-19T16:19:07,224Z Error [scx.client.LocationServices.UpdateManagementPointData:599:23388:139806701348672] Failed to get the MP List. $$<LinuxUNIXClient><08-19-2015 18:19:07.000+120><thread=139806701348672 (0x7fffca922e68)> 2015-08-19T16:19:07,224Z Error [scx.client.LocationServices.UpdateManagementPointData:637:23388:139806701348672] Failed to get the Management point list from the assigned MP. $$<LinuxUNIXClient><08-19-2015 18:19:07.000+120><thread=139806701348672 (0x7fffca9230e8)> 2015-08-19T16:19:07,224Z Error [scx.client.LocationServices.UpdateManagementPointData:653:23388:139806701348672] Failed to get the Management Point list from all the known sources. $$<LinuxUNIXClient><08-19-2015 18:19:07.000+120><thread=139806701348672 (0x7fffca9230e8)> 2015-08-19T16:19:07,224Z Warning [scx.client.LocationServices.ManagementPointManagerr:219:23388:139806701348672] No Management Points have been returned. Using the assigned Management Point. $$<LinuxUNIXClient><08-19-2015 18:19:07.000+120><thread=139806701348672 (0x7fffca923348)> 2015-08-19T16:19:07,260Z Error [scx.client.locationservices.RefreshLocationServicesTask:152:23388:139806701348672] Failed to connect to the assigned management point even after resync. Management point is unavailable. $$<LinuxUNIXClient><08-19-2015 18:19:07.000+120><thread=139806701348672 (0x7fffca9230c8)> 2015-08-19T16:19:07,260Z Warning [scx.client.FSP::SendDeploymentAssignmentFSPMessage:62:23388:139806701348672] A Fallback Status Point has not been specified. Message with STATEID=604 will not be sent. $$<LinuxUNIXClient><08-19-2015 18:19:07.000+120><thread=139806701348672 (0x7fffca9226b8)> 2015-08-19T16:19:07,260Z Error [scx.client.core.CCMClientMain:480:23388:139806701348672] A System task has failed. Please refer to the log file for details $$<LinuxUNIXClient><08-19-2015 18:19:07.000+120><thread=139806701348672 (0x7fffca9246f8)>

I did a fresh re-install of the client, and this time I specified a FSP. I'm now seeing these errors in the trace log:

2015-08-19T17:55:54,763Z Trace [NetworkInterfaceInfo:1297:25633:140664705873728] for net device eth0 ioctl(,SIOCETHTOOL,) fail : Operation not supported $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d078)> 2015-08-19T17:55:54,763Z Trace [NetworkInterfaceInfo:1297:25633:140664705873728] for net device eth1 ioctl(,SIOCETHTOOL,) fail : Operation not supported $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d078)> 2015-08-19T17:55:54,764Z Trace [NetworkInterfaceInfo:1297:25633:140664705873728] for net device eth2 ioctl(,SIOCETHTOOL,) fail : Operation not supported $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d078)> 2015-08-19T17:55:54,764Z Trace [NetworkInterfaceInfo:1297:25633:140664705873728] for net device eth0 ioctl(,SIOCETHTOOL,) fail : Operation not supported $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d218)> 2015-08-19T17:55:54,764Z Trace [NetworkInterfaceInfo:1297:25633:140664705873728] for net device eth1 ioctl(,SIOCETHTOOL,) fail : Operation not supported $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d218)> 2015-08-19T17:55:54,764Z Trace [NetworkInterfaceInfo:1297:25633:140664705873728] for net device eth2 ioctl(,SIOCETHTOOL,) fail : Operation not supported $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d218)> 2015-08-19T17:55:54,765Z Info [scx.client.agents.FSP.FSPStateMessage:1307:25633:140664705873728] Retrieve the value of MACAddress : 00:15:5d:1e:34:27 $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d658)> 2015-08-19T17:55:54,765Z Trace [scx.client.agents.FSP.FSPStateMessage:1315:25633:140664705873728] CFSPStateMessage::GetMACAddress $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d658)> 2015-08-19T17:55:54,765Z Trace [scx.client.agents.FSP.FSPStateMessage:592:25633:140664705873728] CFSPStateMessage::SetStateDetails $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962dab8)> 2015-08-19T17:55:54,765Z Trace [scx.client.agents.FSP.FSPStateMessage:1055:25633:140664705873728] CFSPStateMessage::CreateMsg $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d9d8)> 2015-08-19T17:55:54,765Z Trace [scx.client.agents.FSP.FSPStateMessage:783:25633:140664705873728] CFSPStateMessage::GenerateHeader $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d0c8)> 2015-08-19T17:55:54,774Z Trace [scx.client.utilities.SCXDataStore.SCXDataStore:1333:25633:140664705873728] Repository location changed to: /opt/microsoft/configmgr/root/ccm $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962c778)> 2015-08-19T17:55:54,782Z Trace [scx.client.utilities.SCXDataStore.SCXDataStore:1442:25633:140664705873728] ----->> Inhale opening file /opt/microsoft/configmgr/root/ccm/sms_client.xml $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962b288)> 2015-08-19T17:55:54,794Z Trace [scx.client.utilities.SCXDataStore.SCXDataStore:1741:25633:140664705873728] There are 1 instances in datastore sms_client $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962c8a8)> 2015-08-19T17:55:54,794Z Trace [scx.client.agents.FSP.FSPStateMessage:968:25633:140664705873728] CFSPStateMessage::GenerateBody $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d338)> 2015-08-19T17:55:54,795Z Trace [scx.client.agents.FSP.FSPStateMessage:1091:25633:140664705873728] CFSPStateMessage::SendMsg $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962dac8)> 2015-08-19T17:55:54,795Z Trace [scx.client.agents.FSP.FSPStateMessage:1162:25633:140664705873728] Sending the Message.. $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d5c8)> 2015-08-19T17:55:54,795Z Trace [scx.client.messaging.HttpBroker:90:25633:140664705873728] HttpBroker::Send -- CRL check was not required. $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d288)> 2015-08-19T17:55:54,826Z Trace [scx.client.messaging.HttpBroker:223:25633:140664667637504] Result of call was: 200 $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664667637504 (0x7fef0b8bf968)> 2015-08-19T17:55:54,830Z Trace [scx.client.agents.FSP.FSPStateMessage:1165:25633:140664705873728] ... Sending Async message done ! $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962d5c8)> 2015-08-19T17:55:54,830Z Info [scx.client.agents.FSP.FSPStateMessage:765:25633:140664705873728] State message with TopicType 800 and TopicId D78D02AC-9620-9CF5-54CB-675B7B51DFAE has been sent to the FSP $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962db58)> 2015-08-19T17:55:54,830Z Trace [scx.client.agents.FSP.FSPStateMessage:412:25633:140664705873728] CFSPStateMessage::~CFSPStateMessage $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962e118)> 2015-08-19T17:55:54,830Z Trace [scx.client.agents.FSP.FSPStateMessage:412:25633:140664705873728] CFSPStateMessage::~CFSPStateMessage $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962e7b8)> 2015-08-19T17:55:54,831Z Info [scx.client.locationservices.RefreshLocationServicesTask:292:25633:140664705873728] Failed to detect the assigned Management capabilities. Fatal error. $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe962f9c8)> 2015-08-19T17:55:54,831Z Error [scx.client.core.CCMClientMain:480:25633:140664705873728] A System task has failed. Please refer to the log file for details $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe96301d8)> 2015-08-19T17:55:54,831Z Info [scx.client.core.CCMClientMain:488:25633:140664705873728] Sleeping to retry System tasks for 2 minutes. $$<LinuxUNIXClient><08-19-2015 19:55:54.000+120><thread=140664705873728 (0x7fffe96301d8)>

Share this post


Link to post
Share on other sites

Anyone have any ideas on where to start checking? I see the client reaching the server which holds the management point, yet the MP is returning a 404. Anything I can check on the MP to verify location services are returning valid info?

 

MP self-tests on HTTP pass.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.