Hello,
(if you hear about this the first time, see status.o.o and the ticket
system for some details.)
I applied a workaround to get at least static.o.o back in a reliable
way: since pages running via login2.o.o work without problems, I
switched static.o.o over to use the login proxy.
Changes done:
- added vhost config for static.o.o on daffy1
- added haproxy config for static.o.o via login proxy on anna
- changed DNS entry for static.o.o from "A 195.135.221.143" and "AAAA
2620:113:80c0:8::18" to "CNAME login2.o.o"
Note that this only "fixes" static.o.o which causes the most visible
problems (loosing all styling on several pages).
Other services routed via anna/elsa (everything with CNAME proxy.o.o)
are still affected by the network problems. (We could apply the same
workaround for them, but I'd prefer to get the network issue fixed
instead ;-)
Regards,
Christian Boltz
--
[GUI vs. Command-Line] Einen ähnlichen Streit wird es in 20 Jahren
auch geben, wenn die "2D-Screenfanatiker" auf die "VR Fans" losgehen
und wieder ein Streit vom Zaun bricht der an Sinnfreiheit kaum zu
überbieten ist. [Phillip Richdale in suse-linux]
--
To unsubscribe, e-mail: heroes+unsubscribe(a)opensuse.org
To contact the owner, e-mail: heroes+owner(a)opensuse.org