Closed anmol26s closed 6 years ago
b01xy
commented
6 years ago Hi,
I had the same problem after upgrading the application
I tried to restore backups without success
At the end I re-created a directory /home/etherpad_mypads/ which seems to have been deleted by the upgrade process
and did
chown etherpad_mypads:etherpad_mypads /home/etherpad_mypads/
and then restarted nging and etherpad services and it worked
++
b
b01xy
commented
6 years ago and I add to re-install the plugins threw the admin interface
maniackcrudelis
commented
6 years ago Hi guys,
You're not suppose to have any /home/etherpad_mypads dir, can you say me what's in this directory ? Is there some plugins ? In this case, which ones, all your plugin or only those you've installed by yourself ? The home directory of the user etherpad_mypads is /var/www/etherpad_mypads.
And because, you're not supposed to have this directory, nothing in the upgrade has to remove this directory or doing anything else with it.
If you have any other problem with etherpad, please have a look to the log /var/log/etherpad_mypads/etherpad.log instead of nginx one.
anmol26s
commented
6 years ago I see something like this in the log:
[WARN] console - DirtyDB is used. This is fine for testing but not recommended for production.
events.js:141
throw er; // Unhandled 'error' event
^
Error: EACCES: permission denied, open '/var/www/etherpad_mypads/dirty.db'
at Error (native)
RESTART!
Ensure that all dependencies are up to date... If this is the first time you have run Etherpad please be patient.
Do you have anything related before these lines ? Etherpad's not supposed to use the dirty DB, there's a sql DB configured for this purpose.
anmol26s
commented
6 years ago The workaround I did is after the restore I upgraded the Etherpad and it worked again after the upgrade.
maniackcrudelis
commented
6 years ago Ok, if at least it works after an upgrade it's a good thing. Because, I have to say, I've no idea why it would suddenly use a dirty DB...
Is it ok also for you @b01xy after an upgrade ?
b01xy
commented
6 years ago Hello,
for me it's working fine after what happened related to my previous messages I suspect that my upgrade process did not ended properly because I lost the ssh session nothing special in /var/log/etherpad_mypads/etherpad.log, I'm not using a dirtydb and nothing in :
ls -al /home/etherpad_mypads/
total 20
drwxr-xr-x 3 etherpad_mypads etherpad_mypads 4096 nov. 19 17:00 .
drwxr-xr-x 20 root root 4096 nov. 19 16:32 ..
drwxr-xr-x 222 etherpad_mypads etherpad_mypads 12288 nov. 19 17:39 .npmso all good :) ++ b
maniackcrudelis
commented
6 years ago Ok, nice to see all's good now. Then I close this issue.
After restoring the application it gave 502 Bad Gateway error.
Nginx error access log:
2017/XX/XX XX:XX:XX [error] 6990#0: *5407 connect() failed (111: Connection refused) while connecting to upstream, client: XXX.XX.XX.X, server: pad.domain.tld, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:9001/favicon.ico", host: "pad.domain.tld"