> -----Original Message----- > From: Khem Raj [mailto:raj.k...@gmail.com] > Sent: Friday, March 16, 2018 11:55 AM > To: Greg Wilson-Lindberg <gwil...@sakuraus.com> > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] How to get mysqy/mariadb to start on powerup. > > On Fri, Mar 16, 2018 at 8:58 AM, Greg Wilson-Lindberg <gwil...@sakuraus.com> > wrote: > >> From: Greg Wilson-Lindberg > >> Sent: Thursday, March 15, 2018 02:16 PM > >> To: Khem Raj <raj.k...@gmail.com> > >> Cc: yocto@yoctoproject.org > >> Subject: Re: [yocto] How to get mysqy/mariadb to start on powerup. > > > >> > > > >> > From: Khem Raj <raj.k...@gmail.com> > > > >> > Sent: Thursday, March 15, 2018 1:54 PM > >> > To: Greg Wilson-Lindberg > >> > Cc: yocto@yoctoproject.org > >> > Subject: Re: [yocto] How to get mysqy/mariadb to start on powerup. > > > >> > > > > >> > > On Thu, Mar 15, 2018 at 1:38 PM, Greg Wilson-Lindberg > >> > <gwil...@sakuraus.com> wrote: > >> > > I'm building an RPi3 system that is going to use mysql/mariadb. > >> > > I've got everything installed, but mysqld is not starting. > >> > > install_db.service does run on startup, but the mysqld.service > >> > > file never gets triggered. > >> > > > >> > > > >> > > Is there something that I'm missing to get it to run? I've search > >> > > online, but can't find anything that pertains to yocto. > >> > > > >> > > >> > poke on the system with systemctl/journalctl to see whats going on > > > >> > > > >> journalctl -u mysqld.service says no entries > > > >> systemctl status mysqld.service shows: > > > >> Loaded: loaded (/lib/systemd/system/mysqld.service; disabled; > >> vendor > >> preset: enabled) > > > >> Active: inactive (dead) > > > >> > > > >> I've rebooted the system a couple of times to see if install_db > >> needed to be run before mysql would run, no luck. > > > >> > > > > It's seems that maybe I need to add a bit about my understanding of > > the yocto system. I was assuming that if I included mysql in the > > build, that it would be started when the system powered up. If mysql > > is not normally started automatically that I can do what is necessary > > to start it, I just thought that I shouldn't need to do anything. > > Yes you are right. We try to do runtime testing as much as possible and you > will see > more and more focus on runtime testing in coming days and months. So far we > have had lot of build related features and stability problems to work on so > chances > of runtime bugs are still a bit higher. You can help in fixing this issue if > you can root > cause it. eg. check in system logs using journalctl for possible causes of > this service > not starting up. Often times you will get a decent hint and we can help as > well on > that information
I've run journalctl on both install_db.service & mysqld.service. mysqld comes back with no entries. install_db comes back with a line each for Starting and Started Install MySQL Community Server Database. systemctl status returns exited success for install_db, for mysqld it reports Active: inactive (dead). systemctl list-unit-files shows install_db as enabled and mysqld as disabled. I was able to start mysqld with systemctl start and it showed running with systemctl status & ps. But it did not restart after a reboot. If there is anything else that I can do to help understand what is going on please let me know. Greg -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
