I got just a 502 Bad gateway (no content, just status) from the webserver at /var/run/lighttpd/persondata
I was started a few hours before (14:52 UTC) with "webservice --backend=kubernetes" start and did run fine
because of that 502 Bad gateway I decided to stop the webservice with "webservice stop"
tools.persondata@tools-sgebastion-07:~$ webservice stop
Stopping webservice
Then I started it again, this time without --backend=kubernetes:
tools.persondata@tools-sgebastion-07:~$ webservice start
Starting webservice.........
Still no success, but Status 503 Service Unavailable (but this time with a content, I shall contact the maintainer (which is me).
Looking at the error.log I see a line
2019-03-11 20:19:50: (configfile.c.1154) source: /var/run/lighttpd/persondata line: 631 pos: 1 parser failed somehow near here: (EOL)
No help, since /var/run/lighttpd/persondata does not exists or is not accessible from sgebastion
tools.persondata@tools-sgebastion-07:~$ ls -l /var/run/lighttpd/persondata
ls: cannot access '/var/run/lighttpd/persondata': No such file or directory
The only thing I see is this, and I see it still
tools.persondata@tools-sgebastion-07:~$ kubectl get pods
NAME READY STATUS RESTARTS AGE
persondata-676273626-15020 1/1 Terminating 0 1d
Now, after one hour there is no change, kubectl get pods shows the same line.
tools.persondata@tools-sgebastion-07:~$ date
Mon Mar 11 21:06:52 UTC 2019
What else can I do to get a running webservice?