[Bug 1835188] Re: firewalld attempts to use parameter that requires a newer iptables version

2019-11-17 Thread Soputtra San 
I can confirm that this bug also affects *some* of our desktops running
18.04. I haven't figured out why it didn't affect all (100+) machines.

Here is the status output of firewalld service running on a hostname
'matht335':

```
# systemctl status firewalld
   
● firewalld.service - firewalld - dynamic firewall daemon   
  
   Loaded: loaded (/lib/systemd/system/firewalld.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2019-11-18 09:39:43 AEDT; 23min ago   
  
 Docs: man:firewalld(1) 
  
 Main PID: 1340 (firewalld) 
  
Tasks: 2 (limit: 4915)  
  
   CGroup: /system.slice/firewalld.service  
  
   └─1340 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork --nopid 
  

  
Nov 18 09:39:43 matht335 systemd[1]: Starting firewalld - dynamic firewall 
daemon...  
Nov 18 09:39:43 matht335 systemd[1]: Started firewalld - dynamic firewall 
daemon. 
Nov 18 09:39:44 matht335 firewalld[1340]: WARNING: '/sbin/iptables-restore 
--wait=2 -n' failed: /sbin/iptables-restore: unrecognized option '--wait=2'
  iptables-restore: line 46 failed  
  
Nov 18 09:39:44 matht335 firewalld[1340]: ERROR: COMMAND_FAILED 
  
Nov 18 09:39:48 matht335 firewalld[1340]: WARNING: '/sbin/iptables-restore 
--wait=2 -n' failed: /sbin/iptables-restore: unrecognized option '--wait=2'
  iptables-restore v1.6.1: goto 
'IN_public' is not a chain

  
  Error occurred at line: 2 
  
  Try `iptables-restore -h' or 
'iptables-restore --help' for more information.
Nov 18 09:39:48 matht335 firewalld[1340]: WARNING: '/sbin/ip6tables-restore 
--wait=2 -n' failed: /sbin/ip6tables-restore: unrecognized option '--wait=
  ip6tables-restore v1.6.1: goto 
'IN_public' is not a chain   

  
  Error occurred at line: 2 
  
  Try `ip6tables-restore -h' or 
'ip6tables-restore --help' for more information.  
Nov 18 09:39:48 matht335 firewalld[1340]: ERROR: COMMAND_FAILED
```


itables version:
1.6.1-2ubuntu2

firewalld version:
0.4.4.6-1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835188

Title:
  firewalld attempts to use parameter that requires a newer iptables
  version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1835188/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1695129] Re: sssd service does not start up on boot after upgrading to 1.11.8-0ubuntu0.6

2017-06-02 Thread Soputtra San 
The package sssd also add the autofs checking to /etc/init/sssd.conf in
Ubuntu 16.04 package. The only reason Ubuntu 16.04 wasn't affected is
because it uses systemd instead of upstart in Ubuntu 14.04.

Here is my temporary solution if you use Puppet to manage your systems:


class sssd::config {

  # There is a bug in sssd-common 1.11.8-0ubuntu0.6. The new 
``/etc/init/sssd.conf`` 
  # file does a check for 'autofs' before starting up on boot.  
  
  # The patch in config.pp manually removing autofs checking.
  file_line { 'patch_sssd.conf':
path  => '/etc/init/sssd.conf',
line  => 'start on (filesystem and net-device-up)',
match => '^start.*\s+autofs\)',
  }

}


If you don't use Puppet, just ignore this entirely. This solution could instead 
cause you more troubles.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695129

Title:
  sssd service does not start up on boot after upgrading to
  1.11.8-0ubuntu0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1695129/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1695129] [NEW] sssd service does not start up on boot after upgrading to 1.11.8-0ubuntu0.6

2017-06-01 Thread Soputtra San 
Public bug reported:

After upgrading sssd, sssd-* from 1.11.8-0ubuntu0.5 to
1.11.8-0ubuntu0.6, sssd service no longer starts on boot.

According to the diff, it seems that checking 'autofs' was added to
/etc/init/sssd.conf. All our systems do not have autofs installed. This
may explain why sssd service did not start up. However, sssd service can
be manually started with 'service sssd start'.

This issue may affect other Ubuntu 14.04 systems which don't have autofs
installed.

Reference:

http://launchpadlibrarian.net/316116618/sssd_1.11.8-0ubuntu0.5_1.11.8-0ubuntu0.6.diff.gz

...
diff -u sssd-1.11.8/debian/sssd-common.sssd.upstart.in 
sssd-1.11.8/debian/sssd-common.sssd.upstart.in
--- sssd-1.11.8/debian/sssd-common.sssd.upstart.in
+++ sssd-1.11.8/debian/sssd-common.sssd.upstart.in
@@ -7,7 +7,7 @@

 description"System Security Services Daemon"

-start on (filesystem and net-device-up)
+start on (filesystem and net-device-up and starting autofs)
 stop on runlevel [06] 
...

** Affects: sssd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695129

Title:
  sssd service does not start up on boot after upgrading to
  1.11.8-0ubuntu0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1695129/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs