[rudder-users] 2.5 to 2.9 Migration
Prestasit01
prestasit01 at ouest-france.fr
Thu Jan 23 15:03:35 CET 2014
Hello,
Any idea ?
BR
De : Prestasit01
Envoyé : mercredi 22 janvier 2014 14:45
À : 'Jonathan Clarke'
Cc : 'rudder-users at lists.rudder-project.org'
Objet : RE: [rudder-users] 2.5 to 2.9 Migration
In Addition :
As it's a clone but in the same network than our « correct rudder 2.4 server » , we have changed the hostname and the ips of the clone.
I don't know if it can break something in relation with the rudder-server-root files which have been created with the other ips/hostname informations.
BR
CJARDIN
De : Prestasit01
Envoyé : mercredi 22 janvier 2014 14:38
À : 'Jonathan Clarke'
Cc : rudder-users at lists.rudder-project.org<mailto:rudder-users at lists.rudder-project.org>
Objet : RE: [rudder-users] 2.5 to 2.9 Migration
Hi,
Please find the requested log in attachment.
1.During the yum process
2.During the restart command
3.The Stderrout of the day
Thanks
CJARDIN
De : Jonathan Clarke [mailto:jonathan.clarke at normation.com]
Envoyé : mercredi 22 janvier 2014 12:20
À : Prestasit01
Cc : rudder-users at lists.rudder-project.org<mailto:rudder-users at lists.rudder-project.org>
Objet : Re: [rudder-users] 2.5 to 2.9 Migration
Hi,
The messages about "no version information available" are just warnings, they can safely be ignored.
I see nothing wrong in the logs that you sent.
I have two questions that will help understand what is going on:
1) Please look at the output from when you ran the upgrade. If there are any errors there, please copy them here so we can understand what went wrong (if applicable).
2) Please run "/etc/init.d/rudder-server-root restart", then wait for a few minutes, and confirm the problem is still occuring. If so, please send us the /var/log/rudder/webapp/*.log file that has today's date.
Thanks,
Jonathan
On 22/01/14 11:51, Prestasit01 wrote:
Hello,
Yes jetty seems to be up and running.
I found these errors :
/opt/rudder/libexec/slapd: /usr/lib64/libssl.so.10: no version information available (required by /opt/rudder/lib/libldap_r-2.4.so.2)
/opt/rudder/libexec/slapd: /usr/lib64/libcrypto.so.10: no version information available (required by /opt/rudder/lib/libldap_r-2.4.so.2)
/var/rudder/cfengine-community/bin/cf-serverd: /usr/lib64/libcrypto.so.10: no version information available (required by /var/rudder/cfengine-community/bin/cf-serverd)
Server OS is : Centos 6.3
[root at rud26 /]# ls -altr /usr/lib64/libcrypto.so.10
lrwxrwxrwx 1 root root 18 17 déc. 2012 /usr/lib64/libcrypto.so.10 -> libcrypto.so.1.0.0
[root at rud26 /]# ls -altr /usr/lib64/libssl.so.10
lrwxrwxrwx 1 root root 15 17 déc. 2012 /usr/lib64/libssl.so.10 -> libssl.so.1.0.0
Please find more logs in attachment.
Thanks for the help
BR
CJARDIN
De : Nicolas Charles [mailto:nicolas.charles at normation.com]
Envoyé : mardi 21 janvier 2014 17:26
À : Prestasit01
Cc : rudder-users at lists.rudder-project.org<mailto:rudder-users at lists.rudder-project.org>
Objet : Re: [rudder-users] 2.5 to 2.9 Migration
Hello,
The log you pasted suggest that the application stopped. Is jetty running ?
There are some build in check that verify the application status, and restart the Web interface if any fails; can you see in the logs any message about this ?
Also, did you have any error message during the migration?
Regards,
Nicolas
On 21/01/2014 12:54, Prestasit01 wrote:
Hello,
So my 2.5 server has been cloned and updated in 2.6.10
But now i got one issue : http ERROR 503 Problem accessing /rudder. Reason: Service Unavailable
Here is the log :
2014-01-21 12:45:43.215:INFO::Graceful shutdown SelectChannelConnector at 127.0.0.1:8080<mailto:SelectChannelConnector at 127.0.0.1:8080>
2014-01-21 12:45:43.222:INFO::Graceful shutdown o.e.j.w.WebAppContext{/async-rest,file:/opt/rudder/jetty7/webapps/async-rest/<file:///\\%5C%5Copt%5Crudder%5Cjetty7%5Cwebapps%5Casync-rest%5C>},/opt/rudder/jetty7/webapps/async-rest
2014-01-21 12:45:43.222:INFO::Graceful shutdown o.e.j.w.WebAppContext{/endpoint,[file:/tmp/jetty-127.0.0.1-8080-endpoint.war-_endpoint-any-/webinf/<file:///\\%5C%5Ctmp%5Cjetty-127.0.0.1-8080-endpoint.war-_endpoint-any-%5Cwebinf%5C>, jar:file:/opt/rudder/jetty7/webapps/endpoint.war!/<jar:file:/opt/rudder/jetty7/webapps/endpoint.war%21/>]},/opt/rudder/jetty7/webapps/endpoint.war
2014-01-21 12:45:43.222:INFO::Graceful shutdown o.e.j.w.WebAppContext{/cometd,[file:/tmp/jetty-127.0.0.1-8080-cometd.war-_cometd-any-/webinf/<file:///\\%5C%5Ctmp%5Cjetty-127.0.0.1-8080-cometd.war-_cometd-any-%5Cwebinf%5C>, jar:file:/opt/rudder/jetty7/webapps/cometd.war!/<jar:file:/opt/rudder/jetty7/webapps/cometd.war%21/>]},/opt/rudder/jetty7/webapps/cometd.war
2014-01-21 12:45:43.223:INFO::Graceful shutdown o.e.j.w.WebAppContext{/,file:/opt/rudder/jetty7/webapps/root/<file:///\\%5C%5Copt%5Crudder%5Cjetty7%5Cwebapps%5Croot%5C>},/opt/rudder/jetty7/webapps/root
2014-01-21 12:45:43.223:INFO::Graceful shutdown o.e.j.w.WebAppContext{/test-jndi,file:/opt/rudder/jetty7/webapps/test-jndi/<file:///\\%5C%5Copt%5Crudder%5Cjetty7%5Cwebapps%5Ctest-jndi%5C>},/opt/rudder/jetty7/webapps/test-jndi
2014-01-21 12:45:43.223:INFO::Graceful shutdown o.e.j.w.WebAppContext{/test-jaas,file:/opt/rudder/jetty7/webapps/test-jaas/<file:///\\%5C%5Copt%5Crudder%5Cjetty7%5Cwebapps%5Ctest-jaas%5C>},/opt/rudder/jetty7/webapps/test-jaas
2014-01-21 12:45:43.223:INFO::Graceful shutdown o.e.j.s.h.ContextHandler{/javadoc,file:/opt/rudder/jetty7/javadoc/<file:///\\%5C%5Copt%5Crudder%5Cjetty7%5Cjavadoc%5C>}
2014-01-21 12:45:43.223:INFO::Graceful shutdown o.e.j.w.WebAppContext{/test,file:/tmp/jetty-127.0.0.1-8080-test.war-_test-any-/webapp/<file:///\\%5C%5Ctmp%5Cjetty-127.0.0.1-8080-test.war-_test-any-%5Cwebapp%5C>},/opt/rudder/jetty7/webapps/test.war
2014-01-21 12:45:43.223:INFO::Graceful shutdown o.e.j.s.h.ContextHandler{/,file:/opt/rudder/jetty7/root<file:///\\%5C%5Copt%5Crudder%5Cjetty7%5Croot>}
2014-01-21 12:45:43.224:INFO::Graceful shutdown o.e.j.w.WebAppContext{/test-annotations,file:/opt/rudder/jetty7/webapps/test-annotations/<file:///\\%5C%5Copt%5Crudder%5Cjetty7%5Cwebapps%5Ctest-annotations%5C>},/opt/rudder/jetty7/webapps/test-annotations
2014-01-21 12:45:43.224:INFO::Graceful shutdown o.e.j.w.WebAppContext{/rudder,file:/tmp/jetty-127.0.0.1-8080-rudder.war-_rudder-any-/webapp/<file:///\\%5C%5Ctmp%5Cjetty-127.0.0.1-8080-rudder.war-_rudder-any-%5Cwebapp%5C>},/opt/rudder/jetty7/webapps/rudder.war
2014-01-21 12:45:44.308:INFO:endpoint:Destroying Spring FrameworkServlet 'dispatcher'
Have you ever met this migration issue ?
Regards
CJARDIN
De : rudder-users-bounces at lists.rudder-project.org<mailto:rudder-users-bounces at lists.rudder-project.org> [mailto:rudder-users-bounces at lists.rudder-project.org] De la part de Prestasit01
Envoyé : vendredi 17 janvier 2014 16:34
À : 'Nicolas Charles'; rudder-users at lists.rudder-project.org<mailto:rudder-users at lists.rudder-project.org>
Objet : Re: [rudder-users] 2.5 to 2.9 Migration
Hello,
Thanks, i hope it will possible to do that in the future.
For the moment i will proceed like you told ;)
Regards
CJARDIN
De : rudder-users-bounces at lists.rudder-project.org<mailto:rudder-users-bounces at lists.rudder-project.org> [mailto:rudder-users-bounces at lists.rudder-project.org] De la part de Nicolas Charles
Envoyé : vendredi 17 janvier 2014 16:29
À : rudder-users at lists.rudder-project.org<mailto:rudder-users at lists.rudder-project.org>
Objet : Re: [rudder-users] 2.5 to 2.9 Migration
Hello,
This part of the doc refers to a migration to another Rudder server (you have a Rudder Server A, and want to install on another system a Rudder Server B, and export everything from A to B), but they need to be both in the same version.
Copying everything from a 2.5 to a 2.9 will cause invalid configuration of the serveur.
If you really want to test the migration, you'll have to install a new Rudder 2.5, export all data from the existing Rudder server to the new Rudder server, and then upgrade the new Rudder server to 2.9
Regards,
Nicolas
On 17/01/2014 16:24, Prestasit01 wrote:
Hello,
This is the doc used => http://www.rudder-project.org/rudder-doc-2.9/rudder-doc.html
§10.10.2 Handle configuration files
CJARDIN
De : Jonathan Clarke [mailto:jonathan.clarke at normation.com]
Envoyé : vendredi 17 janvier 2014 16:02
À : Prestasit01; rudder-users at lists.rudder-project.org<mailto:rudder-users at lists.rudder-project.org>
Objet : Re: [rudder-users] 2.5 to 2.9 Migration
Hello,
I'm sorry but I don't understand what doc you are referring to. Could you send a link to that doc, so I can try?
Jonathan
On 17/01/14 15:57, Prestasit01 wrote:
Hello,
As told in the doc (10.10.2), i copied the /var/rudder/configuration-repository and i have followed the procedure.
I don't want to upgrade my 2.5 server to 2.9, but i just want to test the migration between a 2.5 and a 2.9.
In previous version it was possible. I hope that someone got one other idea to correct the issue, Maybe there is a bug ?
Thanks
De : Jonathan Clarke [mailto:jonathan.clarke at normation.com]
Envoyé : vendredi 17 janvier 2014 15:50
À : Prestasit01; rudder-users at lists.rudder-project.org<mailto:rudder-users at lists.rudder-project.org>
Objet : Re: [rudder-users] 2.5 to 2.9 Migration
Hi,
I don't understand - which folder have you copied from the 2.5 server to the 2.9?
This is not the suggested way to upgrade a Rudder server. All our packages are designed for simple upgrade, so you can simply change the yum/apt repoistory and run "aptitude/yum install rudder-server-root" to upgrade. All data migrations are handled automatically. This is explained in http://www.rudder-project.org/rudder-doc-2.9/rudder-doc.html#_upgrade_rudder.
If you want to test this migration, rather than running it directly on your production server (which makes sense :) ), then you have two options:
1) If your server is a VM, the simplest is to clone it, and run the upgrade on the clone.
2) If you can't clone your server, then it will be harder to really test this upgrade. One option would be to reinstall a Rudder 2.5.4 version, then import your data (copy of /var/rudder/configuration-management, then git commit, then restore archive, then run yum/aptitude install rudder-server-root to upgrade to 2.9.2).
I hope this helps you.
Jonathan
On 17/01/14 15:37, Prestasit01 wrote:
In complement : exact versions are =>
- rudder-server-root-2.9.2.release-1.EL.6
- rudder-server-root-2.5.4.release-1.EL.6
De : rudder-users-bounces at lists.rudder-project.org<mailto:rudder-users-bounces at lists.rudder-project.org> [mailto:rudder-users-bounces at lists.rudder-project.org] De la part de Prestasit01
Envoyé : vendredi 17 janvier 2014 15:30
À : rudder-users at lists.rudder-project.org<mailto:rudder-users at lists.rudder-project.org>
Objet : [rudder-users] 2.5 to 2.9 Migration
Hello,
Our rudder-server-root version is 2.5 and we would like to test the migration to a 2.9 version.
I have created a new server in 2.9, then this folder /var/rudder/configuration-repository has been copied from the 2.5 server to the 2.9.
I have reloaded the technique library & restored the global archive with « latest git commit » but nothing appear after the deployement.
Have you got an idea ?
Thanks
CJARDIN
-------------------------------------------------------------------------
Les informations ou pieces jointes contenues dans ce message sont confidentielles. Seul le destinataire expressement vise peut en prendre connaissance. Toute autre personne qui en divulguera, diffusera ou prendra des copies sera passible de poursuites. La societe Ouest-France decline en outre, toute responsabilite de quelque nature que ce soit au titre de ce message s'il a ete altere, deforme ou falsifie.
-------------------------------------------------------------------------
Les informations ou pieces jointes contenues dans ce message sont confidentielles. Seul le destinataire expressement vise peut en prendre connaissance. Toute autre personne qui en divulguera, diffusera ou prendra des copies sera passible de poursuites. La societe Ouest-France decline en outre, toute responsabilite de quelque nature que ce soit au titre de ce message s'il a ete altere, deforme ou falsifie.
_______________________________________________
rudder-users mailing list
rudder-users at lists.rudder-project.org<mailto:rudder-users at lists.rudder-project.org>
http://www.rudder-project.org/mailman/listinfo/rudder-users
-------------------------------------------------------------------------
Les informations ou pieces jointes contenues dans ce message sont confidentielles. Seul le destinataire expressement vise peut en prendre connaissance. Toute autre personne qui en divulguera, diffusera ou prendra des copies sera passible de poursuites. La societe Ouest-France decline en outre, toute responsabilite de quelque nature que ce soit au titre de ce message s'il a ete altere, deforme ou falsifie.
-------------------------------------------------------------------------
Les informations ou pieces jointes contenues dans ce message sont confidentielles. Seul le destinataire expressement vise peut en prendre connaissance. Toute autre personne qui en divulguera, diffusera ou prendra des copies sera passible de poursuites. La societe Ouest-France decline en outre, toute responsabilite de quelque nature que ce soit au titre de ce message s'il a ete altere, deforme ou falsifie.
_______________________________________________
rudder-users mailing list
rudder-users at lists.rudder-project.org<mailto:rudder-users at lists.rudder-project.org>
http://www.rudder-project.org/mailman/listinfo/rudder-users
--
Nicolas CHARLES
-------------------------------------------------------------------------
Les informations ou pieces jointes contenues dans ce message sont confidentielles. Seul le destinataire expressement vise peut en prendre connaissance. Toute autre personne qui en divulguera, diffusera ou prendra des copies sera passible de poursuites. La societe Ouest-France decline en outre, toute responsabilite de quelque nature que ce soit au titre de ce message s'il a ete altere, deforme ou falsifie.
-------------------------------------------------------------------------
Les informations ou pieces jointes contenues dans ce message sont confidentielles. Seul le destinataire expressement vise peut en prendre connaissance. Toute autre personne qui en divulguera, diffusera ou prendra des copies sera passible de poursuites. La societe Ouest-France decline en outre, toute responsabilite de quelque nature que ce soit au titre de ce message s'il a ete altere, deforme ou falsifie.
--
Nicolas CHARLES
-------------------------------------------------------------------------
Les informations ou pieces jointes contenues dans ce message sont confidentielles. Seul le destinataire expressement vise peut en prendre connaissance. Toute autre personne qui en divulguera, diffusera ou prendra des copies sera passible de poursuites. La societe Ouest-France decline en outre, toute responsabilite de quelque nature que ce soit au titre de ce message s'il a ete altere, deforme ou falsifie.
_______________________________________________
rudder-users mailing list
rudder-users at lists.rudder-project.org<mailto:rudder-users at lists.rudder-project.org>
http://www.rudder-project.org/mailman/listinfo/rudder-users
-------------------------------------------------------------------------<br>
Les informations ou pieces jointes contenues dans ce message sont
confidentielles. Seul le destinataire expressement vise peut en prendre
connaissance. Toute autre personne qui en divulguera, diffusera ou prendra des copies sera passible de poursuites. La societe Ouest-France decline en outre, toute responsabilite de quelque nature que ce soit au titre de ce message s'il a ete altere, deforme ou falsifie.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rudder-project.org/pipermail/rudder-users/attachments/20140123/fc2381a6/attachment-0001.html>
More information about the rudder-users
mailing list