1 2 Previous Next 18 Replies Latest reply on Apr 2, 2008 9:57 AM by Golddiggie

    Scans not making it back to the core server

    Apprentice

       

      Sometime after SP3 was applied, new Mac systems stopped appearing in the device list of our core server. We can connect to the install directory on the core, perform the install without error, and even kick off the full scan (or let it do it by itself). Problem is, the scan never makes it back to the server. If we save the scan to a directory on the Mac and manually move it to the server (scan directory) it does get processed. I don't believe the configuration gets updated though, which is another issue.

       

       

      The same issue has been reported by our UK offices, so it's not limited to just our site. I have to wonder what could possibly block the communication with the server and what can be done to resolve it. If anyone else has had this issue, I'd like to hear what was done to fix it. I do think it's something with our network, NOT the LANDesk product. I also think that it's something the security group has done to screw it up. Problem is proving it. The only test I've not performed (yet) is putting a Mac on the same subnet as the core and kicking off the full scan.

       

       

      Any recommendations on what we can look at/test/try to resolve this would be appreciated.

       

       

        • 1. Re: Scans not making it back to the core server
          Expert

           

          It may be a problem with name resolution or not being able to connect to the port. You can open a terminal and run "telnet CoreServerName 5007". This will show whether there is a name resolution problem, or if there is something blocking the connection to the inventory service port Another common problem is a hardware device causing the inventory scanner to crash (this does not sound likely in your case).

           

           

          To troubleshoot this, open the LANDesk.log file, located in the /Library/Application Support/LANDesk folder. With this log open, the user can run the inventory scanner from the System Preferences. They should watch the log file for error messages. If it simply stops logging inventory scan data, without saying that it finished, then open System Preferences. In the inventory scanner section, uncheck the last thing that was logged and try running the scanner again.The last way to fix thing is to get the latest Mac client from the LANDesk website. The client is available for download at: http://kb.landesk.com/article.asp?article=2171&p=5

           

           

           

           

           

          Rick Davies

           

           

          NetworkD Group

           

           

          Certified LANDesk Engineer/Instructor

           

           

          • 2. Re: Scans not making it back to the core server
            Expert

            If you have scans from PCs that are getting to the Core Server then this could also be a problem with SSL.  Since Macintosh will always sent in their scan encrypted.  Make sure that port 443 is working ok to the Core Server. Since you can copy the scan into the ldscan directory I think that this may be the problem.

            Would also make sense if you security team has made changes to the Core.

             

            I hope that helps.

             

            John

            • 3. Re: Scans not making it back to the core server
              Apprentice

               

              I just reinstalled the agent onto the Mac on my desk. It's not showing up under all devices, where it should...

               

               

               

               

               

              Here's the contents of the new log file (created with the agent install)...

               

               

               

               

               

              17-12-2007.09:31:21: LANDesk Agent Install (start)

               

              17-12-2007.09:31:21: Script Directory: /Users/agoldberg/Desktop/LDMSClient 2.pkg/Contents/Resources

              17-12-2007.09:31:21: Package Directory: /Users/agoldberg/Desktop/LDMSClient 2.pkg

              17-12-2007.09:31:21: Destination Volume: /

              17-12-2007.09:31:21: Install Files Source Directory: /Library/Application Support

              17-12-2007.09:31:21: System Directory: /

              17-12-2007.09:31:21: LANDesk Root Directory: /Library/Application Support/LANDesk

               

              Installer: Clean up preferences as needed

              Installer: Remove the now unnecessary items

              Installer: Move preference file, if present

              Installer: Move the Preference Pane

              Installer: Setup cron file

              Installer: Move setup items

              Installer: Installing Tiger or later items

              Installer: Cleaning up LANDesk/LANDesk

              Installer: Creating bin folder

              Installer: Creating Scans folder

              Installer: Creating sdcache folder

              Installer: Creating data folder

              Installer: Creating CustomData folder

              Installer: Creating data/pids folder

              Installer: Move StuffIt Framework

              Installer: Moving executables

              Installer: Installing Secure remote control

              Installer: Setting rights on executables

              Installer: Setting ownership on executables

              Installer: Setting rights on Preference Pane

              Installer: Installing Kaanapali

              Installer: Move Poweroff.exe

              Installer: Place customer certificate.exe

              Installer: Install ping discovery files

              Installer: Installing ping discovery for Tiger or later

              Installer: launching postinstaller script

              Mon Dec 17 09:31:24 2007 ldcron : Started

              Installer: done launching postinstaller script

              Mon Dec 17 09:31:24 2007 ldcron : Scheduling event          (id:0): Delay:0(m)   Frequency:0(m)   Random:0(m)   RunCount:1   Command:/tmp/postinstaller / 6375

              Mon Dec 17 09:31:54 2007 ldcron : Executing scheduled event (id:0): /tmp/postinstaller / 6375

              Mon Dec 17 09:31:54 2007 ldcron : Scheduled event completed (id:0): Command:/tmp/postinstaller / 6375

              Mon Dec 17 09:31:55 2007 ldcron : Scheduler Terminated

              Mon Dec 17 09:32:00 2007 ldwatch : Watcher started.

              Mon Dec 17 09:32:00 2007 ldwatch : SeeApplication::Run: Launching ldscan

              Mon Dec 17 09:32:00 2007 ldremote :     Port 9535: Created accept socket.

              Mon Dec 17 09:32:00 2007 ldremote : Mesopotamia: started.

              Mon Dec 17 09:32:00 2007 ldwatch : SeeLoginLogout::LoginUser: Terminating Launch_Inventory_Scan - called within exclusion period

              Mon Dec 17 09:32:00 2007 ldwatch : User logged in: agoldberg.

              Mon Dec 17 09:32:00 2007 ldslm : Orwell Started.

              Mon Dec 17 09:32:00 2007 ldscan : Got the lock on ldscan.

              Mon Dec 17 09:32:00 2007 ldscan : Scanning started.

              Mon Dec 17 09:32:00 2007 ldscan : ProcessCommandLine[0]: "/Library/Application Support/LANDesk/bin/ldscan"

              Mon Dec 17 09:32:00 2007 ldscan : ProcessCommandLine[1]: "-t"

              Mon Dec 17 09:32:00 2007 ldscan : Commandline -t Mini Scan

              Mon Dec 17 09:32:00 2007 ldscan : Communicating with Core? (10.101.222.119): result=true, flags=0x00000002

              Mon Dec 17 09:32:00 2007 ldscan : The core server "10.101.222.119" is pingable.

              Mon Dec 17 09:32:00 2007 ldscan : Not doing a delta scan, mini-scan is enabled.

              Mon Dec 17 09:32:00 2007 ldscan :  Using the /tmp directory for scan file directory.

              Mon Dec 17 09:32:00 2007 ldscan :  Added file spooler.

              Mon Dec 17 09:32:00 2007 ldscan : Writing header for mini-scan.

              Mon Dec 17 09:32:00 2007 ldslm : Getting Pid of Finder

              Mon Dec 17 09:32:00 2007 ldslm : Found Finder: 6319

              Mon Dec 17 09:32:00 2007 ldslm : Adding Finder notifier to the run loop

              Mon Dec 17 09:32:00 2007 ldtmc : Turner started.

              Mon Dec 17 09:32:00 2007 ldcron : Started

              Mon Dec 17 09:32:00 2007 ldcron : Scheduling event          (id:6737): Delay:0(m)   Frequency:1440(m)   Random:0(m)   RunCount:0   Command:/Library/Application\ Support/LANDesk/bin/ldapm -r

              Mon Dec 17 09:32:00 2007 ldcron : Scheduling event          (id:6737): Delay:0(m)   Frequency:240(m)   Random:0(m)   RunCount:0   Command:/Library/Application\ Support/LANDesk/bin/ldscan

              Mon Dec 17 09:32:00 2007 ldcron : Scheduling event          (id:6737): Delay:0(m)   Frequency:10080(m)   Random:120(m)   RunCount:0   Command:/Library/Application\ Support/LANDesk/bin/ldpatch

              Mon Dec 17 09:32:00 2007 ldcron : Scheduling event          (id:6737): Delay:0(m)   Frequency:10080(m)   Random:0(m)   RunCount:0   Command:find /Library/Application\ Support/LANDesk/sdcache -mtime +2 -exec rm -rf {}\;

              Mon Dec 17 09:32:00 2007 ldtmc :     Port 33354: Created socket.

              Mon Dec 17 09:32:00 2007 ldtmc :     Port 33355: Created socket.

              Mon Dec 17 09:32:00 2007 ldcron : Started

              Mon Dec 17 09:32:00 2007 ldcron : Scheduling event          (id:6738): Delay:10(m)   Frequency:0(m)   Random:0(m)   RunCount:1   Command:/Library/Application\ Support/LANDesk/bin/ldscan

              Mon Dec 17 09:32:00 2007 ldcron : Scheduling event          (id:6738): Delay:30(m)   Frequency:0(m)   Random:0(m)   RunCount:1   Command:/Library/Application\ Support/LANDesk/bin/ldpatch

              Mon Dec 17 09:32:00 2007 ldscan :   Scanning LDMS.

              Mon Dec 17 09:32:00 2007 ldscan :   Scanning network.

              Mon Dec 17 09:32:00 2007 ldscan :     LDAP system version number: 0x104b

              Mon Dec 17 09:32:00 2007 ldscan :     Getting AD information for Tiger.

              Mon Dec 17 09:32:00 2007 ldscan :     LDAP hostname: agoldberg-mp

              Mon Dec 17 09:32:00 2007 ldscan :     Error reading distinguished name information using hostname:agoldberg-mp

              Mon Dec 17 09:32:00 2007 ldscan :   Scanning serial number.

              Mon Dec 17 09:32:00 2007 ldscan :   Done with mini scan.

              Mon Dec 17 09:32:00 2007 ldscan :   Closing scan file

              Mon Dec 17 09:32:00 2007 ldscan : Sending scan file to server.

              Mon Dec 17 09:32:01 2007 ldscan : Finished sending scan file to server.

              Mon Dec 17 09:32:01 2007 ldscan : Temp file deleted.

              Mon Dec 17 09:32:01 2007 ldscan : Scanning done.

              Mon Dec 17 09:32:01 2007 ldscan : Releasing the lock on ldscan.

               

               

               

               

               

              Looks like something is preventing it from working properly... I'll check the link you posted, although I might have already installed it...

               

               

              • 4. Re: Scans not making it back to the core server
                Apprentice

                The security group claims to not block any ports internally on our network. I am able to telnet to the core server on both ports 5007 and 443, so that doesn't look like it's the problem...

                 

                 

                 

                 

                 

                 

                 

                 

                BTW, the security group doesn't touch the servers, especially the LANDesk ones... Those are my babies.

                 

                 

                 

                 

                 

                Any other suggestions?

                • 5. Re: Scans not making it back to the core server
                  Expert

                  Anything in error scan or the Alert log regarding this scan... The client/log seems to believe that the scan was sent successfully If there were issues processing it you should see entries in the Application Log as well and the LANDesk Alert Log. So you are saying that on this same machine you can save an output miniscan and then copy it over and insert it with no issues and see this machine in the console? I wonder if your IIS SSL services are configured correctly?

                  • 6. Re: Scans not making it back to the core server
                    Apprentice

                    Where would I go on the server to check on that? Funny thing is, it was working fine for a long time...

                    • 7. Re: Scans not making it back to the core server
                      leffrt SupportEmployee

                       

                      You stated that you can drop the scan file in the LDSCAN folder and it disappears and is processed correct?  If you do that and notice the device isn't updated then try immediately looking in the Application Log on the Core Server as Rick stated.  If there were any issues processing the scan it should show up there.

                       

                       

                       

                       

                       

                      The Alert history Rick mentioned can be viewed from the Management Console.  Just go to the View toolbar and select Alert history.  Remember the time you dropped the scan in the LDSCAN fodler and compare with the alert logs.

                       

                       

                      • 8. Re: Scans not making it back to the core server
                        Apprentice

                        I was talking about the IIS settings....

                        • 9. Re: Scans not making it back to the core server
                          Expert

                           

                          Under Administative Tools IIS Manager, (See Attached Screen Shot...)

                           

                           

                          This should be a web application and security should be set to use Windows Authentication not Anonymous.

                           

                           

                          If there are issues here they should be logged in the IIS log as well.

                           

                           

                          • 10. Re: Scans not making it back to the core server
                            Expert

                            From the log file it looks like it sent in a mini scan to the Core Server.

                            The error that you are seeing about the LDAP name just means that it was not able to get the FQDN for you machine.

                            This would not make the scan not make the scan not get to the core server.

                             

                            Mon Dec 17 09:32:00 2007 06702 ldscan : LDAP hostname: agoldberg-mp

                            Mon Dec 17 09:32:00 2007 06702 ldscan : Error reading distinguished name information using hostname:agoldberg-mp

                            Mon Dec 17 09:32:00 2007 06702 ldscan : Scanning serial number.

                            Mon Dec 17 09:32:00 2007 06702 ldscan : Done with mini scan.

                            Mon Dec 17 09:32:00 2007 06702 ldscan : Closing scan file

                            Mon Dec 17 09:32:00 2007 06702 ldscan : Sending scan file to server.

                             

                            From this part of the log file you can see that the client was able to talk to the core:

                             

                            Mon Dec 17 09:32:00 2007 06702 ldscan : Communicating with Core? (10.101.222.119): result=true, flags=0x00000002

                            Mon Dec 17 09:32:00 2007 06702 ldscan : The core server "10.101.222.119" is pingable.

                             

                            From this point it would be a good idea to see if the scan is actually getting to the core server.   In configure services in the console on the Core Server you can set the StoreScan option for the inventory service.

                            This will create a storage directory in the ldscan directory on the Core Server.  This will put a copy of every scan file that comes to the inventory service.

                            Even if the scan has an error in the file it will still get copied to this folder.

                             

                            Please try turning this on and see if the scans are getting to the Core server.

                             

                            Also this is a landesk.log file from a machine that was just installed.  It may be a good idea to get a landesk.log file that has already been installed and the scanner has been manually run.

                             

                            I hope this helps out some more.

                             

                            --John

                            • 11. Re: Scans not making it back to the core server
                              Apprentice

                              The storescan option was already enabled...

                              • 12. Re: Scans not making it back to the core server
                                Expert

                                If store scan is already enabled then what are you seeing in the storage directory?

                                Do you see any of the mini scans come in?  Do you see any full scans?  Or is nothing getting there at all?

                                • 13. Re: Scans not making it back to the core server
                                  Rookie

                                  Did you ever resolve this problem? I am having the same issue. I have noticed that it does show up in the IIS logs as a 406 error.

                                  • 14. Re: Scans not making it back to the core server
                                    Apprentice

                                    I updated to LDMS 8.8 and installed the post 8.8 Mac update on the server. Now all the Mac's are reporting back properly and can be remote controlled...

                                    1 2 Previous Next