| View previous topic :: View next topic |
| Author |
Message |
davidphiliplee
Joined: 28 Aug 2012
Posts: 8
Location: Ireland
|
 Posted: Tue Sep 11, 2012 8:03 pm Post subject: Starting UPnP devices daemon: MiniUPnPdSegmentation fault |
 |
|
Installed miniupnpd on debian (already have minissdpd + libminiupnpc5 installed.
When attempting to start the daemon I get the following error:
| Code: | | Starting UPnP devices daemon: MiniUPnPdSegmentation fault |
Does anybody have any ideas as to what the issue may be?
I already verified the ip + subnet of allow parameter in /etc/miniupnpd/miniupnpd.conf
Much appreciated. |
|
| Back to top |
|
 |
miniupnp
Site Admin
Joined: 14 Apr 2007
Posts: 1593
|
| Posted: Wed Sep 12, 2012 8:33 am Post subject: |
|
|
Hu that's pretty bad 
have you tried to run with gdb to find out how it crashes ?
should be | Code: | | gdb --args /usr/sbin/miniupnpd -f /etc/miniupnpd/miniupnpd.conf |
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
| Back to top |
|
|
davidphiliplee
Joined: 28 Aug 2012
Posts: 8
Location: Ireland
|
| Posted: Wed Sep 12, 2012 9:58 am Post subject: |
|
|
Thank you so much for getting back so soon. A web link I found (http://thomas.goirand.fr/blog/?p=9) reports that MiniUPnP (1.7.3) is now fully in debian but it is not available from "deb http://ftp.debian.org/debian wheezy main contrib non-free"
all I could find was the experimental version from "deb http://ftp.debian.org/debian experimental main". I am installing armhf 1.7.4 version on a Raspberry Pi.
On install I get the following error:
| Code: | | [FAIL] MiniUPnPd: /etc/default/miniupnpd isn't set to START_DAEMON=1: exiting: failed! |
as part of the install I made no changes to:
| Code: | | /etc/miniupnpd/miniupnpd.conf |
I changed the following in /etc/default/miniupnpd
| Code: | MiniUPnPd_LISTENING_IP=0.0.0.0
START_DAEMON=1 |
When I run the gbd command it reports "no debugging symbols found".
If you have any suggestions that would be great. |
|
| Back to top |
|
|
miniupnp
Site Admin
Joined: 14 Apr 2007
Posts: 1593
|
| Posted: Wed Sep 12, 2012 12:08 pm Post subject: |
|
|
| davidphiliplee wrote: | Thank you so much for getting back so soon. A web link I found (http://thomas.goirand.fr/blog/?p=9) reports that MiniUPnP (1.7.3) is now fully in debian but it is not available from "deb http://ftp.debian.org/debian wheezy main contrib non-free"
all I could find was the experimental version from "deb http://ftp.debian.org/debian experimental main". I am installing armhf 1.7.4 version on a Raspberry Pi.
On install I get the following error:
| Code: | | [FAIL] MiniUPnPd: /etc/default/miniupnpd isn't set to START_DAEMON=1: exiting: failed! |
as part of the install I made no changes to:
| Code: | | /etc/miniupnpd/miniupnpd.conf |
I changed the following in /etc/default/miniupnpd
| Code: | MiniUPnPd_LISTENING_IP=0.0.0.0
START_DAEMON=1 |
When I run the gbd command it reports "no debugging symbols found".
If you have any suggestions that would be great. |
What is the point of setting MiniUPnPd_LISTENING_IP=0.0.0.0 ?
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
| Back to top |
|
|
davidphiliplee
Joined: 28 Aug 2012
Posts: 8
Location: Ireland
|
| Posted: Wed Sep 12, 2012 12:29 pm Post subject: |
|
|
| I tried the IP address of my device first, but then changed it to 0.0.0.0 in case that was an open wildcard (guessing from comment in config) |
|
| Back to top |
|
|
miniupnp
Site Admin
Joined: 14 Apr 2007
Posts: 1593
|
| Posted: Wed Sep 12, 2012 12:46 pm Post subject: |
|
|
you should supply the network address of your "internal" (LAN) network inteface.
such as 192.168.1.254
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
| Back to top |
|
|
davidphiliplee
Joined: 28 Aug 2012
Posts: 8
Location: Ireland
|
| Posted: Wed Sep 12, 2012 3:02 pm Post subject: |
|
|
Yes I tried that first, only afterwards did I try 0.0.0.0
Is there a way to get additional debug information out?
Thanks. |
|
| Back to top |
|
|
miniupnp
Site Admin
Joined: 14 Apr 2007
Posts: 1593
|
| Posted: Wed Sep 12, 2012 3:04 pm Post subject: |
|
|
| davidphiliplee wrote: | Yes I tried that first, only afterwards did I try 0.0.0.0
Is there a way to get additional debug information out?
|
launch miniupnpd with -d option.
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
| Back to top |
|
|
davidphiliplee
Joined: 28 Aug 2012
Posts: 8
Location: Ireland
|
| Posted: Wed Sep 12, 2012 3:13 pm Post subject: |
|
|
Unfortunately "segment fault" is the only response still. I can pass any command in but it doesn't matter, looks like its not even reading command arguments.
If it is a "porting to armhf issue", I might have to wait for it to get our of experimental for 1.7.4 wheezy?
Thanks. |
|
| Back to top |
|
|
miniupnp
Site Admin
Joined: 14 Apr 2007
Posts: 1593
|
| Posted: Fri Sep 14, 2012 11:19 am Post subject: |
|
|
To understand where the segfault comes from,
you should :
- compile from sources with -g option
- launch in gdb
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
| Back to top |
|
|
davidphiliplee
Joined: 28 Aug 2012
Posts: 8
Location: Ireland
|
| Posted: Sat Sep 15, 2012 12:26 pm Post subject: |
|
|
Hi,
I have created a workaround by coding directly what I was doing (SSDP m-search response and notify). Would you like the results of gdb anyhow? |
|
| Back to top |
|
|
miniupnp
Site Admin
Joined: 14 Apr 2007
Posts: 1593
|
| Posted: Sat Sep 15, 2012 3:05 pm Post subject: |
|
|
| davidphiliplee wrote: | Hi,
I have created a workaround by coding directly what I was doing (SSDP m-search response and notify). Would you like the results of gdb anyhow? |
Yes, I would like to understand how the segfault happen !
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
| Back to top |
|
|
Abraham12li
Joined: 25 Feb 2015
Posts: 1
Location: Afghanistan
|
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
