Re: where to look in logs

2019-10-01 Thread Greg Wooledge
On Tue, Oct 01, 2019 at 03:50:57PM -0400, yoda woya wrote: > > Any other suggestions?? Use the regular dhcp server, that's packaged in Debian, and supported, and which everyone knows how to help you with if you run into problems? wooledg:~$ apt-cache show isc-dhcp-server Package: isc-dhcp-server

Re: where to look in logs

2019-10-01 Thread yoda woya
On Tue, Oct 1, 2019 at 3:36 PM yoda woya wrote: > > > On Tue, Oct 1, 2019 at 1:50 PM yoda woya wrote: > >> >> >> On Tue, Oct 1, 2019 at 1:12 PM Greg Wooledge wrote: >> >>> On Tue, Oct 01, 2019 at 01:02:03PM -0400, yoda woya wrote: >>> > # /run/systemd/generator.late/udhcpd.service >>> > # Autom

Re: where to look in logs

2019-10-01 Thread yoda woya
On Tue, Oct 1, 2019 at 1:50 PM yoda woya wrote: > > > On Tue, Oct 1, 2019 at 1:12 PM Greg Wooledge wrote: > >> On Tue, Oct 01, 2019 at 01:02:03PM -0400, yoda woya wrote: >> > # /run/systemd/generator.late/udhcpd.service >> > # Automatically generated by systemd-sysv-generator >> >> Yikes. So, t

Re: where to look in logs

2019-10-01 Thread yoda woya
On Tue, Oct 1, 2019 at 1:12 PM Greg Wooledge wrote: > On Tue, Oct 01, 2019 at 01:02:03PM -0400, yoda woya wrote: > > # /run/systemd/generator.late/udhcpd.service > > # Automatically generated by systemd-sysv-generator > > Yikes. So, this isn't even a native systemd unit. It's some kind of > sys

Re: where to look in logs

2019-10-01 Thread Greg Wooledge
On Tue, Oct 01, 2019 at 01:02:03PM -0400, yoda woya wrote: > # /run/systemd/generator.late/udhcpd.service > # Automatically generated by systemd-sysv-generator Yikes. So, this isn't even a native systemd unit. It's some kind of sysv-rc init script, and systemd is converting it to a systemd unit

Re: where to look in logs

2019-10-01 Thread yoda woya
On Tue, Oct 1, 2019 at 12:47 PM Greg Wooledge wrote: > On Tue, Oct 01, 2019 at 12:34:27PM -0400, yoda woya wrote: > > How do I " Showing the entire udhcpd.service" ? > > systemctl cat udhcpd.servicewould be one way. > > Or you could locate the file that you created, which is supposed to be >

Re: where to look in logs

2019-10-01 Thread Greg Wooledge
On Tue, Oct 01, 2019 at 12:34:27PM -0400, yoda woya wrote: > How do I " Showing the entire udhcpd.service" ? systemctl cat udhcpd.servicewould be one way. Or you could locate the file that you created, which is supposed to be in /etc/systemd/system/, and cat it. If on the other hand you did

Re: where to look in logs

2019-10-01 Thread yoda woya
On Tue, Oct 1, 2019 at 11:36 AM Greg Wooledge wrote: > On Tue, Oct 01, 2019 at 11:28:26AM -0400, yoda woya wrote: > > Oct 01 11:12:56 nat6pub udhcpd[674]: is interface ens1f0 up and > > configured?: Cannot assign requested address > > > # The private network interface > > allow-auto ens1f0 > > if

Re: where to look in logs

2019-10-01 Thread yoda woya
On Tue, Oct 1, 2019 at 12:17 PM Gene Heskett wrote: > On Tuesday 01 October 2019 11:36:32 Greg Wooledge wrote: > > > On Tue, Oct 01, 2019 at 11:28:26AM -0400, yoda woya wrote: > > > Oct 01 11:12:56 nat6pub udhcpd[674]: is interface ens1f0 up and > > > configured?: Cannot assign requested address

Re: where to look in logs

2019-10-01 Thread Gene Heskett
On Tuesday 01 October 2019 11:36:32 Greg Wooledge wrote: > On Tue, Oct 01, 2019 at 11:28:26AM -0400, yoda woya wrote: > > Oct 01 11:12:56 nat6pub udhcpd[674]: is interface ens1f0 up and > > configured?: Cannot assign requested address > > > > # The private network interface > > allow-auto ens1f0 >

Re: where to look in logs

2019-10-01 Thread Greg Wooledge
On Tue, Oct 01, 2019 at 11:28:26AM -0400, yoda woya wrote: > Oct 01 11:12:56 nat6pub udhcpd[674]: is interface ens1f0 up and > configured?: Cannot assign requested address > # The private network interface > allow-auto ens1f0 > iface ens1f0 inet static > address 192.168.176.6 > net

Re: where to look in logs

2019-10-01 Thread yoda woya
On Mon, Sep 30, 2019 at 5:02 PM Greg Wooledge wrote: > > On Mon, Sep 30, 2019 at 4:06 PM Greg Wooledge > wrote: > > > If you're using systemd, and if you set up the service as a systemd > unit, > > > then you want "systemctl status yourservice" or "journalctl -u > > > yourservice". > > On Mon, S

Re: where to look in logs

2019-09-30 Thread Greg Wooledge
> On Mon, Sep 30, 2019 at 4:06 PM Greg Wooledge wrote: > > If you're using systemd, and if you set up the service as a systemd unit, > > then you want "systemctl status yourservice" or "journalctl -u > > yourservice". On Mon, Sep 30, 2019 at 04:57:54PM -0400, yoda woya wrote: > I used this sudo s

Re: where to look in logs

2019-09-30 Thread yoda woya
I used this sudo systemctl enable udhcpd.service But it is not working On Mon, Sep 30, 2019 at 4:06 PM Greg Wooledge wrote: > On Mon, Sep 30, 2019 at 04:01:36PM -0400, yoda woya wrote: > > I setup a service to start at boot. It does not. Where is that logged > ... > > where are the service th

Re: where to look in logs

2019-09-30 Thread Greg Wooledge
On Mon, Sep 30, 2019 at 04:01:36PM -0400, yoda woya wrote: > I setup a service to start at boot. It does not. Where is that logged ... > where are the service that do start successful logged? Could you be any more vague? If you're using systemd, and if you set up the service as a systemd unit,

where to look in logs

2019-09-30 Thread yoda woya
I setup a service to start at boot. It does not. Where is that logged ... where are the service that do start successful logged?