Etherpad - Broken exports #107

New Issue

Closed

opened 2021-07-19 09:29:53 +02:00 by muppeth · 5 comments

muppeth commented

2021-07-19 09:29:53 +02:00

Owner

Exporting to all formats but .etherpad gives 504

Exporting to all formats but `.etherpad` gives 504

muppeth added the

🤔️ Investigate

etherpad

bug

labels 2021-07-19 09:29:53 +02:00

muppeth commented

2021-07-20 07:22:32 +02:00

Author

Owner

Just did a quick test and looks like the export breaks at random (sometimes works sometimes doesn't). I haven't yet found a root cause or a way to properly reproduce.

muppeth commented

2021-07-21 08:58:48 +02:00

Author

Owner

So it could the that traditional "did you tried to switch it off and on again" could potentially be a fix. Not saying this is it of course and we should look into proper root cause and either report it upstream if its upstream issue or fix it locally, but it could be (of course if it does help) a temorary fix to the situation.

I have switched daily reboot in the cronjob already now (cause why not) but if you agree with my idea here, I will push the cronjob task to ansible.

@meaz perhaps at the end it is a good idea to restart etherpad once a day. I did restart it to set "DEBUG" loglevel to try to see if there is anything specific in the logs, but I did not manage to reproduce the issue after I did that. So it could the that traditional *"did you tried to switch it off and on again"* could potentially be a fix. Not saying this is it of course and we should look into proper root cause and either report it upstream if its upstream issue or fix it locally, but it could be (of course if it does help) a temorary fix to the situation. I have switched daily reboot in the cronjob already now (cause why not) but if you agree with my idea here, I will push the cronjob task to ansible.