[jira] [Commented] (CASSANDRA-15830) Invalid version value: 4.0~alpha4 during startup
[
https://issues.apache.org/jira/browse/CASSANDRA-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17119411#comment-17119411
]
Benjamin Lerer commented on CASSANDRA-15830:
+1
> Invalid version value: 4.0~alpha4 during startup
>
>
> Key: CASSANDRA-15830
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15830
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Packaging
>Reporter: Eric Wong
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> Hi:
> We are testing the latest cassandra-4.0 on Centos 7 using a clean database.
> When we started cassandra the first time, everything is fine. However, when
> we stop and restart cassandra, we got the following error and the db refuses
> to startup:
> {code}
> ERROR [main] 2020-05-22 05:58:18,698 CassandraDaemon.java:789 - Exception
> encountered during startup
> java.lang.IllegalArgumentException: Invalid version value: 4.0~alpha4
> at
> org.apache.cassandra.utils.CassandraVersion.(CassandraVersion.java:64)
> at
> org.apache.cassandra.io.sstable.SSTableHeaderFix.fixNonFrozenUDTIfUpgradeFrom30(SSTableHeaderFix.java:84)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:250)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:650)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:767)
> {code}
> The only way to get the node up and running again is by deleting all data
> under /var/lib/cassandra.
>
> Is that a known issue?
> Thanks, Eric
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15830) Invalid version value: 4.0~alpha4 during startup
[
https://issues.apache.org/jira/browse/CASSANDRA-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17119115#comment-17119115
]
Michael Semb Wever commented on CASSANDRA-15830:
To manually test (though not ideal as {{mck/trunk_15830}} is a branch rather
than a tag)…
{code}
git clone https://github.com/apache/cassandra-builds.git
cd cassandra-builds
docker image rm -f `docker images -f label=org.cassandra.buildenv=centos -q`
docker build -f docker/centos7-image.docker --build-arg
"CASSANDRA_GIT_URL=https://github.com/thelastpickle/cassandra; docker/
mkdir /tmp/test_rpmbuild
docker run --rm -v /tmp/test_rpmbuild:/dist `docker images -f
label=org.cassandra.buildenv=centos -q` /home/build/build-rpms.sh
mck/trunk_15830
{code}
(this is taken from
https://github.com/apache/cassandra-builds/blob/master/cassandra-release/prepare_release.sh
)
> Invalid version value: 4.0~alpha4 during startup
>
>
> Key: CASSANDRA-15830
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15830
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Packaging
>Reporter: Eric Wong
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> Hi:
> We are testing the latest cassandra-4.0 on Centos 7 using a clean database.
> When we started cassandra the first time, everything is fine. However, when
> we stop and restart cassandra, we got the following error and the db refuses
> to startup:
> {code}
> ERROR [main] 2020-05-22 05:58:18,698 CassandraDaemon.java:789 - Exception
> encountered during startup
> java.lang.IllegalArgumentException: Invalid version value: 4.0~alpha4
> at
> org.apache.cassandra.utils.CassandraVersion.(CassandraVersion.java:64)
> at
> org.apache.cassandra.io.sstable.SSTableHeaderFix.fixNonFrozenUDTIfUpgradeFrom30(SSTableHeaderFix.java:84)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:250)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:650)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:767)
> {code}
> The only way to get the node up and running again is by deleting all data
> under /var/lib/cassandra.
>
> Is that a known issue?
> Thanks, Eric
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15830) Invalid version value: 4.0~alpha4 during startup
[
https://issues.apache.org/jira/browse/CASSANDRA-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17119093#comment-17119093
]
Michael Semb Wever commented on CASSANDRA-15830:
Patch in
https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/trunk_15830
Currently we have no way of testing debian or rpm packaging. This is a problem,
it hurts when cutting releases as well as afterwards (like this ticket). I've
entered a separate ticket to add testing of debian or rpm packaging.
> Invalid version value: 4.0~alpha4 during startup
>
>
> Key: CASSANDRA-15830
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15830
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Packaging
>Reporter: Eric Wong
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0-alpha
>
>
> Hi:
> We are testing the latest cassandra-4.0 on Centos 7 using a clean database.
> When we started cassandra the first time, everything is fine. However, when
> we stop and restart cassandra, we got the following error and the db refuses
> to startup:
> {code}
> ERROR [main] 2020-05-22 05:58:18,698 CassandraDaemon.java:789 - Exception
> encountered during startup
> java.lang.IllegalArgumentException: Invalid version value: 4.0~alpha4
> at
> org.apache.cassandra.utils.CassandraVersion.(CassandraVersion.java:64)
> at
> org.apache.cassandra.io.sstable.SSTableHeaderFix.fixNonFrozenUDTIfUpgradeFrom30(SSTableHeaderFix.java:84)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:250)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:650)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:767)
> {code}
> The only way to get the node up and running again is by deleting all data
> under /var/lib/cassandra.
>
> Is that a known issue?
> Thanks, Eric
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15830) Invalid version value: 4.0~alpha4 during startup
[
https://issues.apache.org/jira/browse/CASSANDRA-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17118111#comment-17118111
]
Michael Semb Wever commented on CASSANDRA-15830:
Reproduced with
{code}
cd /tmp
wget
https://downloads.apache.org/cassandra/redhat/40x/cassandra-4.0~alpha4-1.noarch.rpm
rpm2cpio cassandra-4.0\~alpha4-1.noarch.rpm| cpio -idmv
jar xvf ./usr/share/cassandra/apache-cassandra-4.0~alpha4.jar
org/apache/cassandra/config/version.properties
cat org/apache/cassandra/config/version.properties
{code}
The version used is wrong when building the project artifacts inside the
[build-rpms.sh|https://github.com/apache/cassandra-builds/blob/master/docker/build-rpms.sh#L75]
script, either the ${deb_release} or $CASSANDRA_VERSION.
> Invalid version value: 4.0~alpha4 during startup
>
>
> Key: CASSANDRA-15830
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15830
> Project: Cassandra
> Issue Type: Bug
>Reporter: Eric Wong
>Assignee: Michael Semb Wever
>Priority: Normal
>
> Hi:
> We are testing the latest cassandra-4.0 on Centos 7 using a clean database.
> When we started cassandra the first time, everything is fine. However, when
> we stop and restart cassandra, we got the following error and the db refuses
> to startup:
> {code}
> ERROR [main] 2020-05-22 05:58:18,698 CassandraDaemon.java:789 - Exception
> encountered during startup
> java.lang.IllegalArgumentException: Invalid version value: 4.0~alpha4
> at
> org.apache.cassandra.utils.CassandraVersion.(CassandraVersion.java:64)
> at
> org.apache.cassandra.io.sstable.SSTableHeaderFix.fixNonFrozenUDTIfUpgradeFrom30(SSTableHeaderFix.java:84)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:250)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:650)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:767)
> {code}
> The only way to get the node up and running again is by deleting all data
> under /var/lib/cassandra.
>
> Is that a known issue?
> Thanks, Eric
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15830) Invalid version value: 4.0~alpha4 during startup
[
https://issues.apache.org/jira/browse/CASSANDRA-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17115884#comment-17115884
]
Eric Wong commented on CASSANDRA-15830:
---
I actually found out this morning. If I replaced
apache-cassandra-4.0-alpha4.jar from the binary distribution, instead of the
rpm version, I can shutdown and restart the db without issue.
> Invalid version value: 4.0~alpha4 during startup
>
>
> Key: CASSANDRA-15830
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15830
> Project: Cassandra
> Issue Type: Bug
>Reporter: Eric Wong
>Priority: Normal
>
> Hi:
> We are testing the latest cassandra-4.0 on Centos 7 using a clean database.
> When we started cassandra the first time, everything is fine. However, when
> we stop and restart cassandra, we got the following error and the db refuses
> to startup:
> {code}
> ERROR [main] 2020-05-22 05:58:18,698 CassandraDaemon.java:789 - Exception
> encountered during startup
> java.lang.IllegalArgumentException: Invalid version value: 4.0~alpha4
> at
> org.apache.cassandra.utils.CassandraVersion.(CassandraVersion.java:64)
> at
> org.apache.cassandra.io.sstable.SSTableHeaderFix.fixNonFrozenUDTIfUpgradeFrom30(SSTableHeaderFix.java:84)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:250)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:650)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:767)
> {code}
> The only way to get the node up and running again is by deleting all data
> under /var/lib/cassandra.
>
> Is that a known issue?
> Thanks, Eric
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
