I'm having a problem with setting up a local Sugar instance on localhost in a vagrant VM. I created a local host instance from a backup file, which worked well the first time I tried it. But, after restarting vagrant about two weeks later, I get an empty grey screen and an error in the PHP log:
PHP Fatal error: Uncaught Error: Class 'Ramsey\\Uuid\\Uuid' not found in /vagrant/src/Cache/Middleware/MultiTenant/KeyStorage/Configuration.php:44
I deleted this instance and created another one from a different backup file. Again, it worked well initially. But after restarting vagrant today, I got the same error. This time, I looked into this error in more detail and managed to fix it by changing the use statement in Cache/Middleware/MultiTenant/KeyStorage/Configuration.php to "use Rhumsaa\Uuid\Uuid" (https://github.com/ramsey/uuid/issues/217). But now I'm getting a new error:
Uncaught Error: Class 'LoggerManager' not found in /vagrant/include/entryPoint.php:121\nStack trace:\n#0 /vagrant/index.php(17): require_once()\n#1 {main}\n thrown in /vagrant/include/entryPoint.php on line 121
This leads to 3 issues that confuse me at this point:
1) Why is this error thrown when a LoggerManager class does exist in include/SugarLogger/LoggerManager.php?
2) It seems that there is a more fundamental problem with this instance that prevents it from finding existing classes. I was thinking it might be a permissions issue and ran the commands to set the required permissions (using vagrant:vagrant instead of apache:apache), but it had no effect on the error. What else can I try to troubleshoot this?
3) Why did this instance work well initially and started throwing errors after restarting vagrant?
Thank you for any help!
I haven't been able to figure out what the problem was, but it went away after I set up a new local instance using a backup of a newer Sugar version.
Related
For some reason i just can't get an Amazon Aurora DB launched. I haven't launched one before but have read many Amazon help / instruction pages. Launching other Amazon products did work well after some digging. This one just doesn't. Any suggestions?
Error:
Access denied to Performance Insights (Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: 8ef6c7b9-be54-4bd8-aa87-XXXXXXXX)
http://prntscr.com/iug951
Today it works.. selected the same settings as yesterday. All i did different was omit dashes (-) from the database name and other stuff you have to name. If that was the actual cause of the 3h headache yesterday Amazon really sucks it just doesn't tell you that instead of showing a cryptic error message.
I just had the same issue with the same error message, restarting the setup process from the start (with a database name without a dash in it), fixed the issue.
I have a Laravel 3 project, running on a plesk 11.5 CentOS 4(dedicated). It used to be on an IIS server, but i had to migrate it to plesk, since the company i'm working for is dumping the IIS server. Everything seemed to be running smoothly, until i logged out from my application, at first i got a WSOD (white screen of death), then i enabled php error reporting, and this is the error that was displayed:
Fatal error: Cannot override final method Laravel\Database\Eloquent\Model::sync()
This is a very strange error, since i have no method called Sync in any of my classes, and needless to say that there was no such error while the project was running on IIS.
I tried several different combinations of session/cache drivers, the only one that seems to be working is the APC driver.
When i have the APC driver enabled for cache and session, the above Fatal error is not displayed and everything works correctly. The PROBLEM is that i have given the Session Lifetime a value of 60(minutes) but it is completely ignored, meaning that the user is logged out after 2 or 3 minutes.
I've been to the Laravel IRC channel with this issue, some people kindly suggested to tweak the APC memory and ttl (time to leave) settings, but with no luck unfortunately :(.
Here are some APC settings from my server configuration:
apc.gc_ttl 3600
apc.shm_size 1024M
apc.shm_strings_buffer 32M
I desperately need help if anyone has any to offer! This is for a live running project and i need to find a solution asap.
I had the exact same issue and couldn't find a solution. I was going round in circles trying to figure out what on earth was going wrong.
I finally came across this post:
Fatal error: Cannot override final method
You need to make sure that the apc.include_once_override setting is set to 0. In your apc.ini file set like so:
apc.include_once_override=0
This error seems to be caused by caching of included classes.
I solved the problem after looking around the plesk panel.
The problem was that i had "Run PHP as FastCGI application" selected.
I switched to "Run PHP as CGI application" and everything works perfectly.
I'm not sure what the exact source of the problem was, only that FastCGI triggered the error.
I have developed a small accounting application which running fine in xampp in windows machine and also it is working fine in my development server (linux based).
But, when i migrate the total application to client linux server I got the following error:
Parse error: syntax error, unexpected T_STRING in /home/orcilia/public_html/cfm/application/models/sm_main.php on line 1
I have checked it several times but unable to found an error ...
But, I think in the client server there is some issue in case of loading model from controller..
PLEASE HELP ME REGARDING THIS..i have spent a lot of time but unable to get rid of this error...
Thanks,
TANAY GHOSH
If you use <? as an opening tag (check at the very start of your file), change it to
<?php. The server might not allow the shorthand style.
I'm setting up a new website and the site uses asp.net membership. This was working fine but today when I try and log in or do anything such as add a new user/role in the asp.net configuration wizard I get:
Warning: Fatal error 9001 occurred at Jul 30 2012 7:52PM. Note the error and time, and contact your system administrator.
Searching online, it seems to suggest that the logs are full, but I'm advised by the website host that there is ample free space, so I dont really know what to try next.
Has anyone come accross this before and if so, how did you manage to resolve it?
Thanks
I have had this problem recently too and after mountains of research it appears to be common when a database is set to AUTO CLOSE. I set all the databases to AUTO CLOSE = FALSE. This started with one database then went over to two and the next it was on all of them. I simply restarted the SQL Server Instance Service instead of restoring databases. Another way to fix the symptom is to take the problematic database offline and bring it back online again.
As it turns out this was a database issue. I couldn't even create a new table or drop a table and ultimately had to get the database restored, which solved everything.
I started to mess around with the EC2 “Micro Instance” for a new site i’m working on. I put on an ubuntu lamp server and loaded up our favorite php framework and started along the coding path.
One frustrating thing i’m finding is whenever I make a mistake coding (which is rare! j/k), it gives my a “Server Error 500” and won’t display the php error line number or the helpful references to where the mistake might have happened.
Also when ever an error does appear and I try to fix the mistake it will remain the same for a couple of minutes. Its like its caching on my system or something. If I do something like this :
echo "test" //leaving off the semicolon
refresh the browser it comes up with the error. Then when I fix it:
echo "foo"; //corrected
I still get the Server Error 500. Not sure if anyone else has run in to these issues. Maybe its a php.ini configuration, .htaccess configuration (i’m using Paul Irish’s HTML5Boilerplate .htaccess code), or a LAMP configuration issue. Any pointers to where the problem might lie would be a huge help.
Thanks! Steve
this has nothing to do with ec2.
see php error directives in /etc/php5/apache2/php.ini