Hi, There is a problem with toaster start up process. When I'm trying to start the toaster the below error occur. Also, if I start a new build, I cannot see the build in the web interface. Commit: d5a0a6b67632c99ea08e2782e8b7e345962470df $ source toaster start The system will start. Syncing... Creating tables ... Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Synced: > django.contrib.staticfiles > django.contrib.humanize > south Not synced (use migrations): - orm (use ./manage.py migrate to migrate these) Running migrations for orm: - Nothing to migrate. - Loading initial data for orm. Installed 0 object(s) from 0 fixture(s) server address: 127.0.0.1, server port: 8200 Successful start. [ionut@ionut-fedora build]$ [2]+ Exit 1 bitbake --observe-only -u toasterui > ${BUILDDIR}/toaster_ui.log 2>&1 [ionut@ionut-fedora build]$ cat toaster_ui.log ERROR: Could not connect to server at localhost:8200 (global name 'logger' is not defined) [ionut@ionut-fedora build]$ sudo netstat -nltpu | grep python [sudo] password for ionut: tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN 2605/python tcp 0 0 127.0.0.1:8200 0.0.0.0:* LISTEN 2613/python [ionut@ionut-fedora build]$ ps wwauxf | grep toaster ionut 2603 0.4 0.2 232560 18536 pts/0 S 13:55 0:00 \_ python /home/ionut/work/toaster/poky/bitbake/bin/../lib/toaster/manage.py runserver 0.0.0.0:8000 ionut 2605 0.7 0.2 308744 22244 pts/0 Sl 13:55 0:00 | \_ /usr/bin/python /home/ionut/work/toaster/poky/bitbake/bin/../lib/toaster/manage.py runserver 0.0.0.0:8000 ionut 2639 0.0 0.0 112672 916 pts/0 S+ 13:56 0:00 \_ grep --color=auto toaster ionut 2613 0.0 0.2 240508 21068 ? S 13:55 0:00 python /home/ionut/work/toaster/poky/bitbake/bin/bitbake --postread conf/toaster.conf --server-only -t xmlrpc -B localhost:8200 [ionut@ionut-fedora build]$ cat bitbake-cookerdaemon.log [ionut@ionut-fedora build]$ du -sh bitbake-cookerdaemon.log 0 bitbake-cookerdaemon.log Cheers, Ionut C
Patch sent to bibake-devel mailing list.
Verified. Issue is now fixed. IonutC
*** Bug 6084 has been marked as a duplicate of this bug. ***