Forum LAMS for Tech-Heads - General Forum: Re: Requested resource not available

By: Anders Berggren

[ Reply | Forward ]

I think I am using 8080.

Posted by Anders Berggren

By: Ernie Ghiglione

[ Reply | Forward ]

Anders,

Fiona has set up a Changing Server Ports page on the wiki page that might be helpful to make sure what your you are using.

Thanks,

Ernie

Posted by Ernie Ghiglione

By: Fiona Malikoff

[ Reply | Forward ]

Anders,

Can you try accessing the server without the "lams/" bit on the end?

e.g., if you were normally to enter "http://server:8080/lams" then just put in "http://server/lams"

Do you get page with an Apache heading or a JBoss heading?

If you get an Apache heading, then apache is using that port, and you will need to use the instructions on the page Ernie has suggested to move LAMS to another port.

But I don't understand why this would have changed between you running 2.0 and 2.0.1? Unless you configured LAMS to run on a different port for 2.0?

Waiting for LAMS 2.0.2 won't fix this - it will just default to port 8080 just the same as LAMS 2.0.1.

Fiona

Posted by Fiona Malikoff

By: Anders Berggren

[ Reply | Forward ]

http://server/lams leads to a page that
can't be viewed.

Changing the port to 8180 gave the
same result - "resource not available"
It is still an Apache heading.

No, I haven't configured LAMS to run
on any other port than 8080.

Anders

Posted by Anders Berggren

By: Fiona Malikoff

[ Reply | Forward ]

Anders,

I just realised I had a typing mistake in my previous message.

What I meant to say was could you try

http://<yourservernamehere>:8080/

replacing <yourservernamehere> with the name of your server.

What does that give you?

Fiona

Posted by Fiona Malikoff

By: Anders Berggren

[ Reply | Forward ]

Tried "http://localhost:8080/
Response:
"Page can not be viewed - connection to server failed"

Posted by Anders Berggren

By: Anders Berggren

[ Reply | Forward ]

Hi Fiona,

I just had a hunch
that Tomcat is not
a part of the XAMPP
package.

The number of lams2 database tables
vary with each re-installation. For
the moment there are 7 tables.

Now I get no ants-directory. ?!?

Most of the rest of the things on
this testing computer seem to work
properly.

I hope I am not causing too much
inconvenience...

Cheers, Anders

Posted by Anders Berggren

By: Fiona Malikoff

[ Reply | Forward ]

Anders,

First up, an apology. I missed the word "Tomcat" in your first post and went off on a tangent there. The "Tomcat" bit indicates you probably are getting through to JBoss - Tomcat is the webserver that is bundled as part of JBoss.

So that leaves us with a problem with the install again. 7 tables is just plain weird.

Luke is just sending me the 2.0.2 installer for testing, so its is on schedule for release later this week. So either give the 2.0.1 another go or wait till Thursday and fingers crossed the next installer will be ready, with some critical bugs fixed relating to non-Roman characters.

If you do give 2.0.1 another go, can you display the details when you are on the main install screen, copy them to the clipboard and attach them here? See the screendump for the screen I refer to.

Fiona

Posted by Fiona Malikoff

By: Anders Berggren

[ Reply | Forward ]

Hi Fiona,
I don't know if there should be
a slash after the path to 'mysql'
or not. We added that when installing
2.0.

I've attached the installation log.
Seems OK to me.

Anders

Posted by Anders Berggren

By: Fiona Malikoff

[ Reply | Forward ]

Anders,

The error is this bit:

import-db:
      [sql] Executing file: C:\DOCUME~1\ANDERS~1\LOKALA~1\Temp\dump.sql
      [sql] Failed to execute:    /*!40000 ALTER TABLE `lams_auth_method_type` DISABLE KEYS */

BUILD FAILED
C:\DOCUME~1\ANDERS~1\LOKALA~1\Temp\build.xml:95: java.sql.SQLException: Table 'lams_auth_method_type' is read only

But why mysql thinks this table is read only I have no idea.

I assume you are trying to do a fresh install - not upgrade from a previous version. If you are trying to do a fresh install, can you MySQL client and delete the lams2 database manually before running the install.

We are still finalising the 2.0.2 installer so wait till that one is ready (real soon now!)

I'm not sure how you can drop a database in WinMySQLadmin - I've never managed to get it working properly since I reinstalled XAMPP on my PC.

To do it via the command line version you should be able to go to the command line and do the following, replacing "c:\Program Files\xampp\mysql" with your path to mysql:

C:\Documents and Settings\Administrator>"c:\Program Files\xampp\mysql\bin\mysql" -ulams2 -p
Enter password: ********
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 234
Server version: 5.0.33 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> drop database lams2;
Query OK, 139 rows affected (5.00 sec)

mysql> exit
Bye



The number of rows bit will be different if you have only 7 tables!

Fiona

Posted by Fiona Malikoff

By: Anders Berggren

[ Reply | Forward ]

Hi Fiona,
I upgraded to both JDK 1.6.0 and LAMS 2.0.2.
Then I finally got the URL to user info right
in 'Maintain integrated servers' after changing it to:

"http://localhost/moodle/mod/lamstwo/userinfo.php?un=%username%&ts=%timestamp%&hs=%hash%"

by adding 'moodle' according to instructions you had
given to another user in another discussion.

For the moment everything that I have done
seems to function even if some mysterious
stuff interferes temporarily.

Anders

Posted by Anders Berggren

By: Stefano Todaro

[ Reply | Forward ]

Hi,

i've got the same trouble but with LAMS v2.2.
I use XAMPP, i added the totcat add-on, my localhost:8080 display "Welcome JBoss".
What can i do? With the same system configuration LAMS v2.04 it works very well instead LAMS v2.2 it doesnt works!!! What it chanced with this new release?
Thanks a lots

Posted by Stefano Todaro

By: Luke Foxton

[ Reply | Forward ]

Hi Stefano,

Have you updated from 2.0.4 - 2.1 - 2.1.1 - 2.2, or have you installed from scratch using XAMPP.

If you have installed from scratch using XAMPP, there are special instructions listed here:

http://wiki.lamsfoundation.org/display/lamsdocs/Installing+MySQL+on+Windows+for+LAMS

Luke

Posted by Luke Foxton

By: Stefano Todaro

[ Reply | Forward ]

Hi Luke,
this is my system in localhost:
- XP SP3 521 Mb Ram, 1.6 Mhz
- i didn't upgrade old version, i use windows-installer LAMS v2.2.exe.
- i saw all documents about technical instructions in wiki.lamsfoundation.org and i'm completely conform of it
- i used:
XAMPP per Windows Version 1.7.0
Apache/2.2.11 (Win32)
MySQL client: 5.1.30
PHP Version 5.2.8
- i changed LAMS port number reinstalling all from 8080 to 8180, but it doesn't works!
- i'm not any trouble with start LAMS service
- from my IE Explorer v7:
http://localhost/lams: object not found
http://localhost:8180/lams/: The requested resource (/lams/) is not available. - Apache Tomcat/5.5.9
http://localhost:8180/status?full=true#2.0 JBoss it found
- i found any indication about old error for copy of file in other directory it's all OK
- remember this: with LAMS v2.04 it's all OK!!!

What needs for LAMS v2.2? Is it possible follow a complete installation procedure?

I'm looking for other new about it but i didn't think to be alone with this trouble!!!

Thanks a lots

Posted by Stefano Todaro

By: Luke Foxton

[ Reply | Forward ]

Hi Stefano,

I just re-tested on Win XP and XAMPP bundled Mysql, I followed the steps for XAMPP on the wiki. I didnt have a problem with the install, and LAMS started correctly.

Perhaps something else is causing your error, can you please send the lams/jboss-4.0.2/server/default/log/server.log file?

thanks,

Luke

Posted by Luke Foxton

By: Stefano Todaro

[ Reply | Forward ]

Hi Luke,
all it's always possible specially in HiTech ...
But i didn't undestand why it works well with LAMS v2.04 and it doesn't works with LAMS v2.2, repeat: without any modification!

I'm remembering just now from your request about log file and in fact every time are upgrated boot.log, server.log, hibernatelams.log, localhost_access_log.2009-03-05.log

=== boot.log ===
it's too long

=== server.log ===
it's too long

=== hibernatelams.log ===
it's too long

=== localhost_access_log.2009-03-05.log ===
127.0.0.1 - - [05/Mar/2009:11:10:05 +0100] "GET /lams/ HTTP/1.1" 404 968

Unluckily this forum hasn't got any possiblity to enclose files. I don't want full this massage whith hundreds of lines! Could you give your mail addres so i'll send you immediately all file logs?

Thanks

Posted by Stefano Todaro

By: Luke Foxton

[ Reply | Forward ]

Hi Stefano,

As far as I can tell, you need to follow the same steps with LAMS 2.0.4 and LAMS 2.2 with XAMPP installation, and it works fine. Installing with LAMS 2.0.4 and XAMPP still required you to have the my.ini file created before you started the installation.


>> Unluckily this forum hasn't got any possiblity to enclose files

You can actually, when you post a reply there is an option below that says "Attach" you just need to select yes and the next page will allow you to attach the file.

Luke

Posted by Luke Foxton

By: Stefano Todaro

[ Reply | Forward ]

Sorry ...

I'm very stupid, but the harry is always dangerous!!!

Stefano

Posted by Stefano Todaro

By: Luke Foxton

[ Reply | Forward ]

Thats ok Stefano,

It does look like there has been some failure with the database, some tables are missing according to the logs. Do you still have the install logs?

They should be stored in the C:\xampp\lams\install-logs directory.

If you could zip those up and send attach them in the next post I might be able to work out what wen wrong from there.

Otherwise it might be an idea to re-install,

Luke

Posted by Luke Foxton

By: Stefano Todaro

[ Reply | Forward ]

Hi Luke,

I understood what you mean, infact into the install-logs file i found finally something of interesting about the failure.

Following the content about two smart files:

=== configure-deploy.log ===

Buildfile: build.xml

configure-deploy:
[copy] Copying 1 file to C:\DOCUME~1\ADMINI~1\IMPOST~1\Temp\lams
[copy] Copying 1 file to C:\xampp\htdocs\lams\jboss-4.0.2\server\default\deploy
[copy] Copying 1 file to C:\xampp\htdocs\lams\jboss-4.0.2\server\default\deploy\jbossweb-tomcat55.sar
[copy] Copying 1 file to C:\xampp\htdocs\lams\jboss-4.0.2\bin
[copy] Copying 1 file to C:\xampp\htdocs\lams
[copy] Copying 1 file to C:\xampp\htdocs\lams

BUILD SUCCESSFUL
Total time: 2 seconds

=== import-db.log ===
import-db:
[sql] Executing file: C:\DOCUME~1\ADMINI~1\IMPOST~1\Temp\dump.sql
[sql] Failed to execute: CREATE TABLE `lams_events` ( `uid` bigint(20) NOT NULL auto_increment, `scope` varchar(255) NOT NULL, `name` varchar(255) NOT NULL, `event_session_id` bigint(20) default NULL, `triggered` tinyint(4) default NULL, `default_subject` varchar(255) default NULL, `default_message` text, `subject` varchar(255) default NULL, `message` text, `fail_time` datetime default NULL, PRIMARY KEY (`uid`), UNIQUE KEY `uid` (`uid`), KEY `scope` (`scope`,`name`,`event_session_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8

BUILD FAILED
C:\DOCUME~1\ADMINI~1\IMPOST~1\Temp\build.xml:84: java.sql.SQLException: Specified key was too long; max key length is 1000 bytes

Total time: 3 seconds

Furthermore, I tried to change the location about installation.

Before it was c:\XAMPP\lams now C:\xampp\htdocs\lams, but it doesn't change nothing! Remember that whith LAMS v 2.04 i haven't got any troubles about location directory!

Thanks again

Posted by Stefano Todaro

By: Luke Foxton

[ Reply | Forward ]

Hi Stefano,

It seems you have come across a MySQL bug, see here:
http://bugs.mysql.com/bug.php?id=4541

There have been many new database tables introduced since 2.0.4, and it seems this is the source of the problem you are having.

Its very strange that this has not come up before, especially when I installed using the same configurations as you, and didnt get the problem. Also, there have been many, many other people using lams2.2 window installer who have not had this same problem.

The only thing I can think of is that it must either have something to do with the MySQL configurations that come with XAMPP or the version 5.1 (Strictly speaking LAMS supports 5.0.x distributions of MySQL).

This issue has been raised and we will try to make a work-around for this problem as soon as possible. In the mean time I can only suggest trying a different version of XAMPP (with Mysql 5.0), or simply installing mysql-server 5.0 directly (not bundled with XAMPP)

Sorry I couldnt find you a quick solution, but hopefully you will hear from us very soon

Luke

Posted by Luke Foxton

By: Stefano Todaro

[ Reply | Forward ]

Hi Luke,

this is my role live: always for is another think than other and for me is very good, so i can understand always somthing more than standard knowlegde.

Ok i'm waiting your answer about the bug with MySql.
Unfortunatly i haven't got any time in this last period.

Thanks forever

Posted by Stefano Todaro