-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSH Commands Randomly Failing on the Server #306
Comments
#257 I would like to point out that I opened this issue considering that the solution mentioned here does not suit me !!! |
SSHCommandError is a general error when an ssh command that is being ran on your server by Vito is exited with status 1 which means failed. It can be anything, so you need to take a look at the logs to see why the command failed. |
This error in your Laravel project indicates a problem with the execution of an SSH command. I haven't come across a detailed error log, only this log appears... The only conclusion I can draw from this is that the main cause of the error is
|
You need to look at the server logs not application logs. Go to your server in Vito dashboard and then Logs |
Looks like I'm also getting the same error @saeedvaziry .
|
@MelTheDev my answer is the same. you need to check the server logs to see why it failed. |
@saeedvaziry As you have mentioned, I checked logs from the path but it's empty. Update: Thanks |
yes those are the validations that the database itself has. Like if you enter number instead of database name you will get the same error but in the logs you will see the actual reason. in V2 #297 Vito will show an error message on creation with the logs from the server itself. |
Describe the bug
I am encountering an ongoing issue with SSH commands on the server, where I am frequently seeing the error "SSH command failed with an error" even when no changes have been made. This has caused disruption to normal operations, and I am unsure of the root cause. Below is the specific error message and trace that appears.
Error snippet:
To Reproduce
Expected behavior
I expect the SSH command to execute successfully without throwing this error when no changes are made to the server setup or commands being executed.
Screenshots
Additional context
This error appears to occur randomly, and no alterations have been made to the server or environment. I believe it may be related to how the SSH connection is handled or managed. Any insights or potential fixes would be greatly appreciated, as this issue is negatively impacting our workflow.
The text was updated successfully, but these errors were encountered: