-
Notifications
You must be signed in to change notification settings - Fork 11
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
502 Bad Gateway weka.mongodb Failed to start Service for snap application wekan.mongodb. #117
Comments
Are you using edge snap? Please change to stable:
|
Also, there still are problems with Snap on CentOS 7 and RHEL7: |
Anyway, save settings to file:
Then stop wekan:
And backup database etc files, for example:
Then on other server, that is newest Ubuntu or Debian install Wekan Snap, stop Wekan:
|
And then add those snap settings:
etc, and then start wekan
|
hi, |
How do I reinstall wekan? |
Install centos 7 (b) with nginx on a new server, as wekan previously told you and follow the instructions to copy the common folder of the production server that we will call server A to server B (which is the new one), in this server installation B had already enabled a new url cr-bck.domain.com, on server B run set wekan root-url = 'https: //original.domain.com' but it responded 404, then reactivate the url cr-bck. domain.com that refers to the backup of the production url that I had enabled on server A and I was able to reset my Board, that is, I was able to access with the users that I had and see my tasks, but when selecting a task or comments the domino cr-bck.dominio.com continues to request or continue resolving the domain 'https://original.dominio.com'. How can I change or have my board redirected to the new domain? |
Etc, see Snap install page: |
I could already reset my dashboard, apply on the source server sudo su Move my backup to another side and run snap stop wekan And repaint wekan from the beginning So I did not lose my information and it was restored in the same domain and server |
Hello! Its doesnt work.. I had done fresh install on debian 10, without anything. Installed wekan from scratch (snapd packet). Copied old "common" folder with, but it keep crashing after start. 5-10 second and service wekan stoped. Where is snapd wekan place logs? |
Did you reboot your debian 10 server after installing snapd ?
|
no i didnt. I had a backup, before snap was updated. I rolled back vm with wekan and disabled updates with this commands. |
Yes, there is problems with Snap on CentOS 7 #103 (comment) On Snap, MongoDB database raw files are at
Some parts of that process is also described here: |
Back up the common folder well and move it from location, then completely unpack it wekan and snapd, clean your cache. |
A few days ago we installed Wekan and it worked great but after the update on Monday, January 6, it stopped working.
I have tried to lift it and recover my board but it was not possible for me, the MONGODB service does not work
I can't take the backup either because the dumo doesn't work, I get the following error / var / lib / snapd / snap / wekan / 714 / bin / mongodump: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
I tried to do everything that your documentation says but I can't recover my board, or do the backup correctly
========snap version
snap 2.42.2-1.el7
snapd 2.42.2-1.el7
series 16
centos 7
kernel 3.10.0-693.17.1.el7.x86_64
==============snap services
Service Startup Current Notes
wekan.caddy disabled inactive -
wekan.mongodb enabled inactive -
wekan.wekan enabled active -
======PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
80/tcp open http
443/tcp open https
3306/tcp open mysql
9001/tcp open tor-orort
The text was updated successfully, but these errors were encountered: