I have a weird error when I lunch any migrate command (reset refresh rollback etc..), the error is :
[ErrorException]
session_start(): open({APACHEPATH}/sessions\sess_0pb5924dau2oehuo4h32lqnem3
, O_RDWR) failed: No such file or directory (2)
PHP Fatal error: Uncaught exception 'ErrorException' with message 'Unknown: ope
n({APACHEPATH}/sessions\sess_0pb5924dau2oehuo4h32lqnem3, O_RDWR) failed: No such
file or directory (2)' in Unknown:0
Stack trace:
#0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handle
Error(2, 'Unknown: open({...', 'Unknown', 0, Array)
#1 {main}
thrown in Unknown on line 0
PHP Stack trace:
PHP 1. {main}() C:\UwAmp\www\project\artisan:0
The session id
sess_0pb5924dau2oehuo4h32lqnem3
differs is different each time, so I went to the apache sessions folder (C:\UwAmp\bin\apache\sessions) and that session id was not present.
I should mention that this problem occurred while installing the Tracker package , somehow during the process i can't migrate anymore, any ideas ? Thank you.
I definitely think your php.ini's session.save_path is not configured correctly, especially as I'm seeing a forward slash "/" in the path to the directory to save sessions in within your error message.
Try this:
Create a new file within your Laravel install called info.php with just a call to phpinfo().
Navigate to info.php. Under "Loaded Configuration File", find the path to the loaded php.ini file and open it in your favourite text editor.
Add / change the following line: session.save_path = C:\wamp\temp\ - assuming that this is the correct path to the temp folder and it actually exists on your system. Do a bit of research to determine where this directory lives and adjust accordingly, and make sure that the path uses "\" and not any "/".
Restart WAMP and try to run your migrations again.
Related
how to solve this error?
bundling failed: Error: Unable to resolve module ../../assets/images/background.png from src\IntroScreen\IntroScreen.js
Just check this folder with your explorer yourProject/assets/images/background.png is there any background.png exist ?
It's because maybe in the background your server was running and you dragged the image or folder into the assets folder while running the server. Since the newly added file address hasn't been stacked to memory or you can say the background hasn't been noted you already copied the image. So it throws this error.
So now you close the server then you restart it again or rerun npm then the server or interpreter will note that and put it on memory. Then you will not see this error.
I'm not sure if this is an issue with vagrant, virtualbox or a configuration issue inside the box itsef, however:
Using the following setup: Apache is running in the guest with its server root set to /srv/http, this is a synched folder which points to ./public_html on the host.
While most of the time it works as expected, the following steps causes an issue
1) Navigate to a file that doesn't exist localhost:8080/test2.css -- shows a 404 error as expected but correctly connects to the guest which is serving the error
2) Create test2.css with some content and place it in public_html
3) Reload localhost:8080/test2.css -- Still shows a 404 error even though the file now exists
4) To debug, run vagrant ssh and then ls /srv/http. Which shows:
ls: cannot access test2.css: No such file or directory
So it's seeing the file, sort of but it shows without any permissions:
-????????? ? ? ? ? test2.css
-rw-rw-r-- 1 vagrant 7 Oct 23 11:13 test3.css
If I then re-save the file as test3.css, a file that hasn't yet been accessed it works perfectly. E.g. on the host, save the file I had open as test3.css and then navigate to it, it works as expected!
Any ideas? On why this might be?
In short: If apache has tried to read a file that doesn't exist, creating that file will then cause it to have invalid permissions. If apache has never tried to read the file before, it can be created and work as expected.
Thanks for any help, I'm really confused by this!
This turned out to be a kernel bug on the guest. Upgrading to 4.2.4 using the same Vagrant/Virtualbox/Guest Modules solved the issue.
I'm moving a website to a new domain and server and I'm running into some problems. This website works with Smarty, and I've never used it before. I think I got a very basic problem, but I can't find the answer online.
I've moved all the FTP files to the new server
I've copied the database
I've edited the config file with the new database information
Now only EVERY page (even a blank test.php file with a simple echo) I get "failed to open stream" errors.
Warning: rename(/home/*websitename*/domains/*websitename*.com/public_html//skins/default/compiled/65e3d4d7349f9687ce73f56b61992749304409a2.file.index.tpl.php) [function.rename]: failed to open stream: Permission denied in /home/*websitename*/domains/*websitename*.com/public_html/external/smarty/sysplugins/smarty_internal_write_file.php on line 48
Warning: rename(/tmp/wrtPBIHNP,/home/*websitename*/domains/*websitename*.com/public_html//skins/default/compiled/65e3d4d7349f9687ce73f56b61992749304409a2.file.index.tpl.php) [function.rename]: Permission denied in /home/*websitename*/domains/*websitename*.com/public_html/external/smarty/sysplugins/smarty_internal_write_file.php on line 48
Warning: chmod() [function.chmod]: No such file or directory in /home/*websitename*/domains/*websitename*.com/public_html/external/smarty/sysplugins/smarty_internal_write_file.php on line 50
Warning: include(/home/*websitename*/domains/*websitename*.com/public_html//skins/default/compiled/65e3d4d7349f9687ce73f56b61992749304409a2.file.index.tpl.php) [function.include]: failed to open stream: No such file or directory in /home/*websitename*/domains/*websitename*.com/public_html/external/smarty/sysplugins/smarty_internal_template.php on line 432
Warning: include() [function.include]: Failed opening '/home/*websitename*/domains/*websitename*.com/public_html//skins/default/compiled/65e3d4d7349f9687ce73f56b61992749304409a2.file.index.tpl.php' for inclusion (include_path='.:/usr/local/lib/php') in /home/*websitename*/domains/*websitename*.com/public_html/external/smarty/sysplugins/smarty_internal_template.php on line 432
It looks like a problem with premissions, but I've made EVERY file on the FTP premission 777 (to test) and this does not solve it.
There are two backslashes /public_html//skins/ which is weird.
The code is exactly the same on the "old" server, besides the config file. Only thing new is the domain name.
What am I doing wrong?
You should set for directory compiled permissions 755 or 777.
You should probably also remove all compiled and cached files (if you use cache) because it may also cause problems
I installed apache2.2.21 and I need this specific version, I'm trying to load mod_security2.
The apache server is 32bits and is running on windows 8 64bits.
I did everything possible to get the job done, but I couldn't, can anyone help me?
I put mod_security.so in modules directory, and edited httpd.conf file to load the module but when trying to start the server, it gives me this message:
httpd.exe: Syntax error on line 126 of C:/Apache2.2.21/conf/httpd.conf: Cannot load C:/Apache2.2.21/modules/mod_security2.so into server: The specified module could not be found.
Warning: imagejpeg() [function.imagejpeg]: Unable to open '/home/SITENAME/public_html/files/cache/052f225905c1618003df0c5088aec7a9.jpg' for writing: Permission denied in /home/SITENAME/public_html/concrete/helpers/image.php on line 172
I emptied the cache directory and still no luck, and if I change the permissions on the cache folder then I get another error and I can't use the site at all:
Warning: require_once(Zend/Cache/Backend/File.php) [function.require-once]: failed to open stream: No such file or directory in /home/MYACCOUNT/public_html/concrete/libraries/3rdparty/Zend/Cache.php on line 133
Fatal error: require_once() [function.require]: Failed opening required 'Zend/Cache/Backend/File.php' (include_path='.:/usr/lib/php:/usr/local/lib/php:/home/owen/php') in /home/MYACCOUNT/public_html/concrete/libraries/3rdparty/Zend/Cache.php on line 133
I don't get it? I've never had this problem before.
Sounds like a permissions problem to me, but we can't tell from this end.
If you can FTP (or CD) into that /home/SITENAME/public_html/files/
and see if 'files' is owned by, and has the same permissions as public_html
Then see what permissions they NEED to have for your hosting setup.
Check that directory exists.
Check if web server daemon, most of the time - www-data, has write permissions to that particular directory.
For future reference the problem was the PHP handler. It has been changed to CGI mode (as opposed to DSO) and they turned suEXEC ‘off’ - might be useful for someone down the line.