Lab 16.2.3 - neither proxynode nor k8sServers started

I've spun up a new node and installed HAProxy on it. I've edited the haproxy.cfg file as shown in the lab instructions, restarted the service and checked the status. I get the following output:... systemd[1]: Starting HAProxy Load Balancer...
... haproxy[17833]: [WARNING] (17833) : config : 'stats' statement ignored for frontend 'proxynode' as it requires HTTP mode.
... haproxy[17833]: [NOTICE] (17833) : New worker #1 (17835) forked
... systemd[1]: Started HAProxy Load Balancer.
Note: no mention of proxynode nor k8sServers starting, but no error messages to help me work out why not (only the warning about the stats statement - don't know if that's relevant or not). Could someone help me troubleshoot this?
Things I've tried:
sudo journalctl -xeu haproxy.service
(still no error messages)- Using the haproxy.cfg file from the SOLUTIONS tarball (with appropriate IP tweaks)
- Uninstalling and reinstalling haproxy
- Stopping and starting the service (rather than restarting)
- Running haproxy in the foreground (via sudo haproxy -f /etc/haproxy/haproxy.cfg -db)
Best Answer
-
Chris,
Update - I blew away the 22.04 proxy node and tried on a new one with Ubuntu 20.04, and it now works as expected. Since it worked for you on both versions, I suspect there was just something wrong with that particular VM.
Thanks again for your help.0
Answers
-
Hi @chriswigmore,
What type of infrastructure are you using for your cluster nodes (control-plane-1, worker, control-plane-2, control-plane-3, and others if any) and the haproxy load balancer?
With all necessary settings in place, what does your haproxy.cfg look like? Please provide its content in code block to help check for possible typos.
Regards,
-Chris0 -
Chris, thanks for getting back to me. To answer your questions:
- I'm using AWS EC2s for all 5 nodes (3 cp nodes, 1 worker node, 1 proxy node), with specs as per the guidance (t2.large, 20 gp2 storage, etc)
- My haproxy.cfg is below (apologies - the markdown isn't ideal):
global log /dev/log local0 log /dev/log local1 notice chroot /var/lib/haproxy stats socket /run/haproxy/admin.sock mode 660 level admin stats timeout 30s user haproxy group haproxy daemon # Default SSL material locations ca-base /etc/ssl/certs crt-base /etc/ssl/private # Default ciphers to use on SSL-enabled listening sockets. # For more information, see ciphers(1SSL). This list is from: # https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/ ssl-default-bind-ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS ssl-default-bind-options no-sslv3 defaults log global mode tcp option tcplog option dontlognull timeout connect 5000 timeout client 50000 timeout server 50000 errorfile 400 /etc/haproxy/errors/400.http errorfile 403 /etc/haproxy/errors/403.http errorfile 408 /etc/haproxy/errors/408.http errorfile 500 /etc/haproxy/errors/500.http errorfile 502 /etc/haproxy/errors/502.http errorfile 503 /etc/haproxy/errors/503.http errorfile 504 /etc/haproxy/errors/504.http frontend proxynode bind *:80 bind *:6443 stats uri /proxystats default_backend k8sServers backend k8sServers balance roundrobin server cp1 172.31.36.248:6443 check #<-- Edit with your IP addresses. # server cp2 10.128.0.30:6443 check # server cp3 10.128.0.66:6443 check listen stats bind :9999 mode http stats enable stats hide-version stats uri /stats
0 -
Hi @chriswigmore,
Is your hostname "cp1" or something else? The "cp1", "cp2" and "cp3" strings above should be replaced with the hostnames of the respective control plane nodes, which should be somehow derived from the IP address (based on AWS EC2 naming standards). The IP address edit looks correct though.
Regards,
-Chris0 -
Thanks for the suggestion, Chris. The hostname is actually 'ip-172-31-36-248'. I tried using that instead of cp1, but still no joy.
0 -
Hi @chriswigmore,
Is the haproxy instance in the same VPC and same SG as your control plane and worker instances?
Regards,
-Chris0 -
Chris,
Same VPC = yes
Same SG = yesIf it helps, I just tried restarting the haproxy service with the cp node stopped. I saw the following output:
... haproxy[993]: [WARNING] (993) : Server k8sServers/ip-172-31-36-248 is DOWN, reason: Layer4 connection problem, info: "Connection refused", chec> ... haproxy[993]: [NOTICE] (993) : haproxy version is 2.4.22-0ubuntu0.22.04.1 ... haproxy[993]: [NOTICE] (993) : path to executable is /usr/sbin/haproxy ... haproxy[993]: [ALERT] (993) : backend 'k8sServers' has no server available!
So it seems that, if it can't reach the cp node, it lets us know. Which suggests the problem is something else.
0 -
Hi @chriswigmore,
Are your VMs on 22.04 by any chance?
I am trying to spin up a new cluster on AWS, with the recommended OS release though - 20.04, to validate the haproxy config, and to see if I can reproduce your issue.
Regards,
-Chris0 -
Chris,
The cp node is 20.04 (I first span it up months ago). The proxy node is 22.04.0 -
Hi @chriswigmore,
I tried to reproduce the issue, but both attempts were in fact successful. I tried haproxy running on Ubuntu 20.04 and 22.04 and nothing unexpected happened.
Did you notice anything strange with the cp node throughout the earlier lab exercises?
Regards,
-Chris0 -
Chris,
Thanks for investigating. No, I didn't notice anything strange with the cp node - it was well behaved throughout the earlier labs.0
Categories
- 10.1K All Categories
- 35 LFX Mentorship
- 88 LFX Mentorship: Linux Kernel
- 504 Linux Foundation Boot Camps
- 279 Cloud Engineer Boot Camp
- 103 Advanced Cloud Engineer Boot Camp
- 48 DevOps Engineer Boot Camp
- 41 Cloud Native Developer Boot Camp
- 2 Express Training Courses
- 2 Express Courses - Discussion Forum
- 1.8K Training Courses
- 17 LFC110 Class Forum
- 5 LFC131 Class Forum
- 19 LFD102 Class Forum
- 148 LFD103 Class Forum
- 13 LFD121 Class Forum
- 61 LFD201 Class Forum
- LFD210 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 23 LFD254 Class Forum
- 569 LFD259 Class Forum
- 100 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFS145 Class Forum
- 23 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 1 LFS203 Class Forum
- 45 LFS207 Class Forum
- 298 LFS211 Class Forum
- 53 LFS216 Class Forum
- 46 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 10 LFS244 Class Forum
- 27 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- 131 LFS253 Class Forum
- 997 LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 87 LFS260 Class Forum
- 126 LFS261 Class Forum
- 31 LFS262 Class Forum
- 79 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 17 LFS267 Class Forum
- 17 LFS268 Class Forum
- 21 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 212 LFW211 Class Forum
- 153 LFW212 Class Forum
- 899 Hardware
- 217 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 208 Networking
- 101 Printers & Scanners
- 85 Storage
- 749 Linux Distributions
- 88 Debian
- 64 Fedora
- 14 Linux Mint
- 13 Mageia
- 24 openSUSE
- 133 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 355 Ubuntu
- 473 Linux System Administration
- 38 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 94 Linux Security
- 77 Network Management
- 108 System Management
- 49 Web Management
- 63 Mobile Computing
- 22 Android
- 27 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 528 Off Topic
- 127 Introductions
- 213 Small Talk
- 20 Study Material
- 794 Programming and Development
- 262 Kernel Development
- 498 Software Development
- 923 Software
- 258 Applications
- 182 Command Line
- 2 Compiling/Installing
- 76 Games
- 316 Installation
- 53 All In Program
- 53 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)