Skip to content
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

Sandbox offline #365

Closed
jrmyio opened this issue Apr 26, 2017 · 3 comments
Closed

Sandbox offline #365

jrmyio opened this issue Apr 26, 2017 · 3 comments

Comments

@jrmyio
Copy link
Contributor

jrmyio commented Apr 26, 2017

Getting the following error when visiting sandbox.cmf.symfony.com:


Warning: file_put_contents(): Only 0 of 6 bytes written, possibly out of free disk space in /app/vendor/doctrine/cache/lib/Doctrine/Common/Cache/FileCache.php on line 254

Warning: file_put_contents(): Only 0 of 421 bytes written, possibly out of free disk space in /app/vendor/doctrine/cache/lib/Doctrine/Common/Cache/FileCache.php on line 254

Warning: file_put_contents(): Only 0 of 31 bytes written, possibly out of free disk space in /app/vendor/doctrine/cache/lib/Doctrine/Common/Cache/FileCache.php on line 254
Oops! An Error Occurred

The server returned a "500 Internal Server Error".

The admin tool currently allows full access to the entire content tree. As a result its possible to break the entire routing configuration. In many cases when you see an error on this site, its caused by someone having done exactly that. You can reload the entire content to the original state by calling reload-fixtures.php
@dbu
Copy link
Member

dbu commented Apr 27, 2017

looks like either an issue with logrotating or somebody uploaded too many things and filled the disk while experimenting. but its recovered now, http://sandbox.cmf.symfony.com/en loads again.

@dbu dbu closed this as completed Apr 27, 2017
@jrmyio
Copy link
Contributor Author

jrmyio commented Apr 28, 2017

Still issues with disk space. Can't login to admin.

@dbu
Copy link
Member

dbu commented Apr 28, 2017

ah sorry, i thougt the problem was on the front page. now i can see the problem. i re-staged the virtual machine, now i can log into the backend again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants