There is currently an MBS outage, due to the same issue described in:
Could you please restart the fedmsg-hub service on mbs-backend01.phx2.fedoraproject.org?
@smooge thank you. Does it make sense in the future for @jkaluza and I to have sudo access to run systemctl restart fedmsg-hub?
systemctl restart fedmsg-hub
You should already. All members of the 'sysadmin-mbs' fas group should be able to use sudo on mbs-backend01.phx2.fedoraproject.org
Please do test it out and confirm it's all working for you...
Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
@kevin I'm not sure why I don't have access to do it then:
[mprahl@mbs-backend01 ~][PROD]$ sudo systemctl restart fedmsg-hub
Sorry, user mprahl is not allowed to execute '/bin/systemctl restart fedmsg-hub' as root on mbs-backend01.phx2.fedoraproject.org.
[mprahl@mbs-backend01 ~][PROD]$ sudo su -
Sorry, user mprahl is not allowed to execute '/bin/su -' as root on mbs-backend01.phx2.fedoraproject.org.
Ah, I see, it's limited there to journalctl.
I can fix it, but will need a freeze break or waiting until we are out of freeze. Since this isn't urgent, shall we just wait until after freeze?
@kevin sounds good. Should I file a separate ticket?
to comment on this ticket.