READ ONLY FORUM: m23 :: makes software distribution easy

BlackKatMike · Guest

Hi everybody!

It's my first time here. I'm trying out m23 on Virtualbox because I'm curious of how it works.

I tried to install it on Debian 4.0r3 (I know it's a little old, but it's the latest DVD I have, and hopefully apt-get update should help me...) by putting the m23 repository in /etc/apt/sources.list but I end up with an unmanageable server.

Here's what I've done:

And here's the main issue: connecting to https://192.168.0.1 prompts me to save the PHTML file instead of logging me into the server. Apparently it's not a browser issue (tried with both Iceweasel and Konqueror). Actually the m23 online manual tells to connect via HTTP, not HTTPS, but 1) I recall using HTTPS some m23 version ago, and 2) using plain HTTP returns me to a web root page listing "index of /, parent directory, apache2-default etc etc".

The big questions are...:

1) After trying 2 or 3 times (including doing it all over again from scratch), what am I doing wrong?
2) How come apache 1.3.x gets installed, but some components of apache2 do as well? Does this cause any problem? I recall that during bootup there's something like "NOT starting apache2..." scrolling up.

I apologize if this issue has been already dealt with in another thread, but I see that almost all threads here are in German and I understand very little of it. And, my Linux knowledge is somewhat limited, i.e. I've got a LOT to learn yet, so please be patient if I missed something obvious Smile

. Being a Winblows sysadmin for too many years sucks (especially if you don't like M$ from the beginning...) Smile

.

Thank you in advance!

Hauke · Joined: 02 Mar 2003 Posts: 1072

Hi,

I do my tests with VirtualBox too and have sucessfully installed virtual m23 servers by hand and virtual m23 clients with the virtual m23 servers. My VirtualBox setup differs from yours. For my tests I use one NIC that is set to "host interface" to make the virtual servers and clients behave in the network like real machines.

Setting a NIC to NAT should only work if the IP is fetched via DHCP to get the internet access. And the virtual network should only connect between VirtualBox's virtual computers. This is as I understand these network types and maybe I'm wrong.

So if I'm right it's not possible to access the m23 server via the network and maybe the 192.168.0.1 belongs to another computer.

For further investigation please do the following in the installed virtual machine (as root) and post the result to the forum:

BlackKatMike · Guest

Hi Hauke, thanks for your reply.

192.168.0.1 is the m23 server, indeed. I set things up to have the 192.168.0.0 network inside Virtualbox. My "real" network is on 192.168.1.0, and I'm pretty sure there are no other machines using 192.168.0.1.

Moreover, when I ssh into 192.168.0.1 from the other virtual machine (the Knoppix one) I can easily see it's the right one (the shell prompt has the right hostname, and I don't have other sshd hanging around in either net).

Anyway, here are the result of the commands...

Hauke · Joined: 02 Mar 2003 Posts: 1072

Hi,

the network settings seem to work. Then please figure out what Apache version is installed. You can do this by executing (please post all lines that are listed)

BlackKatMike · Guest

Hi Hauke, sorry for having disappeared for a number of days, been quite busy...

The dpkg output is as follows:

Hauke · Joined: 02 Mar 2003 Posts: 1072

BlackKatMike · Guest

Hi! Done compressing and uploading everything. Check your e-mail for details.

Hauke · Joined: 02 Mar 2003 Posts: 1072

Now I had the time to check the virtual machine you sent.

The problem is that the configuration script of the m23 package assumes that Apache 2 is installed and so the configuration is done in the Apache 2 directory. After deleting the /etc/apache2 directory and reconfiguring the m23 package it worked.

Did you install Apache 2 before?
_________________
Hauke Goos-Habermann
- project leader m23 (http://m23.sf.net) -
Jabber: dodgerm23@jabber.org

Schulung, Entwicklung und Support zu m23 und anderen OpenSource-Produkten: www.goos-habermann.de

Auch DU kannst etwas gegen Softwarepatente tun! www.patentfrei.de

BlackKatMike · Guest

No, I didn't install Apache 2 manually before.

As I said in my first post, I purposefully installed just a base Debian system (leaving all other tasks in the expert install deselected) so I would end up with a system as clean as possible. Then I let aptitude handle all the m23 dependencies when installing it, and I ended up with those apache2-related packages installed.

Hauke · Joined: 02 Mar 2003 Posts: 1072

Seems I need to check the installation with aptitude and maybe I need to change the script that detects the used Apache version.

Did you try to try to delete the directory and reconfigured the m23 package like I did? Did it work?
_________________
Hauke Goos-Habermann
- project leader m23 (http://m23.sf.net) -
Jabber: dodgerm23@jabber.org

Schulung, Entwicklung und Support zu m23 und anderen OpenSource-Produkten: www.goos-habermann.de

Auch DU kannst etwas gegen Softwarepatente tun! www.patentfrei.de

Hauke · Joined: 02 Mar 2003 Posts: 1072

Ok, I can reproduce the installation error on Etch. Now I have m23 installation packages that work on Etch with Apache 1 or 2 and PHP 4 or 5.

The packages will be uploaded in the next hours.
_________________
Hauke Goos-Habermann
- project leader m23 (http://m23.sf.net) -
Jabber: dodgerm23@jabber.org

Schulung, Entwicklung und Support zu m23 und anderen OpenSource-Produkten: www.goos-habermann.de

Auch DU kannst etwas gegen Softwarepatente tun! www.patentfrei.de

BlackKatMike · Guest

Hi Hauke, didn't have much time to follow things happening here...

I didn't try to delete /etc/apache2 as you did, but since you were able to reproduce the error I think I don't need to anymore! Smile

I'm gonna try m23 0.7.1 out when I'll have some time these days, and since Lenny came out recently I'm gonna try m23 on that too.

Thank you, I'll let you know my results!