-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Error 500 on Dashboard #2077
Comments
Is this an altered version of Cachet? Could be to do with how the resolve email was implemented. |
Yup this is the one we modified yesterday with the resolve email. Could that have caused the backend to stop loading? |
I'm unsure how it could but it might be worth removing it to see if it is resolved. If not then the first thing to do would be to share the |
Seeing this in the log, not sure if that is the issue: [2016-08-21 14:35:01] production.ERROR: PDOException: could not find driver in /var/www/Cachet/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php:55 |
Ah. Seems your |
It might sound strange, but I cannot locate my .env file anymore. Looks like I might have to recreate it or something. The other strange part is that the front page works normally. I see all components and groups. Thank you for pointing me in the right direction. |
Correction, the .env file is there still. Troubleshooting the file now. |
PDO issue was resolved, now log shows this: Sorry for the length of it.
|
Could you please post the whole stack trace? And could you please do so in a gist or at-least a code block? Cheers. |
My apologies, will provide it in gist. Is there a specific section this is located for cachet? |
Sorry for the delay, here is the full stack: https://gist.github.com/apssupport/ce5b3a834b520b8913def5370434fca3 |
You need to install the pdo mysql extension driver, as every exception in that log indicates. |
Good evening Graham, PDO is installed but that hasn't fixed the issue.
|
This is the new stack trace:
` |
Some progress, I now see the login screen, but get Houston We A Problem after logging in. |
I got in, had to install PHP 5.6 again, disable PHP 7.0 and enable 5.6. |
How did I not see that |
You've cut off the top which is the one thing that actually matters? |
As a side note, Instead:
Don't forget that |
@ConnorVG after further working with it last night, if I disabled both php5 and php5.6, php7.0 and cachet together work as well (98%) which I didn't doubt that it won't. I just ran the command you gave and good news, it still shows them installed. The issue I am now facing is that, from the dashboard if I want to update an incident and change the status to "Fixed" the page goes to a 500 Internal Server Error. At first I thought the zabbix-cachet tigger monitor that I am running stopped functioning, but it seems something in my Cachet is getting 500 internal server error when setting to fixed. This is what I get from that program, which coincides with what I see in the dashboard.
@GrahamCampbell Apologies for cutting off the top of the stack trace, I thought the log started after the message. |
Just an update on this, looking at the stack trace, it looks like it doesn't like something with the custom file app/Bus/Handlers/Events/Incident/SendIncidentResolvedEmailNotificationHandler.php and throws an exception.
|
Then change it to |
Hi Connor, Before I try that, I think the issue might have been how it copied over from the browser to the box. I was comparing them side by side and on my side it was off. I corrected the new files you had created and will test it out soon. If I do need to change it to what you just suggested, which line would I make this change on? Also, the fact you took time to cook something up like this for me on a Saturday is highly appreciated and no apologies needed! |
@ConnorVG Ok, scratch that, looks like I will need to update to what you said. When you have time, what needs to be changed to |
@ConnorVG I changed the few instances of IncidentWasReportedEvent to IncidentWasUpdatedEvent in that first file and now the good news is that the fixed message goes through from zabbix to cachet as well as the dashboard, but now the initial email of an incident got sent out 17 minutes after the incident occurred. Should I have only changed the first instance, line 14 and not the rest? Would something like this cause email delays? I'll see if the resolved email gets sent out as well delayed. So far that hasn't been sent. |
Just change this line: and this line: That's all you need to do. Change those to Let's stop this discussion here, it's going a bit too off course. Cheers, |
@ConnorVG Thank you! |
Before submitting your issue, please make sure that you've checked the checkboxes below.
php -v
.rm -rf bootstrap/cache/*
.Expected behaviour
*Should be able to access dashboard.
Actual behaviour
*Getting HTTP Error 500. Looked at past issues, and saw a mention about xml extension. Xml is already installed and running on system.
The text was updated successfully, but these errors were encountered: