unexpected EOF while looking for matching `"
search cancel

unexpected EOF while looking for matching `"

book

Article ID: 324577

calendar_today

Updated On: 10-03-2024

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
Vcenter services fails to start with SSH banner indicating error " unexpected EOF while looking for matching `"

All VC services would fail to start with limited errors, even VMON would fail to start

End of keyboard-interactive prompts from server
Last login: Fri Jul 22 14:21:03 2022 from 10.11.186.174
-bash: eval: line 11: unexpected EOF while looking for matching `"'
-bash: eval: line 12: syntax error: unexpected end of file

Environment

VMware vCenter Server 7.0.x
VMware vCenter Server 8.0.x

Cause

Vmon.log

Here syslog is configured for the Vcenter server and logs indicating not able to contact the syslog server
The highlighted statement is the same that is seen in the banner of the VC SSH console

Jul 22 15:52:20 vc.com rsyslogd[1554]: action 'action-0-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2106.0 try https://www.rsyslog.com/e/2359 ]
Jul 22 15:52:20 vc.com setupdb.sh[25359]: Creating VMON_TELEMETRY infrastructure.
Jul 22 15:52:20 vc.com  setupdb.sh[25359]: DB Path is not set in arguments, using default path: /etc/vmware/vmware-vmon/telemetry/db/vMonTelemetry.db
Jul 22 15:52:20 vc.com vmon.launcher[25362]: /etc/profile.d/proxy.sh: eval: line 11: unexpected EOF while looking for matching `"'
Jul 22 15:52:20 vc.com vmon.launcher[25362]: /etc/profile.d/proxy.sh: eval: line 12: syntax error: unexpected end of file

Jul 22 15:52:20 vc.com rsyslogd[1554]: omfwd: remote server at serverfqdn.com:1514 seems to have closed connection. This often happens when the remote peer (or an interim system like a load balancer or firewa>
Jul 22 15:52:20 vc.com systemd[1]: vmware-vmon.service: Control process exited, code=exited status=2

Resolution

Login to the VC ssh console

browse to file location:

 /etc/sysconfig/proxy

Cat for the file to validate the configuration file, the output of the file should look like this below.

root@vcsa1 [ /etc/sysconfig ]# cat proxy
# Enable a generation of the proxy settings to the profile.
# This setting allows to turn the proxy on and off while
# preserving the particular proxy setup.
#
PROXY_ENABLED="no"

# Some programs (e.g. wget) support proxies, if set in
# the environment.
# Example: HTTP_PROXY="http://proxy.provider.de:3128/"
HTTP_PROXY=""

# Example: HTTPS_PROXY="https://proxy.provider.de:3128/"
HTTPS_PROXY=""

# Example: FTP_PROXY="http://proxy.provider.de:3128/"
FTP_PROXY=""

# Example: GOPHER_PROXY="http://proxy.provider.de:3128/"
GOPHER_PROXY=""

# Example: SOCKS_PROXY="socks://proxy.example.com:8080"
SOCKS_PROXY=""

# Example: SOCKS5_SERVER="office-proxy.example.com:8881"
SOCKS5_SERVER=""

# Example: NO_PROXY="www.me.de, do.main, localhost"
NO_PROXY="localhost, 127.0.0.1, .*.com"

The line highlighted above is in the correct format, in this case there was an extra quote just after the loopback IP highlighted below

NO_PROXY="localhost, 127.0.0.1", .*..com"

Which was causing the services to fail.

Take a backup of the file using the command:

cp proxy proxy.bkp

Once done, edit the file using VI editor to remove the double quote after the loopback IP, save and quit. esc, wq!

Restart the services of the Vcenter server

Additional Information

Impact/Risks:
Vcenter services would fail immediately with RC=1 error while we start the services (VMON initially fails to start the service eventually all services fail)