Nethsecurity updates opkg_update_failed

NethServer Version: your_version
Module: your_module

Good morning everyone
when I go to update the system I get this error
Command ‘[’/bin/opkg’, ‘update’]’ returned non-zero exit status 6.
{“error”: “opkg_update_failed”}
from terminal
on the web page
AxiosError: Request failed with status code 500

Thanks if anyone can give me a tip

Well…

Try again later? Smells like a “normal” HTTP internal server error. Probably the mirror is taking a nap or is sweating a bit to much.

however the problem of updating nethsecurity persists
this is the error:
Ubus request failed

Request failed
ns.update check-package-updates
ideas

@giacomo might have some idea. But please be aware of possible delayed actions due to the holiday season.

I can’t help without relevant info.

Please follow the troubleshooting documentation and report here all details.

1 Like
### mpossibile recuperare gli aggiornamenti dei pacchetti

Errore del server

AxiosError: Request failed with status code 500
### Richiesta Ubus fallita

Richiesta fallita

ns.update check-package-updates
  _   _      _   _      _____                      _ _         
 | \ | |    | | | |    / ____|                    (_) |        
 |  \| | ___| |_| |__ | (___   ___  ___ _   _ _ __ _| |_ _   _ 
 | . ` |/ _ \ __| '_ \ \___ \ / _ \/ __| | | | '__| | __| | | |
 | |\  |  __/ |_| | | |____) |  __/ (__| |_| | |  | | |_| |_| |
 |_| \_|\___|\__|_| |_|_____/ \___|\___|\__,_|_|  |_|\__|\__, |
                                                          __/ |
                                                         |___/ index-1071f2a7.js:1578:34
[interceptor] 
Object { stack: "Ke@https://192.168.1.1:9090/assets/index-1071f2a7.js:46:70076\nzk@https://192.168.1.1:9090/assets/index-1071f2a7.js:48:1046\ng@https://192.168.1.1:9090/assets/index-1071f2a7.js:48:4240\n", message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…} }
index-1071f2a7.js:1577:183339
[interceptor] opkg_update_failed index-1071f2a7.js:1577:183429
XHRPOST
https://192.168.1.1:9090/api/ubus/call
[HTTP/1.1 500 Internal Server Error 2242ms]

[interceptor] 
Object { stack: "Ke@https://192.168.1.1:9090/assets/index-1071f2a7.js:46:70076\nzk@https://192.168.1.1:9090/assets/index-1071f2a7.js:48:1046\ng@https://192.168.1.1:9090/assets/index-1071f2a7.js:48:4240\nEventHandlerNonNull*qk</<@https://192.168.1.1:9090/assets/index-1071f2a7.js:48:4312\nqk<@https://192.168.1.1:9090/assets/index-1071f2a7.js:48:3217\nb2@https://192.168.1.1:9090/assets/index-1071f2a7.js:50:512\npromise callback*_request@https://192.168.1.1:9090/assets/index-1071f2a7.js:51:1071\nrequest@https://192.168.1.1:9090/assets/index-1071f2a7.js:50:3032\nn/<@https://192.168.1.1:9090/assets/index-1071f2a7.js:51:1664\n_4/<@https://192.168.1.1:9090/assets/index-1071f2a7.js:46:64802\nwo@https://192.168.1.1:9090/assets/index-1071f2a7.js:1577:118846\nle@https://192.168.1.1:9090/assets/UpdateView-2cf37496.js:1:145688\nKr@https://192.168.1.1:9090/assets/index-1071f2a7.js:13:38\nvn@https://192.168.1.1:9090/assets/index-1071f2a7.js:13:111\nn@https://192.168.1.1:9090/assets/index-1071f2a7.js:17:7330\n", message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…} }
index-1071f2a7.js:1577:183339
[interceptor] opkg_update_failed index-1071f2a7.js:1577:183429
Object { stack: "Ke@https://192.168.1.1:9090/assets/index-1071f2a7.js:46:70076\nzk@https://192.168.1.1:9090/assets/index-1071f2a7.js:48:1046\ng@https://192.168.1.1:9090/assets/index-1071f2a7.js:48:4240\nEventHandlerNonNull*qk</<@https://192.168.1.1:9090/assets/index-1071f2a7.js:48:4312\nqk<@https://192.168.1.1:9090/assets/index-1071f2a7.js:48:3217\nb2@https://192.168.1.1:9090/assets/index-1071f2a7.js:50:512\npromise callback*_request@https://192.168.1.1:9090/assets/index-1071f2a7.js:51:1071\nrequest@https://192.168.1.1:9090/assets/index-1071f2a7.js:50:3032\nn/<@https://192.168.1.1:9090/assets/index-1071f2a7.js:51:1664\n_4/<@https://192.168.1.1:9090/assets/index-1071f2a7.js:46:64802\nwo@https://192.168.1.1:9090/assets/index-1071f2a7.js:1577:118846\nle@https://192.168.1.1:9090/assets/UpdateView-2cf37496.js:1:145688\nKr@https://192.168.1.1:9090/assets/index-1071f2a7.js:13:38\nvn@https://192.168.1.1:9090/assets/index-1071f2a7.js:13:111\nn@https://192.168.1.1:9090/assets/index-1071f2a7.js:17:7330\n", message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…} }
index-1071f2a7.js:1577:147924

There is still not enough info, please read the doc carefully! :pray:

The only relevant thing is the launched command: ns.update check-package-updates

Please, provide:

  • Your system configuration: This includes the version of NethSecurity you’re using; you can find the information inside the Dashboard page. Please report the full version like 8 23.05.2-ns.0.0.1-beta1-96-ga759afb

And also:

When reporting an error to the support team, it’s crucial to provide the following essential information:

  1. Request and Response Contents: Include the content of the Request and Response sections found in the error message.
  2. Copied Command: Paste the command copied using the Copy command button.
  3. Execution Output: For further assistance, execute the copied command and report the output.

In your case, you should execute:

/usr/libexec/rpcd/ns.update call check-package-updates

Paste also the result of the following command (make sure to redact secrets, if present):

cat /etc/opkg/distfeeds.conf
cat /etc/opkg/customfeeds.conf
ping -c 1 updates.nethsecurity.nethserver.org
ping -c 1 distfeed.nethesis.it

Also:

  1. report always the error in English
  2. use the markdown syntax to correctly format the messages (I did it for you)
  3. Javascript output is not usually necessary

    If the provided information is insufficient, in extreme cases, it may be necessary to share the content of the JavaScript console if the error is present.

root@firewall:~# /usr/libexec/rpcd/ns.update call check-package-updates
Command '['/bin/opkg', 'update']' returned non-zero exit status 6.
{"error": "opkg_update_failed"}
root@firewall:~#
src/gz nethsecurity_core https://xxx@distfeed.nethesis.it/repo                                                                                                                                                                                                                                                                                                                                                           sitory/community/nethsecurity/23.05.3/targets/x86/64/packages
src/gz nethsecurity_base https://xxx@distfeed.nethesis.it/repo                                                                                                                                                                                                                                                                                                                                                           sitory/community/nethsecurity/23.05.3/packages/x86_64/base
src/gz nethsecurity_luci https://xxx@distfeed.nethesis.it/repo                                                                                                                                                                                                                                                                                                                                                           sitory/community/nethsecurity/23.05.3/packages/x86_64/luci
src/gz nethsecurity_nethsecurity https://xxx@distfeed.nethesis                                                                                                                                                                                                                                                                                                                                                           .it/repository/community/nethsecurity/23.05.3/packages/x86_64/nethsecurity
src/gz nethsecurity_packages https://xxx@distfeed.nethesis.it/                                                                                                                                                                                                                                                                                                                                                           repository/community/nethsecurity/23.05.3/packages/x86_64/packages
src/gz nethsecurity_routing https://xxx@distfeed.nethesis.it/r                                                                                                                                                                                                                                                                                                                                                           epository/community/nethsecurity/23.05.3/packages/x86_64/routing
root@firewall:~# ping -c 1 updates.nethsecurity.nethserver.org
PING nethsecurity.ams3.cdn.digitaloceanspaces.com (172.64.145.29) 56(84) bytes of data.
64 bytes from 172.64.145.29 (172.64.145.29): icmp_seq=1 ttl=55 time=9.06 ms

--- nethsecurity.ams3.cdn.digitaloceanspaces.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 9.056/9.056/9.056/0.000 ms
root@firewall:~# ping -c 1 distfeed.nethesis.it
PING distfeed.nethesis.it (164.92.187.18) 56(84) bytes of data.
64 bytes from disfeed.nethesis.it (164.92.187.18): icmp_seq=1 ttl=51 time=21.9 ms

--- distfeed.nethesis.it ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 21.919/21.919/21.919/0.000 ms

NethSecurity 8 23.05.3-ns.1.1.0-50-g27d6182

You do not have access to the repository because your trial subscription has expired on 20-6-2024, 09:27.

I also see you’re using a dev version, this is worth mentioning on the support request, don’t you think?

You also posted the output with incorrect format and also included secretes (that I have redacted): I strongly suggest you to delete that subscription because it has been compromised.

Please, follow the indications when asking for support: I’m not willing to help anymore on such requests without proper context.

2 Likes

thanks for solution
I’m thinking of proceeding with the annual subscription

1 Like