Hi,

here ist what "sudo systemctl status tvncserver" writes:

● tvncserver.service - LSB: Starts and stops the TurboVNC Server
   Loaded: loaded (/etc/init.d/tvncserver; bad; vendor preset: enabled)
   Active: active (exited) since Sa 2018-05-12 13:55:43 CEST; 1h 26min ago
     Docs: man:systemd-sysv-generator(8)

Mai 12 13:55:43 ws-torsten systemd[1]: Starting LSB: Starts and stops the 
TurboVNC Server...
Mai 12 13:55:43 ws-torsten tvncserver[878]: Starting TurboVNC server: 
1:torsten  * [FAILED]
Mai 12 13:55:43 ws-torsten systemd[1]: Started LSB: Starts and stops the 
TurboVNC Server.
Mai 12 14:03:26 ws-torsten systemd[1]: Started LSB: Starts and stops the 
TurboVNC Server.
Mai 12 14:05:15 ws-torsten systemd[1]: Started LSB: Starts and stops the 
TurboVNC Server.
Mai 12 14:08:23 ws-torsten systemd[1]: Started LSB: Starts and stops the 
TurboVNC Server.
Mai 12 14:19:08 ws-torsten systemd[1]: Started LSB: Starts and stops the 
TurboVNC Server.
Mai 12 14:26:19 ws-torsten systemd[1]: Started LSB: Starts and stops the 
TurboVNC Server.
Mai 12 14:29:24 ws-torsten systemd[1]: Started LSB: Starts and stops the 
TurboVNC Server.

The line with "[FAILED]" appeared directly after the reboot. All subsequent 
lines followed when trying a manual start through systemctl. Are there any 
log files or other sources giving infos, why it's failing? I googled this 
issue without any success.


Am Samstag, 12. Mai 2018 15:04:34 UTC+2 schrieb DRC:
>
> I have no idea.  I just tried it with an Ubuntu 16 virtual machine, and 
> it worked. 
>
> On 5/12/18 7:41 AM, torsten wrote: 
> > Hi DRC, 
> > 
> > I did this. And once (before rebooting) it worked. But after reboot it 
> > doesn't work anymore. Also the manual start by "sudo systemctl start 
> > tvncserver" doesn't work now (it did before rebooting!). 
> > "/opt/TurboVNC/bin/vncserver -list" displays no X display and no process 
> > id. There is no Xvnc process too. Only the start by 
> > "/opt/TurboVNC/bin/vncserver" works as before. 
> > 
> > Could you say, what I'm doing wrong? 
> > 
> > Kind Regards 
> > Torsten 
> > 
> > Am Freitag, 11. Mai 2018 05:20:18 UTC+2 schrieb DRC: 
> > 
> >     Edit /etc/sysconfig/tvncservers and specify the TurboVNC Server 
> >     instances you want to start, as well as their associated display 
> >     numbers, user accounts, and command-line arguments.  Then do 
> > 
> >     sudo systemctl enable tvncserver 
> >     sudo systemctl start tvncserver 
> > 
> >     On 5/10/18 4:02 PM, torsten wrote: 
> >     > Hi, 
> >     > 
> >     > I tried to start "/opt/TurboVNC/bin/vncserver" automatically at 
> boot 
> >     > time by a systemd unit (OS is Ubuntu 16.04). I used these 
> >     instructions: 
> >     > 
> >     > https://wiki.ubuntuusers.de/systemd/Units/ 
> >     <https://wiki.ubuntuusers.de/systemd/Units/> 
> >     > https://wiki.ubuntuusers.de/systemd/Service_Units/ 
> >     <https://wiki.ubuntuusers.de/systemd/Service_Units/> 
> >     > https://wiki.ubuntuusers.de/systemd/systemctl/ 
> >     <https://wiki.ubuntuusers.de/systemd/systemctl/> 
> >     > 
> >     > This is the content of my service unit file: 
> >     > 
> >     > [Unit] 
> >     > Description=TurboVNC-Server 
> >     > 
> >     > [Service] 
> >     > Type=simple 
> >     > User=torsten 
> >     > Group=users 
> >     > WorkingDirectory=~ 
> >     > ExecStart=/opt/TurboVNC/bin/vncserver 
> >     > 
> >     > [Install] 
> >     > WantedBy=multi-user.target 
> >     > 
> >     > When I start "/opt/TurboVNC/bin/vncserver" manually, 
> >     > "/opt/TurboVNC/bin/vncserver -list" writes this: 
> >     > 
> >     > TurboVNC server sessions: 
> >     > 
> >     > X DISPLAY #     PROCESS ID 
> >     > :1              14184 
> >     > 
> >     > The displayed process id represents the Xvnc process created by 
> >     > vncserver, which is the X server used to display the TurboVNC 
> >     session. 
> >     > 
> >     > When I kill this server using "/opt/TurboVNC/bin/vncserver -kill 
> >     :1" and 
> >     > start the above service unit using systemctl, 
> >     > "/opt/TurboVNC/bin/vncserver -list" writes the same (only the 
> >     prosess id 
> >     > differs), but a process with the new process id doesn't exist (and 
> >     the 
> >     > TurboVNC Viewer fails to connect). I compared the log files 
> >     written by 
> >     > both vncserver calls. They are completely identical (only the time 
> >     > stamps differ). So where is the Xvnc process gone when started 
> >     through 
> >     > systemd? Is there a way to get more log file content, that could 
> tell 
> >     > me, why Xvnc won't run? If needed I can give some more detailed 
> >     infos. 
> >     > 
> >     > Kind Regards 
> >     > Torsten 
> > 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/turbovnc-users/aeb40f27-211b-440d-a44e-d5336925a7bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to