UPnP IGD & PCP Service crashes and fails to start
-
@marcosm
24.11 long term -
Any core dumps? IIRC they get saved to
/root/. -
@marcosm Yes, there is a 13Mbyte miniupnp.core file which compresses to 150 k
-
@netblues Can you try this build: https://www.codepro.be/files/miniupnpd-2.3.7_2,1.pkg ?
It contains debug symbols and will hopefully let us figure out where miniupnpd crashes. -
@kprovost Installed, restarted and waiting.
I see two active port maps in status.
-
@netblues anything more on this? I'm having the same issue.
-
@townsenk64
I have the debug build running.
It didn't occur so far., but it does take a couple of days. -
For me the service fails within two minutes after reboot generating the previously mentioned core file. Let me know if help is needed troubleshooting.
-
@townsenk64 Do you run the debug version?
-
@netblues Not yet, I'm not exactly sure the proper way to upgrade a single package locally. I assume the pkg add command?
-
@townsenk64 said in UPnP IGD & PCP Service crashes and fails to start:
@netblues Not yet, I'm not exactly sure the proper way to upgrade a single package locally. I assume the pkg add command?
pkg add -f <path to .pkg> -
@kprovost said in UPnP IGD & PCP Service crashes and fails to start:
https://www.codepro.be/files/miniupnpd-2.3.7_2,1.pkg
I am now running the debug build. Does it contain changes other than having the debugging enabled? The reason I ask is that the service hasn't crashed almost immediately after rebooting like it did before. I will leave it running and see if it behaves.
-
@townsenk64 Well actually it just has debug symbols, which means its more meaningful when looking at the dump.
Most probably network conditions have changed, something has timed out and is not triggering the issue anymore.
Do keep in mind that in upnp we make ports available to the wider Internet, and usually there is little control on what happens next.
From a security point of view its a nightmare, but in a home scenario its too practical to ignore ;-) -
I rolled the system back to a previous state using the package without the debugging symbols and the service crash immediately happened again upon reboot. I then went with the shotgun approach and ran from command line.
pkg clean -y
pkg upgrade -fThis apparently replaced/upgraded the package and the service is again running without issue.
-
@townsenk64 Same here, no issues since I put the debug version.
Maybe a leftover glitch from the upgrades?
