Project

General

Profile

Actions

communication #80454

closed

survey.opensuse.org returns 503

Added by lkocman over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Servers hosted in NBG
Target version:
-
Start date:
2020-11-26
Due date:
% Done:

50%

Estimated time:

Description

Hello admins

as previously raised on irc survey.opensuse.org returns 503.
That would not be normally a critical issue as we do surveys sporadically, however we need to review results of ARM related survey that ended on last Friday.

Can you please have a look at the limesurvey instance?
Person who did the original deployment is Lars.

Thank you

Lubos

Actions #1

Updated by cboltz over 3 years ago

  • Assignee set to bmwiedemann
  • Private changed from Yes to No

limesurvey.infra.opensuse.org doesn't respond to ping, so a SUSE admin will have to look at it. Bernhard, maybe you? ;-)

Actions #2

Updated by bmwiedemann over 3 years ago

  • Assignee changed from bmwiedemann to cboltz
  • % Done changed from 0 to 50

grub bootloader config was bad. Booted it up via DVD for now, but cannot login to fix the bootloader permanently.

pass doesn't have an entry for limesurvey and SSO or ssh-key do not work either.

cboltz maybe?

Otherwise, I could change the root-PW in some other way...

Actions #3

Updated by cboltz over 3 years ago

  • Assignee changed from cboltz to bmwiedemann

I added your and my ssh keys via the salt "backdoor" ;-) so you should be able to login as root now.

We'll need to run highstate, and should afterwards drop the keys from root authorized_keys again.

There's another interesting "detail": On boot, nginx was started, but limesurvey complained about missing permissions for /var/cache/limesurvey. This directory is owned by wwwrun while nginx is running as nginx. Looking at the bash history, it turned out that apache is expected to serve limesurvey. I disabled nginx, then enabled and started apache - limesurvey is back :-)

Actions #4

Updated by cboltz over 3 years ago

  • Assignee changed from bmwiedemann to cboltz

Bernhard reported on IRC that he has fixed the boot issue.

Remaining tasks are running highstate for the base setup (so that for example ssh login works for everybody) and dropping the ssh keys from root authorized_keys again. I'll do that in the next days.

Actions #5

Updated by cboltz about 3 years ago

  • Status changed from New to Resolved

Initial highstate done (now you know what "in the next days" may mean ;-)

I also verified that sudo works, and therefore removed the now-superfluous SSH keys of Bernhard and myself from /root/.ssh/authorized_keys.

Actions

Also available in: Atom PDF