Ubuntu 16.04.1 LTS performed an automatic upgrade to 2.3.0, and now Tyk will not start. It seems like re-running the configuration script may be necessary, based on a 2015 post I found. Here are the logs of what is happening:
2016-12-07 11:54:48 configure tyk-dashboard:amd64 1.3.0.12
2016-12-07 11:54:48 status unpacked tyk-dashboard:amd64 1.3.0.12
2016-12-07 11:54:48 status half-configured tyk-dashboard:amd64 1.3.0.12
2016-12-07 11:54:48 status installed tyk-dashboard:amd64 1.3.0.12
2016-12-07 11:54:48 configure tyk-gateway:amd64 2.3.0.31
2016-12-07 11:54:48 status unpacked tyk-gateway:amd64 2.3.0.31
2016-12-07 11:54:48 status half-configured tyk-gateway:amd64 2.3.0.31
2016-12-07 11:54:48 status installed tyk-gateway:amd64 2.3.0.31
root@ubuntu-512mb-nyc3-01-tyk22:~# sudo service tyk-dashboard start
root@ubuntu-512mb-nyc3-01-tyk22:~# sudo service tyk-dashboard status
● tyk-dashboard.service - Tyk API Dashboard
Loaded: loaded (/lib/systemd/system/tyk-dashboard.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Dec 07 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1846]: /src/github.com/TykTechnologies/tyk-analytics/Main.go:471 +0x416
Dec 07 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1846]: main.main()
Dec 07 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1846]: /src/github.com/TykTechnologies/tyk-analytics/Main.go:833 +0x72
Dec 07 12:10:17 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: tyk-dashboard.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 07 12:10:17 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: tyk-dashboard.service: Unit entered failed state.
Dec 07 12:10:17 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: tyk-dashboard.service: Failed with result ‘exit-code’.
Dec 07 12:10:17 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: tyk-dashboard.service: Service hold-off time over, scheduling restart.
Dec 07 12:10:17 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: Stopped Tyk API Dashboard.
Dec 07 12:10:17 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: tyk-dashboard.service: Start request repeated too quickly.
Dec 07 12:10:17 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: Failed to start Tyk API Dashboard.
Dec 7 12:10:16 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: Started Tyk API Dashboard.
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: time=“Dec 7 12:10:17” level=info msg=“Using /opt/tyk-dashboard/tyk_analytics.conf for configuration”
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: time=“Dec 7 12:10:17” level=info msg=“Creating new Redis connection pool”
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: message repeated 3 times: [ time=“Dec 7 12:10:17” level=info msg=“Creating new Redis connection pool”]
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: time=“Dec 7 12:10:17” level=info msg=“Adding available nodes…”
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: time=“Dec 7 12:10:17” level=info msg=“Tyk Analytics Dashboard v1.3.0.12”
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: time=“Dec 7 12:10:17” level=info msg=“Copyright Martin Buhr 2016”
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: time=“Dec 7 12:10:17” level=info msg=“https://www.tyk.io”
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: time=“Dec 7 12:10:17” level=info msg=“Listening on port: 3000”
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: panic: html/template: pattern matches no files: portal/templates/*.html
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: goroutine 1 [running]:
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: panic(0xa8a660, 0xc42041a4a0)
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: #011/usr/local/go/src/runtime/panic.go:500 +0x1a1
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: html/template.Must(0x0, 0xeb73c0, 0xc42041a4a0, 0x0)
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: #011/usr/local/go/src/html/template/template.go:340 +0x66
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: main.setupPortalTemplates()
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: #011/src/github.com/TykTechnologies/tyk-analytics/Main.go:471 +0x416
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: main.main()
Dec 7 12:10:17 ubuntu-512mb-nyc3-01-tyk22 tyk-analytics[1836]: #011/src/github.com/TykTechnologies/tyk-analytics/Main.go:833 +0x72
sudo service tyk-gateway start
root@ubuntu-512mb-nyc3-01-tyk22:~# sudo service tyk-gateway status
● tyk-gateway.service - Tyk API Gateway
Loaded: loaded (/lib/systemd/system/tyk-gateway.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Dec 07 12:09:48 ubuntu-512mb-nyc3-01-tyk22 tyk[1755]: /src/github.com/TykTechnologies/tyk/main.go:898 +0x6d8
Dec 07 12:09:48 ubuntu-512mb-nyc3-01-tyk22 tyk[1755]: main.main()
Dec 07 12:09:48 ubuntu-512mb-nyc3-01-tyk22 tyk[1755]: /src/github.com/TykTechnologies/tyk/main.go:1073 +0x112
Dec 07 12:09:48 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: tyk-gateway.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 07 12:09:49 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: tyk-gateway.service: Unit entered failed state.
Dec 07 12:09:49 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: tyk-gateway.service: Failed with result ‘exit-code’.
Dec 07 12:09:49 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: tyk-gateway.service: Service hold-off time over, scheduling restart.
Dec 07 12:09:49 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: Stopped Tyk API Gateway.
Dec 07 12:09:49 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: tyk-gateway.service: Start request repeated too quickly.
Dec 07 12:09:49 ubuntu-512mb-nyc3-01-tyk22 systemd[1]: Failed to start Tyk API Gateway.