Vista combinada Visión Plana Vista de árbol
Discusiones [ Anterior | Siguiente ]
toggle
Problems with sign in on move to bigger server Hamish Campbell 8 de septiembre de 2012 15:10
RE: Problems with sign in on move to bigger server Juan Gonzalez 8 de septiembre de 2012 16:04
RE: Sign in form (Was: Problems with sign in on move to bigger server) Philip Coates 10 de septiembre de 2012 4:38
RE: Problems with sign in on move to bigger server Richard Hering 10 de septiembre de 2012 4:34
RE: Problems with sign in on move to bigger server Linus Sphinx 10 de septiembre de 2012 14:27
RE: Problems with sign in on move to bigger server Philip Coates 10 de septiembre de 2012 16:02
RE: Problems with sign in on move to bigger server Hamish Campbell 13 de septiembre de 2012 11:45
RE: Problems with sign in on move to bigger server Luis Mas 11 de septiembre de 2012 9:10
RE: Problems with sign in on move to bigger server Philip Coates 11 de septiembre de 2012 9:20
RE: Problems with sign in on move to bigger server Luis Mas 13 de septiembre de 2012 13:33
RE: Problems with sign in on move to bigger server Hamish Campbell 13 de septiembre de 2012 13:56
RE: Problems with sign in on move to bigger server Hamish Campbell 13 de septiembre de 2012 10:42
RE: Sign in form (Was: Problems with sign in on move to bigger server) Philip Coates 14 de septiembre de 2012 0:00
RE: Sign in form (Was: Problems with sign in on move to bigger server) Juan Gonzalez 14 de septiembre de 2012 0:09
RE: Sign in form (Was: Problems with sign in on move to bigger server) Philip Coates 14 de septiembre de 2012 0:19
RE: Sign in form (Was: Problems with sign in on move to bigger server) Juan Gonzalez 14 de septiembre de 2012 2:06
RE: Sign in form (Was: Problems with sign in on move to bigger server) Philip Coates 14 de septiembre de 2012 2:31
RE: Sign in form (Was: Problems with sign in on move to bigger server) Philip Coates 14 de septiembre de 2012 9:08
RE: Sign in form (Was: Problems with sign in on move to bigger server) Hitoshi Ozawa 15 de septiembre de 2012 19:51
RE: Sign in form (Was: Problems with sign in on move to bigger server) Sampsa Sohlman 17 de septiembre de 2012 12:58
RE: Sign in form (Was: Problems with sign in on move to bigger server) Philip Coates 18 de septiembre de 2012 5:14
RE: Sign in form (Was: Problems with sign in on move to bigger server) Sampsa Sohlman 17 de septiembre de 2012 6:15
RE: Sign in form (Was: Problems with sign in on move to bigger server) Philip Coates 18 de septiembre de 2012 3:51
RE: Sign in form (Was: Problems with sign in on move to bigger server) Sampsa Sohlman 21 de septiembre de 2012 8:49
RE: Sign in form (Was: Problems with sign in on move to bigger server) Philip Coates 24 de septiembre de 2012 16:03
RE: Sign in form (Was: Problems with sign in on move to bigger server) Henry K 17 de septiembre de 2012 13:33
RE: Sign in form (Was: Problems with sign in on move to bigger server) Vitor Silva 18 de septiembre de 2012 3:54
RE: Sign in form (Was: Problems with sign in on move to bigger server) Philip Coates 18 de septiembre de 2012 5:34
RE: Sign in form (Was: Problems with sign in on move to bigger server) Vitor Silva 18 de septiembre de 2012 6:59
RE: Sign in form (Was: Problems with sign in on move to bigger server) Philip Coates 18 de septiembre de 2012 9:34
RE: Sign in form (Was: Problems with sign in on move to bigger server) Philip Coates 18 de septiembre de 2012 7:26
Hamish Campbell
Problems with sign in on move to bigger server
8 de septiembre de 2012 15:10
Respuesta

Hamish Campbell

Ranking: Junior Member

Mensajes: 87

Fecha de incorporación: 20 de agosto de 2008

Mensajes recientes

We have been running our Lifray install for 3 years on a OVH VPS server based in France with 3 cores and 3GB ram and limited hardrive space. Over the time we had a lot of memory problems, and recently we have completely run outa hardrive space so it was time to bite the bullet and spend some more very limited cash. We splashed out on a dedicated OVH server with 4 cores and 16GB of ram and 1TB of hardrive. A day down to move over and re-configure we get it up and running. Every thing works but we cant login, just comes up with a empty page when you click the sign in.

Help needed, to see the problem http://visionon.tv and click on sign in.
Juan Gonzalez
RE: Problems with sign in on move to bigger server
8 de septiembre de 2012 16:04
Respuesta

Juan Gonzalez

LIFERAY STAFF

Ranking: Liferay Legend

Mensajes: 1937

Fecha de incorporación: 28 de octubre de 2008

Mensajes recientes

Any error on logs?

I've seen this errors from browser when hitting the main page:

Uncaught ReferenceError: jwplayer is not defined
Unsafe JavaScript attempt to access frame with URL http://visionon.tv/home from frame with URL http://www.youtube.com/embed/videoseries?list=PL1C0E176BE35948FA&hl=en_GB. Domains, protocols and ports must match.
home:1GET http://sponsume-beta.ndpclient.com/sites/all/themes/sponsume/images/template/project-backs-widget-bk.png 404 (Not Found)
home:1GET http://sponsume-beta.ndpclient.com/sites/all/themes/sponsume/images/template/project-backs-widget.png 404 (Not Found)
home:1GET http://sponsume-beta.ndpclient.com/sites/all/themes/sponsume/images/template/no-thumbnail.png 404 (Not Found)
home:1GET http://sponsume-beta.ndpclient.com/sites/all/themes/sponsume/images/icons/loc-small.png 404 (Not Found)
home:1GET http://sponsume-beta.ndpclient.com/sites/all/themes/sponsume/images/template/progress-mask-small.png 404 (Not Found)
Philip Coates
RE: Sign in form (Was: Problems with sign in on move to bigger server)
10 de septiembre de 2012 4:38
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

Hi,

These are all purely client-side and don't seem to affect other functionality (we'll get round to resolving these soon, as they're mostly resource issues); we get nothing in the console for the sign in page.

We don't see anything specific in the Tomcat logs when we hit the sign in page, although we do occasionally get things like:

 108:48:22,992 ERROR [ajp-bio-8009-exec-4][IncludeTag:253] Current URL /home;jsessionid=9A8137A512C61F1ABF3E7B25246C9B08 generates exception: com.liferay.portal.security.auth.PrincipalException
 208:48:22,994 ERROR [ajp-bio-8009-exec-4][IncludeTag:154] com.liferay.portal.security.auth.PrincipalException
 3    at com.liferay.portlet.asset.service.permission.AssetEntryPermission.check(AssetEntryPermission.java:57)
 4    at com.liferay.portlet.asset.service.impl.AssetEntryServiceImpl.incrementViewCounter(AssetEntryServiceImpl.java:130)
 5    at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:122)
 6    at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:71)
 7    at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
 8    at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
 9    at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
10    at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
11    at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
12    at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
13    at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
14    at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
15    at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
16    at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:211)
17    at com.liferay.portlet.asset.service.AssetEntryServiceUtil.incrementViewCounter(AssetEntryServiceUtil.java:94)
18    at org.apache.jsp.html.portlet.asset_005fpublisher.display.full_005fcontent_jsp._jspService(full_005fcontent_jsp.java:1258)
19    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
20    at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
21    at com.liferay.portal.servlet.DirectRequestDispatcher.include(DirectRequestDispatcher.java:97)
22    at com.liferay.portal.servlet.PACLRequestDispatcherWrapper.doDispatch(PACLRequestDispatcherWrapper.java:90)


As well as the odd null pointer that we'd been seeing on the old server since upgrading and losing our old themes.

Tomcat access log for the page shows:

12.30.155.8 - - [09/Sep/2012:09:02:35 +0000] "GET /home?p_p_id=58&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&saveLastPath=0&_58_struts_action=%2Flogin%2Flogin HTTP/1.1" 200 4646
22.30.155.8 - - [09/Sep/2012:09:02:40 +0000] "GET /c/portal/login?p_l_id=494076 HTTP/1.1" 302 -
32.30.155.8 - - [09/Sep/2012:09:02:41 +0000] "GET /home?p_p_id=58&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&saveLastPath=0&_58_struts_action=%2Flogin%2Flogin HTTP/1.1" 304 -

What we did in this case was to mysqldump the database from one system and recreate it on the new, copy over the webapps and other liferay directories (data, etc.) and then start things up. Everything came back except the issue here (unless there are other things we haven't found yet because they're masked by this).

We didn't have similar issues before when upgrading, which also involved moving chunks of the pre-existing stuff around.

There are two key differences to our old server:

1) Rather than running the server from /opt/liferay, it now lives in the /home partition, with symlinks recreating the previous structure. Inside the liferay directories, the structure is unchanged.

2) We're now running through mod_jk rather than raw Tomcat. The issue seems to be there whether we connect at 80 or 8080, so I don't think this has anything to do with the issue.

Interestingly, we no longer seem to see the /web/guest bit any more, though we haven't changed any settings around this.

Does any of this suggest anything?

Many thanks,

Phil.
Richard Hering
RE: Problems with sign in on move to bigger server
10 de septiembre de 2012 4:34
Respuesta

Richard Hering

Ranking: New Member

Mensajes: 2

Fecha de incorporación: 9 de abril de 2012

Mensajes recientes

Has anyone else had this problem with the disappearing sign-in after migration to new server?

Many thanks for any help.

Richard - visionOntv
Linus Sphinx
RE: Problems with sign in on move to bigger server
10 de septiembre de 2012 14:27
Respuesta

Linus Sphinx

Ranking: Junior Member

Mensajes: 84

Fecha de incorporación: 12 de agosto de 2010

Mensajes recientes

Sounds a bit familiar. Stupid question I have to ask; Did you delete all your client browser's session cache and cookies?
Philip Coates
RE: Problems with sign in on move to bigger server
10 de septiembre de 2012 16:02
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

Hi Linus,

Sadly we already tried that - I did wonder whether switching to a different domain might be the cause, but a completely cleared browser (cache, cookies, etc.) does nothing,

Thanks,

Phil.
Hamish Campbell
RE: Problems with sign in on move to bigger server
13 de septiembre de 2012 11:45
Respuesta

Hamish Campbell

Ranking: Junior Member

Mensajes: 87

Fecha de incorporación: 20 de agosto de 2008

Mensajes recientes

We had to revert back to our old (very creaky) server till we can fix this.

The new server is still running here (with out a domain so some images etc don't work) ns211304.ovh.net

Anyone has any ideas why the login options don't come up? permission's on the server?

Hamish
Luis Mas
RE: Problems with sign in on move to bigger server
11 de septiembre de 2012 9:10
Respuesta

Luis Mas

Ranking: Regular Member

Mensajes: 146

Fecha de incorporación: 18 de mayo de 2009

Mensajes recientes

Could attach any log?

Luis
Philip Coates
RE: Problems with sign in on move to bigger server
11 de septiembre de 2012 9:20
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

Hi Luis,

There doesn't seem to be any log output from catalina.out .

The access logs (localhost_access_log) has:

New server:

1111.111.111.111 - - [11/Sep/2012:16:13:05 +0000] "GET /c/portal/login?p_l_id=494076 HTTP/1.1" 302 -
2111.111.111.111 - - [11/Sep/2012:16:13:05 +0000] "GET /web/guest/home?p_p_id=58&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&saveLastPath=0&_58_struts_action=%2Flogin%2Flogin HTTP/1.1" 200 4731


Old server:

1111.111.111.111 - - [11/Sep/2012:16:16:58 +0000] "GET /c/portal/login?p_l_id=494076 HTTP/1.1" 302 -
2111.111.111.111 - - [11/Sep/2012:16:16:58 +0000] "GET /home?p_p_id=58&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&saveLastPath=0&_58_struts_action=%2Flogin%2Flogin HTTP/1.1" 200 5845


They're pretty much the same.

Thanks,

Phil.
Hamish Campbell
RE: Problems with sign in on move to bigger server
13 de septiembre de 2012 10:42
Respuesta

Hamish Campbell

Ranking: Junior Member

Mensajes: 87

Fecha de incorporación: 20 de agosto de 2008

Mensajes recientes

OK Phil is moving things around on the new server to see if that has any effect. Why would everything work, but the login portal appear blank? what are we missing?
Luis Mas
RE: Problems with sign in on move to bigger server
13 de septiembre de 2012 13:33
Respuesta

Luis Mas

Ranking: Regular Member

Mensajes: 146

Fecha de incorporación: 18 de mayo de 2009

Mensajes recientes

Have you test it with default theme?
Hamish Campbell
RE: Problems with sign in on move to bigger server
13 de septiembre de 2012 13:56
Respuesta

Hamish Campbell

Ranking: Junior Member

Mensajes: 87

Fecha de incorporación: 20 de agosto de 2008

Mensajes recientes

Just went to have a look, with out logging in the is no page with a completely default theme, they are mostly the default theme with some CSS hacking in the root page in the CMS. But exactly the same theme set-up is running on our old server and the login works? Phil can you explain the difference between the server configs?
Philip Coates
RE: Sign in form (Was: Problems with sign in on move to bigger server)
14 de septiembre de 2012 0:00
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

I copied the server files to be in exactly the same place as they were on our old server (rather than using symlinks) to see if that made any difference for any reason.

It didn't; we still see the same problem, that the sign-in page shows no form.

However I did see a bunch of stuff in the Tomcat logs:

 106:54:19,790 ERROR [http-bio-8080-exec-6][IncludeTag:253] Current URL /web/guest/home?p_p_id=58&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&saveLastPath=0&_58_struts_action=%2Flogin%2Flogin generates exception: java.lang.StackOverflowError
 206:54:19,800 ERROR [http-bio-8080-exec-6][IncludeTag:154] java.lang.StackOverflowError
 3    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
 4    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
 5    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
 6    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
 7    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
 8    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
 9    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
10    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
11    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
12    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
13    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
14    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
15    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
16    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
17    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
18    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
19    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
20    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
21    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
22    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)


Could a hidden StackOverflow be the cause? Why would we suddenly start seeing this?

Thanks,

Phil.
Juan Gonzalez
RE: Sign in form (Was: Problems with sign in on move to bigger server)
14 de septiembre de 2012 0:09
Respuesta

Juan Gonzalez

LIFERAY STAFF

Ranking: Liferay Legend

Mensajes: 1937

Fecha de incorporación: 28 de octubre de 2008

Mensajes recientes

Oh man! That error sounds me a lot.

Did you change JDK recently? Is JDK of new server different from old one?
Philip Coates
RE: Sign in form (Was: Problems with sign in on move to bigger server)
14 de septiembre de 2012 0:19
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

Hi Juan,

When we initially set the new server up, it was running a version of OpenJDK 1.7.

One of the first things we tried was moving to a Sun/Oracle JVM. We currently have

1java -version
2java version "1.7.0_07"
3Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
4Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)


1javac -version
2javac 1.7.0_04


Our old server has:

1java -version
2java version "1.6.0_22"
3Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
4Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)

1javac -version
2javac 1.6.0_18


Could this be a factor? Is it worth us dropping down to Java 1.6? I know this shouldn't make that much difference, but it could be a factor.

Thanks,

Phil.
Juan Gonzalez
RE: Sign in form (Was: Problems with sign in on move to bigger server)
14 de septiembre de 2012 2:06
Respuesta

Juan Gonzalez

LIFERAY STAFF

Ranking: Liferay Legend

Mensajes: 1937

Fecha de incorporación: 28 de octubre de 2008

Mensajes recientes

Yep, I remember there are (not sure if it's solved) some known problems using JDK 1.7. Can you test using JDK 1.6._21 or newer? (there are other problems using 6.1 in JDK < 1.6.0.13)
Philip Coates
RE: Sign in form (Was: Problems with sign in on move to bigger server)
14 de septiembre de 2012 2:31
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

Hi Juan,

I'll give that a bash and let you know,

Many thanks for the suggestions!

Phil.
Philip Coates
RE: Sign in form (Was: Problems with sign in on move to bigger server)
14 de septiembre de 2012 9:08
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

Gah! Looks like we spoke too soon.

We're still getting the StackOverflow after changing Java:

1echo `$JAVA_HOME/bin/java -version`
2java version "1.6.0_35"
3Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
4Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)


Back to the drawing board...
Hitoshi Ozawa
RE: Sign in form (Was: Problems with sign in on move to bigger server)
15 de septiembre de 2012 19:51
Respuesta

Hitoshi Ozawa

Ranking: Liferay Legend

Mensajes: 7990

Fecha de incorporación: 23 de marzo de 2010

Mensajes recientes

First, liferay doesn't properly work with OpenJDK and with jjk 1.7 but you seem to have fixed that. Did you clear app server cache, temp, and work after that?

Second, which liferay version are you using and what's your JAVA_OPT settings? Did you increase memory values?
Sampsa Sohlman
RE: Sign in form (Was: Problems with sign in on move to bigger server)
17 de septiembre de 2012 6:15
Respuesta

Sampsa Sohlman

LIFERAY STAFF

Ranking: Regular Member

Mensajes: 218

Fecha de incorporación: 27 de septiembre de 2007

Mensajes recientes

Philip Coates:
Gah! Looks like we spoke too soon.

We're still getting the StackOverflow after changing Java:

1echo `$JAVA_HOME/bin/java -version`
2java version "1.6.0_35"
3Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
4Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)


Back to the drawing board...


Stupid question. Have you removed the work and temp files every time when you have restarted your server?
Sampsa Sohlman
RE: Sign in form (Was: Problems with sign in on move to bigger server)
17 de septiembre de 2012 12:58
Respuesta

Sampsa Sohlman

LIFERAY STAFF

Ranking: Regular Member

Mensajes: 218

Fecha de incorporación: 27 de septiembre de 2007

Mensajes recientes

Hitoshi Ozawa:
Second, which liferay version are you using and what's your JAVA_OPT settings? Did you increase memory values?


I did look http headers, version is 6.1.1 GA2

1(Status-Line)    HTTP/1.1 304 Not Modified
2Server    Apache-Coyote/1.1
3Content-Encoding    gzip
4Liferay-Portal    Liferay Portal Community Edition 6.1.1 CE GA2 (Paton / Build 6101 / July 31, 2012)
5Etag    "d3ae41b1"
6Date    Mon, 17 Sep 2012 19:42:08 GMT



Philip Coates:
 106:54:19,790 ERROR [http-bio-8080-exec-6][IncludeTag:253] Current URL /web/guest/home?p_p_id=58&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&saveLastPath=0&_58_struts_action=%2Flogin%2Flogin generates exception: java.lang.StackOverflowError
 206:54:19,800 ERROR [http-bio-8080-exec-6][IncludeTag:154] java.lang.StackOverflowError
 3    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
 4    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
 5    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
 6    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
 7    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
 8    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
 9    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
10    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
11    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
12    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
13    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
14    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
15    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
16    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
17    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
18    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
19    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
20    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)
21    at com.liferay.portal.kernel.io.unsync.UnsyncPrintWriter.write(UnsyncPrintWriter.java:385)
22    at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:325)



Actually more stacktrace would be intresting to know, since it seems that UnsyncPrintWriter itself all the time through JspWriterImpl. By looking only that part of the code situation is strange.
Henry K
RE: Sign in form (Was: Problems with sign in on move to bigger server)
17 de septiembre de 2012 13:33
Respuesta

Henry K

Ranking: Junior Member

Mensajes: 40

Fecha de incorporación: 27 de enero de 2010

Mensajes recientes

Hi--

What does your mod_jk setup look like? I had some issues with Apache setup; this may be another one. Does the server work without the apache front end?

Another thing I think of is auth.token.check.enabled=true/false . Right now I don't see an auth token in the url, so I'm guessing this property is set to false. But this might be another thing to check.

--Henry
Philip Coates
RE: Sign in form (Was: Problems with sign in on move to bigger server)
18 de septiembre de 2012 3:51
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

I wondered about this, but I got the same thing happening with a completely fresh install of Liferay too (after I'd changed the JDK/JRE versions)

The config is identical to the config I had on the other server where everything was working.

The transfer process used:

1) tarball the liferay instance (with empty temp, logs and work directories)
2) sftp it over to the new machine
3) extracted it
4) took a dump of the database
5) sftp db dump to new machine
6) restore db dump in database on new machine
7) start up Tomcat/Liferay on the new machine

Everything appeared to be fine until we checked sign in and found no form was showing.

I tried again by dumping our portal-ext.properties and liferay-portlet.xml into a fresh Liferay install (pointing at the same db and looking at the same Liferay data directory) and I get exactly the same problem.

We're just really unsure of how to proceed now, so any suggestions gratefully received, even if they seem to be obvious things!

Thanks,

Phil.
Vitor Silva
RE: Sign in form (Was: Problems with sign in on move to bigger server)
18 de septiembre de 2012 3:54
Respuesta

Vitor Silva

LIFERAY STAFF

Ranking: Junior Member

Mensajes: 36

Fecha de incorporación: 3 de mayo de 2012

Mensajes recientes

Hi there,
When migrating from server to server please be careful with the folder structure (if the liferay home changes), you can also delete all the temp files. If you have parts of the system in the filesystem (documentlibrary, indexation) make sure you copy these files.
So please attach the portal-ext.properties, if you have the portal-setup-wizard attach these as well so we can have a look.
Also if you have hooks and ext plugins try to start a vanilla installation see if it works and then install the plugins.
You can also unzip a new bundle and start it and test it, add the properties file and data folder, restart and test, step by step
I will also ask for you to post the catalina log after you start the portal so I can see the startup log.
Philip Coates
RE: Sign in form (Was: Problems with sign in on move to bigger server)
18 de septiembre de 2012 5:14
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

We're running 6.1.1-GA2 CE

JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=UTF8 -Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false -Duser.timezone=GMT -Xmx1024m -XX:MaxPermSize=256m"

I've cleared all caches, but this is behaviour we're seeing from initial startup.

Thanks,

Phil.
Philip Coates
RE: Sign in form (Was: Problems with sign in on move to bigger server)
18 de septiembre de 2012 5:34
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

Hi Vitor,

Folder structure has remained the same internally, based on the Tomcat CE bundle.

Apart from the various email and recaptcha parts, here's our (slightly sanitised) portal-ext.properties:

 1index.on.startup=false
 2
 3setup.wizard.enabled=false
 4
 5jdbc.default.driverClassName=com.mysql.jdbc.Driver
 6jdbc.default.url=jdbc:mysql://localhost/lportal?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
 7jdbc.default.username=lportal
 8jdbc.default.password=<password>
 9
10live.users.enabled=true
11buddy.list.strategy=all
12
13session.timeout=240
14auth.forward.by.last.path=true
15default.landing.page.path=/w


Our catalina.out files get rather large, filled with a lot of information about missing themes.

I'm about to try again with as clean an instance as I can, so I'll give you the head output from Tomcat up to server startup and any messages I get when I do this,

Thanks,

Phil.
Vitor Silva
RE: Sign in form (Was: Problems with sign in on move to bigger server)
18 de septiembre de 2012 6:59
Respuesta

Vitor Silva

LIFERAY STAFF

Ranking: Junior Member

Mensajes: 36

Fecha de incorporación: 3 de mayo de 2012

Mensajes recientes

Hi,
in the control panel, did you change the friendly url under site settings?
also, can you post your modified liferay-portlet.xml?
Philip Coates
RE: Sign in form (Was: Problems with sign in on move to bigger server)
18 de septiembre de 2012 7:26
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

Hi Henry,

I wondered about this too, but I have exactly the same results running raw on Tomcat with Apache stopped.

Where do we set "auth.token.check.enabled"? portal-ext.properties? If so, it wasn't changed from the default on the old server.

Thanks,

Phil.
Philip Coates
RE: Sign in form (Was: Problems with sign in on move to bigger server)
18 de septiembre de 2012 9:34
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

Hi Vitor,

In the control panel on our old server, the friendly URL is set to "/guest" - is this the default? We can't access the control panel on the new server, so if we need to change anything it will have to be done in one of the config files or directly through the db.

My latest attempt was:

1) Drop clean install (i.e. all defaults) onto the new server
2) Drop in our portlet-ext.properties (kept default liferay-portlet.xml)
3) Replace the html directory with the one from our old server
4) Start up...

Still didn't work, which is quite puzzling.

The catalina.out is attached - looks nice and normal (apart from the missing themes).

Thanks,

Phil.
archivos adjuntos: catalina.out (9,2k)
Sampsa Sohlman
RE: Sign in form (Was: Problems with sign in on move to bigger server)
21 de septiembre de 2012 8:49
Respuesta

Sampsa Sohlman

LIFERAY STAFF

Ranking: Regular Member

Mensajes: 218

Fecha de incorporación: 27 de septiembre de 2007

Mensajes recientes

Philip Coates:
We're just really unsure of how to proceed now, so any suggestions gratefully received, even if they seem to be obvious things!


We do not have access to your system and at least I do not want to have ;)

This has to be solved, step by step .. so.

Does the basic Tomcat bundle installation with HSQL db work?

As I undrerstand following does not work:

By adding your portal-ext.properties + your changes at HTML directory -> Does not work
- But does it work with only portal-ext.properites?

What do you have changed at your HTML directory and why you are not doing that with hook?

What does your liferay-portlet.xml contain?

Does the unix account that your Liferay is using has all rights to your server files and does it own them?
Philip Coates
RE: Sign in form (Was: Problems with sign in on move to bigger server)
24 de septiembre de 2012 16:03
Respuesta

Philip Coates

Ranking: Junior Member

Mensajes: 34

Fecha de incorporación: 10 de diciembre de 2010

Mensajes recientes

Hi Sampsa,

Thanks so much for your suggestions! A methodical and measured approach seems to have done the trick, as far as I can see and it's starting to look OK!

I'd gone through the process before, but I think I must have tried too much in one go each time, partly because we had a bit of time pressure.

I went through the steps and got to the point of adding in our portal-ext.properties and then the data directory and the missing parts were visible again. We'll now go about adding portlets and themes back one at a time as we require them (I think a lot were originally added experimentally and unnecessarily)

I'll drop an up-to-date backup of data (db and data dir) onto the server just before we switch over when we're happy with everything else.

The additional stuff we had in the html directory was partly from themes and portlets, some of which seem to have put stuff there, and partly because we made a scripts directory which we put there because we needed somewhere that would be accessible as a location for Javascript.

If there's somewhere better for us to put this, then we can move it.

Once again, thanks again for pushing me to do this the right way, and thanks everyone for your help and suggestions!

Best wishes,

Phil.