tteck / Proxmox

Proxmox VE Helper-Scripts
https://Helper-Scripts.com
MIT License
12.94k stars 2k forks source link

Smokeping-script fails #3453

Closed phellarv closed 1 month ago

phellarv commented 1 month ago

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

Whenever I try to create a Smokeping-container, it fails

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

   _____                 __        ____  _
  / ___/____ ___  ____  / /_____  / __ \(_)___  ____ _
  \__ \/ __ `__ \/ __ \/ //_/ _ \/ /_/ / / __ \/ __ `/
 ___/ / / / / / / /_/ / ,< /  __/ ____/ / / / / /_/ /
/____/_/ /_/ /_/\____/_/|_|\___/_/   /_/_/ /_/\__, /
                                             /____/
Using Default Settings
Using Distribution: debian
Using debian Version: 12
Using Container Type: 1
Using Root Password: Automatic Login
Using Container ID: 116
Using Hostname: smokeping
Using Disk Size: 2GB
Allocated Cores 1
Allocated Ram 512
Using Bridge: vmbr0
Using Static IP Address: dhcp
Using Gateway IP Address: Default
Using Apt-Cacher IP Address: Default
Disable IPv6: No
Using Interface MTU Size: Default
Using DNS Search Domain: Host
Using DNS Server Address: Host
Using MAC Address: Default
Using VLAN Tag: Default
Enable Root SSH Access: No
Enable Verbose Mode: No
Creating a SmokePing LXC using the above default settings
 ✓ Using local for Template Storage.
 ✓ Using vmdata for Container Storage.
 ✓ Updated LXC Template List
 ✓ LXC Container 116 was successfully created.
 ✓ Started LXC Container
 / Setting up Container OS   
[ERROR] in line 90: exit code 0: while executing command locale_line=$(grep -v '^#' /etc/locale.gen | grep -E '^[a-zA-Z]' | awk '{print $1}' | head -n 1)
root@mainframe:~# grep -v '^#' /etc/locale.gen | grep -E '^[a-zA-Z]' | awk '{print $1}' | head -n 1
en_US.UTF-8

Please provide detailed steps to reproduce the issue.

No response

tteck commented 1 month ago

🏁 The script runs without any problems from this end.

   _____                 __        ____  _
  / ___/____ ___  ____  / /_____  / __ \(_)___  ____ _
  \__ \/ __ `__ \/ __ \/ //_/ _ \/ /_/ / / __ \/ __ `/
 ___/ / / / / / / /_/ / ,< /  __/ ____/ / / / / /_/ /
/____/_/ /_/ /_/\____/_/|_|\___/_/   /_/_/ /_/\__, /
                                             /____/
Using Advanced Settings
Using Distribution: debian
Using debian Version: 12
Using Container Type: 1
Using Root Password: Automatic Login
Container ID: 111
Using Hostname: smokeping
Using Disk Size: 2
Allocated Cores: 1
Allocated RAM: 512
Using Bridge: vmbr0
Using IP Address: dhcp
Using Gateway IP Address: Default
Using APT-Cacher IP Address: Default
Disable IPv6: no
Using Interface MTU Size: Default
Using DNS Search Domain: Host
Using DNS Server IP Address: Host
Using MAC Address: AE:1A:60:07:B7:59
Using Vlan: Default
Enable Root SSH Access: no
Enable Verbose Mode: no
Creating a SmokePing LXC using the above advanced settings
 ✓ Using local for Template Storage.
 ✓ Using thin-pool for Container Storage.
 ✓ Updated LXC Template List
 ✓ LXC Container 111 was successfully created.
 ✓ Started LXC Container
 ✓ Set up Container OS
 ✓ Network Connected: 192.168.86.250 
 ✓ IPv4 Internet Connected
 ✗ IPv6 Internet Not Connected
 ✓ DNS Resolved github.com to 140.82.114.4
 ✓ Updated Container OS
 ✓ Installed Dependencies
 ✓ Installed SmokePing
 ✓ Customized Container
 ✓ Cleaned
 ✓ Completed Successfully!

SmokePing should be reachable by going to the following URL.
         http://192.168.86.250/smokeping 

Are you using SSH? Setting up Container OS is used in every LXC creation: https://github.com/tteck/Proxmox/blob/d07353534663f87186eceaf8c4a76ce9e886e0df/misc/install.func#L86-L112

phellarv commented 1 month ago

I tried both from ProxMox-console, and from SSH. Same error. Never had this error, but I'm not sure if I've used Debian 12 before, since it's a long time since I last created a container. I will dig some more, and check what might be the problem for me.

tteck commented 1 month ago

🧐 As this issue is unrelated to the script, it is considered closed.