Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DE8F418C8E for ; Wed, 2 Dec 2015 15:53:11 +0000 (UTC) Received: (qmail 83625 invoked by uid 500); 2 Dec 2015 15:53:11 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 83571 invoked by uid 500); 2 Dec 2015 15:53:11 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 83206 invoked by uid 99); 2 Dec 2015 15:53:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Dec 2015 15:53:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 162FD2C1F72 for ; Wed, 2 Dec 2015 15:53:11 +0000 (UTC) Date: Wed, 2 Dec 2015 15:53:11 +0000 (UTC) From: "Stefania (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10788) Upgrade from 2.2.1 to 3.0.0 fails with NullPointerException MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036000#comment-15036000 ] Stefania commented on CASSANDRA-10788: -------------------------------------- bq. I'd like to stop Cassandra and put the original JAR in place (downgrade from 3.0.0-SNAPSHOT to 3.0.0). Should this work? It should because the code with the bug only runs during an upgrade, if the data was migrated correctly to 3.0, then that code should not run, at least that's the theory. > Upgrade from 2.2.1 to 3.0.0 fails with NullPointerException > ----------------------------------------------------------- > > Key: CASSANDRA-10788 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10788 > Project: Cassandra > Issue Type: Bug > Components: Lifecycle > Reporter: Tomas Ramanauskas > Assignee: Stefania > Fix For: 3.0.x, 3.x > > > I tried to upgrade Cassandra from 2.2.1 to 3.0.0, however, I get this error on startup after Cassandra 3.0 software was installed: > {code} > ERROR [main] 2015-11-30 15:44:50,164 CassandraDaemon.java:702 - Exception encountered during startup > java.lang.NullPointerException: null > at org.apache.cassandra.io.util.FileUtils.delete(FileUtils.java:374) ~[apache-cassandra-3.0.0.jar:3.0.0] > at org.apache.cassandra.db.SystemKeyspace.migrateDataDirs(SystemKeyspace.java:1341) ~[apache-cassandra-3.0.0.jar:3.0.0] > at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:180) [apache-cassandra-3.0.0.jar:3.0.0] > at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:561) [apache-cassandra-3.0.0.jar:3.0.0] > at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689) [apache-cassandra-3.0.0.jar:3.0.0] > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)