Radvd: Shared object "libdaemon.so.0" not found.

[Escorpiom]

Like other people I also had my share of upgrade issues. First SSH would not start, but gladly the solution was posted in another topic.
One issue remains, the "Router Advertisment Daemon" won't start.
On the status-services page it shows as stopped. It seems to be necessary for IPv6.

The log shows:

php: rc.bootup: The command '/usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog' returned exit code '1', the output was 'Shared object "libdaemon.so.0" not found, required by "radvd"'

As I couldn't find any related issues on the forum, has something gone south on my end? Any clues on how to resolve this are most welcome.

Cheers.

[Escorpiom]

Any ideas? Hard to imagine I'm the only one with radvd issues.

Cheers.

[doktornotor]

Works just fine pretty much for everyone. Considering your SSH issues, the permissions on your box are probably screwed… Do a fresh install and restore the config backup.

[Escorpiom]

It seems I was able to fix this, but perhaps the fix is a bit ugly.
Libdaemon.so.0 is located in /usr/local/lib and has the correct permissions.
I copied the file to /usr/lib and radvd started just fine.

So the questions is, what happened? Should the file be "symlinked" from /user/lib and the link wasn't created?
Or does it belong there?

Anyway it runs ok now, my only concern is that this hack may break something later on.

Cheers.

[Gertjan]

Well ….

[2.2-RELEASE][admin@pfsense.xxxxxxxxxxxxxxxx]/: find /usr -name libdaemon.so.0
/usr/local/lib/libdaemon.so.0

My 'radvd' is running fine:

[2.2-RELEASE][admin@pfsense.xxxxxxxxxxxxxxxx]/: ps ax | grep 'radvd'
98540  -  S        0:03.20 /usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog
95788  0  S+       0:00.00 grep radvd

You might be in for more non-explainable unique problems.
Better re-install.

[cmb]

That sounds a lot like what would happen on systems where you were messing with squid3 during a period of time on 2.2 snapshots, where the squid3 package would screw up the file permissions on libraries. Or potentially a consequence of some of the manual symlinking that was being recommended by some in some threads.

There's no telling what else might be messed up there. Backup your config, reinstall, and restore. Nothing bad will have ended up in the config from any of that.

[Escorpiom]

@cmb:

That sounds a lot like what would happen on systems where you were messing with squid3 during a period of time on 2.2 snapshots, where the squid3 package would screw up the file permissions on libraries. Or potentially a consequence of some of the manual symlinking that was being recommended by some in some threads.

Quilty.  :(

Well at least that's cleared up then, in any case I will be reinstalling pf.
Config backup and restore will be no problem I presume. 
Thank you all for the input.

Cheers.

[cmb]

@Escorpiom:

Config backup and restore will be no problem I presume.

Yeah your backup config will be fine, none of that hurt anything in the config itself.