Re: [Koha] Koha VMWare Virtual appliance problem
Thanks Jim for response. You have made a valid point. But as I mentioned earlier I am using vmware player at windows XP. How should I know the ip address of that virtual machine and how can i determine whether apache is running or not. I am not aware of linux commands... Cyberarian On Oct 26, 2007 10:38 PM, Jim Kronebusch <jim@winonacotter.org> wrote:
On Thu, 25 Oct 2007 12:51:43 +0500, cyberarian wrote
Dear All
I have downloaded koha vmware virtual appliance. It is working fine in VMware player. But i am unable to load its gui. I used startx command on shell but it says that is a wrong command. What should i do to access intranet and opac?
Cyberarian
If I understand correctly, it sounds as though you are trying to access the web gui via the server itself. This won't work by default. The VMware image does not include a desktop (as far as I'm aware) by default. Use another machine on the network and access the server via the browser via the servers IP address such as
http://ser.ver.ip.address/cgi-bin/koha/opac-main.pl
Hope this helps.
Jim
-- This message has been scanned for viruses and dangerous content by the Cotter Technology Department, and is believed to be clean.
Try this: 1. Start the koha vmware appliance. 2. Log in to the server once it has started, the default username and password are kohaadmin and kohaadmin if you are using the appliance I made. 3. Type the command 'ifconfig'. You will get some text describing the various network interfaces, for the one named eth0, find the line the begins with 'inet addr:' The ip address is right after it, for mine it looks like:"indet addr:192.168.20.50 Bcast:192.168.20.255 Mask:255.255.255.0'. So my appliances ip address is 192.168.20.50. To access the opac, open a browser on the machine running vmware, and put the ip address in the URL field. To access the librarian interface, append ':8080' to it. Mine would be "192.168.20.50:8080". Kyle -- IT Tech Crawford County Federated Library System On Nov 5, 2007 11:53 PM, cyberarian <cyberarian@gmail.com> wrote:
Thanks Jim for response. You have made a valid point. But as I mentioned earlier I am using vmware player at windows XP. How should I know the ip address of that virtual machine and how can i determine whether apache is running or not. I am not aware of linux commands...
Cyberarian
On Thu, 25 Oct 2007 12:51:43 +0500, cyberarian wrote
Dear All
I have downloaded koha vmware virtual appliance. It is working fine in VMware player. But i am unable to load its gui. I used startx command on shell but it says that is a wrong command. What should i do to access intranet and opac?
Cyberarian
If I understand correctly, it sounds as though you are trying to access
On Oct 26, 2007 10:38 PM, Jim Kronebusch <jim@winonacotter.org > wrote: the web gui via
the server itself. This won't work by default. The VMware image does not include a desktop (as far as I'm aware) by default. Use another machine on the network and access the server via the browser via the servers IP address such as
http://ser.ver.ip.address/cgi-bin/koha/opac-main.pl
Hope this helps.
Jim
-- This message has been scanned for viruses and dangerous content by the Cotter Technology Department, and is believed to be clean.
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- IT Tech Crawford County Federated Library System
Dear Kyle Thanks for detailed email. I followed your instructions step by step. Also I've understand all the steps. inet addr: value in my virtual appliance is 127.0.0.1. But when I point to http://127.0.0.1 it says: Firefox can't establish a connection to the server at 127.0.0.1. It means, my windows xp machine is not connected to vmware player. How it can be connected. Also 127.0.0.1 is default local address of each machine and browser tries to open web service of same machine. Any suggestion? Cyberarian On Nov 6, 2007 5:30 PM, Kyle Hall <kyle.m.hall@gmail.com> wrote:
Try this: 1. Start the koha vmware appliance. 2. Log in to the server once it has started, the default username and password are kohaadmin and kohaadmin if you are using the appliance I made. 3. Type the command 'ifconfig'. You will get some text describing the various network interfaces, for the one named eth0, find the line the begins with 'inet addr:' The ip address is right after it, for mine it looks like:"indet addr:192.168.20.50 Bcast:192.168.20.255 Mask:255.255.255.0'. So my appliances ip address is 192.168.20.50.
To access the opac, open a browser on the machine running vmware, and put the ip address in the URL field. To access the librarian interface, append ':8080' to it. Mine would be "192.168.20.50:8080".
Kyle -- IT Tech Crawford County Federated Library System
On Nov 5, 2007 11:53 PM, cyberarian <cyberarian@gmail.com> wrote:
Thanks Jim for response. You have made a valid point. But as I mentioned earlier I am using vmware player at windows XP. How should I know the ip address of that virtual machine and how can i determine whether apache is running or not. I am not aware of linux commands...
Cyberarian
On Thu, 25 Oct 2007 12:51:43 +0500, cyberarian wrote
Dear All
I have downloaded koha vmware virtual appliance. It is working fine in VMware player. But i am unable to load its gui. I used startx command on shell but it says that is a wrong command. What should i do to access intranet and opac?
Cyberarian
If I understand correctly, it sounds as though you are trying to access
On Oct 26, 2007 10:38 PM, Jim Kronebusch <jim@winonacotter.org > wrote: the web gui via
the server itself. This won't work by default. The VMware image does not include a desktop (as far as I'm aware) by default. Use another machine on the network and access the server via the browser via the servers IP address such as
http://ser.ver.ip.address/cgi-bin/koha/opac-main.pl
Hope this helps.
Jim
-- This message has been scanned for viruses and dangerous content by the Cotter Technology Department, and is believed to be clean.
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- IT Tech Crawford County Federated Library System
Thanks for detailed email. I followed your instructions step by step. Also I've understand all the steps. inet addr: value in my virtual appliance is 127.0.0.1 <http://127.0.0.1>. But when I point to http://127.0.0.1 it says: Firefox can't establish a connection to the server at 127.0.0.1 <http://127.0.0.1>.
You have to take care of your Virtual Machine (VM) Ethernet setting. Your VM network connection can be: bridged, NAT or host-only. (1) It seems you have a host-only connection. It implies that your VM and host system can't communicate at all. In host-only mode, VM don't see the outside, and so the Internet. (2) The 'bridged' connection is the simplest solution: Kyle instructions will work. But you need a DHCP server on your network in order to lease an IP address to your VM. Even in this case, you may encounter some very tricky issues depending of VM Linux OS security policy. (3) NAT setting: don't rember... but I'm almost sure it won't work since host and VM share a unique IP address. -- Frédéric
On 07/11/2007, Frédéric DEMIANS <frederic@tamil.fr> wrote:
Thanks for detailed email. I followed your instructions step by step. Also I've understand all the steps. inet addr: value in my virtual appliance is 127.0.0.1 <http://127.0.0.1>. But when I point to http://127.0.0.1 it says: Firefox can't establish a connection to the server at 127.0.0.1 <http://127.0.0.1>.
You have to take care of your Virtual Machine (VM) Ethernet setting. Your VM network connection can be: bridged, NAT or host-only. (1) It seems you have a host-only connection. It implies that your VM and host system can't communicate at all. In host-only mode, VM don't see the outside, and so the Internet. (2) The 'bridged' connection is the simplest solution: Kyle instructions will work. But you need a DHCP server on your network in order to lease an IP address to your VM. Even in this case, you may encounter some very tricky issues depending of VM Linux OS security policy. (3) NAT setting: don't rember... but I'm almost sure it won't work since host and VM share a unique IP address. -- Frédéric
NAT setting will work fine for VM host -> VM guest connections, actually; I use it frequently with my Evergreen VMWare instance. Your VM will get an IP address like 192.168.135.129; your host will have a corresponding additional entry of 192.168.135.1. (On Windows, running "ipconfig /all" will show you all of your system's IP addresses). So from your Windows host you would be able to connect to your Linux VM guest at "http://192.168.135.129" (assuming, of course, that Apache is configured to enable connections from that block of IP addresses). NAT won't work well for an entirely separate physical machine accessing your VM guest, however. For that, you either need a bridged connection, or to run a router service on your VM host that redirects port 80 + 443 TCP to the VM guest. -- Dan Scott Laurentian University
participants (4)
-
cyberarian -
Dan Scott -
Frédéric DEMIANS -
Kyle Hall