Lightsquid service not starting at boot time

[maverick_slo]

After todays snap, Lightsquid is not starting at boot time anymore.
Also in services status if I press start it does something but it does not start it.

If I go to Status -> Squid proxy reports and save settings, then it gets started.

[cwagz]

@maverick_slo:

After todays snap, Lightsquid is not starting at boot time anymore.
Also in services status if I press start it does something but it does not start it.

If I go to Status -> Squid proxy reports and save settings, then it gets started.

Same issue for me.

[jimp]

Any errors in the system log or anywhere else? I still can't reproduce this. I update, reboot, etc and it always starts up for me.

[maverick_slo]

I checked lighttpd_lightsquid.log there is nothing there…

[jimp]

Are the ones seeing failures perhaps using NanoBSD or /var in a RAM disk?

[maverick_slo]

No full install.
If I save settings it starts and then it works as it should…

[jimp]

@maverick_slo:

No full install.
If I save settings it starts and then it works as it should…

Yeah I get that part, a few people have said it, but since I can't replicate the problem I need more detail about why it's failing. There should be something logged somewhere, on the system log, console, etc. Maybe try, without saving the settings, to run the rc.d script by hand to start it up and see if it produces an error.

[maverick_slo]

Can you please point me to rc script?
I'm just getting my baby to sleep and Im in bed on my phone :)

[jimp]

/usr/local/etc/rc.d/lighttpd_ls.sh

[maverick_slo]

A ha!

2016-03-11 20:15:31: (configfile.c.1016) opening configfile  /var/etc/lightsquid/lighttpd_ls.conf failed: No such file or directory

After each reboot conf file dissapears ??

[jimp]

Does /var/etc/lightsquid/ exist?

If not, add "mkdir -p /var/etc/lightsquid/" to the rc script in the start section, reboot, and see if it comes up

I don't recall it being cleared out each time, which is why I asked about /var in RAM, since that would be wiped on each boot.

[maverick_slo]

No there is no folder.
But it`s weird, this is happening on latest snapshots so something changed?

[jimp]

Nothing changed at all in any area close to that which I'm aware of.

Maybe you added or removed some other package which is causing the boot process to change somehow?

I may split this issue off into its own thread since it seems to be taking over and the cause isn't clear.

[maverick_slo]

No, I changed nothing just pushed a snapshot or 2.

Now my /usr/local/etc/rc.d/lighttpd_ls.sh looks like:

#!/bin/sh
# This file was automatically generated
# by the pfSense service handler.

rc_start() {
	# Start Lightsquid lighttpd webserver
    mkdir -p /var/etc/lightsquid/
	if [ -f /var/etc/lightsquid/lighttpd_ls.conf ]; then
		/usr/local/sbin/lighttpd_ls -f /var/etc/lightsquid/lighttpd_ls.conf
	fi
}

rc_stop() {
	# Terminate lightsquid Lighttpd webserver, if found.
	pidnum="$(/bin/pgrep lighttpd_ls)"
	if [ ! -z "${pidnum}" ]; then
		/usr/bin/killall lighttpd_ls
	fi
}

case $1 in
	start)
		rc_start
		;;
	stop)
		rc_stop
		;;
	restart)
		rc_stop
		rc_start
		;;
esac

It is still not started after reboot.

[maverick_slo]

Possible that something is preventing pkg_edit.php?xml=lightsquid.xml when you click on Save to apply correct permissions or something?

Forgot to mention… This happens on both of my pfsenses...

[jimp]

If the pkg_edit page was failing to apply then it would work at bootup but not the other way around.

It's acting as though it's not performing the boot-time sync for you that it's doing for me. When it boots up I have /var/etc/lightsquid with the config inside and it's running.

[maverick_slo]

So the cfg should be removed on every reboot?

[jimp]

It should be irrelevant - the boot-time sync of packages should trigger a rewrite of the config and restart of the daemon. Which appears to be happening OK on my test VMs.

[xbipin]

well same here on a full install after installing the 11th march snap

[maverick_slo]

I noticed that on reboot there is no more starting packages as it used to be. There is definitly something borked as others report it too.