Still some problems with the 18.1 release

Started by DarkBeard, February 02, 2018, 08:36:52 AM

Previous topic - Next topic
1. When reconfiguring the interfaces, the web GUI falls
---------------
# /usr/local/etc/rc.restart_webgui
Starting web GUI...failed.
Generating RRD graphs...done.
---------------
      This happens when the CARP interfaces are temporarily blocked.

# /usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf
2018-02-01 11:45:22: (network.c.313) can't bind to socket: 192.168.144.254:443 Can't assign requested address


2. In the screenshots, the one and the other zoomlevel in 25 minutes, but the pictures are different.
https://yadi.sk/i/v8OqSYSt3RyXTc
https://yadi.sk/i/1V55xU0A3RyXb7


And about the problem of MultiWAN and DHCP, the forum is full of messages. :'( :'(

Are you restricting the web GUI listening interfaces?

Can you access the GUI even though that message is seen?


Cheers,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

I use the default settings (ALL recommended)
Even if I only use the LAN interface, the CARP address is also hung on it, and if I temporarily disable it, the situation will be the same, since I can not select only the interface address, without the virtual IP


The GUI interface is not available at this time. There are no processes in the system:
/usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf
/usr/local/bin/php-cgi





I haven't seen this, but then again I don't have a productive CARP setting. That issue would have been the same on 17.7, no?

Lighttpd is set to "0.0.0.0", if it has a quarrel with an IP it gets from the system but can't use it that would be upstream territory.

Will you push a ticket for the health graph issue?

https://github.com/opnsense/core/issues


Thanks,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT