Hates_ Posted June 30, 2016 #1 Posted June 30, 2016 I have DSM 5.2 running on a HP Microserver Gen8 but I can't get any community sources to work in the package center. I've tried adding a couple but hitting refresh gives me the following error in the /var/log/messages file: Nov 2 01:04:32 synology PkgSynoMan.cgi: pkgcurltool.cpp:261 Failed to curl perform, code=60, err=Error Nov 2 01:04:32 synology PkgSynoMan.cgi: pkgcurltool.cpp:423 Failed to download https://payment.synology.com/api/getPackageList.php, code=60, err=Error I've tried a few things like adding payment.synology.com to my /etc/hosts and sending it to 127.0.0.1 but then I just get a different code for the error. Any ideas? Wouldn't be so bad if I could figure out how to download spk files manually from community sources but there doesn't seem to a be a way? Quote
brantje Posted July 1, 2016 #2 Posted July 1, 2016 Try setting the DNS to 8.8.8.8 Posted via Xpenology.us Quote
Hates_ Posted July 5, 2016 Author #3 Posted July 5, 2016 A load of fiddling with settings seemed to get it working but nothing I could initially pinpoint. It happened a second time and after looking around the settings again it looked like the time was completely out of whack. So I set it to sync properly and the package centre began working again. Quote
lordakuma Posted August 18, 2016 #4 Posted August 18, 2016 Try setting the DNS to 8.8.8.8 Posted via Xpenology.us I tried this and it worked. I then removed the manually added DNS and i got the same error in the /var/log/messages. Why does this happen? Also a thanks. A load of fiddling with settings seemed to get it working but nothing I could initially pinpoint. It happened a second time and after looking around the settings again it looked like the time was completely out of whack. So I set it to sync properly and the package centre began working again. I checked and my time is correct in the /var/log/messages Maybe it just comes down to the DNS and the ISP provider that we have doesnt like it? EDIT: I have 2 internet connections, I will test this further when I get home today. EDIT 2: I got home and removed the DNS settings, and I got that same error "payment.synology.com". So I switched it to my other internet connection, worked without me having to change it to the 8.8.8.8. Switched it to the 8.8.8.8 just to see, worked without and issue. Removed DNS again and switched back to the 1st internet connection. Same issue. Added DNS back in with 8.8.8.8, worked again. Wonder if its because my ISP that I have the issue with is a small local ISP and the 2nd is a larger national ISP? Aug 18 17:59:59 alpha [212901.090808] init: smbd main process (24785) killed by TERM signal Aug 18 17:59:59 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 17:59:59 alpha ddnsd: ddnsd.c:2852 DDNS get Ext-IP failed. Aug 18 18:00:12 alpha synonetd: net_route_table_edit.c:58 eth0 ip route del failed, instead of route Aug 18 18:00:13 alpha [212915.029610] init: nmbd main process (4400) killed by TERM signal Aug 18 18:00:13 alpha [212915.043134] init: smbd main process (4440) killed by TERM signal Aug 18 18:00:13 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 18:00:19 alpha ddnsd: ddnsd.c:1968 Success to update [*******.noip.me] with IP [**********] at [NoIP.com] Aug 18 18:00:57 alpha upnpd: src/libsynoportmap.cpp:3428 Fail to get external IP. Aug 18 18:04:57 alpha upnpd: src/RandomPortGenerator.cpp:39 pSynoUpnp has not initialized Aug 18 18:04:57 alpha upnpd: src/RouterPortMapProtocol.cpp:272 delete port (80, 80, tcp) failed: -1, UPnPErr: 0 Aug 18 18:04:57 alpha upnpd: src/RouterPortMapProtocol.cpp:272 delete port (5000, 5000, tcp) failed: -1, UPnPErr: 0 Aug 18 18:04:57 alpha upnpd: src/RouterPortMapProtocol.cpp:255 add fix port (80, 80, tcp) failed: -1, UPnPErr: 0 Aug 18 18:04:57 alpha upnpd: src/RouterPortMapProtocol.cpp:255 add fix port (5000, 5000, tcp) failed: -1, UPnPErr: 0 Aug 18 18:06:59 alpha [213320.876373] init: smbd main process (5049) killed by TERM signal Aug 18 18:06:59 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 18:06:59 alpha ddnsd: ddnsd.c:2852 DDNS get Ext-IP failed. Aug 18 18:07:06 alpha synonetd: net_route_table_edit.c:58 eth0 ip route del failed, instead of route Aug 18 18:07:07 alpha [213329.051431] init: nmbd main process (9438) killed by TERM signal Aug 18 18:07:07 alpha [213329.057956] init: smbd main process (9467) killed by TERM signal Aug 18 18:07:07 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 18:07:27 alpha ddnsd: ddnsd.c:2852 DDNS get Ext-IP failed. Aug 18 18:07:56 alpha ddnsd: ddnsd.c:2891 DDNS get Ext-IP failed. Count[1] Aug 18 18:08:06 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11033]: rssfile.cpp:90 failed to exec cmd=[wget --user-agent=synology_bromolow_3615xs DSM5.2-5644 (dsmupdate) -O /var/run/autoupdate_tmp_file_RSS https://update.synology.com/autoupdate/genRSS.php?tz=Pacific&unique=synology_bromolow_3615xs&major=5&minor=2&build_num=5644], ret=4, No such file or directory Aug 18 18:08:06 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11033]: dsmupdate.cpp:231 Fail to get RSS file Aug 18 18:08:06 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11033]: dsmupdate.cpp:392 Fail to get latest DSM info Aug 18 18:08:13 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11307]: rssfile.cpp:90 failed to exec cmd=[wget --user-agent=synology_bromolow_3615xs DSM5.2-5644 (dsmupdate) -O /var/run/autoupdate_tmp_file_RSS https://update.synology.com/autoupdate/genRSS.php?tz=Pacific&unique=synology_bromolow_3615xs&major=5&minor=2&build_num=5644], ret=4, No such file or directory Aug 18 18:08:13 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11307]: dsmupdate.cpp:231 Fail to get RSS file Aug 18 18:08:13 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11307]: dsmupdate.cpp:392 Fail to get latest DSM info Aug 18 18:08:27 alpha entry.cgi_SYNO.Core.Network[1].set[11495]: common_setting.cpp:276 check server_name: alpha -> alpha Aug 18 18:08:27 alpha entry.cgi_SYNO.Core.Network[1].set[11495]: common_setting.cpp:292 check dns_primary: 192.168.0.1 -> 8.8.8.8 Aug 18 18:08:27 alpha entry.cgi_SYNO.Core.Network[1].set[11495]: common_setting.cpp:300 dns_secondary [8.8.4.4] Aug 18 18:08:27 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 18:09:28 alpha ddnsd: ddnsd.c:1968 Success to update [*******.noip.me] with IP [*******] at [NoIP.com] Aug 18 18:09:28 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 18:10:29 alpha ddnsd: ddnsd.c:1968 Success to update [*******.noip.me] with IP [*******] at [NoIP.com] Quote
fexter_ Posted March 5 #5 Posted March 5 В 18.08.2016 в 21:55, lordakuma сказал: I tried this and it worked. I then removed the manually added DNS and i got the same error in the /var/log/messages. Why does this happen? Also a thanks. I checked and my time is correct in the /var/log/messages Maybe it just comes down to the DNS and the ISP provider that we have doesnt like it? EDIT: I have 2 internet connections, I will test this further when I get home today. EDIT 2: I got home and removed the DNS settings, and I got that same error "payment.synology.com". So I switched it to my other internet connection, worked without me having to change it to the 8.8.8.8. Switched it to the 8.8.8.8 just to see, worked without and issue. Removed DNS again and switched back to the 1st internet connection. Same issue. Added DNS back in with 8.8.8.8, worked again. Wonder if its because my ISP that I have the issue with is a small local ISP and the 2nd is a larger national ISP? Aug 18 17:59:59 alpha [212901.090808] init: smbd main process (24785) killed by TERM signal Aug 18 17:59:59 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 17:59:59 alpha ddnsd: ddnsd.c:2852 DDNS get Ext-IP failed. Aug 18 18:00:12 alpha synonetd: net_route_table_edit.c:58 eth0 ip route del failed, instead of route Aug 18 18:00:13 alpha [212915.029610] init: nmbd main process (4400) killed by TERM signal Aug 18 18:00:13 alpha [212915.043134] init: smbd main process (4440) killed by TERM signal Aug 18 18:00:13 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 18:00:19 alpha ddnsd: ddnsd.c:1968 Success to update [*******.noip.me] with IP [**********] at [NoIP.com] Aug 18 18:00:57 alpha upnpd: src/libsynoportmap.cpp:3428 Fail to get external IP. Aug 18 18:04:57 alpha upnpd: src/RandomPortGenerator.cpp:39 pSynoUpnp has not initialized Aug 18 18:04:57 alpha upnpd: src/RouterPortMapProtocol.cpp:272 delete port (80, 80, tcp) failed: -1, UPnPErr: 0 Aug 18 18:04:57 alpha upnpd: src/RouterPortMapProtocol.cpp:272 delete port (5000, 5000, tcp) failed: -1, UPnPErr: 0 Aug 18 18:04:57 alpha upnpd: src/RouterPortMapProtocol.cpp:255 add fix port (80, 80, tcp) failed: -1, UPnPErr: 0 Aug 18 18:04:57 alpha upnpd: src/RouterPortMapProtocol.cpp:255 add fix port (5000, 5000, tcp) failed: -1, UPnPErr: 0 Aug 18 18:06:59 alpha [213320.876373] init: smbd main process (5049) killed by TERM signal Aug 18 18:06:59 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 18:06:59 alpha ddnsd: ddnsd.c:2852 DDNS get Ext-IP failed. Aug 18 18:07:06 alpha synonetd: net_route_table_edit.c:58 eth0 ip route del failed, instead of route Aug 18 18:07:07 alpha [213329.051431] init: nmbd main process (9438) killed by TERM signal Aug 18 18:07:07 alpha [213329.057956] init: smbd main process (9467) killed by TERM signal Aug 18 18:07:07 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 18:07:27 alpha ddnsd: ddnsd.c:2852 DDNS get Ext-IP failed. Aug 18 18:07:56 alpha ddnsd: ddnsd.c:2891 DDNS get Ext-IP failed. Count[1] Aug 18 18:08:06 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11033]: rssfile.cpp:90 failed to exec cmd=[wget --user-agent=synology_bromolow_3615xs DSM5.2-5644 (dsmupdate) -O /var/run/autoupdate_tmp_file_RSS https://update.synology.com/autoupdate/genRSS.php?tz=Pacific&unique=synology_bromolow_3615xs&major=5&minor=2&build_num=5644], ret=4, No such file or directory Aug 18 18:08:06 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11033]: dsmupdate.cpp:231 Fail to get RSS file Aug 18 18:08:06 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11033]: dsmupdate.cpp:392 Fail to get latest DSM info Aug 18 18:08:13 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11307]: rssfile.cpp:90 failed to exec cmd=[wget --user-agent=synology_bromolow_3615xs DSM5.2-5644 (dsmupdate) -O /var/run/autoupdate_tmp_file_RSS https://update.synology.com/autoupdate/genRSS.php?tz=Pacific&unique=synology_bromolow_3615xs&major=5&minor=2&build_num=5644], ret=4, No such file or directory Aug 18 18:08:13 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11307]: dsmupdate.cpp:231 Fail to get RSS file Aug 18 18:08:13 alpha entry.cgi_SYNO.Core.Upgrade.Server[1].check[11307]: dsmupdate.cpp:392 Fail to get latest DSM info Aug 18 18:08:27 alpha entry.cgi_SYNO.Core.Network[1].set[11495]: common_setting.cpp:276 check server_name: alpha -> alpha Aug 18 18:08:27 alpha entry.cgi_SYNO.Core.Network[1].set[11495]: common_setting.cpp:292 check dns_primary: 192.168.0.1 -> 8.8.8.8 Aug 18 18:08:27 alpha entry.cgi_SYNO.Core.Network[1].set[11495]: common_setting.cpp:300 dns_secondary [8.8.4.4] Aug 18 18:08:27 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 18:09:28 alpha ddnsd: ddnsd.c:1968 Success to update [*******.noip.me] with IP [*******] at [NoIP.com] Aug 18 18:09:28 alpha ddnsd: ddnsd.c:2844 DDNS got SIGHUP. UpdateAll. Aug 18 18:10:29 alpha ddnsd: ddnsd.c:1968 Success to update [*******.noip.me] with IP [*******] at [NoIP.com] For a smoother experience with online transactions or accessing services, consider using https://a-pay.one/ for your payments. It’s a global payment service that handles transactions in local currencies, ensuring fast and secure processing. Whether you're managing DNS-related configurations or paying for online services, A-Pay makes it easy and seamless, with transactions credited to your account in just one day. To fix the issue, I recommend: It sounds like the issue is likely related to DNS resolution or a routing issue with your ISP. Here's what might be happening: DNS Resolution Problem: When you remove the manually added DNS settings, your device is likely defaulting to your ISP's DNS, which may not be able to resolve the domain (like "payment.synology.com") properly. This could be due to either a temporary DNS issue on their end or some restrictions. Multiple Internet Connections: Since you're using two internet connections, the problem may lie in how your network is routing traffic. The DNS settings might behave differently depending on which connection you're using. It seems like when you switch to the second connection (where DNS works fine), the issue is resolved. This indicates that the first connection's DNS servers might not be handling requests for the Synology domains properly. ISP DNS Restrictions: Some ISPs use DNS caching or DNS filtering that can interfere with resolving certain external domains, which might explain why switching to public DNS like 8.8.8.8 resolves the issue. To troubleshoot further, I'd suggest: Check ISP DNS Servers: If possible, reach out to your ISP to see if they have any known issues with DNS resolution for certain domains or if they can suggest alternative DNS servers. Consistent DNS Settings: Since using 8.8.8.8 resolves the issue, try to keep it as your default DNS to avoid the issue from recurring. Network Routing/Configuration: If possible, try to isolate the traffic through one of your connections and ensure that both connections are not conflicting in their routing. Ultimately, it looks like DNS is the main culprit here, and the ISP’s DNS settings might not be ideal for all use cases. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.