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

i may have broken http://phpimagick.com/ #31

Closed
MadVillager opened this issue Nov 6, 2018 · 4 comments
Closed

i may have broken http://phpimagick.com/ #31

MadVillager opened this issue Nov 6, 2018 · 4 comments

Comments

@MadVillager
Copy link

was playing around with the whirlygif demo and now every page at phpimagick.com has an error message on it !

( 4 me at least ! )

Exception Predis\Connection\ConnectionException: 'Connection refused [tcp://127.0.0.1:6379]'

etc.

@Danack
Copy link
Collaborator

Danack commented Nov 6, 2018

...thanks. I've poked the redis instance to make it start up again.

I really need to find out why redis keeps falling over. Hmm.

It might be because the server was out of diskspace.....I've made a load of space to see if that 'fixes' it. At some point I'm going to redeploy the whole site using containers, which should make most of this problem 'go away'.

Please give me another shout if you see this again.

@Danack Danack closed this as completed Nov 6, 2018
@MadVillager
Copy link
Author

thanx mate

fyi i'm still seeing some busted pages

errors thrown:

Exception Jig\JigException: 'Failed to render template 'Jig\CompiledTemplate\exampleJig' : Connection refused [tcp://127.0.0.1:6379]'

http://phpimagick.com/ImagickPixel/setColor

as well as

502 Bad Gateway

http://phpimagick.com/ImagickPixel/getColorCount

as well as

Exception Predis\Connection\ConnectionException: 'Connection refused [tcp://127.0.0.1:6379]'

http://phpimagick.com/ImagickPixelIterator

@Danack
Copy link
Collaborator

Danack commented Nov 14, 2018

Thanks. So it’s the redis cache that keeps falling over, but somewhat ironically I won’t be able to restart it until tomorrow morning evening as i’m away from a computer as i’m attending a redis conference...

@Danack
Copy link
Collaborator

Danack commented Nov 16, 2018

It's back again - possibly it was just running out of memory. I will be moving it to a container based deployment soon, so will just keep kicking it when it falls over rather than fixing it properly until it's in a container.

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