Help Center>
CodeArts Deploy>
FAQs>
Custom Application Actions>
Starting or Stopping Spring Boot>
Environment Does Not Exist
Updated on 2024-07-04 GMT+08:00
Environment Does Not Exist
Symptoms
The log failed to obtain environment information. The environment cannot be found.
Cause Analysis
The referenced environment does not exist or has already been deleted.
Solution
- Select the target application, click , and click Edit. The Deployment Actions page is displayed.
- Click the Environment Management tab.
- Click Create Environment, configure the information, click Save and switch to the Resource page.
- Click Import Host. After the host is imported and verified, deploy the application again.
Parent topic: Starting or Stopping Spring Boot
Starting or Stopping Spring Boot FAQs
- Invalid Spring Boot Path
- Startup Failed
- Environment Variables Are Not Configured
- Service Is Not Started Despite Successful Action Deployment
- Spring Boot Can Still Be Detected After Being Stopped (on Windows)
- Instruction
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
Feedback
Was this page helpful?
Provide feedbackThank 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.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore