I'm working on a new project in TYPO3. It's my frist installation of TYPO3 9.5.5 so I don't know if this is some sort of bug or anything but sometimes, and I really can't give you any more information about it since I dont know where it comes from and how to reproduce this error, my enire typo3 crashes with this error message:
(1/1) #1476107295 TYPO3\CMS\Core\Error\Exception
PHP Warning: rename(/var/www/html/var/cache/code/cache_core/5cab444370d80224649952.temp,/var/www/html/var/cache/code/cache_core/site-configuration.php): No such file or directory in /var/www/html/public/typo3/sysext/core/Classes/Cache/Backend/SimpleFileBackend.php line 234
Since it's in my var directory I figured to just delete the entire folder but as soon as I try to delete it Windows tells me I don't have permission to delete this file or even change it. When I try to open it in an editor it tells me that the file doesn't exist and I can't do anything about it unless I restart my entire PC.
I've found some people with the same issue here, but no way to fix it or anything on how to prevent it from happening.
I'm using the composer installation of TYPO3 with ddev on Windows 10.
Does anyone know about this error or can tell me anything on how to fix it?
Did you try to flush all TYPO3 caches?
To do so, go to Admin Tools => Maintenance => Flush TYPO3 and PHP Cache.
If the problem persists, you can try to got to Admin Tools => Environment => Directory Status and check if all permissions are set properly.
And since you run TYPO3 with ddev, you can use the shell (Putty or whatwever) and do a ddev ssh to login directly to the container and delete the files there.
Related
I have a problem installing TYPO3 10.2.2 on Ubuntu 18.04.3 LTS, Apache 2.4.29, PHP 7.2
I did follow the "Install TYPO3 Without Composer" How to. When I want to access the Installer I see a blank page. So far nothing new, I have seen that a lot of times. I did set the access rights correct but still a blank page.
The Apache error log says:
AH01071: Got error 'PHP message: PHP Fatal error: Uncaught
LogicException:PSR-11 Container is not available in
/var/www/typo3_src/typo3/sysext/core/Classes/Utility/GeneralUtility.php:3398
In the mentioned php I see additional information 'PSR-11 Container is not available', 1549404144.
I did search on the web to find a possible solution but this time without any luck.
My question: Did someone see that bevore or has a hnt for me what to do?
Thanks a lot in advance.
Dabbelju
I just ran into the same problem (Installation with composer by the way).
The problem is that the web server does not have the needed access rights on the Typo3 project folder.
When using the Apache HTTP Server this can be solved with
chown -R :www-data YourProjectFolder
chmod -R g+w YourProjectFolder
This recursively changes the group of all contained files to 'www-data' which is the group used by the Apache server and grants write access for this group.
When did you get the error message? Just after accessing the site for the first time after creating FIRST_INSTALL?
Are there any other error messages before this error message? (If you open the file GeneralUtility and look in the specified line, you will notice that the $container was not created. The question is why?). Problem is most likely somewhere during autoloading / dependency injection.
I never had this error, but here are some tips for generally handling exceptions and solving / debugging these types of things yourself.
As already mentioned, the logfile may show additional information. On non-Composer installations you will find this in typo3temp/var/log
If you already got so far to enter the backend, you may want to set the Configuration Preset to "Debug" in settings to see more output (do not do this in production)
If you finished the installation procedure, but cannot access the backend (with /typo3), see if you can access the install tool (with /typo3/install.php, create a file ENABLE_INSTALL_TOOL in typo3conf)
Since you know the code of the Exception, you can look up the Exception page in the wiki: https://wiki.typo3.org/Exception/CMS/1549404144 (unfortunately in this case it is empty, but it may be helpful for other exceptions)
check your permissions, typo3temp must be writable for the user / group Apache is running under (e.g. www-data)
As a last resort, if all else fails, removing the entire content of typo3temp might help. This is not good practice and should usually not be necessary, but it lets you restart with a clean state.
Also see troubleshooting tips in Installation Guide.
P.S. I just followed the Installation Guide: Quick Install without Composer to be sure and it works on my system, Ubuntu 19.04, PHP 7.2, Apache/2.4.38 without any problem.
To wrap this one up:
It was a permission problem. Due to the missleading Error message it took me a while to figure that out. In the mentioned guide it does not say something about permissions.
My conclusion: Whenever it comes to the point that T3 says that a folder can not be created fix the permission problem instead of adding the folder manually.
Thanks to all who did guide me to the right solution.
I'm a fairly new laravel developer, I am developing my website in laravel 5.5 and I've been trying to get my website online for a few days now. it kept giving me error message like:
Warning: require_once(/dirpath/htdocs/vendor/composer/autoload_static.php): failed to open stream: No such file or directory in /dirpath/htdocs/vendor/composer/autoload_real.php on line 28
Fatal error: require_once(): Failed opening required '/dirpath/htdocs/vendor/composer/autoload_static.php' (include_path='.:/usr/share/pear/') in /dirpath/htdocs/vendor/composer/autoload_real.php on line 28
since it is a free shared hosting server without SSH (I cant run laravel command there), I did make sure to do everything from paying attention to folder structure (placing the content of public outside) and every project files/folders in the htdocs content (I know it can be insecure, I just wanted to show the client the progress of the website for a few days before I took it down). I also did composer install, composer update, composer dump-autoload, various artisan command to clear the cache before I push it to the server, but as you can see, the error persist.
a bit of inspecting on my end, and I keep seeing the autoload_static that autoload_real has been trying to require, kept disappearing along with the autoload classmap. What is the reason that is causing this and what should I do to make the error go away?
Thanks in advance, I tried all I know and did some research but I just stuck, hope you guys can help with this.
also: I can't really get myself a vps or a paid hosting right now.
Update 25/04/2018 : I did composer update --no-dev and re-upload the whole thing again to the vendor, but it is still the same error, anybody has a suggestion? I really am stuck at this point.
In this situation you can't do anything on the server without SSH. In your local copy run composer update --no-dev. Then delete server's vendor folder & copy your local's vendor folder to the server.
load psr-4 instead:
inside autoload_real.php, please find the code like shown below:
$classMap = require DIR . '/autoload_psr4.php';
At least this is a dirty trick to make it work. Once you have the money, then may be moved to a well-equipped server later.
I've installed successfully Moodle version 3.3.2 and at the end, i got an error to connection database. But as i've seen it generated all tables in database moodle.
Now, i can't enter, ERR_TOO_MANY_REDIRECTS on loading pages.
URL: http://example.com/admin/index.php?cache=1.
Additional Server information:
OS: Ubuntu 16.04
PHP: 5.6
Mysql: 5.7.20-0ubuntu0.16.04.1
Different approach to solving this problem after checking and making sure that apache and php configuration are ok. I the added this line of code to my noodle config file.
$CFG->sslproxy = true;
And this resolved the issue.
go on your server directory such as "www=>moodle directory=>admin
open index.php
find following
"redirect("index.php?sessionstarted=1&lang=$CFG->lang");"
and comment it
i find this on line 712 in moodle 3.7. it might be changed with version
save file and refresh page
Search the moodledata directory, enter it and delete the following directories
cache
localcache
in my case, this error come out because of the disk was full and yes deleting cache and localcache solve the problem
Delete all the data from moodledata folder (Try this only with the new instance otherwise will loose the data), then try to open yourdomain/moodle in your browser. It will work.
I have been using EasyPHP-12.1 for some years now but, foolishly, tried to add a different version of PHP. (I had backed up the www files but not the whole installation). I added a new version (5.6.21) to the PHP folder, selected it in the admin but it didn't work. Now the server doesn't start. It comes up with the error:
Error in Apache configuration file: AH00526: Syntax error on line 185
of C:/Server/EasyPHP/apache/conf/httpd.conf: invalid command "PHPIniDir",
perhaps misspelled or defined by a module not included
in the server configuration.
I would like to go back to the original PHP (5.4.6) or, at least, reinstall the program and copy the MySQL databases to the new installation. As I said, I have copies of all the working php pages - it's the databases that I am worried about losing.
I hope someone can get me up and running again.
I seemed to have managed to get it all working again. I found an earlier dated backup in the conf folder, renamed it and restarted. Phew!
(Made sure I am backing up all the databases and EasyPHP folder now.)
I have this trouble: i copy symfony project files on my pc, after that change paths and db settings, and it still not working, even dont tell about errors! Maybe there is some specific actions for setting up symhony on another server?
Almost the same problem How to configure symfony project in local server? but when i try execute "php symfony" it prints "no such file or directory"
There are no any php errors at all.
Using Fedora 15 OS, and apache. php work in command line, symfony is not working. I tried to find out what is happening - inside Controller.class some error, when it use processObjects method, it take 11 objects, and after first of them (header.object.php) it stops.
The white screen generally means symfony can't write to cache and/or log dir, check on apache error logs to see details.
if 'php symfony' on command line throws no such file or directory could mean php is not in your system path.
Please add more information to get answers
myabe, as said below is a permission problem of the caché and log files. Check if they are writable. Good Luck!