Stuck with SolusVM 500 Internal Error? We can help you.

Generally, we come across the error when svmstack-fpm service is running instead of svmstack-fpm7 on the Master node.

As part of our Server Management Services, we assist our customers with several SolusVM queries.

Today, let us see how we can fix this error quickly.

SolusVM 500 Internal Error

The major symptom of this error is an unavailable SolusVM panel. We will find the following error in a browser:

This error can cause if the svmstack-fpm service is running instead of svmstack-fpm7 on the Master node:

# systemctl status svmstack-fpm7
● svmstack-fpm7.service – LSB: starts php-fpm7
Loaded: loaded (/etc/rc.d/init.d/svmstack-fpm7; bad; vendor preset: disabled)
Active: inactive (dead) since Wed 2021-06-02 22:28:29 EDT; 8s ago

# systemctl status svmstack-fpm
● svmstack-fpm.service – LSB: starts php-fpm
Loaded: loaded (/etc/rc.d/init.d/svmstack-fpm; bad; vendor preset: disabled)
Active: active (running) since Wed 2021-06-02 22:28:35 EDT; 4s ago
Docs: man:systemd-sysv-generator(8)
Process: 4432 ExecStart=/etc/rc.d/init.d/svmstack-fpm start (code=exited, status=0/SUCCESS)
Tasks: 1
CGroup: /system.slice/svmstack-fpm.service
└─4434 php-fpm: master process (/usr/local/svmstack/fpm/php-fpm.conf)

In order to fix this, our Support Techs suggest the following steps:

1. Initially, we connect to the SolusVM Master node via SSH
2. Then we stop svmstack-fpm service and start svmstack-fpm7 service:

   # systemctl stop svmstack-fpm && systemctl start svmstack-fpm7

Alternate Case

On the other hand, it is also possible for us to run into another internal error. Let us discuss this now.

With this error, we will be unable to add an additional IP address in SolusIO VPS:

Server error: `PUT https://203.0.113.2:8080/servers/098bf5e5-72fa-48d7-9b61-6ccaf66a7554/network` resulted in a `500 Internal Server Error` response: {“code”:”e_unknown”,”message”:”cannot update network on \”098bf5e5-72fa-48d7-9b61-6ccaf66a7554\” VM with parameters (network.UpdateParameters) {\n OperatingSystemType: (network.OperatingSystemType) (len=5) \”Linux\”,\n Action: (network.UpdateParametersAction) (len=3) \”add\”,\n ISOImageURL: (string) (len=77) \”https://203.0.113.2:443/api/v1/storage/iso_images/10506070876052e85280a9c.iso\”,\n ISOStoragePath: (string) (len=31) \”/usr/local/solus/iso_images/441\”,\n IPs: ([]string) (len=1 cap=4) {\ (truncated…)

Cause

This is a product bug with ID SIO-3021. Though, it has been planned to fix it in future product updates.

Moving ahead, let us see how our Support Techs fix this error effectively.

A method to overcome this error is as follows:

1. We access the SolusIO Administrator area.
2. Then we stop the affected VPS in SolusIO > Virtual Servers.
3. Add an IP address.
4. Finally, we start the necessary VPS again.

[Need help with the fix? We can help you]

Conclusion

To conclude, the Internal Error occurs when the svmstack-fpm service is running instead of svmstack-fpm7 on the Master node. Today, we saw how our Support Techs fix this error for our customers.