You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs-website-src/content/getting-started.md
+44Lines changed: 44 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -199,3 +199,47 @@ You may also experience the following issues, among others:
199
199
This list is not comprehensive. We **strongly** recommend you back up (and ideally create a snapshot of) your system before you attempt this process.
200
200
201
201
If you need more help, you can [open a ticket](https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/).
202
+
203
+
204
+
### Application Manager (Passenger) Apps
205
+
206
+
During the ELevate process, it automatically updates your Application Manager apps (powered by mod_passenger). ELevate performs the following actions:
207
+
208
+
* Application registration.
209
+
* Apache virtual host configuration.
210
+
* The renamed package. For example, `ea-ruby27-mod_passenger` to `ea-apache24-mod-passenger`.
211
+
212
+
However, your application's runtime dependencies are not migrated and may no longer work on the upgraded OS.
213
+
214
+
ELevate upgrades the underlying OS, which replaces core language runtimes. For example, it upgrades Python 3.6 to 3.9 and Ruby 2.7 to 3.x. Packages and libraries that you installed against the old runtime (via `pip`, `gem`, `npm`, or similar tools) are still configured for the previous version. After the upgrade, those installed dependencies still exist on disk but may be incompatible with, or invisible to, the new runtime. In some cases, system-level packages that provided dependencies on the older OS version may have different names or may no longer be available on new OS version.
215
+
216
+
After you upgrade your OS with ELevate, perform the following steps:
217
+
218
+
1. Test each application. Use an HTTP request to verify your application responds correctly. An error response (500, connection refused, or a Passenger error page) is the most common indicator of broken dependencies.
219
+
2. Check the Apache error log for import errors, missing module messages, or gem load failures. Run the following command to review the last 100 lines of the Apache error log:
220
+
221
+
```bash
222
+
tail -100 /usr/local/apache/logs/error_log
223
+
```
224
+
3. Reinstall dependencies with the package manager appropriate to the application's language. Run the following commands inside the app directory, as the cPanel user:
225
+
226
+
**Python**
227
+
```bash
228
+
pip install -r requirements.txt
229
+
```
230
+
**Ruby**
231
+
```bash
232
+
bundle install
233
+
```
234
+
**Node.js**
235
+
```bash
236
+
npm install
237
+
```
238
+
4. Run the following script to Restart Apache:
239
+
```bash
240
+
/scripts/restartsrv_httpd
241
+
```
242
+
243
+
You will need to check every cPanel account that had an Application Manager app enabled at the time of ELevate. The upgrade particularly affects apps that use language-specific dependency files (`requirements.txt`, `Gemfile`, `package.json`) or that rely on system packages installed on the previous OS version host.
244
+
245
+
The ELevate upgrade does **not** affect the app's registration in Application Manager, base URI, domain mapping, and Apache include files.
0 commit comments