I'm having an issue where Xampp isn't logging my errors. The file path doesn't exist when I search for it. I read some stuff about this that said I need to enable php_error_log from the php.ini file but i don't know what values to change.
It should be a permissions issue (depending where you installed XAMPP). The XAMPP panel is sometimes unable to create the logs folder. Just create this directory:
...\xampp\php\logs
and the next time PHP error occurs it will create the php_error_log file inside and the logging will start.
Related
I've rent a vServer with ubuntu 20.04 and use plesk
When PHP errors happen, then no error log files are created in the log folder.
On my old vServer which has windows there wasn't such problem, the error file was created in log/php_errors/websitename/php_error.log but in linux nothing.
in the php.ini I have log_errors = on
I've seen several similar questions but they aren't helping
On my Linux server, using Plesk, the error logs are located in the logs directory, one directory up from the website root. So, something like
/var/www/vhosts/<domain.ext>/logs
Sometimes they don't immediately appear there, then they can also be found in:
/var/www/vhost/system/<domain.ext>/logs
I don't know why the logs initially don't appear in the first location.
I swear I saw a error log in the Terminal of C9. I just can't find the path and the file anymore.
Any tips or ideas where / how to find?
To some paths/files I don't have permission with the standard user that is "ubuntu". As I read it isn't possible to use sudo, is it? For example I assumed to find the log at /var/log/apache2 but permission is denied.
Currently mine is at
/home/ubuntu/lib/apache2/log/error.log
I discovered this by looking at the terminal/console that opens up below the editor when you start Apache.
You can find a php.ini copy overhere:
https://raw.githubusercontent.com/c9/templates/master/ws-php/files/home/workspace/php.ini
Part of the Cloud 9 Template repository.
Make the changes...
And copy it in your workspace folder.
Well, I found out following solution on this site:
download an adjusted php.ini file from the link
place it in your workspace folder
start apache again
You'll have an error log file named php_errors.log in the same directory (workspace)
We moved our Magento installation from one FreeBSD VPS server to another (8.2 to 10.0). After that, we can't see anything in Magentos /var/log/system.log anymore.
We have checked and re checked the permission (777) on /var/log/*
Whe have tried to enable logging in /index.php
We have checked the database => dev/log/active = 1
Whe have tried to change owner of system.log and exception.log
Where afraid something might be missing in PHP, maybe som extension? Or could it be permission on the local servers /var/log directory?
How can we produce an error, that should be logged to Magentos /var/log ?
make sure you root magento directory is writable and make sure apache user has permission to write file
Did you try to delete the old logs?
We had that problem - just renamed file and everything went okay.
I have tried two different things on my server:
created a directory php in /var/log/
changed owner:group to www-data:www-data (apache owner)
changed permissions of the directory to 775
php.ini has error_log = "/var/log/php/php.log"
php.ini already had error logging set to on, and error reporting set to all
restarted apache
in the code, changed error_log('message') to error_log('message',3,path_to_logfile)
Neither results in messages in the applicable log file.
You say you created /var/log, but you're trying to write to /var/log/php. Try creating a directory called php in /var/log.
I have configured Amazon EC2 Server and install PHP and MySQL. I have uploaded my website on it. it is in smarty.
Problem is when I update any .tpl file, then the server return white page as output in Firefox and Chrome return 500 Internal Server Error. I have surfed everywhere on internet but got nothing.
When I update any .php file then the code work nicely. problem is only with .tpl file.
I'm willing to bet that your templates_c directory is not writable by Apache (identified as apache or httpd, and you can check in your httpd.conf file), or it hasn't been configured correctly during Smarty initialization.
You can try temporarily setting your templates_c directory to 777 permissions to test this hypothesis.
If this ends up being the case, then you'll want to assign group ownership of templates_c to apache, and set the folder permissions to 775. (They explain this in their documentation.)
An HTTP status of 500, with no page content (Chrome is just being nice and rendering a default error message for you) means that PHP encountered a Fatal Error.
You will need to find out where PHP is configured to log to (usually a file called php_errors.log) and see what the error was.
Alternatively, you could temporarily allow PHP to output errors to screen, using the error_reporting setting.