Hello,

I have several Macbooks which are found on my network but not scanned. I have enabled remote login and management on the Macbooks and verified that I can login via SSH using an admin user.

I have setup SSH credentials at my Inventory Settings but still there is no detailed information about my Macs. Even in the settings it says that the credentials are successfully used at my Macbook.

On my Macbook I found the following in the system log regarding sshd:

Service exited with abnormal code: 255

Can anybody help with this? I only found a post on the internet suggesting to turn of “ChallengeResponseAuthentication” and “UsePAM” but I don’t think that it is a good advice :wink:

Best regards

4 Spice ups

Hi,

If you are using Spiceworks to scan them in, you can try the suggestions on this troubleshooting article: https://community.spiceworks.com/support/inventory/troubleshooting/ssh-scanning-issues

Hello Jaime,

thanks for your answer and sorry for my delayed reply, I was out of office.

Of course, I used spiceworks to scan. I just forgot to mention it. I also did go through the troubleshooting before I posted here.

  1. Confirm the device you’re trying to scan is online

The device is online (my own Macbook) and it is connected to the same network as the server. But the server is connected to two different networks (192.168.179.0 Lan / 192.168.178.0 Mgmt). Could it be that the Spiceworks SSH Client tries to open the connection via the Mgmt Interface? The Macbook is pingable from the server.

  1. Check the hostname and IP address

IP address of my device is 192.168.179.60 and that is the one I see in Spiceworks. I can resolve the device by IP and Name.

  1. Test remote SSH

I can login via Putty from the server with the same credentials stored in Spiceworks.

Any other idea what I could try to test?

Br

Karsten

When you go to the device in Inventory, you can “choose an advanced option” for the device and select “rescan”. This will allow you to attempt some more troubleshooting, including scanning with the specific details for that device and see what error conditions may occur a bit better.

Hi Jackie,

thanks for the hint. Do you mean this “rescan” option shown in the screenshot?

I do not get any further information using this rescan. I can click on the link above and that takes me to the scanning page. But there it just waits some seconds (I assume a timeout occurs) and then says finished and 100% inventoried, nothing else.

Or did you mean another advanced rescan?

Br

Karsten

Hi,

I have done some further testing with other Macbooks. Surprisingly it partially worked on two newer Macbooks (2017) with macOS 10.12.6 and 10.13.2. It shows the system configuration but not the software which is installed.

The two Macbooks where it is not working are “late 2013” Macbooks running macOS 10.13.1. Of course, coming from older macOS versions.

Br

Karsten

Hi,

when I monitore the console of my Macbook I see that ssh login works and credentials are accepted. Hence, my first post is not correct or better to say it seems to be related to some kind of ssh lookup done prior to the login.

But directly after the login I see the following lines:

fehler 16:09:40.651850 0100 sandboxd Sandbox: sshd(2434) deny mach-lookup com.apple.logd
Sandbox Check by: launchd(1)

Violation: deny mach-lookup com.apple.logd
MetaData: {“build”:“Mac OS X 10.13.1 (17B1003)”,“sandbox_checker”:“launchd”,“action”:“deny”,“target”:[“com.apple.logd”],“hardware”:“Mac”,“platform_binary”:“yes”,“profile”:“unknown”,“process”:“sshd”,“op”:“mach-lookup”}

Violation: deny mach-lookup com.apple.diagnosticd
MetaData: {“build”:“Mac OS X 10.13.1 (17B1003)”,“sandbox_checker”:“launchd”,“action”:“deny”,“target”:[“com.apple.diagnosticd”],“hardware”:“Mac”,“platform_binary”:“yes”,“profile”:“unknown”,“process”:“sshd”,“op”:“mach-lookup”}

Seems that the “Scan” is somehow blocked…
Does anyone have an idea how to solve this?

Br
Karsten

Unfortunately, I’m not Mac savvy to answer your Mac question, but just for future reference, the option I was talking about generally appears on unknown devices (I guess because you’re having some luck, it doesn’t appear for you) - and it looks like this: