The first question is very easy to answer: ledgersmb-1.2.7-ebuild In the /etc/network/interfaces I saw only: ----------- # cat /etc/network/interfaces auto lo iface lo inet loopback -----------
So I added eth0: ----------- auto eth0 iface eth0 inet dhcp ----------- Tried to make a bridge following the instructions outlined in https://help.ubuntu.com/11.04/serverguide/C/network-configuration.html#bridging Restarted, no connection, ifconfig gave nothing. Tried to 'ifup eth0': device not available. Then, funny enough, ifconfig -a | grep eth returned an eth5 interface. I 'ifup-ed' it, and was able from the workstation to ping and ssh the VM. After creating a testpage with phpinfo in it in /var/www , this was accessible from within the host's browser. However, opening ledgersmb/login.php gave the 'not available' message, and that's where I got lost. I didn't change anything with respect to Apache/PostgreSQL so I figured I didn't 'deserve' that message. Even ssh-ing the host throught the bridge's interface worked. My knowledge of linux is quite limited and I have no idea now how to proceed, so any help would be welcome. Thanks, ario On Tue, 2011-09-20 at 22:09 -0700, Chris Travers wrote: > On Tue, Sep 20, 2011 at 10:00 PM, ario <[email protected]> wrote: > > Hello, I have (created) a problem caused by moving the (KVM) VM with my > > ledgersmb to another workstation. The previous IP is different from the > > new one and the networking has changed from local access only to > > bridged, so that the service can be accessed from everywhere when that > > works. > > Problem is now, that pointing the browser to > > http://<new IP> says: "It Works!", and to > > http://<new IP>/test.php (which I put myself in /var/www) gives a nice > > phpinfo page, but pointing the browser to > > <new IP>://ledgersmb/login.php says it doesn't exist (anymore). > > > > The logfile /var/log/postgresql/postgresql-8.3-main.log > > says the following: > > > > BST LOG: database system was shut down at 2011-09-21 04:52: 31 BST > > BST LOG: incomplete startup packet > > BST FATAL: the database system is starting up > > BST LOG: autovacuum system started > > BST LOG: database system is ready to accept connections > > > > I'm at a loss now, does anybody have a clue as to how to solve this? > > Which version of LedgerSMB is this? What have you done to try to fix > the problem? > > Best Wishes, > Chris Travers > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Ledger-smb-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ledger-smb-users ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Ledger-smb-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
