Issue w/ RC2, init.d script, and /etc/opentsdb directory?

80 views
Skip to first unread message

Shane O'Donnell

unread,
Apr 7, 2015, 10:31:41 AM4/7/15
to open...@googlegroups.com
I tried using the new RC2 rpm (Thanks, Chris!) to upgrade a couple of OpenTSDB RC1 instances and in the process, ended up losing the ability to start/stop OpenTSDB as a service using:

     service opentsdb [start|stop]

There's no script in /etc/init.d nor any config in /etc at all.

I've removed RC2 and re-installed RC1, verifying that RC1 delivered the init.d script and default config.

There are copies of config and the init.d script in /usr/share/opentsdb/etc, but I don't know when those were created (at RC2 install?  at RC1 re-install?  etc.)  

I know we were tracking a defect around startup scripts, but it appeared to be more around Ubuntu.  I'm running Amazon Linux in EC2.

Shane O.
========================
Shane O'Donnell

4819 Emperor Blvd., Ste 400
Durham, North Carolina 27703
tel: +1.424.262.KNOW x703
skype: shaneodonnell
email: sha...@knownormal.com
========================
:wq!

ManOLamancha

unread,
Apr 23, 2015, 10:08:13 PM4/23/15
to open...@googlegroups.com
On Tuesday, April 7, 2015 at 7:31:41 AM UTC-7, Shane O. wrote:
I tried using the new RC2 rpm (Thanks, Chris!) to upgrade a couple of OpenTSDB RC1 instances and in the process, ended up losing the ability to start/stop OpenTSDB as a service using:

     service opentsdb [start|stop]

There's no script in /etc/init.d nor any config in /etc at all.

I've removed RC2 and re-installed RC1, verifying that RC1 delivered the init.d script and default config.

There are copies of config and the init.d script in /usr/share/opentsdb/etc, but I don't know when those were created (at RC2 install?  at RC1 re-install?  etc.)  

I know we were tracking a defect around startup scripts, but it appeared to be more around Ubuntu.  I'm running Amazon Linux in EC2.

Arggg, that stinks. I had tried it on my build VM but maybe it had an old script left over. I'll take a peek this weekend. Thanks! 

Jari Takkala

unread,
Apr 28, 2015, 4:54:30 PM4/28/15
to open...@googlegroups.com
This is because of the change I introduced in PR#447[1], or to be more precise, it's due to the lack of checks around removing the RPM pre-RC2.

This will be an issue for people running older RPM releases. I believe the work-around would be to 'rpm --erase' the old release, and then 'rpm -ivh' the new version. You'll lose your local config of course. However, upgrades from then on should work properly. I tested this pretty extensively a few months ago when I ran into the problem.


Jari
Reply all
Reply to author
Forward
0 new messages