From: ROGEZ Matthieu <matthieu.rogez@fivesgroup.com>
To: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Some issues with current doc
Date: Tue, 16 Jan 2018 16:19:04 +0000 [thread overview]
Message-ID: <HE1PR0601MB2252D968553759E7E896BE9CF3EA0@HE1PR0601MB2252.eurprd06.prod.outlook.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3703 bytes --]
Hi all,
First time Toaster user here. I've been playing around with the latest version of toaster (rocko) lately and encountered some issue with the current documentation.
Here are some notes and work-arounds I've used to make it work :
- For the "production" server, I've had to add a "dummy" orm/fixtures/custom.xml and use TEMPLATECONF=poky instead of TOASTER_CONF variable so that TOASTER_DIR=`pwd` TEMPLATECONF=poky manage.py checksettings works
- But then other issues (don't remember exactly) made me switch back to use the "normal" configuration (not production).
- The systemd toaster service file doesn't allow stopping the service and didn't work with my company proxy. Also I didn't wanted to run toaster inside screen
Here is what I used:
/etc/system/system/toaster.service
[Unit]
Description=Toaster Service
[Service]
# toaster is not a proper daemon, so we cannot use the forking type
# use the oneshot + RemainAfterExit to model this toaster controller process.
# Proper systemd integration would completely bypass the toaster script and directly
# control runbuilds and runserver as system services.
Type=oneshot
RemainAfterExit=yes
# I use a simple user named "user"
User=user
WorkingDirectory=/home/user/poky/
# UGLY: Patch away the killing loop to let systemd terminate runbuilds and runserver processes
# Otherwise, the original script wasn't able to TERM the other processes
# when executed as a systemd service. Instead it was looping until reaching the systemd timeout
# and therefore was killed without being able to properly terminate child processes
ExecStartPre=/bin/sh -c 'sed -e "s/kill -0 \$pid 2>\/dev\/null/false/" bitbake/bin/toaster > bitbake/bin/toaster2'
# I'm using a system v215 on a Debian 8.5
# I've tried many ways to get my service to honor the {http,https,no}_proxy env variables
# such as PassEnvironment=http_proxy, or [Manage]DefaultEnvironment=http_proxy=my_proxy.address:port/ in system.conf, ...
# but none worked (bugs that may be fixed with recent versions ?)
# So I resort to sourcing a simple proxy.sh script which export the relevant proxy env variables
ExecStart=/bin/bash -c 'source /etc/profile.d/proxy.sh && source oe-init-build-env build && source ../bitbake/bin/toaster2 start webport=0.0.0.0:8000'
ExecStop=/bin/bash -c 'source /etc/profile.d/proxy.sh && source oe-init-build-env build && source ../bitbake/bin/toaster2 stop'
[Install]
WantedBy=multi-user.target
I'm sure there might be better ways of dealing with these issues, but I couldn't find any quickly.
Hope it will help other users here. Maybe some of this could be used to update the current documentation ?
Thanks for this awesome project !
Matthieu
[https://portal.fivesgroup.com/FIRSTspiritWeb/fivesportal/media/images_for_content/fives_1/signatures/logo_tagline_small.jpg]
Matthieu ROGEZ
Software Development Engineer | Ingénieur Développement Info.
- Intralogistics
Fives Intralogistics S.A.S
Rue Fleury Jay
Grigny, 69520 - France
Tel: +33 4 78 73 00 07
Fax: +33 4 78 73 00 89
matthieu.rogez@fivesgroup.com<mailto:matthieu.rogez@fivesgroup.com>
www.fivesgroup.com<http://www.fivesgroup.com>
[https://portal.fivesgroup.com/FIRSTspiritWeb/fivesportal/media/images_for_content/fives_1/signatures/signature_facebook.png]<https://www.facebook.com/pages/Fives/278132595611080>[https://portal.fivesgroup.com/FIRSTspiritWeb/fivesportal/media/images_for_content/fives_1/signatures/signature_linkedin.png]<http://www.linkedin.com/company/fives?trk=top_nav_home>
[-- Attachment #1.2: Type: text/html, Size: 20815 bytes --]
[-- Attachment #2: image001.jpg --]
[-- Type: image/jpeg, Size: 33808 bytes --]
[-- Attachment #3: image002.png --]
[-- Type: image/png, Size: 15089 bytes --]
[-- Attachment #4: image003.png --]
[-- Type: image/png, Size: 15171 bytes --]
next reply other threads:[~2018-01-16 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 16:19 ROGEZ Matthieu [this message]
2018-01-16 22:08 ` Some issues with current doc Reyna, David
[not found] ` <CAFNP8OvwLkAoTW3dzW9kEKZ52L=m945OFvst9A0dTz6y+DOVpw@mail.gmail.com>
2018-01-18 21:13 ` Kristi Rifenbark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=HE1PR0601MB2252D968553759E7E896BE9CF3EA0@HE1PR0601MB2252.eurprd06.prod.outlook.com \
--to=matthieu.rogez@fivesgroup.com \
--cc=toaster@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).