#181 Upgrade failures from 1.10 to 1.2 - Multiple Servers Unable to Upgrade

[Jim Julson]

Hi There,

I'm trying to upgrade from 1.0.10, and having a heck of a time. I'm not sure if it's something I'm doing, or if I'm missing a dependency, or what. But no matter what I do, I end up seeing "The connection was reset" by my webserver as soon as i try to flip to 1.2. I'm following the standard upgrade path found on your main site located here: http://phpipam.net/documents/upgrade/

I'm running Ubuntu 14.04.3 LTS, Apache 2.2, PHP 5.5.9, MySQL 5.5.44 and as noted above, presently running 1.10 which works very well.

I presently use Mod-Rewrite, and it's working fine on 1 of my 2 installs. I've tried the upgrade both with and without that turned on. I've even tried a manual upgrade by following the instructions, and while importing the .SQL into the DB, the path from 1.18 to 1.19, and then 1.19 to 1.2 both throw errors. Unfortunately, I didn't take note of them as it was early on in the adventure. I've rolled back for now, and will give it another shot later.

I'm wondering if anyone else has had issues? The upgrade process is supposed to be a cakewalk, which all the other ones were...

[Jim Julson]

For reference, I find myself having to manually specify the full /upgrade/index.php and only then do I see something. And as stated above, all my Mod-Rewrite is working fine. This is now a secondary vHost, new Database, on a new install.

[Jason Lachowsky]

My symptoms are identical. I saved some of my output from a sequential upgrade, see attached. Thanks for any insights.

[Miha Petkovsek]

Can you manually set each query in db/UPDATE- starting from your currently installed version ?

UPDATE-v1.11.sql
UPDATE-v1.12.sql
...
UPDATE-v1.2.sql

and tell me which query fails ?

[Jim Julson]

Im mobile ATM so pardon the short response.

I had failures and in the final 3 scripts.

1.17 > 1.18
1.18 > 1.19
1.19> 1.2

I will get the oupit of the failures this weekend after i try again.

Thanks Miha

On Thursday, February 11, 2016, Miha Petkovsek myha@users.sf.net wrote:

Can you manually set each query in db/UPDATE- starting from your currently
installed version ?

UPDATE-v1.11.sql
UPDATE-v1.12.sql
...
UPDATE-v1.2.sql

and tell me which query fails ?

• [support-requests:#181]
  http://sourceforge.net/p/phpipam/support-requests/181/ Upgrade failures
  from 1.10 to 1.2 - Multiple Servers Unable to Upgrade*

Status: open
Group: version 0.8
Labels: upgrade 1.2
Created: Mon Feb 01, 2016 03:40 AM UTC by Jim Julson
Last Updated: Thu Feb 11, 2016 04:19 PM UTC
Owner: Miha Petkovsek

Hi There,

I'm trying to upgrade from 1.0.10, and having a heck of a time. I'm not
sure if it's something I'm doing, or if I'm missing a dependency, or what.
But no matter what I do, I end up seeing "The connection was reset" by my
webserver as soon as i try to flip to 1.2. I'm following the standard
upgrade path found on your main site located here:
http://phpipam.net/documents/upgrade/

I'm running Ubuntu 14.04.3 LTS, Apache 2.2, PHP 5.5.9, MySQL 5.5.44 and as
noted above, presently running 1.10 which works very well.

I presently use Mod-Rewrite, and it's working fine on 1 of my 2 installs.
I've tried the upgrade both with and without that turned on. I've even
tried a manual upgrade by following the instructions, and while importing
the .SQL into the DB, the path from 1.18 to 1.19, and then 1.19 to 1.2 both
throw errors. Unfortunately, I didn't take note of them as it was early on
in the adventure. I've rolled back for now, and will give it another shot
later.

I'm wondering if anyone else has had issues? The upgrade process is
supposed to be a cakewalk, which all the other ones were...

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/phpipam/support-requests/181/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

--

Jim C. Julson Jr.