Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

system down after update 0.130.4 #15686

Closed
raspb1 opened this issue Aug 25, 2024 · 20 comments · Fixed by #15703
Closed

system down after update 0.130.4 #15686

raspb1 opened this issue Aug 25, 2024 · 20 comments · Fixed by #15703
Assignees
Labels
bug Something isn't working prio Priority waiting for feedback Suspended progress

Comments

@raspb1
Copy link

raspb1 commented Aug 25, 2024

Describe the bug

After I updated on 0.130.4 (and installation only the upgrade) My system is down and is not able to get started. The system message is: data base disk image malformed (11). The curios thing is: I made the update like always I made it svereal times before.

Steps to reproduce

...
look to the description above

Configuration details

d

Log details

d

What type of operating system are you running?

Linux

Version

d

@0x3d13f
Copy link
Contributor

0x3d13f commented Aug 25, 2024

See also #15685 and #15684
A downgrade to 0.130.3 was reported as helping for the moment there.

@pdonovan
Copy link

I'm seeing the same message on 0.130.4:

Aug 26 10:00:58 raspberrypi3 evcc[16317]: [main ] FATAL 2024/08/26 10:00:58 database disk image is malformed (11)
This is the 'armhf' build.

@RTTTC
Copy link
Contributor

RTTTC commented Aug 26, 2024

@andig

@n0cturne
Copy link

I can also confirm the problem with 0.130.4 and the NightlyBuild (0.130.4+1724639089).
Attached traces with both versions.
evcc-20240826-075728-trace_0_130_4_1724639089.log
evcc-20240826-075610-trace_0_130_4_.log
The rollback to version 0.130.3 can be used as workaround.

@jgantenberg
Copy link

I'm seeing the same message on 0.130.4:

Aug 26 10:00:58 raspberrypi3 evcc[16317]: [main ] FATAL 2024/08/26 10:00:58 database disk image is malformed (11) This is the 'armhf' build.

same here, 0.130.2 starts fine with same DB.

@StefanSchoof
Copy link
Contributor

I don't think any me too are needed at this point.

If someone who is affected, wants to help and is able to build evcc: A git bisect to find the first bad commit can be helpful for the team.

@andig
Copy link
Member

andig commented Aug 26, 2024

Better idea: could someone please email me a "corrupted" database to [email protected]? Might be an issue with the upgraded Gorm library but I'm only guessing.

@andig andig self-assigned this Aug 26, 2024
@andig andig added bug Something isn't working prio Priority labels Aug 26, 2024
@n0cturne
Copy link

Better idea: could someone please email me a "corrupted" database to [email protected]? Might be an issue with the upgraded Gorm library but I'm only guessing.

I have send you a mail.

@andig
Copy link
Member

andig commented Aug 26, 2024

For time being, I have remove the 0.130.4 release packages and Docker image.

/cc @naltatis not sure if Gorm has anything to do with it?

@andig
Copy link
Member

andig commented Aug 26, 2024

This is the 'armhf' build.

I've found the claimed corrupted database to be working on arm64. Which platforms are experiencing the problem?

@andig andig added the waiting for feedback Suspended progress label Aug 26, 2024
@andig
Copy link
Member

andig commented Aug 26, 2024

I can indeed repro on armhf:

❯ GOOS=linux GOARCH=armv6 make build
❯ docker run -it --platform linux/armhf -v $(pwd):/app -v ~/Download/evcc.db:/root/.evcc/evcc.db alpine /app/evcc
[main  ] INFO 2024/08/26 08:12:50 evcc 0.130.3 (91f0e534b)
[main  ] INFO 2024/08/26 08:12:50 missing config file - switching into demo mode
[db    ] INFO 2024/08/26 08:12:50 using sqlite database: /root/.evcc/evcc.db
[db    ] ERROR 2024/08/26 08:12:50 failed to initialize database, got error unable to open database file: out of memory (14)
[main  ] INFO 2024/08/26 08:12:50 listening at :7070
[main  ] FATAL 2024/08/26 08:12:50 unable to open database file: out of memory (14)
[main  ] FATAL 2024/08/26 08:12:50 will attempt restart in: 15m0s
[main  ] INFO 2024/08/26 08:12:51 new version available: 0.130.4

@andig
Copy link
Member

andig commented Aug 26, 2024

Opened glebarez/sqlite#144 upvotes might help.

@Robman1
Copy link

Robman1 commented Aug 26, 2024

This is the 'armhf' build.

I've found the claimed corrupted database to be working on arm64. Which platforms are experiencing the problem?

Same issue at my end. Use a Raspberry 4 with 64 Bit Raspberry OS -> AArch64 platform.
Robert@docker:~ $ cat /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian

@Michel83
Copy link

Michel83 commented Aug 26, 2024

My System:
Rasperry 3

Linux version 6.1.21-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1642 SMP Mon Apr 3 17:20:52 BST 2023

@hoppewf
Copy link

hoppewf commented Aug 26, 2024

Linux raspi-dns 6.1.21-v7+ #1642 SMP Mon Apr 3 17:20:52 BST 2023 armv7l GNU/Linux

PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"

@andig
Copy link
Member

andig commented Aug 26, 2024

So, here's what I've found:

  • issue appears on any linux/arm build but not arm64
  • db is apparently not corruped since it can be opened on arm64 in my tests
  • issue is introduced with modernc.org/sqlite >= v1.29.0 downstream dependency

@homuser2003
Copy link

homuser2003 commented Aug 26, 2024

Also have the corruption problem (Pi2B). Appears that 1.30.5 is not yet listed in the repository? Apt Upgrade says with 1.30.4 I had the latest release...

Did Apt update before...

@andig
Copy link
Member

andig commented Aug 26, 2024

Indeed. The downgraded version does not compile on Windows: https://github.com/evcc-io/evcc/actions/runs/10564539950/job/29267316724

@RTTTC
Copy link
Contributor

RTTTC commented Aug 27, 2024

New version 0.130.6 works fine.

@hardoverflow
Copy link
Contributor

It works again with v0.130.6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working prio Priority waiting for feedback Suspended progress
Projects
None yet
Development

Successfully merging a pull request may close this issue.