dgilmore changed the topic of #fedora-riscv to: Fedora on RISC-V https://fedoraproject.org/wiki/Architectures/RISC-V || Logs: https://libera.irclog.whitequark.org/fedora-riscv || Alt Arch discussions are welcome in #fedora-alt-arches
fuwei has quit [Quit: Konversation terminated!]
fuwei has joined #fedora-riscv
fuwei has quit [Ping timeout: 276 seconds]
fuwei has joined #fedora-riscv
fuwei has quit [Quit: Konversation terminated!]
fuwei has joined #fedora-riscv
fuwei has quit [Ping timeout: 252 seconds]
fuwei has joined #fedora-riscv
fuwei has quit [Quit: Konversation terminated!]
fuwei has joined #fedora-riscv
fuwei has quit [Quit: Konversation terminated!]
fuwei has joined #fedora-riscv
zsun has joined #fedora-riscv
zsun has quit [Quit: Leaving.]
jednorozec has quit [Ping timeout: 276 seconds]
pbsds37 has joined #fedora-riscv
pbsds3 has quit [Ping timeout: 260 seconds]
pbsds37 is now known as pbsds3
davidlt has joined #fedora-riscv
<davidlt> rwmjones, djdelorie, there was some issues with connectivity to fedora.riscv.rocks and that basically killed kojid.service. You need to manually systemctl restart kojid
<rwmjones> davidlt: ok.. on all 3 machines?
<davidlt> rwmjones, looking at Koji Hub results all boards went offline
<rwmjones> ok .. here goes
<davidlt> Assuming kojid.service properly failed, you can do this:
<davidlt> RestartSec=10min
<davidlt> Restart=always
<rwmjones> ok
<davidlt> reload, and restart. In this case systemd would take take relaunching it on failure, any decent value for RestartSec is OK.
<davidlt> We don't know if disruptions to fedora.riscv.rocks are over or not, but hopefully we don't need to restart it more than once.
<rwmjones> back in 30 mins
<djdelorie> done
davidlt has quit [Ping timeout: 252 seconds]