Re: [vpp-dev] VPP Node Debug

2017-06-06 Thread otroan
Silvestro > > > wrote: > > > > > > I am running the vagrant machine provided, so I run on Ubuntu 16.04.02 > > > TLS. > > > > > > I tried clib_warning(), clib_unix_warning(), clib_error() and > > > clib_unix_error(). > > > >

Re: [vpp-dev] VPP Node Debug

2017-06-06 Thread Alessio Silvestro
> On 2 Jun 2017, at 13:31, Alessio Silvestro > wrote: > > > > > > I am running the vagrant machine provided, so I run on Ubuntu 16.04.02 > TLS. > > > > > > I tried clib_warning(), clib_unix_warning(), clib_error() and > clib_unix

Re: [vpp-dev] VPP Node Debug

2017-06-06 Thread otroan
> actually reaching the node. > > > > However, there is no sign in /var/log/syslog or anywhere else I can think > > of about that message > > > > Are you sure there is no other place where they can be printed? > > > > Thanks for the cooperation, > > Ales

Re: [vpp-dev] VPP Node Debug

2017-06-05 Thread Alessio Silvestro
gt; Alessio > > > > On Thu, Jun 1, 2017 at 7:26 PM, John Lo (loj) wrote: > > The output of clib_warning() call should be in the syslog. If running > vpp in Ubuntu, take a look in /var/log/syslog. -John > > > > > > > > From: vpp-dev-boun...@lists.fd.io [m

Re: [vpp-dev] VPP Node Debug

2017-06-02 Thread otroan
f Of Alessio Silvestro > Sent: Thursday, June 01, 2017 12:11 PM > To: Luke, Chris > Cc: vpp-dev@lists.fd.io > Subject: Re: [vpp-dev] VPP Node Debug > > > > I knew VPP run in user space and that printk is not the best option, however > from the documentation it is not cle

Re: [vpp-dev] VPP Node Debug

2017-06-02 Thread Alessio Silvestro
uke, Chris > *Cc:* vpp-dev@lists.fd.io > *Subject:* Re: [vpp-dev] VPP Node Debug > > > > I knew VPP run in user space and that printk is not the best option, > however from the documentation it is not clear to me how to do that. > > > > For example now I inserted t

Re: [vpp-dev] VPP Node Debug

2017-06-01 Thread otroan
Alessio, you may start VPP with the unix {interactive} options too... e.g. put that line in the configuration file pointed to by STARTUP_CONF environment variable (see make help). then do "make run" or "make debug". please let me know your success with the punt socket feature. it is a little ex

Re: [vpp-dev] VPP Node Debug

2017-06-01 Thread John Lo (loj)
@lists.fd.io Subject: Re: [vpp-dev] VPP Node Debug I knew VPP run in user space and that printk is not the best option, however from the documentation it is not clear to me how to do that. For example now I inserted the command clib_warning("I am here!") in the node I create -- that f

Re: [vpp-dev] VPP Node Debug

2017-06-01 Thread Alessio Silvestro
I knew VPP run in user space and that printk is not the best option, however from the documentation it is not clear to me how to do that. For example now I inserted the command clib_warning("I am here!") in the node I create -- that from vppctl show trace I can see processes the packets. Where do

Re: [vpp-dev] VPP Node Debug

2017-06-01 Thread Luke, Chris
printk() is typically a kernel thing, no? This isn’t kernel code. 😊 If you just want stuff on the console when running in a debugger, or interactively, clib_warning() may be what you are looking for. Chris. From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Al