All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Gerson Fernando Budke <nandojve@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: quagga permission issue detected
Date: Wed, 2 Mar 2016 19:07:49 +0100	[thread overview]
Message-ID: <20160302180749.GE10529@jama> (raw)
In-Reply-To: <CABOv41MguBOF24ZvCpDWSxAL8jd0GVbKBC4ZoMWNObLCXDzHHw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2817 bytes --]

On Wed, Mar 02, 2016 at 01:53:37PM -0300, Gerson Fernando Budke wrote:
> Hello Martin and Joe,

Hello Gerson,

I have no experience with quagga, you have higher chance to connect
with people actually using quagga on target machines if you send an
e-mail to oe-devel ML.

Did you check that the files are owned by quagga user? E.g. if you
forget to use --numeric-owner parameter when untaring the image, you
can get wrong UIDs and that could result in errors like this.

Regards,

> I have work with yocto to build quagga and everything is fine but when
> system boot up I receive the messages below:
> 
> Starting Quagga daemons: zebravty_read_config: failed to open configuration
> file /etc/quagga/zebra.conf: Permission denied
> can't open configuration file [/etc/quagga/zebra.conf]
>  bgpdvty_read_config: failed to open configuration file
> /etc/quagga/bgpd.conf: Permission denied
> can't open configuration file [/etc/quagga/bgpd.conf]
>  ripdvty_read_config: failed to open configuration file
> /etc/quagga/ripd.conf: Permission denied
> can't open configuration file [/etc/quagga/ripd.conf]
>  ripngdvty_read_config: failed to open configuration file
> /etc/quagga/ripngd.conf: Permission denied
> can't open configuration file [/etc/quagga/ripngd.conf]
>  ospfdvty_read_config: failed to open configuration file
> /etc/quagga/ospfd.conf: Permission denied
> can't open configuration file [/etc/quagga/ospfd.conf]
>  ospf6dvty_read_config: failed to open configuration file
> /etc/quagga/ospf6d.conf: Permission denied
> can't open configuration file [/etc/quagga/ospf6d.conf]
>  isisdvty_read_config: failed to open configuration file
> /etc/quagga/isisd.conf: Permission denied
> can't open configuration file [/etc/quagga/isisd.conf]
>  babeld.
> vty_read_config: failed to open configuration file /etc/quagga/babeld.conf:
> Permission denied
> can't open configuration file [/etc/quagga/babeld.conf]
> 
> I detect this problem with powerpc kernel 3.12 and cortex-a9 kernel 3.4,
> both embedded system.
> This affect quagga version 0.99.23/0.99.24 and I don't compile quagga with
> any older version.
> 
> I realize that when I put this configuration in /etc/default/quagga file
> the system work:
> 
> zebra_options=" --daemon -A 127.0.0.1 -u root"
> babeld_options="--daemon -A 127.0.0.1 -u root"
> bgpd_options="  --daemon -A 127.0.0.1 -u root"
> ospfd_options=" --daemon -A 127.0.0.1 -u root"
> ospf6d_options="--daemon -A ::1 -u root"
> ripd_options="  --daemon -A 127.0.0.1 -u root"
> ripngd_options="--daemon -A ::1 -u root"
> isisd_options=" --daemon -A 127.0.0.1 -u root"
> 
> So, is this a yocto misconfiguration or quagga configuration?
> 
> Best Regards,
> Gerson

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

           reply	other threads:[~2016-03-02 18:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CABOv41MguBOF24ZvCpDWSxAL8jd0GVbKBC4ZoMWNObLCXDzHHw@mail.gmail.com>]

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=20160302180749.GE10529@jama \
    --to=martin.jansa@gmail.com \
    --cc=nandojve@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.