Activity for Luca Zappi
-
Luca Zappi posted a comment on discussion Webmin
Webmin version: 1.981 Distro version: Ubuntu 20.04.3 LTS System born with Ubuntu 18.4 LTS then release-upgraded.
-
As far I can see some users have problems with DHCP server module, since the interface is not able to read pidfile from directory it is expected to be. path is expected to be /run/dhcp-server, but MUST be considered that during boot phase /run is completely purged, dropped, cleared, so when service starts cannot write pid file because path directory does not exists. Service starts, but webmin module is not able to confirm that service in up and running, so presents the green START button. Simple...
-
Just checked, following result: # echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin Operating System and Environment setting is OK, here is evidence. Often complete path of commands is hard coded into script in order to be indipendent from environment. Is that an option?
-
Just checked, following result: # echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin Operating System and Environment setting il OK, here is evidence. Often complete path of commands is hard coded into script in order to be indipendent from environment. Is that an option?
-
Webmin version 1.960 I just migrated a server from Ubuntu 18.4 to 20.4. Migration has been quite smoot, but iptables configuration was not correctly loaded at boot. The new version Ubuntu 20.4 puts iptables-restore command (symbolic link) under /usr/sbin/ It was under /sbin/ in Ubuntu 18.4 With no clear idea about procedure used by webmin to load iptables configuration at boot time, I only added a symbolic link to iptables-restore under /sbin/ directory. In such way iptables configuration is now...
-
I just migrated a server from Ubuntu 18.4 to 20.4. Migration has been quite smoot, but iptables configuration was not correctly loaded at boot. The new version Ubuntu 20.4 puts iptables-restore command (symbolic link) under /usr/sbin/ It was under /sbin/ in Ubuntu 18.4 With no clear idea about procedure used by webmin to load iptables configuration at boot time, I only added a symbolic link to iptables-restore under /sbin/ directory. In such way iptables configuration is now loaded in the correct...
-
Unlikely after some hour extra delay has been introduced once again.
-
It looks like the problem has been solved. root cause has been identified into unperfect disk partition: # parted -l /dev/sda Error: Can't have a partition outside the disk! applyied following procedure for correct allignment of partition table (note that disk has to be not mounted, so live SO Clonezilla has been used): https://gparted.org/h2-fix-msdos-pt.php#partition-outside-disk After reboot dashboard has been presented without extra long delay. In the next days solution will be checked again,...
-
Let me give evidence of delay in dashboard presentation. I guess delay is related to update of package information: once the system update such information, then the dashboard is presented with no delay. After some ours, system needs to upgrade again package information and then delay is introduced once again. (link to full image: first login with delay evidence) After some minute trying again to login dashboard is presented within 5000 milliseconds without added delay. (link to full image: second...
-
Let me give evidence of delay in dashboard presentation. I guess delay is related to update of package information: once the system update such information, then the dashboard is presented with no delay. After some ours, system needs to upgrade again package information and then delay is introduced once again. (link to full image: first login with delay evidence) After some minute trying again to login dashboard is presented within 5000 milliseconds without added delay. (link to full image: second...
-
Let me give evidence of delay in dashboard presentation. I guess delay is related to update of package information: once the system update such information, then the dashboard is presented with no delay. After some ours, system needs to upgrade again package information and then delay is introduced once again. (link to full image: first login with delay evidence) After some minute trying again to login dashboard is presented within 5000 milliseconds without added delay.
-
Let me give evidence of delay in dashboard presentation. I guess delay is related to update of package information: once the system update such information, then the dashboard is presented with no delay. After some ours, system needs to upgrade again package information and then delay is introduced once again. (link to full image)
-
Let me give evidence of delay in dashboard presentation. I guess delay is related to update of package information: once the system update such information, then the dashboard is presented with no delay. After some ours, system needs to upgrade again package information and then delay is introduced once again. (link to full image)
-
Let me give evidence of delay in dashboard presentation. I guess delay is related to update of package information: once the system update such information, then the dashboard is presented with no delay. After some ours, system needs to upgrade again package information and then delay is introduced once again. (link to full image)
-
Let me give evidence of delay in dashboard presentation. I guess delay is related to update of package information: once the system update such information, then the dashboard is presented with no delay. After some ours, system needs to upgrade again package information and then delay is introduced once again. (link to full image)
-
Let me give evidence of delay in dashboard presentation. I guess delay is related to update of package information: once the system update such information, then the dashboard is presented with no delay. After some ours, system needs to upgrade again package information and then delay is introduced once again. (https://i.postimg.cc/FRpV2Qsb/Webmin-sysinfo-cgi.png)
-
Let me give evidence of delay in dashboard presentation. I guess delay is related to update of package information: once the system update such information, then the dashboard is presented with no delay. After some ours, system needs to upgrade again package information and then delay is introduced once again.
-
So, problem solved.
-
It depends on fail2ban intalled version. The one included into Ubuntu 16.4 distribution was losting all information after each reboot. With Ubuntu 18.4 banned IP survive reboot phase. Not sure with bantime set to -1 as fail2ban is not designed to handle undefinite ban cases, but In my installation there are 10 days of ban for all ports if you break ssh jail rules. They survive reboot with no problems: sqlite DB is used to take track of all ban instance. Test to verify -1 as bantime condiction shoul...
-
Only one SSD disk with two partitions. Webmin version 1.995 I also use to mount some samba network filesystems from two NAS, but only on demand and usually they are not mounted.
-
Only one SSD disk with two partitions. Webmin version 1.995 I also use to mount some samba network filesystems from two NAS, but only on demand and usually they are not nounted.
-
Only one SSD disk with two partitions. Webmin version 1.995
-
Sure sintax used is correct ? $ sudo fail2ban-client status and you get jail list $ sudo fail2ban-client set 'jail-name' bantime -1 you should get -1 as answer for confirmation. Which answer do you get? $ fail2ban-client -V you get back fail2ban version, it should be: Fail2Ban v0.10.2
-
Sure sintax used is correct ? $ sudo fail2ban-client status and you get jail list $ sudo fail2ban-client set \<jail> bantime -1 you should get -1 as answer for confirmation.</jail> Which answer do you get? $ fail2ban-client -V you get back fail2ban version, it should be: Fail2Ban v0.10.2
-
Sure sintax used is correct ? $ sudo fail2ban-client status and you get jail list $ sudo fail2ban-client set <jail> bantime -1 you should get -1 as answer for confirmation.</jail> Which answer do you get? $ fail2ban-client -V you get back fail2ban version, it should be: Fail2Ban v0.10.2
-
Sure sintax used is correct ? $ sudo fail2ban-client status and you get jail list $ sudo fail2ban-client set <jail> bantime -1 you should get -1 as answer for confirmation.</jail> Which answer do you get? $ fail2ban-client -V you get back fail2ban version, it should be: Fail2Ban v0.10.2
-
Sure sintax used is correct ? $ sudo fail2ban-client status and you get jail list $ sudo fail2ban-client set <jail> bantime -1 you should get -1 as answer for confirmation.</jail> Which answer do you get?
-
I notice dashboard take, sometime, long time to get presented to the user. Delay seems to be related with the investigation for package updates. I had some experience with Webmin and Ubuntu 16.4 and under that SO version Webmin was presenting Dashboard with no extra delay. I tryed to resolve the issue removing and installing again webmin, but the same behaviour with extra delay has not bee solved. Is there some other Ubuntu 18 - Webmin user that notice the same behaviour. Is there someone that want...
1