Page MenuHomePhabricator

flossbrowser php5.6 Kubernetes pod stuck in CrashLoopBackOff
Open, Needs TriagePublic

Description

$ kubectl get po
NAME                           READY     STATUS             RESTARTS   AGE
flossbrowser-265587860-jl60h   0/1       CrashLoopBackOff   2269       8d
$ kubectl logs po/flossbrowser-265587860-jl60h
Duplicate config variable in conditional 0 global: server.errorlog
2019-02-19 00:50:51: (configfile.c.957) source: /var/run/lighttpd/flossbrowser line: 65 pos: 19 parser failed somehow near here: (EOL)
$HOME/.lighttpd.conf
server.errorlog = "{home}/logs/error.log"
server.breakagelog = "{home}/logs/error.log"
accesslog.filename = "{home}/logs/access.log"

Event Timeline

Mentioned in SAL (#wikimedia-cloud) [2019-02-19T00:54:51Z] <bd808> Commented out $HOME/.lighttpd.conf contents and restarted webservice (T216462)

I'm currently having a lot of things on my plate. Is this something I have to act on immediately/soonish?