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: >&

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 sys

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

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

Re: Trying to excute things on boot from /etc/rc.local

2019-10-01 Thread yoda woya
On Tue, Oct 1, 2019 at 4:15 AM wrote: > Le lundi 30 septembre 2019 19:50:04 UTC+2, yoda woya a écrit : > > The content of my rc.local has two lines: > > /usr/local/bin/ipnat > > exit 0 > > > > > > > > However on boot > > > > /usr/lo

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 interfa

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?: C

Re: where to look in logs

2019-10-01 Thread yoda woya
;journalctl -u > > > yourservice". > > On Mon, Sep 30, 2019 at 04:57:54PM -0400, yoda woya wrote: > > I used this sudo systemctl enable udhcpd.service > > > > But it is not working > > Your text goes BELOW the text that you're quoting. We read from to

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 > ... > > whe

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?

Re: Trying to excute things on boot from /etc/rc.local

2019-09-30 Thread yoda woya
added #!/bin/sh and still the same problem 洛洛 On Mon, Sep 30, 2019 at 1:48 PM Greg Wooledge wrote: > On Mon, Sep 30, 2019 at 01:43:13PM -0400, yoda woya wrote: > > The content of my rc.local has two lines: > > /usr/local/bin/ipnat > > exit 0 > > > > Howe

Debian 10 udhcpd

2019-09-30 Thread yoda woya
Lord... realy debian is giving me a run for my money :-) how do makesure udhcpd runs at boot this does seem to do the trick: sudo systemctl restart udhcpd.service

Trying to excute things on boot from /etc/rc.local

2019-09-30 Thread yoda woya
The content of my rc.local has two lines: /usr/local/bin/ipnat exit 0 However on boot /usr/local/bin/ipnat in not executed. How can I get debian to execute the content of my rc.local file. BTW after boot, /usr/local/bin/ipnat can be executed manually without issues. Any assistance would

Re: sshd fails to bind to port to IP on boot

2019-09-27 Thread yoda woya
solved issue ... thank u On Fri, Sep 27, 2019 at 11:55 AM Greg Wooledge wrote: > On Fri, Sep 27, 2019 at 11:44:25AM -0400, yoda woya wrote: > > The public interface is listed defined as > > > > # The public network interface > > allow-hotplug eno1 > > iface eno

Re: sshd fails to bind to port to IP on boot

2019-09-27 Thread yoda woya
How can I use to solve the problem: "ssh.service has "After=network.target", and network.target only waits for interfaces marked as "auto" to come up." On Fri, Sep 27, 2019 at 11:26 AM Greg Wooledge wrote: > On Fri, Sep 27, 2019 at 11:16:51AM -0400, yoda woy

Re: sshd fails to bind to port to IP on boot

2019-09-27 Thread yoda woya
The public interface is listed defined as # The public network interface allow-hotplug eno1 iface eno1 inet static address x.x.x.x But I have that same configuration on another server and it works fine. On Fri, Sep 27, 2019 at 11:42 AM yoda woya wrote: > # The public netw

Re: sshd fails to bind to port to IP on boot

2019-09-27 Thread yoda woya
# The public network interface allow-hotplug eno1 iface eno1 inet static address 128.59.176.101 On Fri, Sep 27, 2019 at 11:25 AM Dan Ritter wrote: > yoda woya wrote: > > Below is the error I get. However the service works at boot if > > InternetAddress is comme

Re: sshd fails to bind to port to IP on boot

2019-09-27 Thread yoda woya
, 2019 at 6:23 PM Roberto C. Sánchez wrote: > On Thu, Sep 26, 2019 at 05:34:02PM -0400, yoda woya wrote: > >when I use this, the binding fails: > >Port 2022 > >#AddressFamily any > >ListenAddress x.x.x.x > >#ListenAddress :: > >but

sshd fails to bind to port to IP on boot

2019-09-26 Thread yoda woya
when I use this, the binding fails: Port 2022 #AddressFamily any ListenAddress x.x.x.x #ListenAddress :: but if I do , it binds it to the ip on boot Port 2022 #AddressFamily any #ListenAddress x.x.x #ListenAddress :: How can i fix this. I want sshd to run only on this one IP