[SOLVED] ferm fails to start on rebooting

[brutis]

Hi,
I'm have a problem on a Raspberry pi3 running Raspbian jessie. ferm will not start after rebooting and so the rules are not loaded from ferm.conf

# uname -a = Linux TorrentMachine 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux
# ferm --version = ferm 2.2
# dpkg-query -l = ferm 2.2-3
/etc/rcS.d S16ferm
/etc/defaults/ferm = # Enable the ferm init script? (i.e. run on bootup) ENABLED="yes"
# systemctl status ferm
ferm.service - LSB: ferm firewall configuration
Loaded: loaded (/etc/init.d/ferm)
Active: inactive (dead)

Also there is nothing in the logs to show why and also nothing stored in /var/cache/ferm

I can start ferm manually using /etc/init.d/ferm start and the ferm.conf is loaded correctly

I have done all of this previously and ferm is working 100% correctly on my Rasberry pi2 running Raspbian wheezy
uname -a = Linux TorrentServer 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
ferm --version = ferm 2.1
dpkg-query -l = ferm 2.1-5

I asked on the ferm forum but they said it was a problem with Raspbian (Debian)
Your help is greatly appreciated.

[brutis]

Actually I did find a problem on the RPi3 after probing -

# dmesg | grep -iC 3 "ferm"
[ 2.773519] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:53:43:8e
[ 3.071674] systemd[1]: Found ordering cycle on basic.target/start
[ 3.073576] systemd[1]: Found dependency on sysinit.target/start
[ 3.075409] systemd[1]: Found dependency on ferm.service/start
[ 3.077195] systemd[1]: Found dependency on network-online.target/start
[ 3.078955] systemd[1]: Found dependency on network.target/start
[ 3.080701] systemd[1]: Found dependency on dhcpcd.service/start
[ 3.082379] systemd[1]: Found dependency on basic.target/start
[ 3.084013] systemd[1]: Breaking ordering cycle by deleting job ferm.service/start
[ 3.085719] systemd[1]: Job ferm.service/start deleted to break ordering cycle starting with basic.target/start
[ 3.094180] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 3.096215] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 3.098012] systemd[1]: Starting Remote File Systems (Pre).

To confirm whether the problem was Debian related, I installed Debian onto a PC (uname -a = Linux debian 3.16.0-4-586 #1 Debian 3.16.7-ckt25-2+deb8u2 (2016-06-25) i686 GNU/Linux) and then installed and configured ferm. This is working correctly on reboot so the problem appears to be with Raspbian jessie.

How can I find which package broke it?

[fruitoftheloom]

Actually I did find a problem after probing -

# dmesg | grep -iC 3 "ferm"
[ 2.773519] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:53:43:8e
[ 3.071674] systemd[1]: Found ordering cycle on basic.target/start
[ 3.073576] systemd[1]: Found dependency on sysinit.target/start
[ 3.075409] systemd[1]: Found dependency on ferm.service/start
[ 3.077195] systemd[1]: Found dependency on network-online.target/start
[ 3.078955] systemd[1]: Found dependency on network.target/start
[ 3.080701] systemd[1]: Found dependency on dhcpcd.service/start
[ 3.082379] systemd[1]: Found dependency on basic.target/start
[ 3.084013] systemd[1]: Breaking ordering cycle by deleting job ferm.service/start
[ 3.085719] systemd[1]: Job ferm.service/start deleted to break ordering cycle starting with basic.target/start
[ 3.094180] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 3.096215] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 3.098012] systemd[1]: Starting Remote File Systems (Pre).

I checked by installing Debian uname -a = Linux debian 3.16.0-4-586 #1 Debian 3.16.7-ckt25-2+deb8u2 (2016-06-25) i686 GNU/Linux and ferm and it is working correctly so the problem appears to be with Rasbian jessie.

How can I find which package broke it?

Why are you using i686, that is for x86 CPU Architecture

The RPi is ARM CPU.....

[fruitoftheloom]

You would be better of starting with a fresh install of Raspbian Jessie, then install term from the repository which is newer then the one in EOL Wheezy.

[brutis]

Actually I did find a problem after probing -

# dmesg | grep -iC 3 "ferm"
[ 2.773519] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:53:43:8e
[ 3.071674] systemd[1]: Found ordering cycle on basic.target/start
[ 3.073576] systemd[1]: Found dependency on sysinit.target/start
[ 3.075409] systemd[1]: Found dependency on ferm.service/start
[ 3.077195] systemd[1]: Found dependency on network-online.target/start
[ 3.078955] systemd[1]: Found dependency on network.target/start
[ 3.080701] systemd[1]: Found dependency on dhcpcd.service/start
[ 3.082379] systemd[1]: Found dependency on basic.target/start
[ 3.084013] systemd[1]: Breaking ordering cycle by deleting job ferm.service/start
[ 3.085719] systemd[1]: Job ferm.service/start deleted to break ordering cycle starting with basic.target/start
[ 3.094180] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 3.096215] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 3.098012] systemd[1]: Starting Remote File Systems (Pre).

I checked by installing Debian uname -a = Linux debian 3.16.0-4-586 #1 Debian 3.16.7-ckt25-2+deb8u2 (2016-06-25) i686 GNU/Linux and ferm and it is working correctly so the problem appears to be with Rasbian jessie.

How can I find which package broke it?

Why are you using i686, that is for x86 CPU Architecture

The RPi is ARM CPU.....

Oh sorry when I did that test it was installed on a PC not the RPi. I will edit the post to clarify.

[brutis]

You would be better of starting with a fresh install of Raspbian Jessie, then install term from the repository which is newer then the one in EOL Wheezy.

Yes, I have tried a fresh install (without updates) and a fresh install with apt-get update, apt-get upgrade and apt-get dist-upgrade and still the same problem.

I don't understand your second point. Can you explain more simply - sorry working at this level of Linux is not so easy for me.

[fruitoftheloom]

You would be better of starting with a fresh install of Raspbian Jessie, then install term from the repository which is newer then the one in EOL Wheezy.

Yes, I have tried a fresh install (without updates) and a fresh install with apt-get update, apt-get upgrade and apt-get dist-upgrade and still the same problem.

I don't understand your second point. Can you explain more simply - sorry working at this level of Linux is not so easy for me.

Wheezy is end of life and no longer supported as of April 2016

[brutis]

in /etc/apt/sources.list the repository is -
deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi

doesn't that mean ferm is coming from that repository, which is jessie?

[fruitoftheloom]

in /etc/apt/sources.list the repository is -
deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi

doesn't that mean ferm is coming from that repository, which is jessie?

Let's start again, by talking about a Desktop PC you completely through me.

So you have installed latest May 2016 Raspbian Jessie and undertook:

Code: Select all

sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install ferm

http://ferm.foo-projects.org

[brutis]

Yes that's right and I have also tried without updating

[brutis]

After a lot of testing I eventually installed the latest version (ferm 2.3-2) from the debian testing repository and after a

Code: Select all

systemctl enable ferm

it is all working correctly.
Checking the ferm changelog there have been fixes for problems relating to systemd and ferm starting after other services.

[kevinwlu]

Please provide the commands for installing ferm 2.3-2 on Pi 3. Thank you.

[raspi-user.france]

I do have the same problem (I think). I have a standard installation and almost nothing is installed on top of the standard raspbian lite provided at www.raspberrypi.org/downloads/.
I installed ferm via "sudo apt install -y ferm" (after an update and upgrade). I see that ferm just doesn't start after a reboot. I did "sudo systemctl enable ferm".
Any ideas or suggestions for what I need to look for is highly appreciated (I'm also more than happy to provide additional information if requested)!