Thanks for providing your solution.
But that problem is still not solved and the guacd service is running before
the network is ready.
However, other services that use the network, such as ssh, tomcat, and samba,
run successfully after network preparation.
# systemctl status guacd
● guacd.service - Guacamole Server
Loaded: loaded (/etc/systemd/system/guacd.service; enabled; vendor preset:
enabled)
Active: failed (Result: exit-code) since Tue 2022-04-19 22:19:32 KST; 1min
11s ago
Docs: man:guacd(8)
Process: 444 ExecStart=/usr/local/sbin/guacd -f (code=exited,
status=1/FAILURE)
Main PID: 444 (code=exited, status=1/FAILURE)
4월 19 22:19:32 raspberrypi systemd[1]: Started Guacamole Server.
4월 19 22:19:32 raspberrypi guacd[444]: Guacamole proxy daemon (guacd) version
1.4.0 started
4월 19 22:19:32 raspberrypi guacd[444]: guacd[444]: INFO: Guacamole
proxy daemon (guacd) version 1.4.0 started
4월 19 22:19:32 raspberrypi guacd[444]: guacd[444]: ERROR: Unable to
bind socket to any addresses.
4월 19 22:19:32 raspberrypi guacd[444]: Unable to bind socket to any addresses.
4월 19 22:19:32 raspberrypi systemd[1]: guacd.service: Main process exited,
code=exited, status=1/FAILURE
4월 19 22:19:32 raspberrypi systemd[1]: guacd.service: Failed with result
'exit-code'.
part of /var/log/syslog
========top omission=========
Apr 19 22:19:32 raspberrypi dhcpcd[394]: forked to background, child pid 441
========middle omission=========
Apr 19 22:19:32 raspberrypi guacd[444]: Unable to bind socket to any addresses.
Apr 19 22:19:32 raspberrypi systemd[1]: guacd.service: Main process exited,
code=exited, status=1/FAILURE
Apr 19 22:19:32 raspberrypi systemd[1]: guacd.service: Failed with result
'exit-code'.
========middle omission=========
Apr 19 22:19:32 raspberrypi dhcpcd-run-hooks[522]: wlan0: starting
wpa_supplicant
========middle omission=========
Apr 19 22:19:32 raspberrypi dhcpcd[441]: wlan0: connected to Access Point `'
Apr 19 22:19:32 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 165
(plymouthd).
Apr 19 22:19:32 raspberrypi dhcpcd[441]: eth0: waiting for carrier
Apr 19 22:19:32 raspberrypi dhcpcd[441]: dhcpcd_prestartinterface: wlan0:
Operation not possible due to RF-kill
Apr 19 22:19:32 raspberrypi dhcpcd[441]: wlan0: waiting for carrier
========middle omission=========
4월 19 22:19:37 raspberrypi dhcpcd[441]: eth0: carrier acquired
========bottom omission=========
-----Original Message-----
From: "Nick Couchman"<vn...@apache.org>
To: <user@guacamole.apache.org>;
Cc:
Sent: 2022-04-19 (화) 00:24:19 (GMT+09:00)
Subject: Re: guacd service does not start automatically.
On Mon, Apr 18, 2022 at 11:04 AM 박제형 <sjsanj...@naver.com> wrote:
It seems that the network is not detected normally in systemctl.
/etc/init.d/guacd
### BEGIN INIT INFO
# Provides: guacd
# Required-Start: $network $syslog
# Required-Stop: $network $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Guacamole proxy daemon
# Description: The Guacamole proxy daemon, required to translate remote desktop
protocols into the text-based Guacamole pro$
### END INIT INFO
If you have systemd/systemctl available, you should not be using
/etc/init.d/guacd. When you build guacd, make sure to use the ./configure flags
to enable systemd support (--with-systemd-dir=/etc/systemd/system, for
example), which will create and install the systemd unit file.
-Nick
