cancel
Showing results for 
Search instead for 
Did you mean: 

Painful hotfix installation

Benedikt_Naesse
Confirmed Champ
Confirmed Champ

We recently moved to Nuxeo DM 5.4.2. I tried to install the hotfixes (patch per patch). Now, I didn't do this according to the exact order as was expected (only found the Internet page with the right order when I ran into problems) and now I am unable to login onto Nuxeo with my administrator account.

  • How do I uninstall/ roll back manually from the latest hotfixes ? If possible, specify this in a detailed way, because I am not a full time Nuxeo administrator.
  • Why is this hotfix installation procedure so painful ? It seems that this procedure is not really state-of-the-art ... On any other application/platform, getting the system up-to-date, just involves getting the last available patch and the installation takes care of any other dependencies and doing this in the right order. Also, restarting each time ... well, wasn't this something Windows users were so frustrated about and then Microsoft tried to reduce this as much as possible ? What do other users think about this ?
1 ACCEPTED ANSWER

Julien_Carsique
Elite Collaborator
Elite Collaborator

Hello,

I suppose the issue you had with the order was on DM-5.4.2-PATH-HF05.
/>

In Nuxeo 5.4.2, uninstalling hotfixes is not an easy task.
/> The easier solution would be to replace the whole Nuxeo directory with a clean one. Reusing the same configuration, same data directory, same database, will ensure the "new" Nuxeo to keep your existing data.
/>

If you prefer trying to repair your current install, we need to know the following (use something like http://friendpaste.com/ to share the listings):

  • content of ${nuxeo.data.dir}/packages/.packages file
  • listing of $NUXEO_HOME/nxserver/bundles/ directory

About your other questions:

  • Nuxeo 5.5 comes with a lot of improvements, including a quick install of all hotfixes, automatically taking care of the other dependencies and their respective order, in the state-of-the-art 🙂
  • You will have to restart only once.
  • Nuxeo 5.5 provides management of packages out of Nuxeo, allowing easy uninstall in such a case.
  • Restart of the server is sometimes required because of some Nuxeo Framework technical constraints, but, most of the time, the restart is only required under Windows because of its file locking behavior. Using Linux or Mac, restart is not required so often.

View answer in original post

11 REPLIES 11

rbahntje_Bahntj
Confirmed Champ
Confirmed Champ

I am not sure, but I think that you only need to remove the bad hot fix file from your nxserver/bundles

You can make a backup of the nxserver directory before, so if anithing goes wrong, you can go back 🙂

Thierry_Martins
Star Collaborator
Star Collaborator

Why is this hotfix installation procedure so painful ? It seems that this procedure is not really state-of-the-art ... On any other application/platform, getting the system up-to-date, just involves getting the last available patch and the installation takes care of any other dependencies and doing this in the right order. Also, restarting each time ... well, wasn't this something Windows users were so frustrated about and then Microsoft tried to reduce this as much as possible ? What do other users think about this ?

It will be done for Nuxeo 5.5

Julien_Carsique
Elite Collaborator
Elite Collaborator

Hello,

I suppose the issue you had with the order was on DM-5.4.2-PATH-HF05.
/>

In Nuxeo 5.4.2, uninstalling hotfixes is not an easy task.
/> The easier solution would be to replace the whole Nuxeo directory with a clean one. Reusing the same configuration, same data directory, same database, will ensure the "new" Nuxeo to keep your existing data.
/>

If you prefer trying to repair your current install, we need to know the following (use something like http://friendpaste.com/ to share the listings):

  • content of ${nuxeo.data.dir}/packages/.packages file
  • listing of $NUXEO_HOME/nxserver/bundles/ directory

About your other questions:

  • Nuxeo 5.5 comes with a lot of improvements, including a quick install of all hotfixes, automatically taking care of the other dependencies and their respective order, in the state-of-the-art 🙂
  • You will have to restart only once.
  • Nuxeo 5.5 provides management of packages out of Nuxeo, allowing easy uninstall in such a case.
  • Restart of the server is sometimes required because of some Nuxeo Framework technical constraints, but, most of the time, the restart is only required under Windows because of its file locking behavior. Using Linux or Mac, restart is not required so often.

Ok. Thanks for the fast reply. I understand that since the Nuxeo Admin Centre is quite new, some things need to be improved.

If you installed Nuxeo with APT, then "apt-get remove ..." followed by "apt-get install ..." is enough. DO NOT use "purge" in order to keep your data. You should backup your data before (see http

Benedikt_Naesse
Confirmed Champ
Confirmed Champ

I tried the apt-get remove and install way (clean way), but the install failed:

FATAL: invalid value for parameter "lc_messages": "en_US.UTF-8" psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5433"?

This is probably due to the fact that I use a different port (5432), a different user name, password and database (not nuxeodb). I tried to change nuxeo.conf and restarting nuxeo-dm, but that didn't solve the problem...

Yeah, it seems there's an issue in the current packages when switching between an auto-configured postgresql and a "custom" one, this has been rewritten for 5.5.

I tried to fix it with changing nuxeo.debconf.pqsqldb. Reinstalling it gave me the option to change the db settings, but still there were db connections errors (in server.log) and also some jar files (remaining hotfixes which are not removed by "apt-get remove" so it seems) caused problems. I tried to remove the jar files, still I had problems with the postgresql service. Still, I could connect to the Postgresql server and see that all data was there. I don't want to read a 1000 page manual, so ...

I'm afraid that using "purge", you lost the data directory, even if your custom database was kept.