Script: Checkmk
Reported by: @rongalbraith
Guidelines
- Read and understood guidelines: yes
- Verbose mode used: yes
Issue occurs during: Script Update
Environment
- Linux distribution: Debian
- Proxmox version: 9.1
- Default settings: Yes
- Advanced settings: No
- Exact command:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/checkmk.sh)"
Description
Script failed during update from v2.4 (2.4.0p26.cre) to v2.5 (2.5.0p2.community). Error shows it failing while trying to perform the update with the ".cre" extension but Checkmk have changed the extension to ".community".
Ran "omd -V 2.5.0p2.community update monitoring" and this updated the environment.
Steps to reproduce
I did "update" and then "Verbose".
Error output
checkmk LXC Container
🌐 Provided by: community-scripts ORG | GitHub: https://github.com/community-scripts/ProxmoxVE
🖥️ OS: Debian GNU/Linux - Version: 12
🏠 Hostname: checkmk
💡 IP Address: 192.168.4.159
⏳ Updating checkmkStopping crontab...OK
Stopping apache...killing 689..........................OK
Stopping nagios......OK
Stopping ui-job-scheduler...killing 613...OK
Stopping automation-helper...killing 579...OK
Stopping npcd...OK
Stopping redis...killing 540...OK
Stopping rrdcached...waiting for termination...OK
Stopping mkeventd...killing 517...OK
Stopping agent-receiver...killing 489...OK
Stopping 1 remaining site processes...OK
Copying site monitoring to monitoringbackup...
Adding /opt/omd/sites/monitoringbackup/tmp to /etc/fstab.
- Converted ./.profile
- Converted etc/xinetd.conf
- Converted etc/logrotate.conf
- Converted etc/pnp4nagios/nagios_npcdmod.cfg
- Converted etc/pnp4nagios/npcd.cfg
- Converted etc/pnp4nagios/nagios_npcd.cfg
- Converted etc/pnp4nagios/process_perfdata.cfg
- Converted etc/jaeger/config.yaml
- Converted etc/check_mk/apache.conf
- Converted etc/rabbitmq/definitions.d/00-default.json
- Converted etc/rabbitmq/advanced_conf.d/00-advanced.conf
- Converted etc/logrotate.d/agent-registration
- Converted etc/logrotate.d/agent_bakery
- Converted etc/logrotate.d/web
- Converted etc/logrotate.d/diskspace
- Converted etc/logrotate.d/jaeger
- Converted etc/logrotate.d/license-usage
- Converted etc/logrotate.d/mkeventd
- Converted etc/logrotate.d/audit
- Converted etc/logrotate.d/automation-helper
- Converted etc/logrotate.d/rabbitmq
- Converted etc/logrotate.d/rrdcached
- Converted etc/logrotate.d/security
- Converted etc/logrotate.d/apache-stats
- Converted etc/logrotate.d/livestatus
- Converted etc/logrotate.d/apache
- Converted etc/logrotate.d/xinetd
- Converted etc/logrotate.d/ldap
- Converted etc/logrotate.d/stunnel
- Converted etc/logrotate.d/ui-job-scheduler
- Converted etc/logrotate.d/redis
- Converted etc/logrotate.d/agent-receiver
- Converted etc/logrotate.d/update
- Converted etc/logrotate.d/mk-notify
- Converted etc/logrotate.d/piggyback-hub
- Converted etc/logrotate.d/mk-alerts
- Converted etc/apache/php-wrapper
- Converted etc/apache/apache.conf
- Converted etc/apache/conf.d/auth.conf
- Converted etc/apache/conf.d/stats.conf
- Converted etc/apache/conf.d/security.conf
- Converted etc/apache/conf.d/var_www.conf
- Converted etc/apache/conf.d/02_fcgid.conf
- Converted etc/apache/conf.d/site.conf
- Converted etc/apache/conf.d/01_wsgi.conf
- Converted etc/init.d/rrdcached
- Converted etc/init.d/pnp_gearman_worker
- Converted etc/init.d/nagios
- Converted etc/init.d/stunnel
- Converted etc/init.d/npcd
- Converted etc/init.d/crontab
- Converted etc/nagios/resource.cfg
- Converted etc/nagios/nagios.d/omd.cfg
- Converted etc/nagios/conf.d/check_mk_templates.cfg
- Converted etc/mk-livestatus/nagios.cfg
- Converted etc/mk-livestatus/xinetd.conf
- Converted etc/mk-livestatus/livestatus@.service
- Converted etc/stunnel/server.conf
- Converted etc/stunnel/conf.d/01-livestatus.conf
- Converted etc/nagvis/apache.conf
- Converted etc/nagvis/conf.d/omd.ini.php
- Converted etc/redis/redis.conf
- Converted etc/cron.d/cmk_update_license_usage
- Converted etc/cron.d/cmk_collect_transmit_product_usage_analytics
- Converted etc/cron.d/cmk_bulk_notify
Creating temporary filesystem /omd/sites/monitoringbackup/tmp...OK
agent-receiver port 8000 is in use. I've choosen 8001 instead.
Apache port 5000 is in use. I've choosen 5001 instead.
Livestatus port 6557 is in use. I've choosen 6558 instead.
RabbitMQ distribution port 25672 is in use. I've choosen 25673 instead.
RabbitMQ management port 15671 is in use. I've choosen 15672 instead.
RabbitMQ port 5672 is in use. I've choosen 5673 instead.
The port 14269 is in use. I've choosen 14270 instead.
The port 16686 is in use. I've choosen 16687 instead.
Trace receiving port 4417 is in use. I've choosen 4418 instead.
Executing post-cp script "01_cmk-post-rename-site"...
-| 1/8 Broker certificates and configuration...
-| 2/8 Distributed monitoring configuration...
-| 3/8 Hosts and folders...
-| 4/8 Update core config...
-| Generating configuration for core (type nagios)...
-| Precompiling host checks...OK
-| 5/8 Compute REST API specification...
-| 6/8 Warn about renamed remote site...
-| 7/8 Warn about new network ports...
-|
-| WARNING: Network port configuration may need your attention
-|
-| It seems like you copied an existing site. In case you plan to use both on the same system, you may have to review the network port configuration of your sites. Two sites with the same configuration may cause network port conflicts. For example if you enabled livestatus to listen via TCP or enabled the Event Console to listen for incoming Syslog messages or SNMP traps, you may have to update the configuration in one of the sites to resolve the conflicts.
-|
-| 8/8 Warn about configurations to review...
-|
-| WARNING: Some configs may need to be reviewed
-|
-| Parts of the site configuration cannot be migrated automatically. The following
-| parts of the configuration may have to be reviewed and adjusted manually:
-|
-| - Custom bookmarks (in users bookmark lists)
-| - Hard coded site filters in custom dashboards, views, reports
-| - Path in rrdcached journal files
-| - NagVis maps or custom NagVis backend settings
-| - Notification rule "site" conditions
-| - Event Console rule "site" conditions
-| - "site" field in "Agent updater (Linux, Windows, Solaris)" rules (CEE/CME only)
-| - Alert handler rule "site" conditions (CEE/CME only)
-|
-| Done
OK
Updating core configuration...
Generating configuration for core (type nagios)...
Precompiling host checks...OK
Restarting Apache...OK
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'check-mk-community-2.5.0p2' instead of '/opt/checkmk.deb'
The following NEW packages will be installed:
check-mk-community-2.5.0p2
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/332 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 /opt/checkmk.deb check-mk-community-2.5.0p2 amd64 0.bookworm [332 MB]
Preconfiguring packages ...
Selecting previously unselected package check-mk-community-2.5.0p2.
(Reading database ... 81791 files and directories currently installed.)
Preparing to unpack /opt/checkmk.deb ...
Unpacking check-mk-community-2.5.0p2 (0.bookworm) ...
Setting up check-mk-community-2.5.0p2 (0.bookworm) ...
pre-compile bytecode (.pyc) for Python files..
New default version is 2.5.0p2.community.
update-alternatives: using /omd/versions/2.5.0p2.community to provide /omd/versions/default (omd) in manual mode
Installing systemd unit: omd.service
Activating startup during system boot
Version 2.5.0p2.cre is not installed, available versions:
2.4.0p26.cre 2.5.0p2.community
✖️ in line 38: exit code 1 (General error / Operation not permitted): while executing command omd --force -V ${RELEASE}.cre update --conflict=install monitoring
--- Last 20 lines of log ---
[2026-05-13 21:28:28] [INFO] Updating checkmk
[2026-05-13 21:33:04] [ERROR] in line 38: exit code 1 (General error / Operation not permitted): while executing command omd --force -V ${RELEASE}.cre update --conflict=install monitoring
Script: Checkmk
Reported by: @rongalbraith
Guidelines
Issue occurs during: Script Update
Environment
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/checkmk.sh)"Description
Script failed during update from v2.4 (2.4.0p26.cre) to v2.5 (2.5.0p2.community). Error shows it failing while trying to perform the update with the ".cre" extension but Checkmk have changed the extension to ".community".
Ran "omd -V 2.5.0p2.community update monitoring" and this updated the environment.
Steps to reproduce
I did "update" and then "Verbose".
Error output
checkmk LXC Container
🌐 Provided by: community-scripts ORG | GitHub: https://github.com/community-scripts/ProxmoxVE
⏳ Updating checkmkStopping crontab...OK
Stopping apache...killing 689..........................OK
Stopping nagios......OK
Stopping ui-job-scheduler...killing 613...OK
Stopping automation-helper...killing 579...OK
Stopping npcd...OK
Stopping redis...killing 540...OK
Stopping rrdcached...waiting for termination...OK
Stopping mkeventd...killing 517...OK
Stopping agent-receiver...killing 489...OK
Stopping 1 remaining site processes...OK
Copying site monitoring to monitoringbackup...
Adding /opt/omd/sites/monitoringbackup/tmp to /etc/fstab.
Creating temporary filesystem /omd/sites/monitoringbackup/tmp...OK
agent-receiver port 8000 is in use. I've choosen 8001 instead.
Apache port 5000 is in use. I've choosen 5001 instead.
Livestatus port 6557 is in use. I've choosen 6558 instead.
RabbitMQ distribution port 25672 is in use. I've choosen 25673 instead.
RabbitMQ management port 15671 is in use. I've choosen 15672 instead.
RabbitMQ port 5672 is in use. I've choosen 5673 instead.
The port 14269 is in use. I've choosen 14270 instead.
The port 16686 is in use. I've choosen 16687 instead.
Trace receiving port 4417 is in use. I've choosen 4418 instead.
Executing post-cp script "01_cmk-post-rename-site"...
-| 1/8 Broker certificates and configuration...
-| 2/8 Distributed monitoring configuration...
-| 3/8 Hosts and folders...
-| 4/8 Update core config...
-| Generating configuration for core (type nagios)...
-| Precompiling host checks...OK
-| 5/8 Compute REST API specification...
-| 6/8 Warn about renamed remote site...
-| 7/8 Warn about new network ports...
-|
-| WARNING: Network port configuration may need your attention
-|
-| It seems like you copied an existing site. In case you plan to use both on the same system, you may have to review the network port configuration of your sites. Two sites with the same configuration may cause network port conflicts. For example if you enabled livestatus to listen via TCP or enabled the Event Console to listen for incoming Syslog messages or SNMP traps, you may have to update the configuration in one of the sites to resolve the conflicts.
-|
-| 8/8 Warn about configurations to review...
-|
-| WARNING: Some configs may need to be reviewed
-|
-| Parts of the site configuration cannot be migrated automatically. The following
-| parts of the configuration may have to be reviewed and adjusted manually:
-|
-| - Custom bookmarks (in users bookmark lists)
-| - Hard coded site filters in custom dashboards, views, reports
-| - Path in rrdcached journal files
-| - NagVis maps or custom NagVis backend settings
-| - Notification rule "site" conditions
-| - Event Console rule "site" conditions
-| - "site" field in "Agent updater (Linux, Windows, Solaris)" rules (CEE/CME only)
-| - Alert handler rule "site" conditions (CEE/CME only)
-|
-| Done
OK
Updating core configuration...
Generating configuration for core (type nagios)...
Precompiling host checks...OK
Restarting Apache...OK
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'check-mk-community-2.5.0p2' instead of '/opt/checkmk.deb'
The following NEW packages will be installed:
check-mk-community-2.5.0p2
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/332 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 /opt/checkmk.deb check-mk-community-2.5.0p2 amd64 0.bookworm [332 MB]
Preconfiguring packages ...
Selecting previously unselected package check-mk-community-2.5.0p2.
(Reading database ... 81791 files and directories currently installed.)
Preparing to unpack /opt/checkmk.deb ...
Unpacking check-mk-community-2.5.0p2 (0.bookworm) ...
Setting up check-mk-community-2.5.0p2 (0.bookworm) ...
pre-compile bytecode (.pyc) for Python files..
New default version is 2.5.0p2.community.
update-alternatives: using /omd/versions/2.5.0p2.community to provide /omd/versions/default (omd) in manual mode
Installing systemd unit: omd.service
Activating startup during system boot
Version 2.5.0p2.cre is not installed, available versions:
2.4.0p26.cre 2.5.0p2.community
✖️ in line 38: exit code 1 (General error / Operation not permitted): while executing command omd --force -V ${RELEASE}.cre update --conflict=install monitoring
--- Last 20 lines of log ---
[2026-05-13 21:28:28] [INFO] Updating checkmk
[2026-05-13 21:33:04] [ERROR] in line 38: exit code 1 (General error / Operation not permitted): while executing command omd --force -V ${RELEASE}.cre update --conflict=install monitoring