Greengrass core: unable to listen on address localhost 8000

I'm trying to run AWS Greengrass Core on a new armv7l device. Everything installs correctly. config.conf is edited so "useSystemd" is "no". It looks like GGC crashes because another process is already using port 8000.

Here's the output of the command sudo greengrassd start:

Setting up greengrass daemon
Validating hardlink/softlink protection
Waiting for up to 1m10s for Daemon to start
listen tcp 127.0.0.1:8000: bind: address already in use
runtime failed to start: unable to listen on address: localhost:8000
amazonaws.com/iot/greengrass/ipc.(*Service).Serve
        /opt/src/src/amazonaws.com/iot/greengrass/ipc/server.go:75
main.main.func3
        /opt/src/src/amazonaws.com/iot/greengrass/daemon/daemon.go:289
runtime.goexit
        /usr/local/go/lib/src/runtime/asm_arm.s:1015
unable to start server
main.main.func3
        /opt/src/src/amazonaws.com/iot/greengrass/daemon/daemon.go:291
runtime.goexit
        /usr/local/go/lib/src/runtime/asm_arm.s:1015
The Greengrass daemon process with [pid = 3027] died

Here's relevant output from the command sudo netstat -tulpn:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      584/python3
[the rest deleted]
tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN      585/python3

Python3 version is 3.5.3. For various reasons, changing the Python port from 8000 to something else is not an option. Can I change the Greengrass port from 8000 to something else? Is there another solution I'm missing?

One additional piece of information: when I kill the two python3 process, Greengrass starts successfully. The "port already in use" error is the only obstacle I've encountered.

Edited by: RayFW on Aug 6, 2019 8:52 AM Typo

Edited by: RayFW on Aug 6, 2019 9:59 AM GGC successfully started