So i’ve installed quickbox and everything went fine, using debian 8.
Well then i would like to add a second user, and as simple as that there is the command createSeedboxUser.
So then there is 2 errors/fail messages what i can see.
Job for [email protected] failed. See ‘systemctl status [email protected]’ and ‘journalctl -xn’ for details.
Job for [email protected] failed. See ‘systemctl status [email protected]’ and ‘journalctl -xn’ for details.
Else everything went fine, there is a new user created and able to login to dashboard.
But no rtorrent or irssi running.
so the systemctl status [email protected] says:
● [email protected] - rTorrent
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Tue 2016-10-04 20:12:02 CEST; 31s ago
Process: 3127 ExecStart=/usr/bin/screen -d -m -fa -S rtorrent /usr/bin/rtorrent (code=exited, status=217/USER)
Process: 3124 ExecStartPre=/bin/rm -f /home/%I/.sessions/rtorrent.lock (code=exited, status=217/USER)
Oct 04 20:12:02 DZGD1444 systemd[1]: [email protected]: control process exited, code=exited status=217
Oct 04 20:12:02 DZGD1444 systemd[1]: Failed to start rTorrent.
Oct 04 20:12:02 DZGD1444 systemd[1]: Unit [email protected] entered failed state.
and the journalctl -xn command
- Logs begin at Tue 2016-10-04 20:00:19 CEST, end at Tue 2016-10-04 20:13:01 CEST. –
Oct 04 20:12:01 DZGD1444 CRON[3114]: pam_unix(cron:session): session closed for user root
Oct 04 20:12:02 DZGD1444 systemd[1]: Starting rTorrent…- Subject: Unit [email protected] has begun with start-up
- Defined-By: systemd
- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
- Unit [email protected] has begun starting up.
Oct 04 20:12:02 DZGD1444 systemd[3124]: Failed at step USER spawning /bin/rm: No such process- Subject: Process /bin/rm could not be executed
- Defined-By: systemd
- Support:
- The process /bin/rm could not be executed and failed.
- The error number returned while executing this process is 3.
Oct 04 20:12:02 DZGD1444 systemd[3127]: Failed at step USER spawning /usr/bin/screen: No such process- Subject: Process /usr/bin/screen could not be executed
- Defined-By: systemd
- The process /usr/bin/screen could not be executed and failed.
- The error number returned while executing this process is 3.
Oct 04 20:12:02 DZGD1444 systemd[1]: [email protected]: control process exited, code=exited status=217
Oct 04 20:12:02 DZGD1444 systemd[1]: Failed to start rTorrent.- Subject: Unit [email protected] has failed
- Defined-By: systemd
- Unit [email protected] has failed.
lines 1-31…skipping…- Logs begin at Tue 2016-10-04 20:00:19 CEST, end at Tue 2016-10-04 20:13:01 CEST. –
Oct 04 20:12:01 DZGD1444 CRON[3114]: pam_unix(cron:session): session closed for user root
Oct 04 20:12:02 DZGD1444 systemd[1]: Starting rTorrent…- Subject: Unit [email protected] has begun with start-up
- Defined-By: systemd
- Unit [email protected] has begun starting up.
Oct 04 20:12:02 DZGD1444 systemd[3124]: Failed at step USER spawning /bin/rm: No such process- Subject: Process /bin/rm could not be executed
- Defined-By: systemd
- The process /bin/rm could not be executed and failed.
- The error number returned while executing this process is 3.
Oct 04 20:12:02 DZGD1444 systemd[3127]: Failed at step USER spawning /usr/bin/screen: No such process- Subject: Process /usr/bin/screen could not be executed
- Defined-By: systemd
- The process /usr/bin/screen could not be executed and failed.
- The error number returned while executing this process is 3.
Oct 04 20:12:02 DZGD1444 systemd[1]: [email protected]: control process exited, code=exited status=217
Oct 04 20:12:02 DZGD1444 systemd[1]: Failed to start rTorrent.- Subject: Unit [email protected] has failed
- Defined-By: systemd
- Unit [email protected] has failed.
- The result is failed.
Oct 04 20:12:02 DZGD1444 systemd[1]: Unit [email protected] entered failed state.
Oct 04 20:13:01 DZGD1444 CRON[3173]: pam_unix(cron:session): session opened for user root by (uid=0)
lines 1-35…skipping…- Logs begin at Tue 2016-10-04 20:00:19 CEST, end at Tue 2016-10-04 20:13:01 CEST. –
Oct 04 20:12:01 DZGD1444 CRON[3114]: pam_unix(cron:session): session closed for user root
Oct 04 20:12:02 DZGD1444 systemd[1]: Starting rTorrent…- Subject: Unit [email protected] has begun with start-up
- Defined-By: systemd
–
- Unit [email protected] has begun starting up.
Oct 04 20:12:02 DZGD1444 systemd[3124]: Failed at step USER spawning /bin/rm: No such process- Subject: Process /bin/rm could not be executed
- Defined-By: systemd
- The process /bin/rm could not be executed and failed.
- The error number returned while executing this process is 3.
Oct 04 20:12:02 DZGD1444 systemd[3127]: Failed at step USER spawning /usr/bin/screen: No such process- Subject: Process /usr/bin/screen could not be executed
- Defined-By: systemd
- The process /usr/bin/screen could not be executed and failed.
- The error number returned while executing this process is 3.
Oct 04 20:12:02 DZGD1444 systemd[1]: [email protected]: control process exited, code=exited status=217
Oct 04 20:12:02 DZGD1444 systemd[1]: Failed to start rTorrent.- Subject: Unit [email protected] has failed
- Defined-By: systemd
- Unit [email protected] has failed.
- The result is failed.
Oct 04 20:12:02 DZGD1444 systemd[1]: Unit [email protected] entered failed state.
Oct 04 20:13:01 DZGD1444 CRON[3173]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 04 20:13:01 DZGD1444 CRON[3174]: (root) CMD (bash /usr/local/bin/quickbox/system/set_interface)
Oct 04 20:13:01 DZGD1444 CRON[3173]: pam_unix(cron:session): session closed for user root
So there it is, im not sure but seems like second user cant start rtorrent or irssi. First master user have no issues, but master user have access to everything so thats not so strange why ut works there.
So this might be a bug or am i missing something?
Thanks
OS: Debian 8 64bit
Installed on a fresh new server.
Feel free to ask if there is any other information you would like to have