Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Linux Server Discovery Failed: Pattern name: Linux Server. Storage.bash (Problem writing temporary file: Unable to create temporary file) - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Linux Server Discovery Failed: Pattern name: Linux Server. Storage.bash (Problem writing temporary file: Unable to create temporary file)
KB0691883

Linux Server Discovery Failed: Pattern name: Linux Server. Storage.bash (Problem writing temporary file: Unable to create temporary file)


1200 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms


Linux Server Discovery Failed: Pattern name: Linux Server. Storage.bash (Problem writing temporary file: Unable to create temporary file)

During Linux server Discovery, the Linux Server pattern with the following error in the Agent log:

HorizontalDiscoveryProbe SEVERE *** ERROR *** Unable to create temporary file

Release


Any

Cause


User in credential does not have access to /tmp in the target Linux host

Resolution


  1. Ensure that Credential specified on the Instance is able to write to /tmp on Target Linux host.
  2. Ensure that MID server is run by the Local Administrator account.

If above troubleshooting steps has been completed then try setting the mid server parameter to "mid.ssh.use_snc"

set the mid server to true for "mid.ssh.use_snc"

Set the MID Parameter 
===================== 
1. Navigate to -> MID Server -> Servers -> Select MID Server  
2. Then click on "Configuration Parameters" tab -> New -> Parameter name -> "mid.ssh.use_snc" and value "true". 
Then restart the MID server and ran a quick discovery again to the same IP address to test it out. 

  

 

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.