lighttpd doesn't start after network change

[RaveAngel]

[Solved through reinstallation] lighttpd doesn't start after network change

I changed my network and therewith the adress of my NAS from 192.168.1.3 to 10.0.0.3. Now I always get the message:

Code:

2011-09-15 15:34:26: (network.c.358) can't bind to port: 192.168.1.3 80 Can't assign requested address 
./lighttpd: WARNING: failed to start lighttpd

"server.bind" in /usr/local/etc/lighttpd/lighttpd.conf is still set on the old value. If I change this, I can start lighttpd. But after a reboot this value has been resetted and lighttpd doesn't start again. But where do I have to alter what then?

Regards
Mario

 

[RaveAngel]

I just tried exporting all, then re-installed the system on the usb flash drive and imported the settings... Sadly this value is also reimported... I don't want to reconfigure the whole system and all shares... :-(

 

[Durkatlon]

"Search" is your friend:

http://forums.freenas.org/showthread.php?2143-network-bonding-issue

 

[RaveAngel]

Yes, it is. And I'm it's friend. But I already tried editing the "/conf/base/etc/local/lighttpd/lighttpd.conf". That file is not the same as the one in /usr/local/etc/lighttpd/. server.bind is there already commented out... I tried commenting it in and change it to my actual IP but there's no effect in doing this.

Okay, reconfiguring all... :-(

 

[Durkatlon]

That's weird, if I diff those two files they are absolutely identical. I have BETA4, not RC1, so I can't reproduce the problem you are seeing here on my end.

The erroneous setting you're trying to fix is likely put there when one of the /etc/rc.d/ix-* scripts runs. I would've guessed /etc/rc.d/ix-httpd, but a quick reading of the BETA4 version doesn't make it any clearer to me.

It looks like the only thing in BETA4 that is read from SQLite is the protocol (http/https). If you can find a line in RC1 that appears to try to read the bonding IP, you can comment out that section of /conf/base/etc/rc.d/ix-httpd and try rebooting.

 

[RaveAngel]

Thank you for the effort of answering me, but I already set up a new installation and reconfigured it like my old installation. Either way my problem is solved now and I don't intend to change it's IP in the next few years. :)