[Bug 1891751] Re: firehol ubuntu 20.04 ERROR: Neither IPv4 nor IPv6 is available - exiting
I previously have firehol installed on a 20.04 (server A), and it runs just fine (have encountered #264 of course). Yesterday, I tried to install firehol on another 20.04 (server B), and encountered error: user@B:~$ sudo firehol try WARNING: error initializing iptables: IPv4 disabled WARNING: error initializing ip6tables: IPv6 disabled ERROR: Neither IPv4 nor IPv6 is available - exiting Both server A and B user install.config: $ grep iptables /usr/lib/firehol/install.config IPTABLES_CMD="/sbin/iptables" IPTABLES_RESTORE_CMD="/sbin/iptables-restore" IPTABLES_SAVE_CMD="/sbin/iptables-save" I I found out the difference is that on server A, there is a default config file: root@A:~# grep iptables /etc/firehol/firehol-defaults.conf | grep -v \# IPTABLES_CMD="/usr/sbin/iptables" IPTABLES_SAVE_CMD="/usr/sbin/iptables-save" IPTABLES_RESTORE_CMD="/usr/sbin/iptables-restore" So, the correct command is listed in firehol-defaults.conf I tried to list the file dates: root@A:~# ls -lah /usr/lib/firehol/ drwxr-xr-x 2 root root 4.0K Oct 10 2019 . drwxr-xr-x 96 root root 12K Mar 9 03:06 .. -rwxr-xr-x 1 root root 357K Jun 22 2020 firehol -rwxr-xr-x 1 root root 102K Nov 4 2017 fireqos -rw-r--r-- 1 root root 2.1K Nov 4 2017 functions.common -rw-r--r-- 1 root root 2.3K Nov 4 2017 install.config root@A:~# ls -lah /etc/firehol drwxr-xr-x 4 root root 4.0K Oct 13 2019 . drwxr-xr-x 181 root root 12K Mar 10 03:21 .. -rw-r--r-- 1 root root 2.0K Mar 8 04:26 firehol.conf -rw-r--r-- 1 root root 22K Jun 22 2020 firehol-defaults.conf -rw-r--r-- 1 root root 190 Sep 20 2017 fireqos.conf While I cannot be sure whether I touched the file or not, it seems highly likely to me that the firehol-defaults.conf could come from a installation back in the 2020. Maybe somehow the file got lost in the packaging process? Or maybe I installed firehol through source (I doubt that, yet I really don't know)? It is suggested by firehol website that firehol-defaults.conf should better be included: https://firehol.org/firehol-manual/firehol-defaults-conf/ Quote " From FireHOL 3 upwards, variables which control FireHOL behaviour are held in a separate file: /etc/firehol/firehol-defaults.conf. Some variables can also be set in the main firehol.conf file but that is not recommended, since they may be used before the main configuration is processed. FireHOL also sets some variables before processing the configuration file which you can use as part of your configuration. These are described in firehol.conf(5). " Just my two cents. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891751 Title: firehol ubuntu 20.04 ERROR: Neither IPv4 nor IPv6 is available - exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firehol/+bug/1891751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685794] Re: Boot delayed for about 90 seconds until 'random: crng init done'
To add to Andrew's solution, in my case, the UUID in /etc/initramfs- tools/config.d/resume was correct. But my swap was on an LVM partition. I have found this blog post: https://www.hiroom2.com/2018/05/01/ubuntu-1804-lvm-swap-wait-for-root- en/ and changed the line in /etc/initramfs-tools/config.d/resume from using UUID to using device path of LVM swap partition, i.e.: from something like: RESUME=UUID=----x to something like: RESUME=/dev/mapper/ubuntuvg-lvswap After that, sudo update-initramfs -u Then restart and the problem was solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685794 Title: Boot delayed for about 90 seconds until 'random: crng init done' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725848] Re: libstdc++-5-dev:amd64 5.5.0-1ubuntu1 configured without _GLIBCXX_USE_C99
This is a big problem. I am using https://github.com/NetSys/bess. BESS relies on gRPC. gRPC fails to compile under gcc 5 due to the to_string not declared error. gRPC does compile under gcc 6 or 7 but it breaks BESS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725848 Title: libstdc++-5-dev:amd64 5.5.0-1ubuntu1 configured without _GLIBCXX_USE_C99 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1725848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 469005] Re: GDB: Failed to set controlling terminal
same on Code::Blocks r7955 and Ubuntu 12.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/469005 Title: GDB: Failed to set controlling terminal To manage notifications about this bug go to: https://bugs.launchpad.net/codeblocks/+bug/469005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 586400] Re: After using Ubuntu 10.04 LTS at a stretch for somtime, a black screen comes which says checking battery etc. and the PC goes into loop of black screens
I have this bug too, and I can assure you, ti's no Docky bug. I haven't even installed that yet. -- After using Ubuntu 10.04 LTS at a stretch for somtime, a black screen comes which says checking battery etc. and the PC goes into loop of black screens https://bugs.launchpad.net/bugs/586400 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
