tpdaemon.service error

Linux distribution specific questions
Post Reply
tenforty
Posts: 3
Joined: Thu Jan 17, 2019 3:51 pm

tpdaemon.service error

Post by tenforty » Thu Jan 17, 2019 4:16 pm

Jan 11 07:49:33 localhost.localdomain systemd[1]: tpdaemon.service: Refusing to accept PID outside of service control group, acquired through unsafe symlink chain: /var/spool/turboprint/tpdaemon.pid
Jan 11 07:49:33 localhost.localdomain systemd[1]: tpdaemon.service: Refusing to accept PID outside of service control group, acquired through unsafe symlink chain: /var/spool/turboprint/tpdaemon.pid
Jan 11 07:49:33 localhost.localdomain systemd[1]: Failed to start Turboprint Monitor Daemon.

Printing to a pixma pro-10 does work even if some coaxing may be required. It doesn't feel like a hard issue to fix. I just don't know how. The command issued is: sudo systemctl start tpdaemon.service . Can anyone suggest a way to make systemd happy?
This is on fedora 29 workstation. Turboprint version 2.46 .
Thanks much.
- Jeremy

zedonet
Site Admin
Posts: 1777
Joined: Fri Oct 06, 2006 8:02 am

Re: tpdaemon.service error

Post by zedonet » Mon Jan 21, 2019 12:09 pm

Hello,

I just tried to verify this problem under Fedora 29 Workstation but could not find a problem - TurboPrint Daemon is started correctly (after the first reboot after installation of TurboPrint) and "sudo systemctl start/stop tpdaemon" works properly.

It should help to modify /etc/systemd/system/tpdaemon.service, e.g. change the line PIDFile= to

PIDFile=/var/run/tpdaemon.pid

tenforty
Posts: 3
Joined: Thu Jan 17, 2019 3:51 pm

Re: tpdaemon.service error

Post by tenforty » Thu Jan 24, 2019 3:14 pm

Thank you for the reply. Sadly, no joy.

I made the change you suggested, changing:

PIDFile=/var/spool/turboprint/tpdaemon.pid

to:

PIDFile=/var/run/tpdaemon.pid

and then rebooted. Tpdaemon didn't start. This is in journalctl -b -p err.

Jan 24 09:26:58 tracy systemd[1285]: Failed to start Turboprint User Service.
Jan 24 09:26:58 tracy systemd[1]: Failed to start Turboprint Monitor Daemon.
Jan 24 09:26:58 tracy su[1413]: pam_systemd(su:session): Failed to create session: Bad message
Jan 24 09:26:58 tracy TUSB_Daemon[1423]: TP-Daemon already installed...quitting
Jan 24 09:26:58 tracy systemd[1]: Failed to start Turboprint Monitor Daemon.
Jan 24 09:26:58 tracy su[1470]: pam_systemd(su:session): Failed to create session: Bad message
Jan 24 09:26:58 tracy TUSB_Daemon[1481]: TP-Daemon already installed...quitting
Jan 24 09:26:58 tracy systemd[1]: Failed to start Turboprint Monitor Daemon.
Jan 24 09:26:58 tracy systemd[1285]: Failed to start Sound Service.
Jan 24 09:26:58 tracy su[1550]: pam_systemd(su:session): Failed to create session: Bad message
Jan 24 09:26:58 tracy TUSB_Daemon[1559]: TP-Daemon already installed...quitting
Jan 24 09:26:58 tracy systemd[1]: Failed to start Turboprint Monitor Daemon.
Jan 24 09:26:58 tracy su[1593]: pam_systemd(su:session): Failed to create session: Bad message
Jan 24 09:26:58 tracy TUSB_Daemon[1595]: TP-Daemon already installed...quitting
Jan 24 09:26:58 tracy systemd[1]: Failed to start Turboprint Monitor Daemon.
Jan 24 09:26:58 tracy systemd[1]: Failed to start Turboprint Monitor Daemon.

I tried starting tpdaemon manually and got this:

[jgeorge@tracyf29 /var/spool/turboprint]$ sudo systemctl start tpdaemon
Job for tpdaemon.service failed because the service did not take the steps required by its unit configuration.

This may not be helpful, but just for completeness sake I checked status:

[jgeorge@tracyf29 ~]$ sudo systemctl status tpdaemon
● tpdaemon.service - Turboprint Monitor Daemon
Loaded: loaded (/etc/systemd/system/tpdaemon.service; enabled; vendor preset: disabled)
Active: failed (Result: protocol) since Thu 2019-01-24 09:26:58 EST; 5min ago
Process: 1590 ExecStart=/usr/lib/turboprint/tpdaemon start (code=exited, status=0/SUCCESS)

Jan 24 09:26:58 tracy systemd[1]: tpdaemon.service: Service RestartSec=100ms expired, scheduling restart.
Jan 24 09:26:58 tracy systemd[1]: tpdaemon.service: Scheduled restart job, restart counter is at 5.
Jan 24 09:26:58 tracy systemd[1]: Stopped Turboprint Monitor Daemon.
Jan 24 09:26:58 tracy systemd[1]: tpdaemon.service: Start request repeated too quickly.
Jan 24 09:26:58 tracy systemd[1]: tpdaemon.service: Failed with result 'protocol'.
Jan 24 09:26:58 tracy systemd[1]: Failed to start Turboprint Monitor Daemon.


One possibly interesting datum is that the pid file is still being placed in the original
directory /var/spool/turboprint and is not placed in /var/run despite the change in
/etc/systemd/system/tpdaemon.service and a reboot.

[jgeorge@tracyf29 ~]$ ls /var/spool/turboprint
gdm/ ink/ jgeorge/ lp/ root/ tpdaemon.pid tpstatus

Thanks again for the help.
- Jeremy

zedonet
Site Admin
Posts: 1777
Joined: Fri Oct 06, 2006 8:02 am

Re: tpdaemon.service error

Post by zedonet » Fri Jan 25, 2019 3:33 pm

Strange, the message "TP-Daemon already installed" means that the TurboPrint daemon is already running.

Please start TurboPrint Monitor and check if the message "No connection to to TurboPrint Daemon" is displayed next to the label "Printer:". Otherwise everything should be okay.

tenforty
Posts: 3
Joined: Thu Jan 17, 2019 3:51 pm

Re: tpdaemon.service error

Post by tenforty » Fri Jan 25, 2019 9:27 pm

The printer monitor does not show an error and never did. Everything works. This is a snip from turboprint.log

----------- Start of print job -----------
backchannel_fd=5
tpprint 2.46-1 x64 (09-JUL-2018) - TurboPrint printer driver
Copyright (C)ZEDOnet GmbH, Irsee, Germany. All rights reserved.
24-Jan-2019 16:32
PPD file: /etc/cups/ppd/Pro10-TurboPrint.ppd
header file: /tmp/pstoturboprint6423.chunk
Searching PPD file and postscript header for options...


The only issue I mentioned was that there appears to be some sort of systemd related error.

[jgeorge@tracyf29 ~]$ sudo systemctl start tpdaemon
Job for tpdaemon.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status tpdaemon.service" and "journalctl -xe" for details.
[jgeorge@tracyf29 ~]$ sudo systemctl status tpdaemon
● tpdaemon.service - Turboprint Monitor Daemon
Loaded: loaded (/etc/systemd/system/tpdaemon.service; enabled; vendor preset>
Active: failed (Result: protocol) since Fri 2019-01-25 16:12:13 EST; 18s ago
Process: 5022 ExecStart=/usr/lib/turboprint/tpdaemon start (code=exited, stat>

Jan 25 16:12:13 tracy systemd[1]: tpdaemon.service: Service RestartSec=100ms ex>
Jan 25 16:12:13 tracy systemd[1]: tpdaemon.service: Scheduled restart job, rest>
Jan 25 16:12:13 tracy systemd[1]: Stopped Turboprint Monitor Daemon.
Jan 25 16:12:13 tracy systemd[1]: tpdaemon.service: Start request repeated too >
Jan 25 16:12:13 tracy systemd[1]: tpdaemon.service: Failed with result 'protoco>
Jan 25 16:12:13 tracy systemd[1]: Failed to start Turboprint Monitor Daemon.

This might be an uproductive rabbit hole not worth chasing down. I just noticed an error message and thought I'd mention it. Thanks for the help.

zedonet
Site Admin
Posts: 1777
Joined: Fri Oct 06, 2006 8:02 am

Re: tpdaemon.service error

Post by zedonet » Mon Jan 28, 2019 8:25 am

Maybe the daemon was already started before systemd tries to load it. Please check /etc/init.d and subdirectories for *tpdaemon
If tpdaemon and links in the subdirectories are present, this could mean that systemv-init and systemd are active, in this case delete *tpdaemon from the /etc/init.d directories.

Post Reply