Forum Problems Installing LAMS: Re: Re: Re: Re: Re: Re: Re: Re: LAMS service stops running

By: Luke Foxton

[ Reply | Forward ]

Hi David,

This is indeed strange behaviour, I havent found an explanation from the lams logs. Perhaps something is causing your server CPU to spike unexpectedly.

Is your server running anything else apart from lams
Are you using Windows or linux? Are you using the wrapper and if so can you please send us the jboss-4.0.2/logs/wrapper.log. Perhaps that will tell us why your server is suddenly stopping.

Thanks,

Luke

Posted by Luke Foxton

By: David McGeary

[ Reply | Forward ]

OK> Got a new server - fresh install and now lams isn't throwing any errors, but it isn't starting up either. The logs look different, too. I am attaching for your edification.

BTW, you have no idea how much I appreciate your time and patience with me. We are very much looking forward to using LAMS with our students and we are very excited about the opportunities it will create!

Posted by David McGeary

By: Luke Foxton

[ Reply | Forward ]

Hi David,

These logs are strange... again it seems like there is problems conecting to the database.

How are you setting up the server are you using the unix installer, the windows installer or are you building manually from source?

Luke

Posted by Luke Foxton

By: David McGeary

[ Reply | Forward ]

I am using the Unix installer 2.2 on a running Moodle server (with MySQL running as well).

Posted by David McGeary

By: Luke Foxton

[ Reply | Forward ]

Hey David,

Sorry to ask for more info again, but now I know its a unix installer instance, there may be a few bits of info that can help me get to the bottom of this.

Can you please send me:

1) The installation logs, which will be stored in your installer package under "logs"

2) The wrapper logs which will be stored under jboss-4.0.2/logs

3) If its available, the non-secret settings in your lams.properties file, perhaps there is something in here which is slighly off.

Luke

Posted by Luke Foxton

By: David McGeary

[ Reply | Forward ]

Here you go! Thanks again!

Posted by David McGeary

By: Luke Foxton

[ Reply | Forward ]

Thanks David,

This is definitely something that I haven't come across before. What I did notice in the wrapper.log is this exception (which is related to the JDBC MySQL database connection:

INFO | jvm 1 | 2009/02/25 13:01:33 | java.net.SocketException: Broken pipe
INFO | jvm 1 | 2009/02/25 13:01:33 | at java.net.SocketOutputStream.socketWrite0(Native Method)
INFO | jvm 1 | 2009/02/25 13:01:33 | at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
INFO | jvm 1 | 2009/02/25 13:01:33 | at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
INFO | jvm 1 | 2009/02/25 13:01:33 | at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
INFO | jvm 1 | 2009/02/25 13:01:33 | at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2692)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2621)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1552)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1666)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.Connection.execSQL(Connection.java:2994)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:936)
INFO | jvm 1 | 2009/02/25 13:01:33 | at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1030)
INFO | jvm 1 | 2009/02/25 13:01:33 | at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:296)
INFO | jvm 1 | 2009/02/25 13:01:33 | at org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.obtainLock(StdRowLockSemaphore.java:137)
INFO | jvm 1 | 2009/02/25 13:01:33 | at org.quartz.impl.jdbcjobstore.JobStoreCMT.doRecoverMisfires(JobStoreCMT.java:1337)
INFO | jvm 1 | 2009/02/25 13:01:33 | at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:2449)
INFO | jvm 1 | 2009/02/25 13:01:33 | at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:2468)

Looking at this MySQL thread:
http://forums.mysql.com/read.php?39,42763,42763#msg-42763
It seems in general that this problem is caused by a discrepancy in the MySQL configuration.

I noticed in your lams.properties that you are using the mysql-connector-java-5.1.7-bin.jar jdbc library instead of the packaged mysql-connector-java-3.1.12-bin.jar is there a reason for this?

What version of MySQL are you using and how did you install it? Have any configurations been made on the MySQL server? And is there anything else apart from LAMS using this MySQL instance?

Thanks

Luke

Posted by Luke Foxton