lavinmq
lavinmq copied to clipboard
Outdated schema version 0 for /var/lib/lavinmq/42099b4af021e53fd8fd4e056c2568d7c2e3ffa8/97c1c36cf4b13e7f763f7ca5
hello i'm new to lavinmq
i'm installing lavinmq on my ubuntu laptop for experiment, but i get this error log when starting lavinmq service (found from command => journalctl -xeu lavinmq.service)
Outdated schema version 0 for /var/lib/lavinmq/42099b4af021e53fd8fd4e056c2568d7c2e3ffa8/97c1c36cf4b13e7f763f7ca5
after i delete the folder then restart, it works again, why this is happening ? If my experiment run smoothly, i'm planning to replace rabbitmq with lavinmq on my production server
Hi @superdit
Which version of LavinMQ are you using?
Could you please provide the content of your /var/lib/lavinmq/42099b4af021e53fd8fd4e056c2568d7c2e3ffa8/97c1c36cf4b13e7f763f7ca5 folder?
i'm running lavinmq version 1.2.7 installed using ubuntu repository
sorry since i already deleted the folder I don't know what content inside the folder
but now. after I deleted it, inside this folder (/var/lib/lavinmq/42099b4af021e53fd8fd4e056c2568d7c2e3ffa8) i get only these files definitions.amqp .vhost
Okay, thanks.
Have you had any earlier versions of LavinMQ installed on your machine?
I'm not able to reproduce this on my machine at the moment. Could you please provide the following information:
- What version of Ubuntu are you running?
- What are the permissions for
/var/lib/lavinmq? - Steps to reproduce (what commands did you run)
Closing because of inactivity.
can we re-open this? I'm testing FreeBSD port upgrade from 1.2.9 -> 1.2.11 and seeing the same issue:
FreeBSD 15.0-CURRENT amd64crystal 1.10.1
$ lavinmq --config=/usr/local/etc/lavinmq/lavinmq.ini --debug
2024-05-15T09:19:41.074772Z INFO launcher logger settings
2024-05-15T09:19:41.074787Z INFO launcher LavinMQ 1.2.11
2024-05-15T09:19:41.074790Z INFO launcher Crystal 1.10.1 [84f389ac5424] (2023-10-13)
2024-05-15T09:19:41.074794Z INFO launcher LLVM: 16.0.6
2024-05-15T09:19:41.074797Z INFO launcher Default target: x86_64-portbld-freebsd15.0
2024-05-15T09:19:41.074803Z INFO launcher Build flags: --release --debug
2024-05-15T09:19:41.074806Z INFO launcher Pid: 24617
2024-05-15T09:19:41.074811Z INFO launcher Config file: /usr/local/etc/lavinmq/lavinmq.ini
2024-05-15T09:19:41.074815Z INFO launcher Data directory: /var/db/lavinmq
2024-05-15T09:19:41.074824Z INFO launcher FD limit: 65000
2024-05-15T09:19:41.080477Z DEBUG userstore Loading users from file
2024-05-15T09:19:41.081118Z DEBUG userstore 2 users loaded
2024-05-15T09:19:41.081143Z DEBUG vhoststore Loading vhosts from file
2024-05-15T09:19:41.081285Z DEBUG vhost[name=/] 0 items loaded from operator_policies.json
2024-05-15T09:19:41.081292Z DEBUG vhost[name=/] 0 items loaded from policies.json
2024-05-15T09:19:41.081297Z DEBUG vhost[name=/] 0 items loaded from parameters.json
2024-05-15T09:19:41.081302Z INFO vhost[name=/] Loading definitions
2024-05-15T09:19:41.081307Z DEBUG vhost[name=/] Verifying schema
2024-05-15T09:19:41.081362Z INFO vhost[name=/] Applying 7 exchanges
2024-05-15T09:19:41.081386Z INFO vhost[name=/] Applying 1 queues
Unhandled exception: Outdated schema version 0 for /var/db/lavinmq/42099b4af021e53fd8fd4e056c2568d7c2e3ffa8/f192fd7ea451ab2158be9701c5ec2f1852de3bdd/msgs.0000000001 (LavinMQ::OutdatedSchemaVersion)
I can provide a tarball of /var/db/lavinmq via lavinmq slack if thats helpful, @ me dch.
42099b4af021e53fd8fd4e056c2568d7c2e3ffa8/
42099b4af021e53fd8fd4e056c2568d7c2e3ffa8/definitions.amqp
42099b4af021e53fd8fd4e056c2568d7c2e3ffa8/f192fd7ea451ab2158be9701c5ec2f1852de3bdd/
42099b4af021e53fd8fd4e056c2568d7c2e3ffa8/f192fd7ea451ab2158be9701c5ec2f1852de3bdd/msgs.0000000001
backups/
backups/2024-03-07T16:47:30Z/
schema_version
users.json
vhosts.json
Yes, we will have a look. Sent you a message on slack about those files!
@dch Do you have a reliable way of reproducing this error? We're having problems recreating it.
Sorry for the delay 🙈
no worries. what platform/lavinmq version are you testing this on? for me it's easy, using the tarball we exchanged on slack, and v1.2.11.
Just adding here for clarity: Had a chat with @dch on slack earlier today, and the fix in https://github.com/cloudamqp/lavinmq/pull/685 is verified to solve the problem for them.
It's still not clear how one would end up with empty msg files, but this fix should handle it regardless.