Raspberry Pi: clock_gettime(CLOCK_MONOTONIC, _) failed: Operation not permitted (1) #2302

KennethEgholm · 2022-01-12T17:22:56Z

Is there an existing issue for this?

I have searched the existing issues

What happened?

The main container of teslamate keeps restarting.

Expected Behavior

No response

Steps To Reproduce

No response

Relevant log output

teslamate_1  | clock_gettime(CLOCK_MONOTONIC, _) failed: Operation not permitted (1)
teslamate_1  | Aborted (core dumped)
teslamate_1  | clock_gettime(CLOCK_MONOTONIC, _) failed: Operation not permitted (1)
teslamate_1  | Aborted (core dumped)
teslamate_1  | clock_gettime(CLOCK_MONOTONIC, _) failed: Operation not permitted (1)
teslamate_1  | Aborted (core dumped)
teslamate_1  | clock_gettime(CLOCK_MONOTONIC, _) failed: Operation not permitted (1)
teslamate_1  | Aborted (core dumped)
teslamate_1  | clock_gettime(CLOCK_MONOTONIC, _) failed: Operation not permitted (1)
teslamate_1  | Aborted (core dumped)

Screenshots

No response

Additional data

No response

Type of installation

Docker

Version

v1.25.2

KennethEgholm · 2022-01-12T17:23:10Z

ke@new-rasp:/temp $ uname -a
Linux new-rasp 5.10.17-v7l+ #1421 SMP Thu May 27 14:00:13 BST 2021 armv7l GNU/Linux
ke@new-rasp:/temp $ docker -v
Docker version 20.10.7, build f0df350
ke@new-rasp:~/temp $

vanruix · 2022-01-12T17:32:58Z

Same here

KennethEgholm · 2022-01-12T17:37:36Z

Reverting back to 1.25.0 makes the bootloop stop..

cwanja · 2022-01-12T17:40:10Z

Similar issues getting the container started. Errors differ though, as provided in #2300

teslamate_1  | =ERROR REPORT==== 12-Jan-2022::17:12:06.303755 ===
teslamate_1  | erts_poll_wait() failed: eperm (1)
teslamate_1  | 
teslamate_1  | 
teslamate_1  | =ERROR REPORT==== 12-Jan-2022::17:12:06.303778 ===
teslamate_1  | erts_poll_wait() failed: eperm (1)
teslamate_1  | 
teslamate_1  | 
teslamate_1  | =ERROR REPORT==== 12-Jan-2022::17:12:06.303792 ===
teslamate_1  | erts_poll_wait() failed: eperm (1)
teslamate_1  | 
teslamate_1  | 
teslamate_1  | =ERROR REPORT==== 12-Jan-2022::17:12:06.303805 ===
teslamate_1  | erts_poll_wait() failed: eperm (1)
teslamate_1  | 
teslamate_1  | 
teslamate_1  | =ERROR REPORT==== 12-Jan-2022::17:12:06.303819 ===
teslamate_1  | erts_poll_wait() failed: eperm (1)

More logs:

teslamate_1  | (no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642008600030132}}
teslamate_1  | (no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642008600030145}}
teslamate_1  | (no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642008600030160}}

Have decided to rollback to 1.25 for the time being.

vanruix · 2022-01-12T18:05:32Z

Reverting back to 1.25.0 makes the bootloop stop..

Could you tell me how you do this ?

cwanja · 2022-01-12T18:09:24Z

Reverting back to 1.25.0 makes the bootloop stop..

Could you tell me how you do this ?

Change the yml file from

services:
  teslamate:
    image: teslamate/teslamate:latest

To

services:
  teslamate:
    image: teslamate/teslamate:1.25.0

adriankumpf · 2022-01-12T18:18:38Z

@leewillis77 posted a soluation here: #2300 (comment)

petebocken · 2022-01-12T18:24:46Z

I upgraded directly to v1.25.2 and I cannot load teslamate at port 4000. Grafana on 3000 loads to a login window.

pi@teslamate:~ $ docker-compose --version
docker-compose version 1.29.2, build unknown
pi@teslamate:~ $ docker --version
Docker version 20.10.12, build e91ed57
pi@teslamate:~ $ cat /sys/firmware/devicetree/base/model
Raspberry Pi 3 Model B Plus Rev 1.3

I believe it actually upgraded to v1.25.2, how do I find the current installed version?

Appears I'm up-to-date:

pi@teslamate:~ $ docker-compose pull
Pulling teslamate ... done
Pulling database ... done
Pulling grafana ... done
Pulling mosquitto ... done
pi@teslamate:~ $ docker-compose up -d
pi_grafana_1 is up-to-date
pi_database_1 is up-to-date
pi_mosquitto_1 is up-to-date
pi_teslamate_1 is up-to-date

cwanja · 2022-01-12T18:26:19Z

I upgraded directly to v1.25.2 and I cannot load teslamate at port 4000. Grafana on 3000 loads to a login window.

pi@teslamate:~ $ docker-compose --version docker-compose version 1.29.2, build unknown pi@teslamate:~ $ docker --version Docker version 20.10.12, build e91ed57 pi@teslamate:~ $ cat /sys/firmware/devicetree/base/model Raspberry Pi 3 Model B Plus Rev 1.3

I believe it actually upgraded to v1.25.2, how do I find the current installed version?

Appears I'm up-to-date:

pi@teslamate:~ $ docker-compose pull Pulling teslamate ... done Pulling database ... done Pulling grafana ... done Pulling mosquitto ... done pi@teslamate:~ $ docker-compose up -d pi_grafana_1 is up-to-date pi_database_1 is up-to-date pi_mosquitto_1 is up-to-date pi_teslamate_1 is up-to-date

If you did not modify anything in your YML file and the teslamate service says latest then that is 1.25.2. You can also pull the first couple logs of the teslamate container (if you can, mine was flooded with errors) and it will post the version.

leewillis77 · 2022-01-12T18:27:16Z

how do I find the current installed version?

@petebocken
docker ps -a

cwanja · 2022-01-12T18:27:50Z

@leewillis77 posted a soluation here: #2300 (comment)

@leewillis77 - do you happen to have a small or quick right up for your fix as linked above? I suspect you are right, I am on v10 and facing errors. Although, it seems inconsistent what errors people are getting.

petebocken · 2022-01-12T18:30:23Z

docker ps -a

That doesn't appear to show any versions.. It does show latest cause that's what my config is set to. I did first try switching that to 1.25.0 and try to downgrade, but that didn't appear to downgrade at all.

pi@teslamate:~ $ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
03668f36cb36 teslamate/teslamate:latest "tini -- /bin/sh /en…" 15 minutes ago Up 47 seconds 0.0.0.0:4000->4000/tcp, :::4000->4000/tcp pi_teslamate_1
a19c57b8f61d teslamate/grafana:latest "/run.sh" 16 minutes ago Up 13 minutes 0.0.0.0:3000->3000/tcp, :::3000->3000/tcp pi_grafana_1
1de50c51422c postgres:12 "docker-entrypoint.s…" 16 minutes ago Up 13 minutes 5432/tcp pi_database_1
bbe0088d545c eclipse-mosquitto:1.6 "/docker-entrypoint.…" 16 minutes ago Up 13 minutes 0.0.0.0:1883->1883/tcp, :::1883->1883/tcp pi_mosquitto_1
46ee2b91c708 hello-world "/hello" 7 months ago Exited (0) 7 months ago hungry_yalow

petebocken · 2022-01-12T18:31:23Z

I upgraded directly to v1.25.2 and I cannot load teslamate at port 4000. Grafana on 3000 loads to a login window.
pi@teslamate:~ $ docker-compose --version docker-compose version 1.29.2, build unknown pi@teslamate:~ $ docker --version Docker version 20.10.12, build e91ed57 pi@teslamate:~ $ cat /sys/firmware/devicetree/base/model Raspberry Pi 3 Model B Plus Rev 1.3
I believe it actually upgraded to v1.25.2, how do I find the current installed version?
Appears I'm up-to-date:
pi@teslamate:~ $ docker-compose pull Pulling teslamate ... done Pulling database ... done Pulling grafana ... done Pulling mosquitto ... done pi@teslamate:~ $ docker-compose up -d pi_grafana_1 is up-to-date pi_database_1 is up-to-date pi_mosquitto_1 is up-to-date pi_teslamate_1 is up-to-date

If you did not modify anything in your YML file and the teslamate service says latest then that is 1.25.2. You can also pull the first couple logs of the teslamate container (if you can, mine was flooded with errors) and it will post the version.

Yup, mine is throwing errors like crazy:

=ERROR REPORT==== 12-Jan-2022::18:13:49.931687 ===
erts_poll_wait() failed: eperm (1)

leewillis77 · 2022-01-12T18:31:53Z

@cwanja There's not much to say really - download package, and install. I'm not really sure I want to provide step-by-step instructions as I'm not wholly convinced that it's a valid fix. From my understanding of how debian manage their repositories it probably is, and I'm comfortable applying that fix to my server, but I'm not (personally) comfortable declaring it as the "proper" fix for everyone.

cwanja · 2022-01-12T18:32:11Z

03668f36cb36 teslamate/teslamate:latest "tini -- /bin/sh /en…" 15 minutes ago Up 47 seconds 0.0.0.0:4000->4000/tcp, :::4000->4000/tcp pi_teslamate_1

That tells us that you are running the "latest" version. Which would be 1.25.2. For example, here is mine running 1.25.0 specifically.

pi@teslapi:~/Documents/teslamate $ docker container ls
CONTAINER ID   IMAGE                        COMMAND                  CREATED          STATUS          PORTS                                       NAMES
b5a21097be3d   teslamate/teslamate:1.25.0

petebocken · 2022-01-12T18:33:12Z

03668f36cb36 teslamate/teslamate:latest "tini -- /bin/sh /en…" 15 minutes ago Up 47 seconds 0.0.0.0:4000->4000/tcp, :::4000->4000/tcp pi_teslamate_1

That tells us that you are running the "latest" version. Which would be 1.25.2.

Figured. But i'm still dead in the water. I went straight from whatever the last version was before today to 1.25.2 and it won't let me load teslamate in the browser.

cwanja · 2022-01-12T18:34:32Z

03668f36cb36 teslamate/teslamate:latest "tini -- /bin/sh /en…" 15 minutes ago Up 47 seconds 0.0.0.0:4000->4000/tcp, :::4000->4000/tcp pi_teslamate_1

That tells us that you are running the "latest" version. Which would be 1.25.2.

Figured. But i'm still dead in the water. I went straight from whatever the last version was before today to 1.25.2 and it won't let me load teslamate in the browser.

You definitely should be able to downgrade. I have gone from 1.25.0 to .2 back to .0 then to .1 and back to .0. You might need to do a docker system prune in between there to remove any lingering images.

leewillis77 · 2022-01-12T18:35:15Z

@petebocken see #2300 (comment) for info on how to downgrade the teslamate image to 1.25.0

petebocken · 2022-01-12T18:46:13Z

@petebocken see #2300 (comment) for info on how to downgrade the teslamate image to 1.25.0

Yup, that's what I did the first time, but I had to run docker system prune first. I got downgraded back to 1.25.0 and then teslamate opened up fine. Then I tried switching config back to latest and updated and then teslamate won't open again and logs are flooded.

I downgraded to 1.25.0 again and it's working. Soooo apparently this isn't fixed in 1.25.2 or am I dealing with a different issue?

(no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642012829015831}}
(no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642012829015844}}
(no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642012829015863}}
=ERROR REPORT==== 12-Jan-2022::18:40:29.015876 ===
erts_poll_wait() failed: eperm (1)


=ERROR REPORT==== 12-Jan-2022::18:40:29.015889 ===
erts_poll_wait() failed: eperm (1)


=ERROR REPORT==== 12-Jan-2022::18:40:29.015902 ===
erts_poll_wait() failed: eperm (1)

petebocken · 2022-01-12T18:48:34Z

Ah, teslamate loads fine on 1.25.0, but grafana still sits at a login window.

cwanja · 2022-01-12T18:49:22Z

Ah, teslamate loads fine on 1.25.0, but grafana still sits at a login window.

admin | admin unless you changed it.

cwanja · 2022-01-12T18:50:52Z

@petebocken see #2300 (comment) for info on how to downgrade the teslamate image to 1.25.0

Yup, that's what I did the first time, but I had to run docker system prune first. I got downgraded back to 1.25.0 and then teslamate opened up fine. Then I tried switching config back to latest and updated and then teslamate won't open again and logs are flooded.

I downgraded to 1.25.0 again and it's working. Soooo apparently this isn't fixed in 1.25.2 or am I dealing with a different issue?
(no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642012829015831}}
(no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642012829015844}}
(no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642012829015863}}
=ERROR REPORT==== 12-Jan-2022::18:40:29.015876 ===
erts_poll_wait() failed: eperm (1)


=ERROR REPORT==== 12-Jan-2022::18:40:29.015889 ===
erts_poll_wait() failed: eperm (1)


=ERROR REPORT==== 12-Jan-2022::18:40:29.015902 ===
erts_poll_wait() failed: eperm (1)

You have the same errors I do in 1.25.2 which leads us back to @leewillis77 post here. Yet to sit down and try and fix it, but I assume you would be running Debian v10 and that is why you are facing the errors on 1.25.2.

petebocken · 2022-01-12T18:50:58Z

Ah, teslamate loads fine on 1.25.0, but grafana still sits at a login window.

admin | admin unless you changed it.

Thanks, that worked

petebocken · 2022-01-12T18:52:58Z

@petebocken see #2300 (comment) for info on how to downgrade the teslamate image to 1.25.0

Yup, that's what I did the first time, but I had to run docker system prune first. I got downgraded back to 1.25.0 and then teslamate opened up fine. Then I tried switching config back to latest and updated and then teslamate won't open again and logs are flooded.
I downgraded to 1.25.0 again and it's working. Soooo apparently this isn't fixed in 1.25.2 or am I dealing with a different issue?
(no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642012829015831}}
(no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642012829015844}}
(no logger present) unexpected logger message: {log,error,"~s~n",["erts_poll_wait() failed: eperm (1)\n"],#{error_logger=>#{emulator=>true,tag=>error},time=>1642012829015863}}
=ERROR REPORT==== 12-Jan-2022::18:40:29.015876 ===
erts_poll_wait() failed: eperm (1)


=ERROR REPORT==== 12-Jan-2022::18:40:29.015889 ===
erts_poll_wait() failed: eperm (1)


=ERROR REPORT==== 12-Jan-2022::18:40:29.015902 ===
erts_poll_wait() failed: eperm (1)
You have the same errors I do in 1.25.2 which leads us back to @leewillis77 post here. Yet to sit down and try and fix it, but I assume you would be running Debian v10 and that is why you are facing the errors on 1.25.2.

Yup, I'm on Debian Buster 10. I'll sit tight on 1.25.0. :-)

cwanja · 2022-01-12T19:06:25Z

So I do not want to solicit this as an "official" fix, but I find this fix working and comfortable applying.
https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/

Specifically this section:

The steps for libseccomp2 are well documented, as this has been a problem on multiple platforms (not just RPI4). You could do a 'oneshot' installation of a newer version, which can be found here itzg/docker-minecraft-server#755 (comment)

Personally I feel the better method is to install it from the Buster Backports repo, which is very safe to add. It also means any future updates to libseccomp will be applied to the Pi.

# Get signing keys to verify the new packages, otherwise they will not install
rpi ~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 04EE7237B7D453EC 648ACFD622F3D138
# Add the Buster backport repository to apt sources.list
rpi ~$ echo 'deb http://httpredir.debian.org/debian buster-backports main contrib non-free' | sudo tee -a /etc/apt/sources.list.d/debian-backports.list
rpi ~$ sudo apt update
rpi ~$ sudo apt install libseccomp2 -t buster-backports

I was able to follow that and got 1.25.2 working.

pi@teslapi:~/Documents/teslamate $ docker-compose logs teslamate
Attaching to teslamate_teslamate_1
teslamate_1  | 2022-01-12 19:02:54.294 [info] Migrations already up
teslamate_1  | 2022-01-12 19:03:00.696 [info] System Info: Erlang/OTP 24 (emu)
teslamate_1  | 2022-01-12 19:03:00.697 [info] Version: 1.25.2

This will also ensure that any future libseccomp updates are included when I update the Pi.

Apply at your own will and risk.

ploegy · 2022-01-12T19:17:46Z

I have the same Issue on a Raspberry Pi 3 Model B Rev 1.2,
1.25.0 works fine
1.25.1 Only Grafana
1.25.2 Not starting

Just did the same as cwanja and it worked for me.
#2302 (comment)

cwanja · 2022-01-12T19:30:54Z

I have the same Issue on a Raspberry Pi 3 Model B Rev 1.2,
1.25.0 works fine
1.25.1 Only Grafana
1.25.2 Not starting

1.25.1 introduced an error, referenced in #2300, preventing TeslaMate web interface to start.
1.25.2 fixed that error, but seemed to introduce a new range of errors as outlined in this thread. There is a fix back in @leewillis77 comment on #2300 or outlined in my comment above.

Edit: to be clear, the errors in 1.25.2 are not related to TeslaMate specifically. Seems there is a core Linux service (file? Dameon?) that was not updated in v10 for Raspbian OS. Someone can better explain it than I can, I am sure.

adriankumpf · 2022-01-12T19:45:23Z

The TeslaMate Docker image is based on the official elixir image which in turn is based on the official erlang image. A month ago, the latter was upgraded from Debian Buster to Bullseye even though the major version did not change: erlang/docker-erlang-otp@f14a791#diff-d12fb60cfa187f3314e96974fb7d9c0bc5f5667838c6d86211ae00cb1d64ccccL1

TeslaMate images built after this date are therefore implicitly also based on Debian Bullseye, although no changes have been made by TeslaMate. Thus, unfortunately, we cannot undo this.

Raspberry Pi users therefore have no choice but to either upgrade Raspbian or perform the workarounds described above.

Warlord711 · 2022-01-24T18:07:03Z

You can fix this by adding hosts /etc/timezone and /etc/localtime as volumes to the container.
Change the docker-composer.yml this way:

services:
  teslamate:
    image: teslamate/teslamate:latest
    restart: always
    environment:
      - DATABASE_USER=teslamate
      - DATABASE_PASS=secret
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
      - MQTT_HOST=mosquitto
    ports:
      - 4000:4000
    volumes:
      - ./import:/opt/app/import
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    cap_drop:
      - all

thunder2k · 2022-01-25T21:21:11Z

You can fix this by adding hosts /etc/timezone and /etc/localtime as volumes to the container. Change the docker-composer.yml this way:

services:
  teslamate:
    image: teslamate/teslamate:latest
    restart: always
    environment:
      - DATABASE_USER=teslamate
      - DATABASE_PASS=secret
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
      - MQTT_HOST=mosquitto
    ports:
      - 4000:4000
    volumes:
      - ./import:/opt/app/import
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    cap_drop:
      - all

This didn't work for me, same error message appeared in the logs

Warlord711 · 2022-01-25T22:07:43Z

This didn't work for me, same error message appeared in the logs

Hmm, weird. My first solution was to run the container with full privileges.
That worked for sure but was way to much privs.

If you run only local or can take the risk, you can add
privileged: true

But the volumes: entry should also do the trick.
Have you rebooted or at least restarted docker ?

thunder2k · 2022-01-26T11:43:17Z

This didn't work for me, same error message appeared in the logs

Hmm, weird. My first solution was to run the container with full privileges. That worked for sure but was way to much privs.

If you run only local or can take the risk, you can add privileged: true

But the volumes: entry should also do the trick. Have you rebooted or at least restarted docker ?

Thanks for the advice, I'd rather not run it full privileges :)

What I did was to add the 2 extra lines on the volumes and then I run the following commands:

docker-compose pull
docker-compose up -d

Is this right?

jakest · 2022-01-27T20:44:53Z

You can fix this by adding hosts /etc/timezone and /etc/localtime as volumes to the container. Change the docker-composer.yml this way:
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro

I can confirm that unfortunately, adding these two entries doesn't work, even after restarting Docker, and/or the machine it's running on. Looks like I'm stuck on 1.25.0 for now.

umb87 · 2022-01-28T09:35:31Z

I resolved add previleges : true on docker compose for teslamate image

namoona1 · 2022-01-30T16:20:45Z

After upgrading to bullseye on raspberry pi whenever I start up teslamate in docker it seems to be unable to connect to the internet. I tried running my container in privileged mode with no luck either. Without the docker container running I am able to ping external servers. Any suggestions what I am doing wrong here?

cwanja · 2022-01-30T16:23:25Z

After upgrading to bullseye on raspberry pi whenever I start up teslamate in docker it seems to be unable to connect to the internet. I tried running my container in privileged mode with no luck either. Without the docker container running I am able to ping external servers. Any suggestions what I am doing wrong here?

Are you able to connect to any sites on the Pi? I had to reconfigure Ethernet configuration post upgrade.

namoona1 · 2022-01-30T16:34:28Z

This is on my Wireless LAN and yes I am able to connect to sites if I keep my Docker container shut down. Also I am able to SSH to my Raspberry Pi via WLAN regardless of the state in which the docker container is in

thunder2k · 2022-01-30T16:41:06Z

I know we're going a bit off topic here, but which guide did you follow to upgrade to Bullseye? I have a lot of stuff running on my Pi and I'm scared it'll take me ages to be up&running again

natrlhy · 2022-01-30T16:47:25Z

I know we're going a bit off topic here, but which guide did you follow to upgrade to Bullseye? I have a lot of stuff running on my Pi and I'm scared it'll take me ages to be up&running again

I did this...

#2320 (comment)

namoona1 · 2022-01-30T16:47:59Z

I followed this guide https://blues.io/blog/guide-upgrade-raspberry-pi-buster-bullseye/ and after the upgrade reinstalled docker compose

thunder2k · 2022-01-30T16:57:11Z

Thanks both for your suggestion.. I'll find a moment to try it ASAP

cwanja · 2022-01-30T17:07:58Z

I know we're going a bit off topic here, but which guide did you follow to upgrade to Bullseye? I have a lot of stuff running on my Pi and I'm scared it'll take me ages to be up&running again

Thanks both for your suggestion.. I'll find a moment to try it ASAP

For you, backporting the required file will probably be the safer solution.
#2302 (comment)

thunder2k · 2022-01-30T17:11:35Z

I know we're going a bit off topic here, but which guide did you follow to upgrade to Bullseye? I have a lot of stuff running on my Pi and I'm scared it'll take me ages to be up&running again

Thanks both for your suggestion.. I'll find a moment to try it ASAP

For you, backporting the required file will probably be the safer solution. #2302 (comment)

Thanks for your comment, unfortunately I've already tried it but it doesn't work for 1.26. Is it working for you on the latest version?

cwanja · 2022-01-30T17:13:04Z

I know we're going a bit off topic here, but which guide did you follow to upgrade to Bullseye? I have a lot of stuff running on my Pi and I'm scared it'll take me ages to be up&running again

Thanks both for your suggestion.. I'll find a moment to try it ASAP

For you, backporting the required file will probably be the safer solution. #2302 (comment)

Thanks for your comment, unfortunately I've already tried it but it doesn't work for 1.26. Is it working for you on the latest version?

I backported for 1.25.X to work. Then upgraded Bullseye on top of it and it was still working. Currently running the latest version of TeslaMate no issues.

thunder2k · 2022-01-30T17:16:32Z

I think I've tried it directly on the latest but without upgrading to Bullseye and it didn't work. I guess it's a mandatory step regardless the backport install

thunder2k · 2022-01-31T10:24:31Z

I know we're going a bit off topic here, but which guide did you follow to upgrade to Bullseye? I have a lot of stuff running on my Pi and I'm scared it'll take me ages to be up&running again

Thanks both for your suggestion.. I'll find a moment to try it ASAP

For you, backporting the required file will probably be the safer solution. #2302 (comment)

Thanks for your comment, unfortunately I've already tried it but it doesn't work for 1.26. Is it working for you on the latest version?

I backported for 1.25.X to work. Then upgraded Bullseye on top of it and it was still working. Currently running the latest version of TeslaMate no issues.

So this morning I upgraded my docker version to 20.10.5 with the following guide:
https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/

and now teslamate 1.25.2 works fine!

Now I just need to find the time to upgrade to Bullseye and try the latest teslamate image.

@cwanja I'm wondering if, after upgrading to Bullseye,did you remove the Apt Preferences file /etc/apt/preferences.d/bullseye-docker.pref ?

EDIT:
I tried the following guide:
https://blues.io/blog/guide-upgrade-raspberry-pi-buster-bullseye/
but I ended up in a hybrid state where it was still showing buster as OS but the latest version of teslamate worked but a lot more of other stuff I need didn't, so I'm restoring my backup now.

EDIT2:
I didn't realize the latest teslamate version 1.26.1 works fine with just upgrading docker and libseccomp2. So after doing it, I'm happily running the latest version.

Thanks everybody for your help!

cwanja · 2022-02-01T15:38:13Z

@cwanja I'm wondering if, after upgrading to Bullseye,did you remove the Apt Preferences file /etc/apt/preferences.d/bullseye-docker.pref ?

I did not.

To get TeslaMate upgraded on Buster, all you needed to do was update libseccomp2. Nevertheless, glad to see you were able to get to 1.26.1.

natrlhy · 2022-02-02T13:33:52Z

Everything has been running fine on bullseye and version 1.26.1. Today though the TeslaMate and grafana containers keep restarting over and over

cwanja · 2022-02-02T13:35:16Z

What are in the logs?

…

On Feb 2, 2022, at 7:34 AM, natrlhy ***@***.***> wrote: Everything has been running fine on bullseye and version 1.26.1. Today though the TeslaMate and grafana containers keep restarting over and over — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.

natrlhy · 2022-02-02T13:42:06Z

It never stays up long enough to view the logs

24984021aa9f   eclipse-mosquitto:2          "/docker-entrypoint.…"   4 days ago   Up 20 minutes   0.0.0.0:1883->1883/tcp, :::1883->1883/tcp   docker_mosquitto_1
158dbbff421a   teslamate/teslamate:latest   "tini -- /bin/sh /en…"   4 days ago   Up 21 minutes   0.0.0.0:4000->4000/tcp, :::4000->4000/tcp   docker_teslamate_1
6c393974d300   postgres:13                  "docker-entrypoint.s…"   4 days ago   Up 1 second     5432/tcp                                    docker_db_1
ea689f9000ea   teslamate/grafana:latest     "/run.sh"                4 days ago   Up 1 second     0.0.0.0:3000->3000/tcp, :::3000->3000/tcp   docker_grafana_1```

natrlhy · 2022-02-02T13:48:10Z

Sorry, looks like it's the DB and grafana that won't stay up.

EDIT: Ah / has no space left... hm...
Deleted some backup files and running again ;)

tsl367 · 2022-08-17T13:05:26Z

It's because of libseccomp version, we can upgrade libseccomp.
You can download it from https://ftp.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.4-1+b1_armhf.deb
then install it

curl https://ftp.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.4-1+b1_armhf.deb -o libseccomp2.deb
sudo dpkg -i libseccomp2.deb

adriankumpf changed the title ~~Bootloop in teslamate_1~~ Raspberry Pi: clock_gettime(CLOCK_MONOTONIC, _) failed: Operation not permitted (1) Jan 12, 2022

adriankumpf mentioned this issue Jan 12, 2022

Cannot start v1.25.1 teslamate container: `GLIBC_2.29' not found #2300

Closed

1 task

cpswan mentioned this issue Feb 12, 2022

../../runtime/vm/os_linux.cc: 464: error: unreachable code when compiling AOT binary inside Docker on Armv7 dart-lang/sdk#48366

Closed

adriankumpf unpinned this issue Jul 15, 2022

cwanja mentioned this issue Dec 21, 2022

Can't browse web UI #3029

Closed

1 task

Dulanic added the Stale label Nov 12, 2023

JakobLichterfeld closed this as completed Nov 16, 2023

brianmay mentioned this issue Jul 11, 2024

Teslamate is failing to run after update #4080

Closed

1 task

Raspberry Pi: clock_gettime(CLOCK_MONOTONIC, _) failed: Operation not permitted (1) #2302

Raspberry Pi: clock_gettime(CLOCK_MONOTONIC, _) failed: Operation not permitted (1) #2302

Comments

KennethEgholm commented Jan 12, 2022 • edited Loading

Is there an existing issue for this?

What happened?

Expected Behavior

Steps To Reproduce

Relevant log output

Screenshots

Additional data

Type of installation

Version

KennethEgholm commented Jan 12, 2022

vanruix commented Jan 12, 2022

KennethEgholm commented Jan 12, 2022

cwanja commented Jan 12, 2022 • edited Loading

vanruix commented Jan 12, 2022

cwanja commented Jan 12, 2022

adriankumpf commented Jan 12, 2022

petebocken commented Jan 12, 2022

cwanja commented Jan 12, 2022

leewillis77 commented Jan 12, 2022

cwanja commented Jan 12, 2022 • edited Loading

petebocken commented Jan 12, 2022

petebocken commented Jan 12, 2022

leewillis77 commented Jan 12, 2022

cwanja commented Jan 12, 2022 • edited Loading

petebocken commented Jan 12, 2022

cwanja commented Jan 12, 2022

leewillis77 commented Jan 12, 2022

petebocken commented Jan 12, 2022

petebocken commented Jan 12, 2022 • edited Loading

cwanja commented Jan 12, 2022

cwanja commented Jan 12, 2022

petebocken commented Jan 12, 2022

petebocken commented Jan 12, 2022

cwanja commented Jan 12, 2022 • edited Loading

ploegy commented Jan 12, 2022 • edited Loading

cwanja commented Jan 12, 2022 • edited Loading

adriankumpf commented Jan 12, 2022 • edited Loading

Warlord711 commented Jan 24, 2022 • edited Loading

thunder2k commented Jan 25, 2022

Warlord711 commented Jan 25, 2022

thunder2k commented Jan 26, 2022 • edited Loading

jakest commented Jan 27, 2022

umb87 commented Jan 28, 2022

namoona1 commented Jan 30, 2022

cwanja commented Jan 30, 2022

namoona1 commented Jan 30, 2022 • edited Loading

thunder2k commented Jan 30, 2022

natrlhy commented Jan 30, 2022

namoona1 commented Jan 30, 2022

thunder2k commented Jan 30, 2022

cwanja commented Jan 30, 2022 • edited Loading

thunder2k commented Jan 30, 2022

cwanja commented Jan 30, 2022 • edited Loading

thunder2k commented Jan 30, 2022

thunder2k commented Jan 31, 2022 • edited Loading

cwanja commented Feb 1, 2022

natrlhy commented Feb 2, 2022

cwanja commented Feb 2, 2022 via email

natrlhy commented Feb 2, 2022 • edited Loading

natrlhy commented Feb 2, 2022 • edited Loading

tsl367 commented Aug 17, 2022

KennethEgholm commented Jan 12, 2022 •

edited

Loading

cwanja commented Jan 12, 2022 •

edited

Loading

cwanja commented Jan 12, 2022 •

edited

Loading

cwanja commented Jan 12, 2022 •

edited

Loading

petebocken commented Jan 12, 2022 •

edited

Loading

cwanja commented Jan 12, 2022 •

edited

Loading

ploegy commented Jan 12, 2022 •

edited

Loading

cwanja commented Jan 12, 2022 •

edited

Loading

adriankumpf commented Jan 12, 2022 •

edited

Loading

Warlord711 commented Jan 24, 2022 •

edited

Loading

thunder2k commented Jan 26, 2022 •

edited

Loading

namoona1 commented Jan 30, 2022 •

edited

Loading

cwanja commented Jan 30, 2022 •

edited

Loading

cwanja commented Jan 30, 2022 •

edited

Loading

thunder2k commented Jan 31, 2022 •

edited

Loading

natrlhy commented Feb 2, 2022 •

edited

Loading

natrlhy commented Feb 2, 2022 •

edited

Loading