Pironman5 service failed

General
1

I reinstalled pironman5 software like mentioned in

tried all articles I found in this forum, but it still is not working.

sudo systemctl status pironman5 × pironman5.service - pironman5 service Loaded: loaded (/etc/systemd/system/pironman5.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sat 2026-09-12 08:40:01 CEST; 4min 47s ago Duration: 1.593s Process: 6757 ExecStart=/usr/local/bin/pironman5 start (code=exited, status=1/FAILURE) Main PID: 6757 (code=exited, status=1/FAILURE) CPU: 1.005s

Sep 12 08:40:00 raspberrypi-tv pironman5[6757]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sep 12 08:40:00 raspberrypi-tv pironman5[6757]: File “/usr/lib/python3/dist-packages/lgpio.py”, line 645, in gpiochi>
Sep 12 08:40:00 raspberrypi-tv pironman5[6757]: return _u2i(handle)
Sep 12 08:40:00 raspberrypi-tv pironman5[6757]: ^^^^^^^^^^^^
Sep 12 08:40:00 raspberrypi-tv pironman5[6757]: File “/usr/lib/python3/dist-packages/lgpio.py”, line 458, in _u2i
Sep 12 08:40:01 raspberrypi-tv pironman5[6757]: raise error(error_text(v))
Sep 12 08:40:01 raspberrypi-tv pironman5[6757]: lgpio.error: ‘can not open gpiochip’
Sep 12 08:40:01 raspberrypi-tv systemd[1]: pironman5.service: Main process exited, code=exited, status=1/FAILURE
Sep 12 08:40:01 raspberrypi-tv systemd[1]: pironman5.service: Failed with result ‘exit-code’.
Sep 12 08:40:01 raspberrypi-tv systemd[1]: pironman5.service: Consumed 1.005s CPU time.

The log in /var/log/pironman5/pironman5.log says:

26/09/12 08:40:00.942 [INFO] ############################################################
26/09/12 08:40:00.942 [INFO] Pironman5 Start
26/09/12 08:40:00.942 [INFO] Pironman5 version: 1.3.18
26/09/12 08:40:00.942 [INFO] Variant: Pironman 5 Max V2
26/09/12 08:40:00.942 [INFO] Config:
26/09/12 08:40:00.942 [INFO] {
26/09/12 08:40:00.943 [INFO] “system”: {
26/09/12 08:40:00.943 [INFO] “data_interval”: 1,
26/09/12 08:40:00.943 [INFO] “database_retention_days”: 30,
26/09/12 08:40:00.943 [INFO] “temperature_unit”: “C”,
26/09/12 08:40:00.943 [INFO] “enable_history”: true,
26/09/12 08:40:00.943 [INFO] “oled_enable”: true,
26/09/12 08:40:00.943 [INFO] “oled_rotation”: 0,
26/09/12 08:40:00.943 [INFO] “oled_sleep_timeout”: 10,
26/09/12 08:40:00.943 [INFO] “oled_pages”: [“mix”, “performance”, “ips”, “disk”],
26/09/12 08:40:00.943 [INFO] “rgb_enable”: true,
26/09/12 08:40:00.943 [INFO] “rgb_color”: “#0a1aff”,
26/09/12 08:40:00.943 [INFO] “rgb_brightness”: 100,
26/09/12 08:40:00.943 [INFO] “rgb_style”: “breathing”,
26/09/12 08:40:00.944 [INFO] “rgb_speed”: 50,
26/09/12 08:40:00.944 [INFO] “rgb_led_count”: 4,
26/09/12 08:40:00.944 [INFO] “rgb_led_count_min”: 4,
26/09/12 08:40:00.944 [INFO] “gpio_fan_pin”: 6,
26/09/12 08:40:00.944 [INFO] “gpio_fan_mode”: 0,
26/09/12 08:40:00.944 [INFO] “gpio_fan_led”: “follow”,
26/09/12 08:40:00.944 [INFO] “gpio_fan_led_pin”: 5,
26/09/12 08:40:00.944 [INFO] “debug_level”: “INFO”
26/09/12 08:40:00.944 [INFO] }
26/09/12 08:40:00.944 [INFO] }
26/09/12 08:40:00.944 [INFO] Device info:
26/09/12 08:40:00.944 [INFO] {
26/09/12 08:40:00.944 [INFO] “name”: “Pironman 5 Max”,
26/09/12 08:40:00.944 [INFO] “id”: “pironman5-max”,
26/09/12 08:40:00.945 [INFO] “peripherals”: [
26/09/12 08:40:00.945 [INFO] “oled_page_ips”,
26/09/12 08:40:00.945 [INFO] “oled_page_mix”,
26/09/12 08:40:00.945 [INFO] “temperature_unit”,
26/09/12 08:40:00.945 [INFO] “oled_page_disk”,
26/09/12 08:40:00.945 [INFO] “clear_history”,
26/09/12 08:40:00.945 [INFO] “gpio_fan_mode”,
26/09/12 08:40:00.945 [INFO] “history”,
26/09/12 08:40:00.945 [INFO] “mac_address”,
26/09/12 08:40:00.945 [INFO] “oled_page_performance”,
26/09/12 08:40:00.945 [INFO] “storage”,
26/09/12 08:40:00.945 [INFO] “delete_log_file”,
26/09/12 08:40:00.945 [INFO] “reboot”,
26/09/12 08:40:00.945 [INFO] “ip_address”,
26/09/12 08:40:00.945 [INFO] “oled_sleep”,
26/09/12 08:40:00.945 [INFO] “shutdown”,
26/09/12 08:40:00.945 [INFO] “network”,
26/09/12 08:40:00.946 [INFO] “memory”,
26/09/12 08:40:00.946 [INFO] “gpio_fan_led”,
26/09/12 08:40:00.946 [INFO] “cpu”,
26/09/12 08:40:00.946 [INFO] “ws2812”,
26/09/12 08:40:00.946 [INFO] “gpu_temperature”,
26/09/12 08:40:00.946 [INFO] “pi5_power_button”,
26/09/12 08:40:00.946 [INFO] “pwm_fan_speed”,
26/09/12 08:40:00.946 [INFO] “gpio_fan_state”,
26/09/12 08:40:00.946 [INFO] “oled”,
26/09/12 08:40:00.946 [INFO] “log”,
26/09/12 08:40:00.946 [INFO] “restart_service”,
26/09/12 08:40:00.946 [INFO] “cpu_temperature”,
26/09/12 08:40:00.946 [INFO] “debug_level”
26/09/12 08:40:00.946 [INFO] ],
26/09/12 08:40:00.946 [INFO] “version”: “1.3.18”,
26/09/12 08:40:00.946 [INFO] “app_name”: “pironman5”,
26/09/12 08:40:00.946 [INFO] “config_path”: “/opt/pironman5/config.json”
26/09/12 08:40:00.946 [INFO] }
26/09/12 08:40:00.946 [INFO] PM_Auto version: 2.0.5
26/09/12 08:40:00.946 [INFO] PM_Dashboard version: 2.0.4

uname -a
Linux raspberrypi-tv 6.12.96+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.96-1+rpt1 (2026-07-24) aarch64 GNU/Linux

If you need further informations, please let me know.

Tried to repair using google ki, but it’s still not working.

1 Like
2

Thank you very much for providing the complete log and system information, and we are sorry for the trouble this has caused.

Based on the information you provided, we have identified the cause of the issue:

Your system kernel is Linux raspberrypi-tv 6.12.96+rpt-rpi-2712, and the error is lgpio.error: ‘can not open gpiochip’. This is a compatibility issue between Raspberry Pi OS kernel 6.12.96 and the outdated GPIO-related Python packages in the Pironman 5 virtual environment. This issue causes pironman5.service to fail to start, which in turn makes the OLED, RGB LEDs, fan control, and Dashboard stop working. It is not a problem with the installation steps or the hardware connection.

Please follow the steps below:

Upgrade the GPIO-related packages in the Pironman 5 virtual environment:
sudo /opt/pironman5/venv/bin/pip3 install --upgrade adafruit-blinka rpi-lgpio lgpio

After the upgrade is complete, restart the Pironman 5 service:
sudo systemctl restart pironman5.service

Check the service status:
sudo systemctl status pironman5.service --no-pager

If the service shows Active: active (running), please check whether the OLED, RGB LEDs, and fan have returned to normal.

:warning: Important: Please do NOT reinstall the Pironman 5 software for now. The reinstallation process may reinstall the outdated GPIO packages and cause the issue to reappear.

If the service still fails to start after running the above commands, please send us the complete output of the following two commands so we can investigate further:
sudo /opt/pironman5/venv/bin/pip3 show Adafruit-Blinka rpi-lgpio lgpio
sudo journalctl -u pironman5.service -n 100 --no-pager

Once we receive the output, we will continue to help you troubleshoot as soon as possible. Thank you again for your patience and cooperation.

1 Like
3

I just came here with precisely the same issue. Thanks to the OP and then the Mod above, this fixed my installation.

4

We are glad to hear that the fix from the previous post resolved your installation issue!

If you have any further questions or run into any other problems, please feel free to reach out. We’re always happy to help.

5

One issue remains that I can see, the OLED display still does not work. The web GUI seems fine, as far as I can tell the fan control is good (I am accessing it remotely so I cannot go and look). I don’t use the RGB lighting so I cannot comment on that. But it would be nice if we could get the OLED display working again.

6

Regarding the OLED display not working, please follow the dedicated “OLED Screen Not Working?” section in our official FAQ, step by step. Here is the link (it takes you directly to that section):

Please go through the steps in that section one by one (for example, whether the OLED-related feature is enabled in the Pironman 5 configuration, whether the OLED cable/connector is fully and firmly plugged in, etc.), and let us know the result of each step so we can help you further.

Once we receive your troubleshooting results, we will continue to help you as soon as possible.

1 Like
7

Thank you for your attention.

Everything is fine according to the resource above but the OLED display remains completely blank.

Please see the contents of the requested file below - the website won’t let me attach a text file. I did change the logging level to “DEBUG” before restarting the Pi to catch as much data as possible and noticed that the OLED panel seems to have gone to sleep:

26/09/18 11:24:59.510 [INFO] 
26/09/18 11:24:59.510 [INFO] ############################################################
26/09/18 11:24:59.510 [DEBUG] Config path: /opt/pironman5/config.json
26/09/18 11:24:59.510 [INFO] Pironman5 Start
26/09/18 11:24:59.510 [INFO] Pironman5 version: 1.3.18
26/09/18 11:24:59.510 [INFO] Variant: Pironman 5 Max V2
26/09/18 11:24:59.510 [INFO] Config:
26/09/18 11:24:59.511 [INFO] {
26/09/18 11:24:59.511 [INFO]   "system": {
26/09/18 11:24:59.511 [INFO]     "data_interval": 1,
26/09/18 11:24:59.511 [INFO]     "database_retention_days": "5",
26/09/18 11:24:59.511 [INFO]     "temperature_unit": "C",
26/09/18 11:24:59.511 [INFO]     "enable_history": true,
26/09/18 11:24:59.511 [INFO]     "oled_enable": true,
26/09/18 11:24:59.511 [INFO]     "oled_rotation": 0,
26/09/18 11:24:59.511 [INFO]     "oled_sleep_timeout": 30,
26/09/18 11:24:59.511 [INFO]     "oled_pages": ["performance"],
26/09/18 11:24:59.511 [INFO]     "rgb_enable": false,
26/09/18 11:24:59.511 [INFO]     "rgb_color": "#0a1aff",
26/09/18 11:24:59.511 [INFO]     "rgb_brightness": 100,
26/09/18 11:24:59.511 [INFO]     "rgb_style": "breathing",
26/09/18 11:24:59.511 [INFO]     "rgb_speed": 45,
26/09/18 11:24:59.511 [INFO]     "rgb_led_count": 4,
26/09/18 11:24:59.511 [INFO]     "rgb_led_count_min": 4,
26/09/18 11:24:59.511 [INFO]     "gpio_fan_pin": 6,
26/09/18 11:24:59.511 [INFO]     "gpio_fan_mode": 2,
26/09/18 11:24:59.511 [INFO]     "gpio_fan_led": "off",
26/09/18 11:24:59.511 [INFO]     "gpio_fan_led_pin": 5,
26/09/18 11:24:59.511 [INFO]     "debug_level": "DEBUG"
26/09/18 11:24:59.511 [INFO]   }
26/09/18 11:24:59.511 [INFO] }
26/09/18 11:24:59.512 [INFO] Device info:
26/09/18 11:24:59.512 [INFO] {
26/09/18 11:24:59.512 [INFO]   "name": "Pironman 5 Max",
26/09/18 11:24:59.512 [INFO]   "id": "pironman5-max",
26/09/18 11:24:59.512 [INFO]   "peripherals": [
26/09/18 11:24:59.512 [INFO]     "network",
26/09/18 11:24:59.512 [INFO]     "oled_page_disk",
26/09/18 11:24:59.512 [INFO]     "restart_service",
26/09/18 11:24:59.512 [INFO]     "oled_page_performance",
26/09/18 11:24:59.512 [INFO]     "gpu_temperature",
26/09/18 11:24:59.512 [INFO]     "gpio_fan_led",
26/09/18 11:24:59.512 [INFO]     "cpu_temperature",
26/09/18 11:24:59.512 [INFO]     "delete_log_file",
26/09/18 11:24:59.512 [INFO]     "oled_page_mix",
26/09/18 11:24:59.512 [INFO]     "ip_address",
26/09/18 11:24:59.512 [INFO]     "history",
26/09/18 11:24:59.512 [INFO]     "storage",
26/09/18 11:24:59.512 [INFO]     "shutdown",
26/09/18 11:24:59.512 [INFO]     "pi5_power_button",
26/09/18 11:24:59.512 [INFO]     "gpio_fan_state",
26/09/18 11:24:59.512 [INFO]     "log",
26/09/18 11:24:59.512 [INFO]     "clear_history",
26/09/18 11:24:59.512 [INFO]     "oled_sleep",
26/09/18 11:24:59.512 [INFO]     "ws2812",
26/09/18 11:24:59.512 [INFO]     "temperature_unit",
26/09/18 11:24:59.512 [INFO]     "oled",
26/09/18 11:24:59.513 [INFO]     "reboot",
26/09/18 11:24:59.513 [INFO]     "cpu",
26/09/18 11:24:59.513 [INFO]     "pwm_fan_speed",
26/09/18 11:24:59.513 [INFO]     "debug_level",
26/09/18 11:24:59.513 [INFO]     "gpio_fan_mode",
26/09/18 11:24:59.513 [INFO]     "oled_page_ips",
26/09/18 11:24:59.513 [INFO]     "mac_address",
26/09/18 11:24:59.513 [INFO]     "memory"
26/09/18 11:24:59.513 [INFO]   ],
26/09/18 11:24:59.513 [INFO]   "version": "1.3.18",
26/09/18 11:24:59.513 [INFO]   "app_name": "pironman5",
26/09/18 11:24:59.513 [INFO]   "config_path": "/opt/pironman5/config.json"
26/09/18 11:24:59.513 [INFO] }
26/09/18 11:24:59.513 [INFO] PM_Auto version: 2.0.6
26/09/18 11:24:59.513 [INFO] PM_Dashboard version: 2.0.4
26/09/18 11:24:59.572 [INFO] Addons: FanAddon, OLEDAddon, Pi5PowerButtonAddon, SystemAddon, WS2812Addon
26/09/18 11:24:59.572 [DEBUG] Update gpio_fan_mode to 2
26/09/18 11:24:59.572 [DEBUG] Init GPIO Fan with pin: 6, led_pin: 5
26/09/18 11:24:59.576 [DEBUG] Set led to follow
26/09/18 11:24:59.576 [DEBUG] Init PWM Fan
26/09/18 11:24:59.593 [INFO] FanAddon service initialized
26/09/18 11:24:59.594 [DEBUG] Update oled_enable to True
26/09/18 11:24:59.595 [DEBUG] Update oled_rotation to 0
26/09/18 11:24:59.595 [DEBUG] Update oled_sleep_timeout to 30
26/09/18 11:24:59.595 [DEBUG] Update temperature_unit to C
26/09/18 11:24:59.595 [DEBUG] Update oled_pages to ['performance']
26/09/18 11:24:59.636 [INFO] OLEDAddon service initialized
26/09/18 11:24:59.638 [INFO] Pi5PowerButtonAddon service initialized
26/09/18 11:24:59.638 [INFO] SystemAddon service initialized
26/09/18 11:24:59.638 [DEBUG] Update LED count: 4
26/09/18 11:24:59.638 [DEBUG] Update RGB enable: False
26/09/18 11:24:59.638 [DEBUG] Update RGB color: #0a1aff
26/09/18 11:24:59.638 [DEBUG] Update RGB brightness: 100
26/09/18 11:24:59.638 [DEBUG] Update RGB speed: 45
26/09/18 11:24:59.638 [DEBUG] Update RGB style: breathing
26/09/18 11:24:59.661 [INFO] WS2812Addon service initialized
26/09/18 11:24:59.662 [DEBUG] Initializing Dashboard Server
26/09/18 11:24:59.663 [INFO] Pi5PowerButtonAddon service started
26/09/18 11:24:59.664 [INFO] Starting Dashboard Server on 0.0.0.0:34001
26/09/18 11:24:59.664 [INFO] FanAddon service started
26/09/18 11:24:59.664 [INFO] OLEDAddon service started
26/09/18 11:24:59.664 [INFO] SystemAddon service started
26/09/18 11:24:59.664 [INFO] WS2812Addon service started
26/09/18 11:24:59.664 [INFO] PWM Fan is supported, sync all other fan with pwm fan
26/09/18 11:24:59.666 [DEBUG] Update pages to: [PagePerformance]
26/09/18 11:24:59.666 [DEBUG] Starting Database
26/09/18 11:24:59.666 [INFO] Dashboard Server Started
26/09/18 11:24:59.715 [INFO] Starting influxdb service
26/09/18 11:24:59.846 [DEBUG] SystemAddon main loop started
26/09/18 11:24:59.977 [INFO] Addons started
26/09/18 11:25:01.716 [DEBUG] Waiting for InfluxDB to be ready
26/09/18 11:25:01.719 [INFO] Influxdb is ready
26/09/18 11:25:01.756 [INFO] Updated retention policy to 5d
26/09/18 11:25:01.757 [INFO] Updated inconsistent retention policy: 120h0m0s → 5d
26/09/18 11:25:01.757 [INFO] Database Started
26/09/18 11:25:01.757 [DEBUG] Starting Data Logger
26/09/18 11:25:01.765 [INFO] Data Logger Start
26/09/18 11:25:01.766 [INFO] Data Logger Started
26/09/18 11:25:01.776 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:02.773 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:03.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:04.768 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:05.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:06.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:07.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:08.767 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:09.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:10.767 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:11.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:12.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:13.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:14.767 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:15.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:16.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:17.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:18.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:19.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:20.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:21.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:22.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:23.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:24.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:25.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:26.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:27.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:28.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:29.675 [DEBUG] OLED sleep timeout, sleeping
26/09/18 11:25:29.675 [DEBUG] OLED sleep
26/09/18 11:25:29.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:30.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}
26/09/18 11:25:31.766 [ERROR] Failed to set data: {"error":"not attempting to open shard 484; opening shard previously failed with: [shard 484] failed opening /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx: open /var/lib/influxdb/data/pironman5-max/default_policy/484/fields.idx.tmp: permission denied"}

To confirm the OLED display should be working, see the attached screenshot. Please note that it used to work with a sharp tap on the top until a recent (Pi) update that led to this problem in the first place.

2026-09-18 11_50_07-Pi5 RemoteIT screen share – Raspberry Pi Connect
2026-09-18 11_50_07-Pi5 RemoteIT screen share – Raspberry Pi Connect778×444 24 KB

8

Thank you very much for following up so patiently and for providing the detailed logs and troubleshooting results — this really helps us narrow down the issue.

First, we are glad to hear that the service startup failure has been resolved by upgrading the GPIO-related packages. Regarding the OLED display still being completely blank, let’s look into it further together.

One important note: with recent version updates, the Pironman 5 Max has removed the “tap the case to wake the OLED” feature for compatibility reasons. Instead, the OLED is now woken by pressing the power button once. So please first press the power button once and see whether the OLED wakes up (please note: press the power button, not tap the case). If you have been trying to wake it by tapping the case, it is normal that the OLED does not respond.

In addition, we noticed that there are many ERROR messages in your logs. These errors are most likely caused by the old and new versions of the pironman5 service conflicting with each other by occupying some of the same resources (such as GPIO, I2C, etc.). In this case, the simplest and most thorough solution is to reinstall a clean system and then install the latest version of pironman5. If it is convenient for you, we suggest backing up your important data first and then reinstalling the system. This usually resolves both the service conflict and the display issues caused by it.

Please try pressing the power button once and let us know the result. If the OLED still does not display, please also let us know whether you are able to reinstall a clean system. Once we hear back from you, we will continue to help you troubleshoot as soon as possible. Thank you again for your patience and cooperation!

9

Thanks again for your continued support on this, especially since I am not the original poster (@mandolyn - did your problem get fixed ?).

I can confirm that the display now works by pressing the power button, not a tap on the top of the unit that used to be how it worked. I have looked through the recent build instructions for this with regards to the OLED stopping working and see that my unit (built to the original instructions) will still have the jumper link in place that enables the vibration sensor.

Is it possible that the presence of this jumper link is causing the never ending stream of errors in my log file ? If so that’s an easy fix the next time I am in front of the unit.

Less easy would be rebuilding the system. I usually maintain the unit by remote and it’s busy most of the time making a rebuild possible but undesirable. I did use your resources to uninstall the Pironman client and reinstall it but the constant stream of errors remains.

If this can be resolved without having to start again then clearly that would be my preferred route if removing the jumper link does not solve the problem. If it’s a software issue caused by an upgrade I would like to think it’s recoverable without nuking it from orbit.

What do we think about the jumper link ? Is that likely to be the problem or do I need to put some time aside ?

10

Thank you very much for your patience in providing the complete logs and troubleshooting results, and we are sorry for the trouble this has caused.

Regarding that jumper wire: please rest assured that its presence will not cause any error — it is not the cause of the problem, and you do not need to do anything about it.

Regarding the issue you reported: we will try to reproduce it internally to further confirm the root cause. If it is not currently affecting your normal use, you can keep using it as is for now — there is no need to repeatedly reinstall or tinker with it.

We will keep you updated as soon as we have any progress. Thank you again for your patience and cooperation!

1 Like