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

    SG-1100 22.01-RC built on Thu Jan 13 20:10:51 UTC 2022

    Scheduled Pinned Locked Moved
    Plus 22.01 Development Snapshots (Retired)
    2
    9
    426
    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.
    • N
      NOCling
      last edited by

      I got a PHP Warning after install and if i reboot.

      [14-Jan-2022 23:24:01 Europe/Berlin] PHP Warning:  file_put_contents(/var/db/notifyqueue.messages): failed to open stream: Permission denied in /etc/inc/notices.inc on line 307
[14-Jan-2022 23:24:06 Europe/Berlin] PHP Warning:  file_put_contents(/var/db/notifyqueue.messages): failed to open stream: Permission denied in /etc/inc/notices.inc on line 307

      Does this have any negative effects?

      Netgate 6100 & Netgate 2100

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

        Is there anything else in the system logs around those times?

        I haven't seen that here, but depending on what triggered the problem it might be specific to your setup.

        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
        • N
          NOCling
          last edited by

          Hey jimp, yes there is a log entry at the same Time:

          [17-Jan-2022 19:28:42 Europe/Berlin] PHP Warning:  file_put_contents(/var/db/notifyqueue.messages): failed to open stream: Permission denied in /etc/inc/notices.inc on line 307
[17-Jan-2022 19:28:47 Europe/Berlin] PHP Warning:  file_put_contents(/var/db/notifyqueue.messages): failed to open stream: Permission denied in /etc/inc/notices.inc on line 307
[17-Jan-2022 19:28:52 Europe/Berlin] PHP Warning:  file_put_contents(/var/db/notifyqueue.messages): failed to open stream: Permission denied in /etc/inc/notices.inc on line 307

          System Log:

          Jan 17 19:31:30	php-fpm	372	/rc.dyndns.update: phpDynDNS (): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Jan 17 19:31:27	php-fpm	372	/rc.dyndns.update: phpDynDNS (): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Jan 17 19:31:23	check_reload_status	386	Reloading filter
Jan 17 19:31:23	check_reload_status	386	Restarting OpenVPN tunnels/interfaces
Jan 17 19:31:23	check_reload_status	386	Restarting IPsec tunnels
Jan 17 19:31:23	check_reload_status	386	updating dyndns WAN_DHCP
Jan 17 19:31:23	rc.gateway_alarm	48885	>>> Gateway alarm: WAN_DHCP (Addr:1.1.1.1 Alarm:1 RTT:23.953ms RTTsd:4.735ms Loss:21%)
Jan 17 19:29:57	sshguard	63506	Now monitoring attacks.
Jan 17 19:29:57	php-fpm	576	/index.php: Successful login for user 'admin' from: 192.168.10.77 (Local Database)
Jan 17 19:29:01	php	24147	[pfBlockerNG] filterlog daemon started
Jan 17 19:29:00	tail_pfb	23983	[pfBlockerNG] Firewall Filter Service started
Jan 17 19:28:59	lighttpd_pfb	21941	[pfBlockerNG] DNSBL Webserver started
Jan 17 19:28:59	vnstatd	15654	Monitoring (8): pfsync0 (1000 Mbit) pflog0 (1000 Mbit) mvneta0.4092 (1000 Mbit) mvneta0.4091 (1000 Mbit) mvneta0.4090 (1000 Mbit) mvneta0.167 (1000 Mbit) mvneta0 (1000 Mbit) enc0 (1000 Mbit)
Jan 17 19:28:59	vnstatd	15654	vnStat daemon 2.8 started. (pid:15654 uid:0 gid:0)
Jan 17 19:28:59	vnstatd	18590	Error: pidfile "/var/run/vnstat/vnstat.pid" lock failed (Resource temporarily unavailable), exiting.
Jan 17 19:28:59	php_pfb	18388	[pfBlockerNG] filterlog daemon stopped
Jan 17 19:28:59	tail_pfb	16990	[pfBlockerNG] Firewall Filter Service stopped
Jan 17 19:28:59	root	17262	Bootup complete
Jan 17 19:28:59	lighttpd_pfb	15143	[pfBlockerNG] DNSBL Webserver stopped
Jan 17 19:28:59	vnstatd	7750	SIGTERM received, exiting.
Jan 17 19:28:52	php	8219	nut_email.php: Message sent to a@b.com OK
Jan 17 19:28:50	upsmon	1673	Communications with UPS qnapups established
Jan 17 19:28:50	php	7508	[pfBlockerNG] filterlog daemon started
Jan 17 19:28:49	vnstatd	7750	Monitoring (8): pfsync0 (1000 Mbit) pflog0 (1000 Mbit) mvneta0.4092 (1000 Mbit) mvneta0.4091 (1000 Mbit) mvneta0.4090 (1000 Mbit) mvneta0.167 (1000 Mbit) mvneta0 (1000 Mbit) enc0 (1000 Mbit)
Jan 17 19:28:49	vnstatd	7750	vnStat daemon 2.8 started. (pid:7750 uid:0 gid:0)
Jan 17 19:28:49	tail_pfb	7362	[pfBlockerNG] Firewall Filter Service started
Jan 17 19:28:49	php_pfb	5340	[pfBlockerNG] filterlog daemon stopped
Jan 17 19:28:49	tail_pfb	5322	[pfBlockerNG] Firewall Filter Service stopped
Jan 17 19:28:49	php-fpm	372	[pfBlockerNG] Starting firewall filter daemon
Jan 17 19:28:47	php	10822	nut_email.php: Message sent to a@b.com OK
Jan 17 19:28:45	upsmon	1673	UPS qnapups is unavailable
Jan 17 19:28:45	upsmon	1673	Poll UPS [qnapups] failed - Driver not connected
Jan 17 19:28:45	upsd	9693	Connected to UPS [qnapups]: usbhid-ups-qnapups
Jan 17 19:28:44	usbhid-ups	78985	Startup successful
Jan 17 19:28:42	php	9917	nut_email.php: Message sent to a@b.com OK
Jan 17 19:28:40	upsmon	1673	Communications with UPS qnapups lost
Jan 17 19:28:40	upsmon	1673	Poll UPS [qnapups] failed - Driver not connected
Jan 17 19:28:40	upsd	9693	User local-monitor@::1 logged into UPS [qnapups]
Jan 17 19:28:40	upsd	9693	Startup successful
Jan 17 19:28:40	upsd	9412	Can't connect to UPS [qnapups] (usbhid-ups-qnapups): Connection refused
Jan 17 19:28:40	upsd	9412	listening on 127.0.0.1 port 3493
Jan 17 19:28:40	upsd	9412	listening on ::1 port 3493
Jan 17 19:28:40	upsd	9412	listening on 192.168.166.1 port 3493
Jan 17 19:28:40	lighttpd_pfb	6314	[pfBlockerNG] DNSBL Webserver started
Jan 17 19:28:40	lighttpd_pfb	5291	[pfBlockerNG] DNSBL Webserver stopped
Jan 17 19:28:39	upsmon	1159	Startup successful
Jan 17 19:28:36	upsd	49562	Startup successful
Jan 17 19:28:36	upsd	48799	Connected to UPS [qnapups]: usbhid-ups-qnapups
Jan 17 19:28:36	upsd	48799	listening on 127.0.0.1 port 3493
Jan 17 19:28:36	upsd	48799	listening on ::1 port 3493
Jan 17 19:28:36	upsd	48799	listening on 192.168.166.1 port 3493
Jan 17 19:28:35	usbhid-ups	23269	Startup successful
Jan 17 19:28:35	upsmon	13357	Startup successful

          Looks like NUTs mail notification is the trigger.
          I try to apply the NUT setting gain, but 2 Reboot later the Crash report is back.

          Netgate 6100 & Netgate 2100

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

            Could be some kind of timing issue with the way it's being setup at boot time.

            Do you have /var/ in a RAM disk?

            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
            • N
              NOCling
              last edited by

              Yes, it look like.
              No Ramdisk is in use.

              My sg-3100 got the Crash report to, but only after a System Update 1 times, but it is faster and use a M.2 SSD.

              Netgate 6100 & Netgate 2100

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

                Do both of those have the NUT package?

                I don't have that package on any of mine, but I have an 1100, a couple 3100s, and other various hardware around and I'm not seeing that on any Plus install I have.

                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
                • N
                  NOCling
                  last edited by

                  Yes, both use BUT. I had no problems until the last releases. The first time I got the crash report was 12/24/21, but I haven't followed it up sorry.

                  Netgate 6100 & Netgate 2100

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

                    OK, I found the cause and we'll have a workaround in place soon.

                    https://redmine.pfsense.org/issues/12281#note-4

                    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
                    • N
                      NOCling
                      last edited by

                      This is a good news.
                      Thanks

                      Netgate 6100 & Netgate 2100

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