Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Lightsquid service not starting at boot time

    Scheduled Pinned Locked Moved 2.3-RC Snapshot Feedback and Issues - ARCHIVED
    38 Posts 4 Posters 13.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • cwagzC
      cwagz
      last edited by

      I am not using a ramdisk or nano system.

      I am running on a Supermicro C2558 board with 8GB ram and a 120GB Intel SSD

      Here is what happens when I hit save in both Avahi and then Lightsquid:

      Mar 12 20:19:47  check_reload_status   Syncing firewall  
Mar 12 20:19:46  php-fpm  80705  /pkg_edit.php: [lightsquid] Updating cronjobs...  
Mar 12 20:19:46  check_reload_status   Syncing firewall  
Mar 12 20:19:45  php-fpm  80705  /pkg_edit.php: [lightsquid] Removing old cronjobs...  
Mar 12 20:19:45  php-fpm  80705  /pkg_edit.php: [lightsquid] Successfully created '/usr/local/etc/lightsquid/lightsquid.cfg' configuration file.  
Mar 12 20:19:45  php-fpm  80705  /pkg_edit.php: [lightsquid] Loaded default '/usr/local/etc/lightsquid/lightsquid.cfg.sample' configuration file.  
Mar 12 20:19:45  check_reload_status   Syncing firewall  
Mar 12 20:19:15  avahi-daemon  34886  Service "pfsense" (/usr/local/etc/avahi/services/sftp-ssh.service) successfully established.  
Mar 12 20:19:15  avahi-daemon  34886  Service "pfsense" (/usr/local/etc/avahi/services/ssh.service) successfully established.  
Mar 12 20:19:15  avahi-daemon  34886  Server startup complete. Host name is pfsense.local. Local service cookie is 3393655586.  
Mar 12 20:19:14  avahi-daemon  34886  Registering HINFO record with values 'AMD64'/'FREEBSD'.  
Mar 12 20:19:14  avahi-daemon  34886  Registering new address record for 192.168.1.1 on igb1.IPv4.  
Mar 12 20:19:14  avahi-daemon  34886  Registering new address record for fe80::225:90ff:fef2:d557 on igb1.*.  
Mar 12 20:19:14  avahi-daemon  34886  Registering new address record for 192.168.3.1 on igb3.IPv4.  
Mar 12 20:19:14  avahi-daemon  34886  Registering new address record for fe80::225:90ff:fef2:d559 on igb3.*.  
Mar 12 20:19:14  avahi-daemon  34886  Registering new address record for 192.168.10.1 on ovpns1.IPv4.  
Mar 12 20:19:14  avahi-daemon  34886  Registering new address record for fe80::225:90ff:fef2:d556 on ovpns1.*.  
Mar 12 20:19:14  avahi-daemon  34886  Network interface enumeration completed.  
Mar 12 20:19:14  avahi-daemon  34886  New relevant interface igb1.IPv4 for mDNS.  
Mar 12 20:19:14  avahi-daemon  34886  Joining mDNS multicast group on interface igb1.IPv4 with address 192.168.1.1.  
Mar 12 20:19:14  avahi-daemon  34886  New relevant interface igb1.IPv6 for mDNS.  
Mar 12 20:19:14  avahi-daemon  34886  Joining mDNS multicast group on interface igb1.IPv6 with address fe80::225:90ff:fef2:d557.  
Mar 12 20:19:14  avahi-daemon  34886  New relevant interface igb3.IPv4 for mDNS.  
Mar 12 20:19:14  avahi-daemon  34886  Joining mDNS multicast group on interface igb3.IPv4 with address 192.168.3.1.  
Mar 12 20:19:14  avahi-daemon  34886  New relevant interface igb3.IPv6 for mDNS.  
Mar 12 20:19:14  avahi-daemon  34886  Joining mDNS multicast group on interface igb3.IPv6 with address fe80::225:90ff:fef2:d559.  
Mar 12 20:19:14  avahi-daemon  34886  New relevant interface ovpns1.IPv4 for mDNS.  
Mar 12 20:19:14  avahi-daemon  34886  Joining mDNS multicast group on interface ovpns1.IPv4 with address 192.168.10.1.  
Mar 12 20:19:14  avahi-daemon  34886  New relevant interface ovpns1.IPv6 for mDNS.  
Mar 12 20:19:14  avahi-daemon  34886  Joining mDNS multicast group on interface ovpns1.IPv6 with address fe80::225:90ff:fef2:d556.  
Mar 12 20:19:14  avahi-daemon  34886  Loading service file /usr/local/etc/avahi/services/ssh.service.  
Mar 12 20:19:14  avahi-daemon  34886  Loading service file /usr/local/etc/avahi/services/sftp-ssh.service.  
Mar 12 20:19:14  avahi-daemon  34886  WARNING: No NSS support for mDNS detected, consider installing nss-mdns!  
Mar 12 20:19:14  avahi-daemon  34886  avahi-daemon 0.6.31 starting up.  
Mar 12 20:19:14  avahi-daemon  34886  Successfully dropped root privileges.  
Mar 12 20:19:14  avahi-daemon  34886  Found user 'avahi' (UID 558) and group 'avahi' (GID 558). 

      Netgate 6100 MAX

      1 Reply Last reply Reply Quote 0
      • M
        maverick_slo
        last edited by

        I use pppoe with ipv6.
        Guys with problems, do you also use pppoe?

        1 Reply Last reply Reply Quote 0
        • cwagzC
          cwagz
          last edited by

          @maverick_slo:

          I use pppoe with ipv6.
          Guys with problems, do you also use pppoe?

          I am on DHCP.

          Netgate 6100 MAX

          1 Reply Last reply Reply Quote 0
          • M
            maverick_slo
            last edited by

            I think it`s related to this:
            https://github.com/pfsense/pfsense/commit/80d3cf1cdd79517cad7676813641d2e0fe73b445
            https://redmine.pfsense.org/issues/5952

            This is definitly a bug in my opinion.

            1 Reply Last reply Reply Quote 0
            • M
              maverick_slo
              last edited by

              Hi!

              I also have:

              /rc.start_packages: Skipping STARTing packages process because previous/another instance is already running

              And a lot of those (I don`t know if it is connected):

              Mar 14 21:07:45 	php-cgi 		rc.bootup: The command '/sbin/route change -inet6 default fe80::2c1:64ff:fed8:3f00' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable change net default: gateway fe80::2c1:64ff:fed8:3f00 fib 0: Network is unreachable' 

              /rc.filter_configure_sync: The command '/sbin/route change -inet6 default fe80::2c1:64ff:fed8:3f00' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable change net default: gateway fe80::2c1:64ff:fed8:3f00 fib 0: Network is unreachable' 

              /rc.start_packages: The command '/sbin/route change -inet6 default fe80::2c1:64ff:fed8:3f00' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable change net default: gateway fe80::2c1:64ff:fed8:3f00 fib 0: Network is unreachable'

              /rc.dyndns.update: The command '/sbin/route change -inet6 default fe80::2c1:64ff:fed8:3f00' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable change net default: gateway fe80::2c1:64ff:fed8:3f00 fib 0: Network is unreachable'
              1 Reply Last reply Reply Quote 0
              • M
                maverick_slo
                last edited by

                What fixed it was editing /etc/rc.start_packages and changing:

                
FROM:
if (time() - $stat['mtime'] >= 90) {

TO:
if (time() - $stat['mtime'] >= 5) {

                So it does only wait 5 seconds and then starts packages.
                It`s a dirty hack and will work only until next update or gitsync.

                I`m still very much interested in resolving this without hacks like this.

                1 Reply Last reply Reply Quote 0
                • jimpJ
                  jimp Rebel Alliance Developer Netgate
                  last edited by

                  Sounds like this actually has nothing to do with lightsquid but is instead a general package startup problem. Feel free to open a bug entry on redmine.pfsense.org with what you've found so far. I would not emphasize lightsquid on the redmine report since it happens to other packages as well for some people (e.g. Avahi)

                  Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                  Need help fast? Netgate Global Support!

                  Do not Chat/PM for help!

                  1 Reply Last reply Reply Quote 0
                  • M
                    maverick_slo
                    last edited by

                    Here we go: https://redmine.pfsense.org/issues/6001

                    1 Reply Last reply Reply Quote 0
                    • M
                      maverick_slo
                      last edited by

                      I`ve updated https://redmine.pfsense.org/issues/6001#change-25756 with new findings.

                      Snort takes really long time to start and this interrupts other packages.

                      Is there a way to alter the package startup order?

                      1 Reply Last reply Reply Quote 0
                      • M
                        maverick_slo
                        last edited by

                        OK final post here as this won`t change in near future :)

                        I found a workaround.

                        Edit config.xml and move lightsquid to top of packages.
                        The XML tag is: <package>So lightsquid will start first and snort last in my case.</package>

                        1 Reply Last reply Reply Quote 0
                        • cwagzC
                          cwagz
                          last edited by

                          This mostly worked for me as well. I moved light squid first and Avahi second. Light squid is starting now at reboot but Avahi still requires a manual restart.

                          Netgate 6100 MAX

                          1 Reply Last reply Reply Quote 0
                          • cwagzC
                            cwagz
                            last edited by

                            Seems like a similar error I was seeing in previous versions while running in hyper-v. Some type of timing issue.  Should this be a new topic? I was thinking it is all related.

                            Mar 19 21:58:46 avahi-daemon 54193 dbus_bus_get_private(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
                            Mar 19 21:58:46

                            Netgate 6100 MAX

                            1 Reply Last reply Reply Quote 0
                            • jimpJ
                              jimp Rebel Alliance Developer Netgate
                              last edited by

                              Anyone that was hitting this problem, update to the latest snapshot and see if the problem persists. A fix was put in yesterday that should address the problem.

                              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                              Need help fast? Netgate Global Support!

                              Do not Chat/PM for help!

                              1 Reply Last reply Reply Quote 0
                              • M
                                maverick_slo
                                last edited by

                                I just updated my ticket.
                                It`s OK and others report that Avahi is starting too.

                                Thanks!

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post
                                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.