rhl2000
4th July 2007, 01:46
Greetings!
Since this is my first post here, let me start by expressing my heatfelt gratitude to all the ISPConfig developers. Your creation is pretty much everything I ever dreamed of finding in an open-source hosting controller. Many thanks!
On to my problem: I refer you to the VMware Appliance uploaded by Till (aka "tadorna" on VMware's site), and which can be found at www.vmware.com/vmtn/appliances/directory/342.
First, I updated this appliance to the current state of Debian 3.1 (aka "Sarge"), upgraded the kernel, added the VMware Tools and made some other minor changes to improve clock synchronization between host and guest. All this went without trouble, and if anyone wants the step-by-step description of what was done, I can post it.
At that point, ISPConfig version 2.2.3, which was the one provided in the original upload to VMware's site, seemed to have no problem (in my very limited testing so far). However, I came here looking for newer versions, and found that 2.2.14 was the current one. So I downloaded it to the VM and installed it on top of the old one, as recommended, and as far as I can tell, it went fine (well, at least it signaled successful completion). However, although I have not YET done substantial testing of the upgraded installation, two issues (one minor, one not so minor) became immediately apparent. Here they are:
1) The console boot messages have just ONE slight difference with the boot messages from 2.2.3:
After "Starting ProFTPD ftp daemon:", on the same line, this appears: " - setting default address to 127.0.0.1". I see that this corresponds to a new line being inserted in /etc/proftpd_ispconfig.conf, with the content "DefaultAddress 127.0.0.1". May I presume this is intentional, and not a bug?
2) The network_setup script misbehaves in the following way:
a) the first prompt (language selection) appears normally
b) I answer it (with "en"), I press ENTER, and in very quick sequence the rest of the prompts appear (without line breaks, in one string that wraps around the console display as two lines...), but do not pause to let me type my chosen network settings.
c) The following is then displayed:
IP Address:
Netmask: 0.0.0.0
Gateway:
Network: 0.0.0.0
Broadcast: 255.255.255.255
....
https://:81
I checked the file /etc/network/interfaces, and indeed all the previous values were zapped out, and the last few lines are as follows:
auto eth0
iface eth0 inet static
address
netmask 0.0.0.0
network 0.0.0.0
broadcast 255.255.255.255
gateway
HOWEVER, the command "ifconfig" still displays the previous IP settings, most logically since the values in /etc/network/interfaces are invalid (and the network is still functional).
I located the php script that is called (i.e. /root/ispconfig/scripts/shell/ispconfig_network_setup.php), and looked at it a bit. Mind you, I am NOT a fluent PHP programmer, although I have read up on it a bit. Still, what I see is that the "$fn->getInput()" lines apparently do not wait for a keyboard response. Thus the variables that those getInput() calls are supposed to fill end up remaining empty or null, and those null values are then used in the following "str_replace()" lines that are meant to update /etc/network/interfaces. However, the $interfaces_action command ("/etc/init.d/networking restart") fails to change anything, and if its standard output were not redirected to /dev/null, we would see the following:
Setting up IP spoofing protection: rp_filter.
Reconfiguring network interfaces.../etc/network/interfaces:11: option with empty value
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:11: option with empty value
ifup: couldn't read interfaces file "/etc/network/interfaces"
done.
Thus the system is left in a state where everything still works normally, but the network WILL fail to start on the NEXT boot (unless /etc/network/interfaces is manually corrected before shutdown or reboot).
Would anyone have an idea of the cause of that bug (and its solution)?
Thanks in advance,
_ renald _
. \_____/
Since this is my first post here, let me start by expressing my heatfelt gratitude to all the ISPConfig developers. Your creation is pretty much everything I ever dreamed of finding in an open-source hosting controller. Many thanks!
On to my problem: I refer you to the VMware Appliance uploaded by Till (aka "tadorna" on VMware's site), and which can be found at www.vmware.com/vmtn/appliances/directory/342.
First, I updated this appliance to the current state of Debian 3.1 (aka "Sarge"), upgraded the kernel, added the VMware Tools and made some other minor changes to improve clock synchronization between host and guest. All this went without trouble, and if anyone wants the step-by-step description of what was done, I can post it.
At that point, ISPConfig version 2.2.3, which was the one provided in the original upload to VMware's site, seemed to have no problem (in my very limited testing so far). However, I came here looking for newer versions, and found that 2.2.14 was the current one. So I downloaded it to the VM and installed it on top of the old one, as recommended, and as far as I can tell, it went fine (well, at least it signaled successful completion). However, although I have not YET done substantial testing of the upgraded installation, two issues (one minor, one not so minor) became immediately apparent. Here they are:
1) The console boot messages have just ONE slight difference with the boot messages from 2.2.3:
After "Starting ProFTPD ftp daemon:", on the same line, this appears: " - setting default address to 127.0.0.1". I see that this corresponds to a new line being inserted in /etc/proftpd_ispconfig.conf, with the content "DefaultAddress 127.0.0.1". May I presume this is intentional, and not a bug?
2) The network_setup script misbehaves in the following way:
a) the first prompt (language selection) appears normally
b) I answer it (with "en"), I press ENTER, and in very quick sequence the rest of the prompts appear (without line breaks, in one string that wraps around the console display as two lines...), but do not pause to let me type my chosen network settings.
c) The following is then displayed:
IP Address:
Netmask: 0.0.0.0
Gateway:
Network: 0.0.0.0
Broadcast: 255.255.255.255
....
https://:81
I checked the file /etc/network/interfaces, and indeed all the previous values were zapped out, and the last few lines are as follows:
auto eth0
iface eth0 inet static
address
netmask 0.0.0.0
network 0.0.0.0
broadcast 255.255.255.255
gateway
HOWEVER, the command "ifconfig" still displays the previous IP settings, most logically since the values in /etc/network/interfaces are invalid (and the network is still functional).
I located the php script that is called (i.e. /root/ispconfig/scripts/shell/ispconfig_network_setup.php), and looked at it a bit. Mind you, I am NOT a fluent PHP programmer, although I have read up on it a bit. Still, what I see is that the "$fn->getInput()" lines apparently do not wait for a keyboard response. Thus the variables that those getInput() calls are supposed to fill end up remaining empty or null, and those null values are then used in the following "str_replace()" lines that are meant to update /etc/network/interfaces. However, the $interfaces_action command ("/etc/init.d/networking restart") fails to change anything, and if its standard output were not redirected to /dev/null, we would see the following:
Setting up IP spoofing protection: rp_filter.
Reconfiguring network interfaces.../etc/network/interfaces:11: option with empty value
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:11: option with empty value
ifup: couldn't read interfaces file "/etc/network/interfaces"
done.
Thus the system is left in a state where everything still works normally, but the network WILL fail to start on the NEXT boot (unless /etc/network/interfaces is manually corrected before shutdown or reboot).
Would anyone have an idea of the cause of that bug (and its solution)?
Thanks in advance,
_ renald _
. \_____/