Help Center> Server Migration Service> User Guide(ME-Abu Dhabi Region)> FAQs> Agent Installation and Startup> How Do I Fix Error "SMS.5103: Agent startup failed." When I Fail to Start the Agent on a Linux Source Server? Folder /tmp is missing

Updated on 2023-06-28 GMT+08:00

View PDF

How Do I Fix Error "SMS.5103: Agent startup failed." When I Fail to Start the Agent on a Linux Source Server? Folder /tmp is missing

Symptom

On a Linux source server, the Agent failed to be started, and message"SMS.5103: Agent startup failed. Folder /tmp is missing" was displayed.

Possible Causes

The /tmp folder is missing on the source server.

Check whether there is a /tmp folder.

# ls

Solution

Create the /tmp folder on the source server.
```
#mkdir /tmp
```
Check that the /tmp folder has been created and restart the SMS-Agent.
```
# ls
```

Parent topic: Agent Installation and Startup

Previous topic: What Do I Do If the SMS-Agent Fails to Start and Error "SMS.0609 An earlier version of Agent is detected. Please exit the old Agent, uninstall the old Agent completely, and install the latest version" Is Displayed?

Next topic: How Do I Fix Error "SMS.1353: Bind mount or repeated mount detected on /xxx of the source server" When I Fail to Start the Agent on a Linux Source Server?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.