StoreGrid Forum

4.2 Upgrade gone awry

Vembu StoreGrid: Online backup software for Service Providers, SMBs & ROBOs

4.2 Upgrade gone awry

Postby beddo » Fri Mar 30, 2012 1:40 pm

I ran the upgrade which passed without errors but now all I get when trying to log in is:

Unable to log you in. Make sure StoreGrid is running

StoreGrid is running with the pid in SG.pid

SGLog.log contains nothing since I did the upgrade and there's nothing in the system log files. The log folder only contains an email subdirectory with SGMailerLog.log in it.

I'm running CentOS release 6.2 (Final)

There doesn't appear to be much in the way of CPU or disk activity.

I'm bit stuck without having any logs to go on!
beddo
 
Posts: 8
Joined: Wed May 30, 2007 3:27 am

Re: 4.2 Upgrade gone awry

Postby beddo » Fri Mar 30, 2012 3:25 pm

Looks like the upgrade turned off logging:

01000 : Failed to connect to datasource: [unixODBC][Driver Manager]Can't open lib '/usr/local/lib/libmyodbc3-3.51.27.so' : file not found :: [Open DB] : IN DB /home/storegrid/Vembu/StoreGrid/data/sgserver.db#### Error in opening DB Connection ####::

libmyodbc3-3.51.27.so exists in /usr/local/lib but not /home/storegrid/Vembu/StoreGrid/chroot/usr/local/lib

I have manually copied it however it still doesn't work.

I then looked for /home/storegrid/Vembu/StoreGrid/data/sgserver.db which apparently doesn't exist so this may be the problem.

How do I get this file created?
beddo
 
Posts: 8
Joined: Wed May 30, 2007 3:27 am

Re: 4.2 Upgrade gone awry

Postby ilavarasan » Mon Apr 02, 2012 4:10 am

Hi,

Further to the remote session to your problematic machine, our support team has resolved the issue by creating the symbolic link to the file "libodbcinst.so.1" by running the following command

ln -s /usr/lib/libodbcinst.so /usr/lib/libodbcinst.so.1

Regards,
Ilavarasan M.,
Vembu Technologies.
ilavarasan
 
Posts: 139
Joined: Wed Dec 20, 2006 12:04 am

Re: 4.2 Upgrade gone awry

Postby beddo » Mon Apr 02, 2012 9:11 am

Thanks for confirming the answer in case it helps others.

I can confirm that everything is up and running fine now so hopefully no more issues!
beddo
 
Posts: 8
Joined: Wed May 30, 2007 3:27 am

Re: 4.2 Upgrade gone awry

Postby mhonkomp » Mon Apr 02, 2012 11:14 am

How do I resolve this on a Windows 2008 R2 server? Same issue when trying to logon?
mhonkomp
 
Posts: 7
Joined: Thu Jun 03, 2010 9:01 am

Re: 4.2 Upgrade gone awry

Postby ilavarasan » Tue Apr 03, 2012 8:52 am

Hi,

To investigate this issue in detail, we may have to look in your problematic machine. Could you please contact our support team at storegrid-support AT vembu DOT com. They will work with you on this issue.

Regards,
Ilavarasan M.,
Vembu Technologies.
ilavarasan
 
Posts: 139
Joined: Wed Dec 20, 2006 12:04 am

Re: 4.2 Upgrade gone awry

Postby gillonba » Wed May 09, 2012 6:50 pm

Has anyone managed to resolve this issue? I did a fresh install a few hours ago on Win 2008 R2 and am experiencing the same issue. I found the troubleshooting guide at http://storegrid.vembu.com/online-backu ... ckup-tsg27 and have determined that nothing is listening on port 32005
gillonba
 
Posts: 33
Joined: Mon Sep 12, 2011 11:57 am

Re: 4.2 Upgrade gone awry

Postby ilavarasan » Thu May 10, 2012 6:23 am

Hi,

Please start StoreGrid as Administrator in command prompt and check you are able to login in to the StoreGrid webconsole. If so then please check your current logged in user has enough permission to access StoreGrid installation location.

If still the problem persists please contact our support team, they will assist you with better solution.

Regards,
Ilavarasan M,
Vembu Technologies.
ilavarasan
 
Posts: 139
Joined: Wed Dec 20, 2006 12:04 am

Re: 4.2 Upgrade gone awry

Postby gillonba » Thu May 10, 2012 11:25 am

I figured it out; I didn't install MySQL first. It would be nice if the installer installed MySQL for you, or at least provided a warning because if there is one already, I didn't see it. I last installed a StoreGrid server a year and a half ago so I didn't remember from last time, and since I already had the installation files on my workstation, I had no need to visit the download page (where I eventually saw that I did need to install MySQL)
gillonba
 
Posts: 33
Joined: Mon Sep 12, 2011 11:57 am

Re: 4.2 Upgrade gone awry

Postby vidhya » Fri May 11, 2012 4:08 am

Hi gillonba,

Probably we need to highlight this in the builds download section in the partner zone from where our partners download the builds. We have the installer as well in the partner zone that downloads and installs the MySQL.

We will put in content to show the two links more prominently and show more clearly to partners that both the MySQL installer and the builds have to be installed.

Thanks for pointing this out.

Vidhya
vidhya
 
Posts: 1459
Joined: Fri Feb 29, 2008 8:14 am

Re: 4.2 Upgrade gone awry

Postby gillonba » Fri May 11, 2012 8:53 am

That wouldn't have helped in my particular case. I finally figured it out when I saw the existing warning on the download page. However, since I already had the installer on my workstation, I had no reason to visit the download page and thus couldn't see the warning, no matter how well it is highlighted
gillonba
 
Posts: 33
Joined: Mon Sep 12, 2011 11:57 am

Re: 4.2 Upgrade gone awry

Postby suredata » Sat May 12, 2012 9:44 pm

Can't the install check for the MySQL instance and prompt if it's not found?
suredata
 
Posts: 352
Joined: Fri May 27, 2011 12:10 am

Re: 4.2 Upgrade gone awry

Postby vidhya » Sun May 13, 2012 1:55 pm

Hi

The current design is to let you install the StoreGrid server build before you install the MySQL. I guess we could add a check for MySQL and abort the StoreGrid server install. We'll look into adding this check in future.

Vidhya
vidhya
 
Posts: 1459
Joined: Fri Feb 29, 2008 8:14 am


Return to StoreGrid Discussions