[tor-bugs] #33483 [Internal Services/Tor Sysadmin Team]: Why did ZNC go down? How to prevent in future?
    Tor Bug Tracker & Wiki 
    blackhole at torproject.org
       
    Fri Feb 28 16:12:25 UTC 2020
    
    
  
#33483: Why did ZNC go down? How to prevent in future?
-----------------------------------------------------+-----------------
     Reporter:  pastly                               |      Owner:  tpa
         Type:  defect                               |     Status:  new
     Priority:  Medium                               |  Milestone:
    Component:  Internal Services/Tor Sysadmin Team  |    Version:
     Severity:  Normal                               |   Keywords:
Actual Points:                                       |  Parent ID:
       Points:                                       |   Reviewer:
      Sponsor:                                       |
-----------------------------------------------------+-----------------
 ZNC went down last week. Luckily people knew to contact me so I could log
 in and bring it back.
 As far as I can tell, it should have come back up; the word "enabled" on
 the Loaded line tells me that.
 {{{
 ircbouncer at chives:~$ systemctl --user status znc
 ● znc.service - ZNC IRC bouncer service
    Loaded: loaded (/home/ircbouncer/.config/systemd/user/znc.service;
 enabled; vendor preset: enabled)
    Active: active (running) since Fri 2020-02-21 14:51:10 UTC; 1 weeks 0
 days ago
  Main PID: 32354 (znc)
    CGroup: /user.slice/user-1579.slice/user at 1579.service/znc.service
            └─32354 /usr/bin/znc --foreground
 }}}
 I think I should be able to do the following in order to access ZNC's logs
 myself, but can't. I do not know enough about systemd to know if I'm
 making a silly mistake/assumption or otherwise missing something obvious.
 {{{
 # This is how I'd normally do it on my own servers, but as root.
 # Not surprised this doesn't work
 ircbouncer at chives:~$ journalctl -eu znc.service
 Hint: You are currently not seeing messages from other users and the
 system.
       Users in the 'systemd-journal' group can see all messages. Pass -q
 to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
 # But after a skim of the man page, I would assume something like
 # the following commands to work. None of them do.
 # They all output the same as above.
 ircbouncer at chives:~$ journalctl --user-unit znc
 ircbouncer at chives:~$ journalctl --user
 ircbouncer at chives:~$ journalctl --user --user-unit znc
 }}}
 Here is the znc.service file
 {{{
 [Unit]
 Description=ZNC IRC bouncer service
 [Service]
 Type=simple
 ExecStart=/usr/bin/znc --foreground
 [Install]
 WantedBy=multi-user.target
 }}}
 Maybe it needs to depend on networking to be up already?
 I'm at a loss and have no logs to help me.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33483>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
    
    
More information about the tor-bugs
mailing list