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.

Sign up for GitHub

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

Jump to bottom

No more acces to pad after upgrade to 1.8.18~ynh2 #175

Open
tutle opened this issue Sep 4, 2022 · 5 comments
Open

No more acces to pad after upgrade to 1.8.18~ynh2 #175

tutle opened this issue Sep 4, 2022 · 5 comments

Comments

@tutle
Copy link

tutle commented Sep 4, 2022

Hello
Most of my pads mention nothing or I'm not allowed .
Also the first windows is basely grey (it used to be green).
Quiet lost, any suggestion ?

image
image
@tutle
Copy link
Author

tutle commented Sep 4, 2022

image

@tutle
Copy link
Author

tutle commented Sep 5, 2022

Seems to be solved with server reboot...

@tutle tutle closed this as completed Sep 5, 2022
@tutle
Copy link
Author

tutle commented Sep 5, 2022

After an electric shutdown, still have problem to access to my pads, seems to be random, any way to restart the app once the server is on ?

@tutle tutle reopened this Sep 5, 2022
@tutle
Copy link
Author

tutle commented Sep 5, 2022

Seems to be a boot services order problem (etherpad appears starting earlier than uwsgi-app@pgadmin), solved by reboot etherpad once server on
systemctl restart etherpad_mypads.service

@yalh76
Copy link
Member

yalh76 commented Sep 28, 2022

There is no link between etherpad_mypads and uwsgi-app@pgadmin, so you should look at the log from /var/log/etherpad_mypads/etherpad.log to look what's happens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tutle @yalh76