[Resolved] Why Something Fails

If none of the more specific forums is the right place to ask

[Resolved] Why Something Fails

Postby Soapm » 2020-09-29 02:58

I'm looking at "systemcto --failed" command, how do I tell why an application fails to start on bootup?

Code: Select all
root@lenny:/# systemctl --failed
  UNIT                        LOAD   ACTIVE SUB    DESCRIPTION
? ifup@enp2s0.service         loaded failed failed ifup for enp2s0
? transmission-daemon.service loaded failed failed Transmission BitTorrent Daemon

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Last edited by Soapm on 2020-09-29 05:30, edited 1 time in total.
User avatar
Soapm
 
Posts: 582
Joined: 2012-05-22 04:23

Re: Why Something Fails

Postby Soapm » 2020-09-29 03:03

More info from command "systemctl status transmission-daemon.service"

Code: Select all
root@lenny:/#   systemctl   status   transmission-daemon.service
?   transmission-daemon.service   -   Transmission   BitTorrent   Daemon
Loaded:   loaded   (/lib/systemd/system/transmission-daemon.service;   enabled;   vendor   preset:   enabled)
Active:   failed   (Result:   timeout)   since   Mon   2020-09-28   21:41:57   MDT;   9min   ago
Process:   747   ExecStart=/usr/bin/transmission-daemon   -f   --log-error   (code=exited,   status=0/SUCCESS)
Main   PID:   747   (code=exited,   status=0/SUCCESS)

Sep   28   21:39:58   lenny   systemd[1]:   Starting   Transmission   BitTorrent   Daemon...
Sep   28   21:41:29   lenny   systemd[1]:   transmission-daemon.service:   Start   operation   timed   out.   Terminating.
Sep   28   21:41:57   lenny   transmission-daemon[747]:   [2020-09-28   21:41:57.167]   UDP   Failed   to   set   receive   buffer
Sep   28   21:41:57   lenny   transmission-daemon[747]:   [2020-09-28   21:41:57.167]   UDP   Failed   to   set   send   buffer
Sep   28   21:41:57   lenny   transmission-daemon[747]:   [2020-09-28   21:41:57.167]   UDP   Failed   to   set   receive   buffer
Sep   28   21:41:57   lenny   transmission-daemon[747]:   [2020-09-28   21:41:57.167]   UDP   Failed   to   set   send   buffer
Sep   28   21:41:57   lenny   transmission-daemon[747]:   Closing   transmission   session...   done.
Sep   28   21:41:57   lenny   systemd[1]:   transmission-daemon.service:   Failed   with   result   'timeout'.
Sep   28   21:41:57   lenny   systemd[1]:   Failed   to   start   Transmission   BitTorrent   Daemon.


Looks like it's failing to set a buffer? Now sure what that would mean???

Could it be that the network interface isn't active yet?
User avatar
Soapm
 
Posts: 582
Joined: 2012-05-22 04:23

Re: Why Something Fails

Postby sickpig » 2020-09-29 04:13

Soapm wrote:Could it be that the network interface isn't active yet?

possibly, you can add After=network.target in the [unit] section to see if that remedies the issue.
Also check what journalctl says regarding this service.
User avatar
sickpig
 
Posts: 575
Joined: 2019-01-23 10:34

Re: [Resolved] Why Something Fails

Postby Soapm » 2020-09-29 05:33

I guess my network didn't update to systemd. I followed the instructions here https://wiki.debian.org/SystemdNetworkd

and now she's up and running fine.

What I still can't figure out is how to tell my true network interface name. I used enp2s0 because that's what's in the error message but I'm only lucky that worked???
User avatar
Soapm
 
Posts: 582
Joined: 2012-05-22 04:23

Re: [Resolved] Why Something Fails

Postby sickpig » 2020-09-29 05:37

Code: Select all
ls /sys/class/net
User avatar
sickpig
 
Posts: 575
Joined: 2019-01-23 10:34

Re: [Resolved] Why Something Fails

Postby Soapm » 2020-09-29 06:19

Cool, thanks...
User avatar
Soapm
 
Posts: 582
Joined: 2012-05-22 04:23

Re: [Resolved] Why Something Fails

Postby Head_on_a_Stick » 2020-09-29 19:03

Soapm wrote:I guess my network didn't update to systemd.

Debian doesn't use systemd-networkd. Your other failed service was for ifupdown (networking.service), which is the native Debian networking tool.

You could troubleshoot that by examining the journal:
Code: Select all
journalctl --unit ifup@enp2s0.service --unit networking.service
Black Lives Matter

Debian buster-backports ISO image: for new hardware support
User avatar
Head_on_a_Stick
 
Posts: 12650
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: [Resolved] Why Something Fails

Postby Soapm » 2020-09-29 20:29

So based on what you're saying my network was probably fine but I broke it by moving it to a system not native to Debian.

Code: Select all
root@lenny:/# journalctl --unit ifup@enp2s0.service --unit networking.service
-- Logs begin at Tue 2020-09-29 01:19:36 MDT, end at Tue 2020-09-29 15:12:33 MDT. --
Sep 29 01:19:48 lenny systemd[1]: Starting Raise network interfaces...
Sep 29 01:19:48 lenny ifup[617]: ifup: couldn't open interfaces file "/etc/network/interfaces":
Sep 29 01:19:52 lenny systemd[1]: Started Raise network interfaces.


I saw the "ifup@enp2s0.service loaded failed failed ifup for enp2s0" and just assumed it was saying my networking wasn't starting right and googling took me to converting it as I did. The link I found was on a debian site???
User avatar
Soapm
 
Posts: 582
Joined: 2012-05-22 04:23

Re: [Resolved] Why Something Fails

Postby Head_on_a_Stick » 2020-09-30 17:37

Soapm wrote:So based on what you're saying my network was probably fine but I broke it by moving it to a system not native to Debian.

No, your networking wasn't functional (according to the code block in your OP) but systemd-networkd works just fine in Debian buster. I use it myself sometimes:
Code: Select all
~$ networkctl --no-p
IDX LINK             TYPE               OPERATIONAL SETUP     
  1 lo               loopback           carrier     unmanaged
  2 enp2s0           ether              no-carrier  configuring
  3 wlp4s0           wlan               routable    configured

3 links listed.
~$

It just isn't the native tool, that's all. I don't know of any distribution that uses systemd-networkd as the default tool.

Soapm wrote:
Code: Select all
Sep 29 01:19:48 lenny ifup[617]: ifup: couldn't open interfaces file "/etc/network/interfaces":

^ That error message seems significant. Did you try using the right-arrow key (→) to see the rest of it? Or bypass the pager as I have done for networkctl(1) in my posted terminal output above.
Black Lives Matter

Debian buster-backports ISO image: for new hardware support
User avatar
Head_on_a_Stick
 
Posts: 12650
Joined: 2014-06-01 17:46
Location: /dev/chair


Return to General Questions

Who is online

Users browsing this forum: No registered users and 10 guests

fashionable