Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Peter Dimitri
Staging: What happens behind the scenes?
April 24, 2013 1:29 AM
Answer

Peter Dimitri

Rank: Junior Member

Posts: 36

Join Date: January 9, 2013

Recent Posts

I'm trying to track down some problems with staging in a customers Liferay Installation. I see that the *.lar files appear on the live servers /temp folder, but anyway new content, which was created since the last publishing process, won't be created on the live server. I guess, the *.lar files only contain configuration information about the staged pages and the portlets on these pages, as well as the theme(s) used on the pages. But how is the web-content transfered between stage und live server? How can I find out why the new content won't be published to the live server?

When the user publishes some changes to the live system, there is a success message in his browser, and there are nor exceptions or errors in the Liferay logs. But as said above, no content will be created on the live server.

Is there any technical information available about how staging really works behind the scenes?
Anonymous
RE: Staging: What happens behind the scenes?
April 24, 2013 6:17 PM
Answer

Anonymous

The .lar files should contain everything including configurations and web content. Without a stacktrace it is a little hard to determine (at least for me) why exactly it is not publishing but it could be configuration. One test to do is export the site as a .lar and import it on the Live server and see if that works, make sure you checked everything to be exported with the .lar file.
Peter Dimitri
RE: Staging: What happens behind the scenes?
April 29, 2013 5:47 AM
Answer

Peter Dimitri

Rank: Junior Member

Posts: 36

Join Date: January 9, 2013

Recent Posts

The problem is in this case, that the customer prepared literally thousands of web-content articles in the staging system before activating staging to the live site. So an export, as you propose, would be huge and the import on the live system will kill the server. Therefore I suggested to simply "clone" the staging server into production, by using a database dump, a copy of the staging servers document-library and also deploy all plugings from the staging server into the production system. After startup the "cloned" server looks exactly as the staging server, has all users configured as in the staging server, and of course the staging configuration in the staging server was adjusted to address the "cloned" server as the live server.

I don't think there is a configuration issue, because the *.lar files show up on the live server while publishing changes from the staging server, and they are processed by the live server.

The most strange thing I notice in the logs, both on the stagings server and also on the live server, is that there are hundreds and thousands of lines like these:

 1
 211:57:37,568 WARN  [http-bio-8080-exec-18][RepositoryEntryPersistenceImpl:545] No RepositoryEntry exists with the primary key 41308
 311:57:37,570 WARN  [http-bio-8080-exec-18][RepositoryEntryPersistenceImpl:545] No RepositoryEntry exists with the primary key 41308
 411:57:37,574 WARN  [http-bio-8080-exec-18][RepositoryPersistenceImpl:493] No Repository exists with the primary key 10180
 511:57:37,577 WARN  [http-bio-8080-exec-18][RepositoryPersistenceImpl:493] No Repository exists with the primary key 10180
 611:57:40,440 WARN  [http-bio-8080-exec-18][RepositoryPersistenceImpl:493] No Repository exists with the primary key 10180
 711:57:40,443 WARN  [http-bio-8080-exec-18][RepositoryPersistenceImpl:493] No Repository exists with the primary key 10180
 8....
 9....
1014:44:20,360 WARN  [http-bio-8080-exec-35][GroupPersistenceImpl:2177] No Group exists with the key {companyId=10154, classNameId=10002, classPK=12036}
1114:44:20,361 WARN  [http-bio-8080-exec-35][GroupPersistenceImpl:2177] No Group exists with the key {companyId=10154, classNameId=10002, classPK=12036}
1214:44:20,362 WARN  [http-bio-8080-exec-35][GroupPersistenceImpl:2177] No Group exists with the key {companyId=10154, classNameId=10002, classPK=12036}
1314:44:20,453 WARN  [http-bio-8080-exec-35][GroupPersistenceImpl:830] No Group exists with the primary key 0
1414:44:20,578 WARN  [http-bio-8080-exec-35][PortletPreferencesPersistenceImpl:2414] No PortletPreferences exists with the key {ownerId=10180, ownerType=2, plid=0, portletId=178}
1514:44:20,580 WARN  [http-bio-8080-exec-35][PortletPreferencesPersistenceImpl:2414] No PortletPreferences exists with the key {ownerId=10154, ownerType=1, plid=0, portletId=178}
1614:44:20,583 WARN  [http-bio-8080-exec-35][GroupPersistenceImpl:830] No Group exists with the primary key 0
1714:44:20,636 WARN  [http-bio-8080-exec-35][PortletPreferencesPersistenceImpl:2414] No PortletPreferences exists with the key {ownerId=0, ownerType=3, plid=12036, portletId=8}
1814:44:20,638 WARN  [http-bio-8080-exec-35][PortletPreferencesPersistenceImpl:2414] No PortletPreferences exists with the key {ownerId=10154, ownerType=1, plid=0, portletId=8}
1914:44:20,641 WARN  [http-bio-8080-exec-35][GroupPersistenceImpl:830] No Group exists with the primary key 0
2014:44:20,651 WARN  [http-bio-8080-exec-35][PortletPreferencesPersistenceImpl:2414] No PortletPreferences exists with the key {ownerId=10180, ownerType=2, plid=0, portletId=56}
2114:44:20,655 WARN  [http-bio-8080-exec-35][PortletPreferencesPersistenceImpl:2414] No PortletPreferences exists with the key {ownerId=10154, ownerType=1, plid=0, portletId=56}
2214:44:20,658 WARN  [http-bio-8080-exec-35][GroupPersistenceImpl:830] No Group exists with the primary key 0
2314:44:20,807 WARN  [http-bio-8080-exec-35][UserPersistenceImpl:965] No User exists with the primary key 10915
2414:44:21,080 WARN  [http-bio-8080-exec-35][PortletPreferencesPersistenceImpl:2414] No PortletPreferences exists with the key {ownerId=10154, ownerType=1, plid=0, portletId=20}
2514:44:21,082 WARN  [http-bio-8080-exec-35][GroupPersistenceImpl:830] No Group exists with the primary key 0
2614:44:24,366 WARN  [http-bio-8080-exec-35][UserPersistenceImpl:965] No User exists with the primary key 10915
2714:44:25,565 WARN  [http-bio-8080-exec-35][UserPersistenceImpl:965] No User exists with the primary key 10915
2814:44:25,979 WARN  [http-bio-8080-exec-35][UserPersistenceImpl:965] No User exists with the primary key 10915
2914:44:26,457 WARN  [http-bio-8080-exec-35][UserPersistenceImpl:965] No User exists with the primary key 10915
3014:44:26,727 WARN  [http-bio-8080-exec-35][UserPersistenceImpl:965] No User exists with the primary key 10915
3114:44:27,386 WARN  [http-bio-8080-exec-35][UserPersistenceImpl:965] No User exists with the primary key 10915
3214:44:27,657 WARN  [http-bio-8080-exec-35][UserPersistenceImpl:965] No User exists with the primary key 10915
3314:44:28,098 WARN  [http-bio-8080-exec-35][UserPersistenceImpl:965] No User exists with the primary key 10915
3414:44:28,370 WARN  [http-bio-8080-exec-35][UserPersistenceImpl:965] No User exists with the primary key 10915


I tried to force such errors in a test system I've set up (both staging server and live server), by letting users create pages and content, and then change their userId's and groupId's in the database, messing up the document-library by renaming the folders, but I can't reproduce these kinds of errors (but of course a lot of expeption of any kind).

What could have happened with this staging server so that I get these warnings in my logs. As said before: Same log output while exporting from staging server and importing to live server.