Messages

1

23.7 Legacy Series / [Solved] 23.7.2 Update stuck at "Fetching base-23.7.2-amd64.txz: ......."

« on: August 28, 2023, 04:51:55 pm »

I'm trying to update from 23.7.1_3 to 23.7.2, via GUI, but was stuck at "Fetching base-23.7.2-amd64.txz: ............" on several tried.

From the logs below, the 1st run seems partially update successfully, except base and kernel.

Did a Audit-Health check but found nothing.

Update work fine after changed Mirror from Default to Cloudflare CDN.

2

23.1 Legacy Series / os-ddclient does not work with Dynu DDNS 23.1.10_1

« on: June 28, 2023, 04:34:28 am »

Hello, after upgrade from 23.1.9_x to 23.1.10_1, os-ddclient does not udpdate properly with dynu ddns anymore, no matter what I tried with different setting. It worked fine in previous version with "Backend=ddclient" and "check ip method=interface".

Could someone help with below logs:

1) When check ip method=interface:

Code: [Select]

2023-06-28T10:25:54 Notice ddclient[37187] 42012 - [meta sequenceId="4"] SUCCESS: abcd.efgh.org: skipped: IPv4 address was already set to x.x.x.x.
2023-06-28T10:25:54 Notice ddclient[37187] 38967 - [meta sequenceId="3"] WARNING: 'if-skip' is deprecated and does nothing for IPv4
2023-06-28T10:25:29 Notice ddclient[91303] 97895 - [meta sequenceId="2"] SUCCESS: abcd.efgh.org: skipped: IPv4 address was already set to x.x.x.x.
2023-06-28T10:25:29 Notice ddclient[91303] 94498 - [meta sequenceId="1"] WARNING: 'if-skip' is deprecated and does nothing for IPv4

2) When "check ip method=dyndns"

Code: [Select]

2023-06-28T10:28:32 Notice ddclient[1013] 48693 - [meta sequenceId="20"] WARNING: updating abcd.wfgh.org: nochg: No update required; unnecessary attempts to change to the current address are considered abusive
2023-06-28T10:28:32 Notice ddclient[1013] 47288 - [meta sequenceId="19"] RECEIVE: nochg
2023-06-28T10:28:32 Notice ddclient[1013] 45462 - [meta sequenceId="18"] RECEIVE:
2023-06-28T10:28:32 Notice ddclient[1013] 43487 - [meta sequenceId="17"] RECEIVE: Content-Type: text/html; charset=UTF-8
2023-06-28T10:28:32 Notice ddclient[1013] 41134 - [meta sequenceId="16"] RECEIVE: Content-Length: 5
2023-06-28T10:28:32 Notice ddclient[1013] 39381 - [meta sequenceId="15"] RECEIVE: X-Powered-By: Dynu Dynamic DNS Service
2023-06-28T10:28:32 Notice ddclient[1013] 38052 - [meta sequenceId="14"] RECEIVE: Server: Dynu Web Server
2023-06-28T10:28:32 Notice ddclient[1013] 34698 - [meta sequenceId="13"] RECEIVE: Date: Wed, 28 Jun 2023 2:28:32 GMT
2023-06-28T10:28:32 Notice ddclient[1013] 33003 - [meta sequenceId="12"] RECEIVE: HTTP/1.1 200 OK
2023-06-28T10:28:32 Notice ddclient[1013] 29347 - [meta sequenceId="11"] SENDING:
2023-06-28T10:28:32 Notice ddclient[1013] 29347 - [meta sequenceId="10"] SENDING: Connection: close
2023-06-28T10:28:32 Notice ddclient[1013] 29347 - [meta sequenceId="9"] SENDING: User-Agent: ddclient/3.10.0
2023-06-28T10:28:32 Notice ddclient[1013] 29347 - [meta sequenceId="8"] SENDING: Authorization: Basic amxzeWFuOlMwMGtjaGluZw==
2023-06-28T10:28:32 Notice ddclient[1013] 29347 - [meta sequenceId="7"] SENDING: Host: api.dynu.com
2023-06-28T10:28:32 Notice ddclient[1013] 29347 - [meta sequenceId="6"] SENDING: GET /nic/update?system=dyndns&hostname=abcd.efgh.org&myip= HTTP/1.1
2023-06-28T10:28:32 Notice ddclient[1013] 27998 - [meta sequenceId="5"] CONNECTED: using SSL
2023-06-28T10:28:31 Notice ddclient[1013] 23814 - [meta sequenceId="4"] CONNECT: api.dynu.com
2023-06-28T10:28:31 Notice ddclient[1013] 22702 - [meta sequenceId="3"] UPDATE: updating abcd.efgh.org
2023-06-28T10:28:31 Notice ddclient[1013] 21305 - [meta sequenceId="2"] WARNING: abcd.efgh.org: unable to determine IP address with strategy use=cmd
2023-06-28T10:28:31 Notice ddclient[1013] 18828 - [meta sequenceId="1"] WARNING: found neither IPv4 nor IPv6 address

3

23.1 Legacy Series / Re: 23.1.2 system log full of errors Netdata

« on: March 29, 2023, 03:55:38 am »

Hi, i am also getting the same error messages.
Further checking, I found there are 2 netdata instances running from "top"; one of it in "pause" state and another was running in "kqread".

Code: [Select]

root@jlofw:/usr/local/etc/netdata # service status netdata
status does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable

Code: [Select]

root@jlofw:/usr/local/etc/netdata # service netdata onestatus
netdata is running as pid 84739 85003.

Code: [Select]

top:
84739 netdata      42  52   19   243M   156M pause    0   0:14   1.41% /usr/local/sbin/netdata -u netdata -P /var/db/netdata/netdata.pid
85003 netdata       2  52   19    25M    11M kqread   0   0:00   0.00% /usr/local/sbin/netdata --special-spawn-server
Sorry for my limited linux experience. Could anyone help? Thanks.

4

Intrusion Detection and Prevention / Re: ET Telemetry data collected in every minutes

« on: September 12, 2022, 09:11:59 am »

Anyone can help? The message still flooding in the system logs every minutes. 

5

Intrusion Detection and Prevention / ET Telemetry data collected in every minutes

« on: September 11, 2022, 06:43:33 pm »

Hi, in system logs the message shows that the "ET telemetry data collected" in every minutes and still counting.

It start happened since upgraded to 22.7.x.
No alert in IPS and my opnsense at version 22.7.4.

Code: [Select]

2022-09-12T00:32:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:31:25.105493
2022-09-12T00:31:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:30:25.052477
2022-09-12T00:30:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:29:25.002711
2022-09-12T00:29:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:28:24.950363
2022-09-12T00:28:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:27:24.914220
2022-09-12T00:27:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:26:24.871320
2022-09-12T00:26:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:25:24.806481
2022-09-12T00:25:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:24:24.757845
2022-09-12T00:24:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:23:24.719155
2022-09-12T00:23:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:22:24.674378
2022-09-12T00:20:00 Notice send_telemetry.py telemetry data collected 2 records in 0.05 seconds @2022-09-11 16:19:34.750318
2022-09-12T00:19:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:18:34.697775
2022-09-12T00:18:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:17:34.642315
2022-09-12T00:17:00 Notice send_telemetry.py telemetry data collected 1 records in 0.05 seconds @2022-09-11 16:16:34.594241
Appreciate any help, thanks.

6

22.1 Legacy Series / Re: Google Backups failing

« on: May 30, 2022, 06:00:25 am »

I'm probably the only one that uses this, but backups to Google drive started failing for me recently.
Has been working for a long time, not sure if something changed on Google's end or what.

Error message:

[29-May-2022 01:00:01 America/New_York] PHP Fatal error:  Uncaught Google_Service_Exception: {
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "wrongUrlForUpload",
    "message": "Uploads must be sent to the upload URL. Re-send this request to https://www.googleapis.com/upload/drive/v3/files?uploadType=media"
   }
  ],
  "code": 400,
  "message": "Uploads must be sent to the upload URL. Re-send this request to https://www.googleapis.com/upload/drive/v3/files?uploadType=media"
 }
}
 in /usr/local/share/google-api-php-client/src/Google/Http/REST.php:118
Stack trace:
#0 /usr/local/share/google-api-php-client/src/Google/Http/REST.php(94): Google_Http_REST::decodeHttpResponse(Object(GuzzleHttp\Psr7\Response), Object(GuzzleHttp\Psr7\Request), 'Google_Service_...')
#1 /usr/local/share/google-api-php-client/src/Google/Task/Runner.php(176): Google_Http_REST::doExecute(Object(GuzzleHttp\Client), Object(GuzzleHttp\Psr7\Request), 'Google_Service_...')
#2 /usr/local/share/google-api-php-client/src/Google/Http/REST.php(58): Google_Task_Runner->run()
#3 /usr/l in /usr/local/share/google-api-php-client/src/Google/Http/REST.php on line 118

Hi, I had the same issue yesterday.
I managed to solve it by provide a "password" for encryption backup. I didn't provide a password previously and working fine all the while until it failed on yesterday.

Hope this help.

7

Intrusion Detection and Prevention / Re: Rejected ETPro Telemetry registration

« on: May 02, 2022, 06:32:20 am »

I'm getting the same rejected message too by using an gmail address.

I was wondering if the registration of ET Pro Telemetry is freeze?

8

21.7 Legacy Series / Fresh Installation Failed - segfaults

« on: September 02, 2021, 04:13:01 pm »

Hi,
I have been using opnsense for few months and happy with it. Unfortunately, I am having numerous instability issues since upgrade from 21.1.9 to 21.7.1 few weeks ago. Do let me provide as much info as possible for what I have did so far.

first of all, error messages such as "cannot define table bogons: Invalid argument", Reporting page was inconsistent and sometime having blank page & etc.
The last error was I can't login to webGui with Internal Server Error 500. After connect a display to it, continuous error with "Segmentation Fault". Reboot doesn't help.

So, I decide to have a fresh install and with numerous tried,  Even with USB installer from v20.1, 20.7, 21.1
The installer just stop in between (exit -11, core dumped, segfaults) and never properly boot up, with the last few messages shown:

Code: [Select]

CARP event system: pid 54060 (php), jid 0, uid 0: exited on signal 11 (core dumped)
Error (-11)
Launching the init system...done.
Initializing...pid 43093 (php), jid 0, uid 0: exited on signal 11
Segmentation fault.
Enter full pathname of shell or RETURN for /bin/sh:

In the past few weeks, I have tested this chinese made "minipc" with several other OS and appliances and most happily stay and run on it. (Such as IPFire, Ubuntu, Windows 10, OMV ... etc), the only exception is pfsense in which able to install and work just fine, however "cannot define table bogons: Invalid argument" still popping up whenever apply changes or a reboot.

It seems to me that the hardware shouldn't be the problem and try install opnsense again today. Unfortunately, same error happened, sounds like FreeBSD's firewall doesn't like me at all


Could anyone help me further? And sorry for my bad english.

9

21.7 Legacy Series / Re: Blank page on Unbound DNS Statistic

« on: August 07, 2021, 11:01:38 am »

@Fright, thanks for your help.

It seems the problem was due to time-sync issue, which happened in Virtualbox.
The page shown correctly now with a proper ntp sync, tested with several reboots.

Thanks again.

10

21.7 Legacy Series / Re: Blank page on Unbound DNS Statistic

« on: August 07, 2021, 09:21:51 am »

can you run

Code: [Select]

configctl unbound statsin shell and share results?

The result was "Execute Error".

11

21.7 Legacy Series / Re: Blank page on Unbound DNS Statistic

« on: August 07, 2021, 02:31:56 am »

@BlueHatDinuX
hi
any errors in browser dev console?

Yes, there were errors on Chrome and Firefox as well.

Code: [Select]

This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. stats
Uncaught TypeError: can't convert undefined to object
    updateStats https://10.0.0.1/ui/unbound/stats:1198
    complete https://10.0.0.1/ui/js/opnsense.js?v=3e683bdcd9ca1a86:242
    jQuery 6
    ajaxGet https://10.0.0.1/ui/js/opnsense.js?v=3e683bdcd9ca1a86:234
    updateStats https://10.0.0.1/ui/unbound/stats:1190
    <anonymous> https://10.0.0.1/ui/unbound/stats:1252
    jQuery 13
stats:1198:43
    updateStats https://10.0.0.1/ui/unbound/stats:1198
    complete https://10.0.0.1/ui/js/opnsense.js?v=3e683bdcd9ca1a86:242
    jQuery 6
    ajaxGet https://10.0.0.1/ui/js/opnsense.js?v=3e683bdcd9ca1a86:234
    updateStats https://10.0.0.1/ui/unbound/stats:1190
    <anonymous> https://10.0.0.1/ui/unbound/stats:1252
    jQuery 13

12

21.7 Legacy Series / Re: Blank page on Unbound DNS Statistic

« on: August 05, 2021, 01:14:20 pm »

That is correct, mine is not a VM.
And you are sure the VM is serving the DNS requests? Could it possibly be the clients are sending the traffic to another DNS resolver?

Yes, the VM is handling DNS DOT request which shown in unbound logs.

13

21.7 Legacy Series / Re: Blank page on Unbound DNS Statistic

« on: August 05, 2021, 12:54:24 pm »

Thanks for your replied.
Believe you are installed it in APU4D4.

Weird it happened on my VBox, restore config doesn't help either.

14

21.7 Legacy Series / Blank page on Unbound DNS Statistic

« on: August 05, 2021, 12:16:26 pm »

Hi, I was trying a fresh install of 21.7 on a Virtualbox, before proceed to live system.
Installation went smooth and everything seems working fine.

But there are nothing shown when browse into Unbound DNS statistic page, as attached.

Same issue with a number of tries of fresh installation, updated to 21.7.1 doesn't help either...


Is anyone having the same issue?


Edit: no problem on the statistic page when upgrading from 21.1.9 > 21.7 > 21.7.1.