Some organisations might have the policy not to create HOME directory for a particular user in their Linux OS. ServiceNow does not recommend this as a best practice for the Discovery user (i.e. user used for discovery must have a home directory).

If the discovery user is setup without a HOME Directory, the following warning will be captured during pattern execution:
"Could not chdir to home directory /nohome: No such file or directory".

This warning will not stop the pattern execution, but may cause unexpected results depending on the logic used in the pattern.

E.g. we observed that CI insertion for a Linux Server pattern failed with following error:
Insertion failed with error,In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [cmdb_ci_storage_device]. Add these input values in payload item '{"className":"cmdb_ci_iscsi_disk","values":{"storage_type":"network","size_bytes":"NaN","discovery_source":"ServiceNow" ......

Steps to Reproduce


  1. Create a user in Linux server without HOME directory.
  2. Run discovery for that Linux server with that user credential you have just created.
  3. Observe the failed Linux Server pattern.


This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available.

As a workaround you can seek an exception for the Discovery user to have a HOME directory.

If this is not possible due to certain internal policy, you can modify the step 13.35 (Get proc_scsi) of Linux Server pattern. Add "nonExistingLineSeparator" as parsing option in this step. You can check the attached screenshot Workaround_PRB1388105.png for the detail.

Related Problem: PRB1388105

Seen In

SR - ITBM - Essential SAFe Dashboards v1.0
SR - ITBM - Scrum Dashboards Common v1.0.2
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-10-04 23:30:57