Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] CentOS 7 upgrade issue - backup is failing

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] CentOS 7 upgrade issue - backup is failing


Chronological Thread 
  • From: Jim Nauer CWRU <>
  • To:
  • Subject: [perfsonar-user] CentOS 7 upgrade issue - backup is failing
  • Date: Mon, 17 Dec 2018 17:12:38 -0500
  • Ironport-phdr: 9a23:7biZRhWLx9G5+o+hRghmZBKBEuHV8LGtZVwlr6E/grcLSJyIuqrYYxyDt8tkgFKBZ4jH8fUM07OQ7/iwHzRYqb+681k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRoLerpBIHSk9631+ev8JHPfglEnjWwba9xIRmssQndqtQdjJd/JKo21hbHuGZDdf5MxWNvK1KTnhL86dm18ZV+7SleuO8v+tBZX6nicKs2UbJXDDI9M2Ao/8LrrgXMTRGO5nQHTGoblAdDDhXf4xH7WpfxtTb6tvZ41SKHM8D6Uaw4VDK/5KptVRTmijoINyQh/W7YkMx+jKxVrhG8qRJh34HZe5uaOOZkc67HYd8WWWhMU8BMXCJBGIO8aI4PAvIFM+ZZqon2ukMAogGjBQayHuPk1yFFiX/q06I0zu8sFgPG0xYmH98Aq3nbsM/6NLwMXuyv0qbH0CjDYupQ1Dzg5obIdRUhruuNXbJ2acfd1FcjGgHfglmMs4DpIymZ2vkLvmOG7ORgTfqih3M5pwx1uDSj2NkghpPUio4JxF3I7zh1zYI1KNGgVkJ3fdqpHIFTuiyaLYd6XN0uT3xytCs417ELv4OwcjIQx5Q93RHfbuSKc4iW7RLnU+acOTJ4hGp7eL+wnhq+71SsxvD8W8WuzFlFtDFFncfWun8TyhPT99CLSvp7/ki/xTaCzx3f5v9ALEwui6bXNYQtzqMsmpcdq0jPAyv7lUXugK+TbEok++yo6+r9YrXho5+RL410hRv4MqkggcGwHf43MhMQUGSB5+uzyaDj8VXjQLpWlv02jrXZsJfCKMQDuKG5GQFV0p0k6xa5FTimys0UnWQcLF1bYhKKlIzpO1DVIPDkFveznU6gkDZtx/DaILLhGJPNIWbfkLv/Z7py9VNTyBdghexYsopZEL8aJ/T6QArsr9HCJh4/LwGuxev7UpNw2p5NY2+XBr6lN/bQuFqF/aQpKvSBfqcesS3wbfUp+q3Al3g8zH0ceOGP1IYacjiTIc5baxGbaHy3qtwICmpMswYjGr+5wGaeWCJeMi7hF5k34Ss2Xdqr

I'm trying to get rid of an old CentOS 6 / PS 4.0.2 setup & get it up to the supported CentOS 7 / PS 4.1.x configuration...but the very first step is failing, the backup of the old system.

I've googled around & found one reference to this problem back in the PS 4.0-RC1 timeframe -- but no answer.

When I run "/usr/lib/perfsonar/scripts/ps-migrate-backup.sh --data ~/ps-backup.tgz", I get an error on snapshotting the cassandra database:

# /usr/lib/perfsonar/scripts/ps-migrate-backup.sh --data ~/ps-backup.tgz
Backing-up users...[SUCCESS]
Backing-up groups...[SUCCESS]
Backing-up passwords...[SUCCESS]
Backing-up perfsonar configuration...[SUCCESS]
Backing-up bwctl-server configuration...[SUCCESS]
Backing-up owamp-server configuration...[SUCCESS]
Backing-up NTP configuration...[SUCCESS]
Backing-up cassandra data for esmond...Unable to snapshot cassandra database

If I run the first "nodetool" comand from the backup script, I get:
# nodetool clearsnapshot esmond -t esmond_snapshot
Failed to connect to '127.0.0.1:7199': Connection refused (Connection refused)
#

This is not entirely surprising, since there is no process listening on port 7199 (on any interface - 127.0.0.1, 0.0.0.0, or the node's actual IP address).

The backup script _does_ work with the '--data' flag omitted.

So...why is cassandra (apparently) not configured the way the toolkit expects it to be, and how can I fix it?

Thanks,
  --Jim

P.S. node is running CentOS 6 + PS 4.0.2 - but was originally installed as a NetInstall back in the PS 3.0.x days, I think (updated continually via yum-cron since then).  

--
James A. Nauer                   | "I shall not yield one whit of  maturity,
Engineer III, Enterprise Systems | not grace, not respectability, to  the
University Technology, [U]Tech   | passing of time. I declare that I  shall
Case Western Reserve University  | forever be, if not a child,  certainly
(216) 368-MACS  (368-6227)       | childish"  --Kennet Shardik
USPA D-25604




Archive powered by MHonArc 2.6.19.

Top of Page