Page 1 of 1
[Resolved] Troubleshooting qbittorrent-nox
Posted: Fri Jul 12, 2019 4:11 am
by NastyButler
Edit: This is now resolved. When you run qbittorrent-nox v4.1.6, it does NOT say that it is running the Web UI...
Original post:
I am running a fresh install of qBittorrent v4.1.6 (qbittorrent-nox) on a fresh Ubuntu Server 19.04 x64.
It seems to hang starting the Web UI:
Code: Select all
******** Information ********
To control qBittorrent, access the Web UI at http://localhost:8080
The Web UI administrator user name is: admin
The Web UI administrator password is still the default one: adminadmin
This is a security risk, please consider changing your password from program preferences.
^C Catching signal: SIGINT
Exiting cleanly
Troubleshooting I have done
Run as root instead of qbtuser
-no change
Left it alone for an hour
-no change
Used a different webui port (--webui-port=8888)
-no change
Nothing in the logs:
Code: Select all
root@hostname:/var/log# journalctl -u qbittorrent.service
-- Logs begin at Thu 2019-07-11 16:46:26 XXX, end at Thu 2019-07-11 20:32:15 XXX. --
-- No entries --
Looking for what else I could try or what I might be doing wrong.
Thanks!
Re: Troubleshooting qbittorrent-nox
Posted: Fri Jul 12, 2019 4:23 am
by NastyButler
More info:
Code: Select all
# pidstat -p 1099
Linux 5.0.0-20-generic (hostname) 07/11/2019 _x86_64_ (2 CPU)
10:21:38 PM UID PID %usr %system %guest %wait %CPU CPU Command
10:21:38 PM 1001 1099 0.02 0.03 0.00 0.00 0.05 1 qbittorrent-nox
Code: Select all
# cat /proc/1099/status
Name: qbittorrent-nox
Umask: 0002
State: S (sleeping)
Tgid: 1099
Ngid: 0
Pid: 1099
PPid: 576
TracerPid: 0
Uid: 1001 1001 1001 1001
Gid: 1001 1001 1001 1001
FDSize: 256
Groups: 1001
NStgid: 1099
NSpid: 1099
NSpgid: 1099
NSsid: 556
VmPeak: 696520 kB
VmSize: 696520 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM: 24052 kB
VmRSS: 24052 kB
RssAnon: 5444 kB
RssFile: 18608 kB
RssShmem: 0 kB
VmData: 104300 kB
VmStk: 132 kB
VmExe: 1860 kB
VmLib: 17048 kB
VmPTE: 216 kB
VmSwap: 0 kB
HugetlbPages: 0 kB
CoreDumping: 0
THP_enabled: 1
Threads: 13
SigQ: 0/29431
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 0000000180004422
CapInh: 0000000000000000
CapPrm: 0000000000000000
CapEff: 0000000000000000
CapBnd: 0000003fffffffff
CapAmb: 0000000000000000
NoNewPrivs: 0
Seccomp: 0
Speculation_Store_Bypass: thread vulnerable
Cpus_allowed: f
Cpus_allowed_list: 0-3
Mems_allowed: 00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001
Mems_allowed_list: 0
voluntary_ctxt_switches: 4339
nonvoluntary_ctxt_switches: 36
Re: Troubleshooting qbittorrent-nox
Posted: Fri Jul 12, 2019 2:55 pm
by NastyButler
More logs, looks like just installation noise:
Code: Select all
# grep -r -i qbittorrent /var/log/
/var/log/dpkg.log:2019-07-11 19:17:32 install qbittorrent-nox:amd64 <none> 4.1.6.99~201907060905-6710-e954835~ubuntu19.04.1
/var/log/dpkg.log:2019-07-11 19:17:32 status half-installed qbittorrent-nox:amd64 4.1.6.99~201907060905-6710-e954835~ubuntu19.04.1
/var/log/dpkg.log:2019-07-11 19:17:33 status unpacked qbittorrent-nox:amd64 4.1.6.99~201907060905-6710-e954835~ubuntu19.04.1
/var/log/dpkg.log:2019-07-11 19:17:34 configure qbittorrent-nox:amd64 4.1.6.99~201907060905-6710-e954835~ubuntu19.04.1 <none>
/var/log/dpkg.log:2019-07-11 19:17:34 status unpacked qbittorrent-nox:amd64 4.1.6.99~201907060905-6710-e954835~ubuntu19.04.1
/var/log/dpkg.log:2019-07-11 19:17:34 status half-configured qbittorrent-nox:amd64 4.1.6.99~201907060905-6710-e954835~ubuntu19.04.1
/var/log/dpkg.log:2019-07-11 19:17:34 status installed qbittorrent-nox:amd64 4.1.6.99~201907060905-6710-e954835~ubuntu19.04.1
/var/log/apt/history.log:Commandline: apt-get install qbittorrent-nox
/var/log/apt/history.log:Install: qbittorrent-nox:amd64 (4.1.6.99~201907060905-6710-e954835~ubuntu19.04.1), libqt5dbus5:amd64 (5.12.2+dfsg-4ubuntu1, automatic),
libqt5xml5:amd64 (5.12.2+dfsg-4ubuntu1, automatic), libtorrent-rasterbar9:amd64 (1.1.13+git20190505.6f1250c653+patched-configure-1ppa1~19.04, automatic),
libqt5core5a:amd64 (5.12.2+dfsg-4ubuntu1, automatic), qttranslations5-l10n:amd64 (5.12.2-1, automatic), libqt5network5:amd64 (5.12.2+dfsg-4ubuntu1, automatic),
libpcre2-16-0:amd64 (10.32-5, automatic), libdouble-conversion1:amd64 (3.1.0-2, automatic), libboost-system1.67.0:amd64 (1.67.0-13, automatic)
/var/log/apt/term.log:Selecting previously unselected package qbittorrent-nox.
/var/log/apt/term.log:Preparing to unpack .../8-qbittorrent-nox_4.1.6.99~201907060905-6710-e954835~ubuntu19.04.1_amd64.deb ...
/var/log/apt/term.log:Unpacking qbittorrent-nox (4.1.6.99~201907060905-6710-e954835~ubuntu19.04.1) ...
/var/log/apt/term.log:Setting up qbittorrent-nox (4.1.6.99~201907060905-6710-e954835~ubuntu19.04.1) ...
/var/log/auth.log:Jul 11 19:16:27 hostname sudo: luser : TTY=pts/0 ; PWD=/home/luser ; USER=root ; COMMAND=/usr/bin/add-apt-repository ppa:qbittorrent-team/qbittorrent-stable
/var/log/auth.log:Jul 11 19:17:07 hostname sudo: luser : TTY=pts/0 ; PWD=/home/luser ; USER=root ; COMMAND=/usr/bin/apt-get install qbittorrent-nox
/var/log/auth.log:Jul 11 19:25:06 hostname sudo: luser : TTY=pts/0 ; PWD=/home/luser ; USER=root ; COMMAND=/usr/bin/nano /etc/systemd/system/qbittorrent.service
Binary file /var/log/journal/9b32490b6feb4957a777d7316a576cf6/system.journal matches
Resolved: Troubleshooting qbittorrent-nox
Posted: Fri Jul 12, 2019 3:36 pm
by NastyButler
So it looks like I assumed it wasn't working when it was... I was following
these instructions and I was expecting to see this:
Code: Select all
03/02/2016 15:51:03 - The Web UI is listening on port 8080
03/02/2016 15:51:04 - qBittorrent is successfully listening on ...
Which I did not. But the Web UI is up and running and I can connect:
Code: Select all
# lsof -i TCP:8888
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
qbittorre 1099 qbtuser 36u IPv6 1202692 0t0 TCP hostname.fqdn:8888->web.browser.fqdn:63100 (ESTABLISHED)
qbittorre 1099 qbtuser 44u IPv6 1202690 0t0 TCP *:8888 (LISTEN)
Is this a problem? Should this be submitted as a bug?