High CPU usage and temperatures after script update IPTAG

[kendikaku]

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

iptag

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/add-iptag.sh)"

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

After updating the script to the latest version, I noticed a significant increase in CPU usage and system temperature.

I’ve already tried uninstalling and reinstalling the script, as well as updating everything again, but the issue persists.

Please let me know if there’s any workaround or if additional logs are needed.

🔄 Steps to reproduce the issue.

after installing or updating to the new version

❌ Paste the full error output (if available).

root@pve:~ ps -ef | grep 'pct config'
root 1243017 1243015 99 09:00 ? 00:00:00 /usr/bin/perl -T /usr/sbin/pct config 201
root 1243027 1243023 99 09:00 ? 00:00:00 /usr/bin/perl -T /usr/sbin/pct config 202
root 1243029 1243024 99 09:00 ? 00:00:00 /usr/bin/perl -T /usr/sbin/pct config 200
root 1243063 1243059 99 09:00 ? 00:00:00 /usr/bin/perl -T /usr/sbin/pct config 203
root 1243073 1243072 99 09:00 ? 00:00:00 /usr/bin/perl -T /usr/sbin/pct config 204
root 1243077 1243074 99 09:00 ? 00:00:00 /usr/bin/perl -T /usr/sbin/pct config 205
root 1243081 1243080 99 09:00 ? 00:00:00 /usr/bin/perl -T /usr/sbin/pct config 206
root 1243085 1242808 0 09:00 pts/0 00:00:00 grep pct config
root@pve:~

🖼️ Additional context (optional).

No response

[MickLesk]

can you try to optimize these file:
/opt/iptag/iptag.conf

with this values:

LXC_IP_CACHE_TTL=300
LXC_STATUS_CACHE_TTL=300
LXC_BATCH_SIZE=5
MAX_PARALLEL_LXC_CHECKS=3

after this: systemctl restart iptag

how it work now?

[kendikaku]

can you try to optimize these file: /opt/iptag/iptag.conf

with this values:

LXC_IP_CACHE_TTL=300
LXC_STATUS_CACHE_TTL=300
LXC_BATCH_SIZE=5
MAX_PARALLEL_LXC_CHECKS=3

after this: systemctl restart iptag

how it work now?

I'll try and let you know if it works.

I don't know if I can post it here or create a new issue, but every manual tag I add it deletes and leaves only the IP, it shouldn't be like that, right?

EDIT: decreased, but still has high consumption compared to previous versions.

[DesertGamer]

Please use these commands, I want to see what kind of processor and temperature you have.

apt install i7z
sudo i7z

I also assure you that the script is optimized. I tested it on different systems, with different conditions, and there were no problems.

There are a lot of parameters in the config, I advise you to change them so you get better performance, I'm ready to tell you exactly what you need to change for your system.

Please tell me how many containers and machines you have on the node.

[kendikaku]

Please use these commands, I want to see what kind of processor and temperature you have.

apt install i7z
sudo i7z

I also assure you that the script is optimized. I tested it on different systems, with different conditions, and there were no problems.

There are a lot of parameters in the config, I advise you to change them so you get better performance, I'm ready to tell you exactly what you need to change for your system.

Please tell me how many containers and machines you have on the node.

i5-14500T
Optiplex Micro 7010

The issue is that consumption is high just for a script to check the IP of containers and VMs.
As I mentioned previously, this did not happen in previous versions.

[DesertGamer]

Here are my data and my test server, and as you can see, there are no critical values, everything is fine.

My Processor: CPU E5-2640 v2 @ 2.00GHz (2 Sockets)

[DesertGamer]

I don't see any critical temperatures, 60 degrees is absolutely normal.

Tell me, please, what processor do you use?

[DesertGamer]

To reduce the load, you can try changing the values for caching, as well as batching (how many containers will be processed at the same time).

# Extreme LXC optimizations
LXC_BATCH_SIZE=20 # You can reduce this value to 5, for example, then 1 iteration will change only 5 machines, not 20, which is probably a lot for your CPU.
LXC_STATUS_CACHE_TTL=30 # This is the caching time, I advise you to set it to about 120 seconds if you are not constantly changing the IP addresses of your servers.
LXC_AGGRESSIVE_CACHING=true
LXC_SKIP_SLOW_METHODS=true

This config is located in /opt/iptag/iptag.conf

[kendikaku]

I don't see any critical temperatures, 60 degrees is absolutely normal.

Tell me, please, what processor do you use?

i5-14500T

My temperature and consumption is almost zero in this configuration that I have. It is in the range of about 40 to 47 degrees with this update of your script it went up 13 degrees or even more

[DesertGamer]

I don't see any critical temperatures, 60 degrees is absolutely normal.
Tell me, please, what processor do you use?

i5-14500T

My temperature and consumption is almost zero in this configuration that I have. It is in the range of about 40 to 47 degrees with this update of your script it went up 13 degrees or even more

Try to reduce the number of servers per iteration according to the instructions above. I will definitely change the standard configuration so that there are no such requests and, if necessary, the user can speed up the script. After that, be sure to restart the service so that it pulls up the new config correctly.

[DesertGamer]

The fact is that I have tried many configurations and most likely there are several unused variables in the config, sorry for that, I will fix it in a couple of hours.

[kendikaku]

The fact is that I have tried many configurations and most likely there are several unused variables in the config, sorry for that, I will fix it in a couple of hours.

There is no need to apologize, I only raised this issue because there may be other users who will report the same problem.

[DesertGamer]

Most likely, it would be correct to add the ability through the config to choose for users to use the batching method (increased CPU consumption, but a faster installation option), or using the standard slower method.

[kendikaku]

The previous version of the script worked fine, except that it was not recognizing the IP 172.16.0.0/12, otherwise everything worked correctly.