[SOLVED, kinda]Teamviewer PID file not readable

developej · 2013-11-16 15:14:33

_____________________________________________________________________________________________________________________________________________________
edit: the service stopping had nothing to with PID problem. It was the NetworkManager in Teamviewerd service file. After commenting that line out, the service doesn't stop any more.
PID not readable is still there, but the service starts after that message.
_____________________________________________________________________________________________________________________________________________________

Hey,

I'm trying to setup Teamviewer daemon.

 systemctl status teamviewerd.service
teamviewerd.service - TeamViewer remote control daemon
   Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; enabled)
   Active: active (running) since Sat 2013-11-16 11:32:57 CET; 4h 39min ago
  Process: 418 ExecStart=/opt/teamviewer8/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
 Main PID: 481 (teamviewerd)
   CGroup: /system.slice/teamviewerd.service
           └─481 /opt/teamviewer8/tv_bin/teamviewerd -d

 sudo journalctl -u teamviewerd.service

***

-- Reboot --
Nov 14 22:28:35 workstation systemd[1]: Starting TeamViewer remote control daemon...
Nov 14 22:28:35 workstation systemd[1]: PID file /var/run/teamviewerd.pid not readable (yet?) after start.
Nov 14 22:28:35 workstation systemd[1]: Started TeamViewer remote control daemon.
Nov 14 22:35:14 workstation systemd[1]: Stopping TeamViewer remote control daemon...
Nov 14 22:35:14 workstation systemd[1]: Stopped TeamViewer remote control daemon.

and it's like that after every reboot...I always have to manually start Teamviewer application if I want to connect...

I found this old topic - https://bbs.archlinux.org/viewtopic.php?id=155990 and there is no answer in it...

Last edited by developej (2013-11-17 20:31:23)

henk · 2013-11-16 21:54:22

It's a PID path confusion between the init script and systemd.
if your service config file has another path than systemd standard path (/var/run/XXX.pid) it will complain.
In your case the path could be /var/run/teamviewer(d)/teamviewerd.pid ; you have to check your service config file.

developej · 2013-11-16 22:41:42

There is a line in service file

After = NetworkManager-wait-online.service network.target

and I found a comment in the Teamviewer AUR :

I switched from NetworkManager to netctl, and this caused systemctl start teamviewerd to hang indefinately. For a workaround, I commented out the line starting with "After" in the service file, and this seems to work.
Disclaimer: There's a very good chance I botched my netctl configuration, I just stopped messing with it when I could consistently get online.

so I did the same. And the output is this:

 sudo journalctl -u teamviewerd.service

-- Reboot --
Nov 16 23:27:01 workstation systemd[1]: Starting TeamViewer remote control daemon...
Nov 16 23:27:01 workstation systemd[1]: PID file /var/run/teamviewerd.pid not readable (yet?) after start.
Nov 16 23:27:01 workstation systemd[1]: Started TeamViewer remote control daemon.

There is no more stopping of service, but the PID problem is still there. I didn't find /var/run/teamviewer(d)/, there is only /var/run/teamviewer.pid. Here is the service file (it's default, minus the commented out 'After' line)

 cat /usr/lib/systemd/system/teamviewerd.service
[Unit]
Description = TeamViewer remote control daemon
Wants = display-manager.service
# After = NetworkManager-wait-online.service network.target

[Service]
Type = forking
PIDFile = /var/run/teamviewerd.pid
ExecStart = /opt/teamviewer8/tv_bin/teamviewerd -d
Restart = on-abort
StartLimitInterval = 60
StartLimitBurst = 10

[Install]
WantedBy = graphical.target

henk · 2013-11-17 04:30:55

What happens if you change the path in your service file:

PIDFile = /var/run/teamviewerd/teamviewerd.pid

Note: regarding my first post, I found it on the Fedora forums.

developej · 2013-11-17 08:17:10

edit:

So I changed the teamviewerd.serivce PID line to:

PIDFile = /var/run/teamviewerd/teamviewerd.pid

and then I get this in journal:

 sudo journalctl -u teamviewerd.service

***

-- Reboot --
Nov 17 09:20:47 workstation systemd[1]: Starting TeamViewer remote control daemon...
Nov 17 09:20:47 workstation systemd[1]: PID file /var/run/teamviewerd/teamviewerd.pid not readable (yet?) after start.
Nov 17 09:22:17 workstation systemd[1]: teamviewerd.service operation timed out. Terminating.
Nov 17 09:22:17 workstation systemd[1]: Failed to start TeamViewer remote control daemon.
Nov 17 09:22:17 workstation systemd[1]: Unit teamviewerd.service entered failed state.

edit2:

Ok, after reboot, journal show this:

-- Reboot --
Nov 17 09:27:35 workstation systemd[1]: Starting TeamViewer remote control daemon...
Nov 17 09:27:35 workstation systemd[1]: PID file /var/run/teamviewerd/teamviewerd.pid not readable (yet?) after start.

First time I created a directory teamviewerd in /var/run, guess that was a mistake. So I deleted it, did a reboot and now it's the same problem as before, still 'not readable (yet?) after start.

Last edited by developej (2013-11-17 08:30:57)

henk · 2013-11-17 13:40:16

Is your /var/run symlinked to /run?
https://bbs.archlinux.org/viewtopic.php?id=159681

developej · 2013-11-17 15:26:52

It is symlinked, also the /var/lock as it says in the topic you linked.
One thing I noticed, after doing a

# mkdir /var/run/teamviewerd
# touch teamviewerd.pid

and editing the service to point to the new PID, I do a reboot and the /var/run/teamviewerd dir is gone? And I get the

Nov 17 09:20:47 workstation systemd[1]: PID file /var/run/teamviewerd/teamviewerd.pid not readable (yet?) after start.

kind of error. Am I doing something wrong here?

henk · 2013-11-17 18:59:14

Perhaps you should have created the teamviewerd directory in /run, as /var/run is linked to /run, not the other way around.
See post #4 in the linked topic.
This is just merely guessing though, I'm sorry, but I'm running out of ideas.

Edit: found some links which might be of interest.
https://mailman.archlinux.org/pipermail … 22226.html
http://stackoverflow.com/questions/1615 … art-apache

Last edited by henk (2013-11-17 19:29:04)

developej · 2013-11-17 20:28:10

Tried that, not helping with PID problem.

Maybe

-- Reboot --
Nov 17 21:21:23 workstation systemd[1]: Starting TeamViewer remote control daemon...
Nov 17 21:21:23 workstation systemd[1]: PID file /var/run/teamviewerd.pid not readable (yet?) after start.
Nov 17 21:21:23 workstation systemd[1]: Started TeamViewer remote control daemon.

is as good as it gets - it doesn't stop the service any more, so that "(yet?)" is all there is to it, I don't know...maybe the system needs to do something first, and when it does it starts the service...

So, to sum up - problem was with the NetworkManager. After commenting out that line, the service doesn't stop any more, and the PID thing is maybe not even a problem, I don't know...

Thanks for your help, henk, I'll mark this one as solved.

Last edited by developej (2013-11-17 20:28:48)

Arch Linux

#1 2013-11-16 15:14:33

[SOLVED, kinda]Teamviewer PID file not readable

#2 2013-11-16 21:54:22

Re: [SOLVED, kinda]Teamviewer PID file not readable

#3 2013-11-16 22:41:42

Re: [SOLVED, kinda]Teamviewer PID file not readable

#4 2013-11-17 04:30:55

Re: [SOLVED, kinda]Teamviewer PID file not readable

#5 2013-11-17 08:17:10

Re: [SOLVED, kinda]Teamviewer PID file not readable

#6 2013-11-17 13:40:16

Re: [SOLVED, kinda]Teamviewer PID file not readable

#7 2013-11-17 15:26:52

Re: [SOLVED, kinda]Teamviewer PID file not readable

#8 2013-11-17 18:59:14

Re: [SOLVED, kinda]Teamviewer PID file not readable

#9 2013-11-17 20:28:10

Re: [SOLVED, kinda]Teamviewer PID file not readable

Board footer